GRUB doesn't detect NTFS partition

I recently installed windows to my second hard disk (/dev/sdb2 or (hd1,msdos2)), but GRUB fails to recognize the NTFS file system on it.
GRUB> ls
(hd0,msdos1) (hd0,msdos2) (hd0,msdos3) (hd0,msdos4) (hd1,msdos1) (hd1,msdos2)
GRUB> ls (hd1,msdos1)
Partition (hd1,msdos1): File system type ext* # etc
GRUB> ls (hd1,msdos2)
Partition (hd1,msdos2): No known file system detected
And yet there is a fully-functioning NTFS file system on this partition. Why do I know this? Because when I boot the entire hard disk from within QEMU, suddenly...
GRUB from within QEMU> ls (hd1,msdos2)
Partition (hd1,msdos2): File system type ntfs # etc
... and windows successfully boots from the disk.
I realise QEMU is not really comparable to BIOS, but I wonder why GRUB fails to recognize this single one NTFS partition, while it does recognize the other ext4 partition... Now, this isn't currently a severe issue, since I'm simply booting the windows partition with QEMU. The main reason I need to boot windows is to run some graphics-heavy programs, and as far as I know, QEMU can't do Direct3D emulation (or hardware acceleration?).
Last edited by DeatzoSeol (2015-05-21 00:20:14)

Hmm, I don't think that could be the cause, I've tried insmod'ing all the necessary deps but to no avail... grub simply doesn't see the ntfs partition...
Relevant menuentry:
menuentry 'Windows 7 (loader) (on /dev/sdb2)' --class windows --class os $menuentry_id_option 'osprober-chain-0530C8122E9BEF62' {
insmod part_msdos
insmod ntfs
insmod chain
insmod ntldr
set root='hd1,msdos2'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd1,msdos3 --hint-efi=hd1,msdos3 --hint-baremetal=ahci1,msdos3 0530C8122E9BEF62
else
search --no-floppy --fs-uuid --set=root 0530C8122E9BEF62
fi
chainloader +1
This was generated with os-prober, so I'm assuming it should work out of the box?

Similar Messages

Grub doesn't detect Windows partition (UEFI)/ xorg won't start either

Hey guys,
1) Looking for some help here. I've installed Arch on to my desktop and I'm running into some issues with my dual boot (UEFI).
When I went to create my Arch partitions I was running into some issues with cgdisk, but I was able to fix it and able to create a successful partition table. However, I don't think for some reason my windows installation had an EFI partiton. Which is odd, because I'm pretty sure it was setup with GPT & UEFI, which if I understand it correctly needs an EFI partition. Anyways I created my own efi partition and made a directory in /boot/efi for grub. I installed grub and it worked fine, detected Arch and everything. I followed the step to install os-prober first too. I think the error lies in the fact that I didn't mount the windows EFI, I created my own. Which again brings me back to: should I have had an EFI partition created by windows? I'd like to be able to get back to my windows system if possible, if I messed something up with the windows bootloader and it's not salvageable, it's not a huge deal.
The table is the following
sda1 ntfs system reserved (windows)
sda2 ntfs (windows partition)
sda3 ext4 (root partition)
sda4 fat32 (efi boot partiton-not windows)
sda5 ext5 (home partition)
2) I'm also having issues get X started. I think it is a driver issue but I can't be sure. I have 2 nvidia GTX 660s in SLI. I installed xorg-server and then installed both nvidia and nvidia-304xx. But whenever I try to run startx I get the following error
(EE) no screens found(EE)
xinit: giving up
this is with gnome installed and my .xinitrc file in my user directory.
I check out the log file of /var/log/Xorg.0.log and get the following errors
(EE) Failed to load module "nouveau" (module does not exist, 0)
(EE) Failed to load module "nv" (module does not exist, 0)
(EE) Failed to load module "modesetting" (module does not exist 0)
(EE) Failed to load module "fbdev" (module does not exist 0)
(EE) Failed to load module "vesa" (module does not exist, 0)
(EE) no drivers available
(EE) so screens found
Not sure what I am missing here. I've tried reinstalling xorg and gnome and all the drivers I could think of that the error above listed. However it always throws the same error.
Thanks for you time, if you need anything else I would be happy to provide it!

FWIW: reFind doesn;t mind multiple GPTs. I can't speak for GRUB. But shouldn't you be able to boot into the setup (what used to be "BIOS") and see if there is a boot order there or something? If your firmware is similar to mine, you can set "boot options" and allow the machine to let you pick a boot device. Windows should show there if it's available.

Trying to run from logical partition - GRUB doesn't detect it

Hi all, I only have a single SSD in my laptop with the following setup (in order on disk):
sda1 - System Reserved
sda2 - Windows 8
sda4 - Extended Partition
sda5 - Arch 2 (this is where I'm trying to move my Arch install to)
sda3 - Arch (this is the one I can actually boot into
(unallocated space)
This is what I want things to look like eventually:
sda1 - System Reserved
sda2 - Windows 8
sda3 - Extended Partition
sda4 - Arch
sda5 - some other distro
sda6 - storage (I want this accessible by all OSes)
Here's how I think I'm going to do this:
- move Arch installation from after the extended partition to before it (since the extended partition is a big chunk of mostly free space, and I would like it to go last.
- after verifying that I can boot the Arch installation from the logical partition, delete the Arch installation on the primary partition and absorb the free space into the extended partition
Here's what I've done:
- used 'dd if=/dev/sda3 of=/dev/sda5 bs=4096 conv=notrunc,noerror' to clone my working Arch installation to the logical partition (sda5).
- ran 'grub-mkconfig -o /boot/grub/grub.cfg' to update GRUB and add the logical partition to the list of things to choose from in the Grub menu.
After running 'grub-mkconfig' nothing new was added to the menu.
Questions:
- Is what I want to do even possible?
- can I have the logical partition marked for storage be accessible to Windows 8?
- Is there an easier way to do what I want to do?
- How do I get GRUB to detect the logical partition?
- Is it possible to boot into a logical partition?

grub doesn't always automatically pick up arch installations. Is os-prober installed? You can always add the entry manually e.g. in 40_custom or whatever. Don't forget to adjust fstab.
Just to be clear: you have an MBR formatted disk and are talking about traditional logical partitions, right? Not lvm?
Last edited by cfr (2013-02-02 01:31:48)

Arch and Win7 cannot open an NTFS partition created by the other

This is almost certainly related to another post where I was struggling to create logical partitions from Windows. Basically, Linux and Minitool Partition Wizard agreed that there were no logical partitions, but the built-in Windows disk utility said there was. I ended up using fdisk from Arch install media, and Minitool and Arch now both saw the logical partitions (Windows shows a big extended partition of free space). I installed Arch just fine, can boot to it and win7... life is good.
Not so much. A key to my setup is having an encrypted partition to share data between OS's. I used TrueCrypt with great success on my former laptop and am now having great difficulty!
Some preliminary information:
# fdisk -l /dev/sda
Disk /dev/sda: 238.5 GiB, 256060514304 bytes, 500118192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x1e6513b3
Device Boot Start End Sectors Size Id Type
/dev/sda1 * 2048 2101247 2099200 1G 7 HPFS/NTFS/exFAT
/dev/sda2 2101248 172433407 170332160 81.2G 7 HPFS/NTFS/exFAT
/dev/sda3 172433408 390537215 218103808 104G 7 HPFS/NTFS/exFAT
/dev/sda4 390537216 500118191 109580976 52.3G 5 Extended
/dev/sda5 390539264 391587839 1048576 512M 83 Linux
/dev/sda6 391589888 500118191 108528304 51.8G 83 Linux
I also went partition by partition to check Minitool's agreement on sectors (they match perfectly with the exception that it doesn't show the extended /dev/sda4 container). I triple checked the Minitool partition info properties as you can't copy and paste from it's window, and pasted the fdisk output to minimize errors. I'm showing a column for mini/Arch for both start/stop sectors, and just subtracted them to make sure I got 0. Appears to be perfect alignment:
| part | start (mini) | start (arch) | diff | | end (mini) | end (arch) | diff |
|------+--------------+--------------+------+---+------------+------------+------|
| sda1 | 2048 | 2048 | 0 | | 2101247 | 2101247 | 0 |
| sda2 | 2101248 | 2101248 | 0 | | 172433407 | 172433407 | 0 |
| sda3 | 172433408 | 172433408 | 0 | | 390537215 | 390537215 | 0 |
| sda4 | 390539264 | 390539264 | 0 | | 391587839 | 391587839 | 0 |
| sda5 | 391589888 | 391589888 | 0 | | 500118191 | 500118191 | 0 |
- Screenshot of how Minitool sees my disk
- Screenshot of how Windows disk utility sees my disk
I used TrueCrypt 7.1a on both OS's. I created a non-system encrypted partition using the GUI on Arch with the AES cipher/sha-512 hash, with filesystem as "none." Once created I did:
$ sudo cryptesetup --type tcrypt open /dev/sda3 vault
That worked fine, which I followed with:
$ sudo mkfs.ntfs /dev/mapper/vault
It initialized the device with zero's and then gave me the success/have a nice day message. Closed the volume and rebooted. When I tried to open the device from win7, I got "Incorrect password or not a TrueCrypt volume." Hmmm. I guess I'll try in reverse. I duplicated the procedure exactly as above from win7, this time having TrueCrypt automatically format with NTFS. All succeeds and I can open the device. Reboot into Arch and I get the same message from TrueCrypt! If I try with cryptsetup, it's "No device header detected with this passphrase."
Next, I tried just doing NTFS with no encryption. From Arch:
$ sudo mkfs.ntfs /dev/sda3
All goes well and I can mount it. I boot into Windows and it's not even listed! I used Minitool to issue it a drive letter, at which point clicking that pops up a windows dialog box asking me if I want to format the disk. Format the partition with NTFS in Windows, reboot into Arch and I get:
[jwhendy@arch_zbook ~]$ sudo mount /dev/sda3 /mnt/scratch/
NTFS signature is missing.
Failed to mount '/dev/sda3': Invalid argument
The device '/dev/sda3' doesn't seem to have a valid NTFS.
Maybe the wrong device is used? Or the whole disk instead of a
partition (e.g. /dev/sda, not /dev/sda1)? Or the other way around?
Doesn't matter if I add "-t ntfs" or "-t ntfs-3g." I get the same result.
Just to add a couple more oddities... when I created the NTFS partition in Arch, I also created a file called vault.tc as a TrueCrypt file-based encrypted container. My thinking was that the issue was with TrueCrypt full-partitions and that I could get around it with a plain partition containing an encrypted file. Reboot into windows and the partition isn't shown (as stated above). From Minitool, if I right click the partition and choose "Explore," it lists the partition contents and there is my vault.tc file. Windows thinks it's unformatted!
I noticed the option to backup/restore a TrueCrypt header, and gave a shot at backing up the working TrueCrypt setup on windows to a flash drive, booting to Arch, and then restoring the /dev/sda3 header from the flash drive file. Arch still couldn't open it.
Lastly, I noticed when I go to select a device to encrypt in TrueCrypt, my logical partitions aren't showing up (just like Windows only sees the end of the disk as free space). I just can't help but think something is tweaked in the partition table... basically:
- TrueCrypt sees what Windows sees
- Arch sees what Minitool sees
How could I go about diagnosing further or fixing the issue. This is driving me crazy!
I'd hate to do this given that I already setup my wm, configs, packages, etc... but my last resort attempt would be to wipe my logical partitions and see if I can at least get the win7 disk utility, minitool, arch, and truecrypt to like each other with respect to /dev/sda1-3... and then try to re-add the logicals afterward and re-install arch? I honestly don't know why this would be any different, but was just a thought. The issues from the other post seem to arise with logical partitions not being recognized the same between win/linux.
Or figure out how to just use primaries (like dedicated boot on a USB drive or something). Or fiddle with growing/shrinking windows to see if I can undo whatever is telling windows where/what things are? Really grasping at straws here.
Last edited by jwhendy (2015-06-10 23:32:22)

Hi Ramesh,
Please install the hotfix package and test the issue again:
http://support.microsoft.com/kb/2817576/en-us
In addition, try uncheck the option “confirm open after download” per:
http://jritmeijer.wordpress.com/2006/08/20/some-files-can-harm-your-computer-if-the-file-information-looks-suspicious-or-you-do-not-fully-trust-the-source-do-not-open-the-file/
Regards,
Rebecca Tu
TechNet Community Support

Solved. Installer doesn't detect harddrives

Hello, so this is my first time trying to install arch linux outside of virtualbox and the installer doesn't seem to detect my hard drives.
I get to the point in installation where I'm supposed to partition my harddrives and nothing is there, so I selected other and by using "dmesg | grep sd" I managed to find out that the drive i wanted to contain my arch install was called sdb. I wrote /dev/sdb in the "other"-box and was able to partition my hard dive the way I want. However, when I get to the step where I'm supposed to set my filesystems mountpoints there is no detected hard drives and no "other" option, so I'm pretty much stuck there.
I have tried searching but I didn't find anything on this particular problem, only GRUB related issues. Is there anyone here that know how to solve this?
Sorry for my English, it's not my first language but hopefully i made some sense at least.
edit, I forgot to add that I have tried the legacy IDE booting method too, but it did not help.
Last edited by göteborg-johan (2009-02-28 19:07:29)

nowahn wrote:
I have no idea why the installer doesn't detect your hardrive, but you should be able to workaround by mounting the partitions manually.
- mount the root partition to /mnt
- create a directory in /mnt for each separate partition
- mount all the partitions
then go to the step after setting hard drives in the installer.
I'm not sure this will work, just try. the installer should complains that you did not set any mountpoints, maybe entering the Set Filesystem Mountpoints step, and exiting with DONE can fix this.
Thanks for your reply, will try that.
One question tho, how would I set the swap partition using that method?

Renaming files with invalid characters in their names on NTFS partitions, introduced by operating systems other than Windows

Essentially, Linux created some files with colons (:) in the name on a NTFS partition where I have Windows installed. I have since uninstalled Linux, but now I can only view these files in Windows Explorer. I can't open them, I can't even rename them to
correct the problem. It's as if they don't exist, because of the invalid search paths.
If I try to rename them in Windows Explorer I get following message.
The file name you specified is no valid or too long.
Specify a different file name.
Well isnt' that something?... isn't that nice? Windows is able to display these files, but it doesn't allow me to open them and it certainly doesn't like me to rename them. So why is it whining about it then, when I'm trying to help? It says "try a different
file name". Yeah, right! Like I haven't tried that one already! It doesn't matter what file name I input it will never accept it.
So what am I supposed to do now? Ditch Windows and go back to Linux? Surely, Microsoft doesn't like the sound of that. Sure, I could reinstall Linux or run a Linux live system to correct the problem. But what good is Windows then? I might as well switch to
Linux altogether.
After doing some research I now know by fact that it's (kind of) possible to rename files from UNIX and UNIX-like operating systems to those compliant with Windows by using something called file name character translation. To some level this is essential and
necessary for Windows interoperability with other operating systems (Windows is not the only operating system in the world). But this seems to be very complicated and I can't get my head around it. My brain is in overload. I don't know where to start.
Once there was a...
There's the Windows Services for UNIX (SFU) 1.0, 2.0, 3.0, 3.5. The first two versions were based on MKS Toolkit, a package licensed by Microsoft from MKS Inc. The later versions were based on the similar Interix product, after Microsoft purchased the company
that made it.
Then there's the new Subsystem for UNIX-based Applications (SUA). These are services for UNIX components. They are supposed to have Client for NFS v3 included as well. But the server components from the SFU line is missing (e.g. Server for NFS). These are included
in Server editions of Windows.
Then there's the Microsoft Knowledge Base article
289627: "How to Enable File Name Character Translation". This article seems to describe exactly my situation.
Windows and UNIX operating systems have restrictions on valid characters that can be used in a file name. The list of illegal characters for each operating system, however, is different. For example, a UNIX file name can use a colon (:), but a Windows
file name cannot use a colon (:). If a UNIX user attempts to create a file with a Windows illegal character on a Windows Services for UNIX network file system (NFS) share, the attempt is unsuccessful and the UNIX client computer receives an input or output
error.
It goes further than that. At first glance, this KB article also seems to offer a solution to this exact problem, with examples as shown below.
For example, the following maps the UNIX colon (:) to a Windows dash (-):
0x3a : 0x2d ; replace client : with - on server
I checked these values in charmap.exe and they are correct. Except for 2D not being a "dash", it's rather a hyphen ("hyphen minus" to be exact), but these two have pretty much the same appearance and they get interchanged a lot, I'm sure
they are used to it by now. (Yes, the characters! They don't mind.)
Then there's this registry key.
HKEY_LOCAL_MACHINE\Software\Microsoft\Server For NFS\CurrentVersion\Mapping
Well, of course, I don't have Server for NFS. So this is a dead end. Well, actually, it was a dead end from the beginning...
1. First of all, I'm not working with a network share on a NAS or SAN storage. The files are on the local disk drive where Windows is installed, so that's a DAS for you.
2. I don't have SFU! Well obviously, I'm on Windows Vista! So that means SUA!
3. SUA are service components only. No server components. Can you guess what that means? Yeah... no "Server for NFS" since it's a server component.
4. Windows Vista is a client side operating system! Server for NFS is only offered for use with Windows Server systems.
5. Back to square one!
So there you have it. They all lived happy for the rest of their lives...
I'm stuck here. Can someone tell me what to do? I mean beyond the obvious option to use Linux to fixa a Windows problem? The NTFS file system itself supports colons in file names. It's Windows that doesn't, and so by default it proclaims it invalid character.
Surely, even a Windows client operating system like Windows Vista should be able to allow the user to at least rename files with invalid characters to something more sensible (from the system point of view) and valid, if not being able to open them as they
are. Just add some crazy voodoo code to it and it will work. If you can make it possible on Windows Server with UNIX user-mode subsystem on NT kernel, then what's stopping you from giving the Windows client system the same benefit?
So what now? Purchase a Windows Server 2012 R2 license, copy my invalid files to a NAS share with NFS on a UNIX or Linux system, and have a go at the Windows registry and Server for NFS? Yeah... you're right, it's probably a bit over the top...
On a second thought... I might as well install Linux again. There are countless situations where Linux has helped me solve problems related to, and more often than not caused by Windows.

Essentially, Linux created some files with colons (:) in the name on a NTFS partition where I have Windows installed. I have since uninstalled Linux, but now I can only view these files in Windows Explorer. I can't open them, I can't even rename them to
correct the problem. It's as if they don't exist, because of the invalid search paths.
If I try to rename them in Windows Explorer I get following message.
The file name you specified is no valid or too long.
Specify a different file name.
Well isnt' that something?... isn't that nice? Windows is able to display these files, but it doesn't allow me to open them and it certainly doesn't like me to rename them. So why is it whining about it then, when I'm trying to help? It says "try a different
file name". Yeah, right! Like I haven't tried that one already! It doesn't matter what file name I input it will never accept it.
So what am I supposed to do now? Ditch Windows and go back to Linux? Surely, Microsoft doesn't like the sound of that. Sure, I could reinstall Linux or run a Linux live system to correct the problem. But what good is Windows then? I might as well switch to
Linux altogether.
After doing some research I now know by fact that it's (kind of) possible to rename files from UNIX and UNIX-like operating systems to those compliant with Windows by using something called file name character translation. To some level this is essential and
necessary for Windows interoperability with other operating systems (Windows is not the only operating system in the world). But this seems to be very complicated and I can't get my head around it. My brain is in overload. I don't know where to start.
Once there was a...
There's the Windows Services for UNIX (SFU) 1.0, 2.0, 3.0, 3.5. The first two versions were based on MKS Toolkit, a package licensed by Microsoft from MKS Inc. The later versions were based on the similar Interix product, after Microsoft purchased the company
that made it.
Then there's the new Subsystem for UNIX-based Applications (SUA). These are services for UNIX components. They are supposed to have Client for NFS v3 included as well. But the server components from the SFU line is missing (e.g. Server for NFS). These are included
in Server editions of Windows.
Then there's the Microsoft Knowledge Base article
289627: "How to Enable File Name Character Translation". This article seems to describe exactly my situation.
Windows and UNIX operating systems have restrictions on valid characters that can be used in a file name. The list of illegal characters for each operating system, however, is different. For example, a UNIX file name can use a colon (:), but a Windows
file name cannot use a colon (:). If a UNIX user attempts to create a file with a Windows illegal character on a Windows Services for UNIX network file system (NFS) share, the attempt is unsuccessful and the UNIX client computer receives an input or output
error.
It goes further than that. At first glance, this KB article also seems to offer a solution to this exact problem, with examples as shown below.
For example, the following maps the UNIX colon (:) to a Windows dash (-):
0x3a : 0x2d ; replace client : with - on server
I checked these values in charmap.exe and they are correct. Except for 2D not being a "dash", it's rather a hyphen ("hyphen minus" to be exact), but these two have pretty much the same appearance and they get interchanged a lot, I'm sure
they are used to it by now. (Yes, the characters! They don't mind.)
Then there's this registry key.
HKEY_LOCAL_MACHINE\Software\Microsoft\Server For NFS\CurrentVersion\Mapping
Well, of course, I don't have Server for NFS. So this is a dead end. Well, actually, it was a dead end from the beginning...
1. First of all, I'm not working with a network share on a NAS or SAN storage. The files are on the local disk drive where Windows is installed, so that's a DAS for you.
2. I don't have SFU! Well obviously, I'm on Windows Vista! So that means SUA!
3. SUA are service components only. No server components. Can you guess what that means? Yeah... no "Server for NFS" since it's a server component.
4. Windows Vista is a client side operating system! Server for NFS is only offered for use with Windows Server systems.
5. Back to square one!
So there you have it. They all lived happy for the rest of their lives...
I'm stuck here. Can someone tell me what to do? I mean beyond the obvious option to use Linux to fixa a Windows problem? The NTFS file system itself supports colons in file names. It's Windows that doesn't, and so by default it proclaims it invalid character.
Surely, even a Windows client operating system like Windows Vista should be able to allow the user to at least rename files with invalid characters to something more sensible (from the system point of view) and valid, if not being able to open them as they
are. Just add some crazy voodoo code to it and it will work. If you can make it possible on Windows Server with UNIX user-mode subsystem on NT kernel, then what's stopping you from giving the Windows client system the same benefit?
So what now? Purchase a Windows Server 2012 R2 license, copy my invalid files to a NAS share with NFS on a UNIX or Linux system, and have a go at the Windows registry and Server for NFS? Yeah... you're right, it's probably a bit over the top...
On a second thought... I might as well install Linux again. There are countless situations where Linux has helped me solve problems related to, and more often than not caused by Windows.

GRUB doesn't load on HP 6220

hey everyone,
tried to install arch on an hp 6220 laptop this afternoon. the installation worked fine and everything was working out of the box .... BUT ...
unfortuneatly grub doesn't load after powering up the machine, it just waits and do nothing.
fedora's running on the machine atm and grub's loading fine ... so any ideas?
>> i want that laptop to boot arch!!!!!11 <<
best regards

swordfish wrote:- if you are able to start a live system (let's say a usb stick with an Ubuntu) you could check the SSD with the disks utility. Check before, if you have to enable S.M.A.R.T in your BIOS.
Thanks for the hint! I checked the SMART values and got an UDMA CRC Error Count of 432. Apparently, this is a sign of cable issues so I put in my old drive and checked again, it has an UDMA CRC Error Count of 0. I'm not sure if this means the SSD is broken or not.
I also tested the speed of my old drive with hdparm:
cached reads: ~3000MB/s
buffered disk reads: ~83MB/s
This is seems normal to me, so I guess the cable works properly after all.
Also, the Ubuntu Disks utility couldn't find any partitions on the SSD, which is odd. I was able to mount them, read from them and write to them using an Arch Linux Live disk. Why can't Gnome Disks find the partitions?

No option to make an NTFS partition

Hello
I try to install Windows XP 32bits SP3 with Bootcamp, but when i get to select partition and i select BOOTCAMP FAT32 partition on 32GB my windows just starts to install. i do not get the option to do an format of disc to NTFS. Windows just starts to install and when my mac reboots all i get is Disc Error and i have to boot back to MAC OS.
Did anyone else have this problem before or?
Tnx to all that replays

It is a bad version of XP if it doesn't stop and ask, that does happen. Heck, some are so bad they wipe out the whole hard drive and use the entire Mac HD partition.
PS: don't ever use Disk Utility to create a partition for Windows XP, it doesn't work and not sure where you came up with that idea. Only Boot Camp Assistant works with XP and where installing Windows on same drive as Mac OS.
The BOOTCAMP partition is MSDOS/FAT32 and a 'proper' Windows installer will give you option to choose where target volume, click on ADVANCED OPTIONS to format or delete and create NTFS partition.

Thunar doesn't show the partitions mounted in fstab[SOLVED]

Hi everyone,
I am running XFCE 4.10 in archlinux and today when i added couple of partitions to fstab and rebooted my system I noticed that thunar doesn't show the partitions that I added to my fstab. what should i do to make it appear in thunar ?
here is my fstab:
/dev/sda5 /media/disk ntfs-3g defaults 0 0
/dev/sda2 /media/disk-1 ntfs-3g defaults 0 0
Last edited by pyarch (2012-10-03 22:03:54)

Maybe an old thread, but I came up with a different solution. By default Thunar mounts NTFS partitions under
/run/media/<username>/<UUID of NTFS drive> .
If the fstab is updated with a path different from above for your NTFS partitions, they end up not being displayed in bookmarks.
So, to overcome this, create your mount points in
/run/media/<username>/<mount point dir>
and point to those dirs while adding entries to fstab.

HOWTO: Resize Bootcamp (NTFS) partition for free using gparted

Hi,
Well, if you find your Bootcamp/NTFS/Windows partition running out of space, you may want to increase it or decrease it. The OSX Bootcamp utility doesn't allow resizing the NTFS partitio nor does Disk Utility. Here is a free solution ...
NOTE: I've tried this on Windows 7 64bit, but it should work with other windows setups in a similar manner.
Requirements:
1. SysRescueCD (for an NTFS capable 'gparted')
- http://www.sysresccd.org/Download
2. rEFIt bootable CD (or install to hard disk, doesn't matter)
- http://refit.sourceforge.net/doc/c1s5_burning.html
3. Windows XP/Vista/7 CD (depends what you've installed)
- just for a quick 'repair' at the end, no reinstall here!
In short:
1 Shrink Mac partition in OSX's Disk Utility
2 Grow the NTFS partition in gparted booting off sysrescue CD (reboot->option key). This may take 30mins to a few hours to complete!
3 Boot the rEFIt CD -> choose "start partitioning tool" -> hit yes when it says it needs to sync the MBR with the GPT.
4 Boot your Windows CD.
Vista/Windows7 CD -> hit the repair option to fix the boot record.
XP CD -> you may need to go to the administrative shell and type fixboot and then fixmbr.
5. Reboot and you should be able to boot into Windows via the option key as before. I liked rEFIt a lot so I installed it to my disk itself. (FYI, I did notice I needed to install rEFIt a few times to get it to show up during boot time)
Message was edited by: SidOnline

One bug I learnt:
if
1. you set the 'boot' flag on the Windows partition in gparted AND
2. you use gptsync to sync the GPT with the MBR (i.e. MBR->GPT translation)
then
you will find that your Windows partition becomes inaccessible in OS X. Your partition is OK - you can boot in windows etc - OS X just doesn't see it as a NTFS partition.
Solution:
1. Don't enable the boot flag in gparted. Simple, no need to read further.
If you're done it and have been hit by the bug and would like to see Windows/Bootcamp again in Finder, read on...
1. Goto http://www.insanelymac.com/forum/index.php?showtopic=31562, post #9 has a tool to fix it. Download the diskpart.zip file (it's got diskpart.efi)
2. Extract the diskpart.zip file, copy the diskpart.efi to /efi/tools on your OSX volume (default location for hard disk install of rEFIt).
3. Reboot, in the rEFIt menu, select the EFI terminal
4. type fs1: and hit enter. This should take you to your Leopard volume (for me fs0: was the 1st partition (EFI boot partition), fs1: was the 2nd partition (Leopard)
5. type _cd /efi/tools_ and hit enter
6. type diskpart and hit enter
7. As the post linked above says, type
+select <zero-based disk number>+
inspect
+chtype <zero-based partition number> MSDATA+
For me this was
+select 0+
inspect
+chtype 2 MSDATA+
Look at the output of select to make sure you're using the right number - if you have your eyes open it's hard to make a mistake!
Behind the scene details:
Your partition type is set to NTFS in the MBR table (which is why windows can load it up etc) but if you do the above then the partition type in the GPT is written as EFI instead of NTFS (or more accurately 'MSDATA'). This is a bug in gptsync and I believe Chris (writer of rEFIt) is aware of this - at least another post elsewhere made it look like that. I guess you can't blame it since EFI, GPT tools are still in their infancy.
BTW, to sync the GPT with the MBR, there is a tool gptsync. I believe it's a tool from Intel's EFI toobox. It exists as either an efi program (i.e. gptsync.efi, runs when you select it from rEFIt's menu) or as a OSX program (just gptsync, runs when you download it and type 'sudo gptsync').

"Lag" when Nautilus is opened with NTFS partition mounted

Hi, I have a problem with Nautilus 3.14. I have a mounted shared Windows partition with the options below in fstab:
defaults,nls=utf8,umask=000,uid=1000,gid=1000,windows_names,hide_dot_files,hide_hid_files
Everytime I open Nautilus, it "lags" (I don't know what to call it. It freezes and then be usable again for an uncertain amount of time). Tried to unmount the ntfs partition and it worked flawlessly. Nautilus' shell output doesn't show anything strange (just some random GTK warning).
This "lag" doesn't happen when I use Nemo. It runs well with the NTFS partition mounted.
Is anyone knows the solution or has the same problem?

solstice wrote:
it began to make a few click noise when I was copying data to/from it.
I can't believe it. It's a 2 week old harddrive. a western digital suposed to be good quality.
Have I broken it or what ?
I have made a badblocks scan before trying to use it and found no problem. I'll try again but I fear loosing data any moment now :-(((
Western Digital is great but every manufacturer ships out defective drives now and again. Run a hard test with Sea Tools or the WD equivalent and if anything comes up, call them immediately. Your drive is still under warranty if it's brand new so they should replace it for free.

Arch64: wine won't launch exe on NTFS partitions but will do on reiser

Hi everyone!
OK, this is an other issue with wine and x64 (2.6.30). I say another because I saw that a lot of us have issues with wine and x64 that end up being answered "wine and 32 bit applications under x64 architecture won't do fine" but this one is driving me nuts: it looks like i'm not far away from making it.
My problem is: wine can't launch applications if the exe is on my NTFS partition but will do if the same exe is on one of my reiserfs partition.
ie:
[miguel@WKM_MSI ~]$ wine /mnt/win_NTFS/WINDOWS/NOTEPAD.EXE
wine: Unhandled page fault on read access to 0x0044b6ab at address 0x44b6ab (thread 0009), starting debugger...
wine: Unhandled page fault on read access to 0x00000028 at address 0x7eb73c83 (thread 0018), starting debugger...
wine: Unhandled page fault on read access to 0x00000028 at address 0x7eb67c83 (thread 001c), starting debugger...
wine: Unhandled page fault on read access to 0x00000028 at address 0x7eb67c83 (thread 001e), starting debugger...
^C
I get the usual wine popup saying that "NOTEPAD.exe has encountered a serious problem and needs to close" (http://img410.imageshack.us/i/ekrangrnts1.png/)
But:
[miguel@WKM_MSI ~]$ cp /mnt/win_NTFS/WINDOWS/NOTEPAD.EXE /mnt/my_reiserfs_partition/
[miguel@WKM_MSI ~]$ wine /mnt/my_reiserfs_partition/NOTEPAD.EXE
And NOTEPAD works like a charm!
To answer usual questions:
- I gave each bin32-wine* package a try, even some old versions but none make any difference
- all lib32-* packages are installed (except for community/lib32-libgl and community/lib32-nvidia-utils which would conflict with my aur/lib32-nvidia-utils-beta)
- I tried several nvidia configuration but it really doesn't look like a video driver issue... rather a 64 problem
- I installed many things throught winetricks such as DirectX etc...
- I didn't find any similar issue on google
Here is how I mount my partitions if you think that could come from some right issues:
[miguel@WKM_MSI ~]$ cat /etc/fstab
/dev/sda1 /mnt/win_NTFS ntfs-3g users,locale=en_US.utf8 0 0
/dev/sda8 /mnt/my_reiserfs_partition reiserfs defaults 0 0
Some threads with similar problems but no mention of the "partition behavior"
http://bbs.archlinux.org/viewtopic.php?id=60639
http://bbs.archlinux.org/viewtopic.php?id=80394
http://bbs.archlinux.org/viewtopic.php?id=80703
Any clue would be apreciated!
Cheers!
(and keep on the good job )

Hi Slightlystoopid!
Thanks for the idea but that doesn't look like it. I tried the "umask" but no luck!
Actually the line I quoted in the original post was already "experimental". My usual fstab before I tried this one was:
/dev/sda1 /mnt/win_NTFS ntfs-3g users,uid=1000,gid=100,fmask=0113,dmask=0002,locale=fr_FR.utf8 0 0
/dev/sda8 /mnt/my_reiserfs_partition reiserfs defaults 0 0
That gives me:
[root@WKM_MSI miguel]# ll /mnt/
total 8.0K
drwxrwxr-x 1 miguel users 8.0K 2009-09-23 10:42 win_NTFS
drwxrwxrwx 12 root root 384 2009-09-23 10:33 my_reiserfs_partition
Which doesn't work neither!
BTW as we talk about it: "my_reiserfs_partition" is owned by root! Isn't it a security issue? I mean: I can read/write/execute on it as regular user but shouldn't it be mounted with the same rights as /mnt/win_NTFS?
Still interested in any piece of advice on the original issue !

[SOLVED] NTFS partition unmounted after suspend to ram

I recently did a from-scratch installation after I bought an SSD to replace of my old harddrive. Since this fresh install I have been having a problem with an NTFS partition that is mounted by way of fstab (it's not _the_ windows partition just a bit of shared space on a dual-boot setup): Whenever I suspend the computer and bring it back up, the NTFS partition is invariably unmounted.
The mount point is empty and the mount command makes no mention of the mount. A simple "sudo mount /mnt/SAND" will bring the partition back up again although sometimes it needs to be umounted first (the mount point is still empty despite the 'mount'). Here is the fstab line:
/dev/sda3 /mnt/SAND ntfs-3g defaults,noatime,uid=1000,gid=100 0 0
Testing and screwing around I've noticed that if the WINDOWS partition is mounted using nautilus (as it is not mentioned in fstab) that too will be unmounted while a non-root ext4 partition (UBUNTU) is not.
So my hypothesis is that these NTFS partitions are singled out for unmounting when suspending (but apparently not mounting when reawakening?) -- maybe because they are assumed to be external drives? Given that it happens across mounting solutions (fstab/nautilus) I'm inclined to think it's not a bug?
At any rate I'm looking for a solution that will allow me to stop the unmounting when suspending -- ideally for all internal drives, secondarily for these specific partitions. I have checked the suspend to ram article on the wiki but it doesn't seem to mention anything about unmounting...
EDIT: After the Great Big Arch Switch To Systemd this problem no longers occurs on so I'm closing it. Not necessarily much of a solution to anyone who happens on this from google, sorry.
Last edited by madchine (2012-10-13 12:58:54)

Hi all,
It seems that most freezes are gone with:
- 270.29 beta driver
- MTRR enabled by appending enable_mtrr_cleanup mtrr_spare_reg_nr=1 to the list of kernel options (see http://www.nvnews.net/vbulletin/showpos … tcount=39)
I didn't investigate further to know if both the driver and the MTRR trick are required.
Thanks a lot,
Aurel.

Can't mount ntfs partition

hi.. i am running tiger, have no boot camp, but decided to run windows on it.. i've divided the drive into 2 partitions, mac and fat32. everything looked ok until i formatted the fat32 drive to ntfs using the partition utility on a windows xp install cd. since then, mac doesn't mount the ntfs drive. i wanted to copy my windows via some ntfs driver on my mac, but it doesn't want to mount it and i can't mount it via disk utility either.. any ideas??
thanx much

ok, here's the story:
when i had leopard, i ran also windows xp via boot camp, i remember that when i formatted the windows partition from fat32 (default boot camp filesystem), leopard stopped mounting it after restart. that changed when i actually installed windows and started using it (i am almost sure boot camp made leopard be able to mount it normally (read only though, which changed when i installed mac fuse)). so after boot camp took care of the partition, leopard was able to mount it. now i am having this sort of problem: i am running tiger (downgraded back to it because of some bugs in leopard i dislike pretty much) but i cannot run boot camp any more. i partitioned the disk using disk utility (by default into fat32 fs) before installing of tiger. then i used a windows installation cd to reformat the windows partition to ntfs, and from that point on, i can see the disk in terminal (/dev/disk0s3 as well as in disk utility-unmounted) but i am unable to mount it, nobody knows why (i was able to do so when it was fat32). i have already installed the mac fuse with the ntfs driver, but nothing changed, the partition remains unmounted after reboot... this is what boot camp could handle, but unfortunately i have no boot camp any more... i also tried installing refit, an alternative bootloader, hoping it would help with this issue, but nothing works...
i hope u get what i'm talking about now:)
the only thing i want to do is to mount the ntfs partition, because i have backed my old windows up and just want to copy it back with help of mac fuse.
anyone has any ideas??
thanx a lot

Lnstalled Arch alongside windows 8.1 (uefi), grub doesn't show up

Hello people,
I've been following the Beginner's guide to install Arch on my laptop (HP) via the arch.iso on usb flash drive. I have windows 8.1 already installed and I'd like to install Arch alongside it, in uefi mode too.
I could follow most of the steps in the guide, installing arch, grub, ran pacstrap, installed lxde, gummiboot, efibootmgr, etc. But in the end when I reboot, grub doesn't show up and Windows 8.1 boots instead. I even used efibootmgr to display the order of booting (and seeing that Windows was in front of grub), changed the order of booting but to no avail; when rebooted, Windows booted up.
Some information: My efi partition was created by Windows so I used the same partition for Arch's uefi, namely /dev/sda2.
I've got a / partition at /dev/sda6 and a swap partition at /dev/sda7.
I've perfomed the commands
grub-install /dev/sda
but was told that it was wrong (on IRC) and thus I later installed it on the efi partition.
I generated grub.cfg twice:
grub-mkconfig -o /boot/grub/grub.conf
but I was told that this was wrong and so I also did
grub-mkconfig -o /mnt/boot/efi/grub.conf
because the efi partition was mounted at /mnt/boot/efi.
I've also created some files related to gummiboot as the Arch wiki stated to do and set Arch as default OS to boot, but that didn't seem to work.
Lastly I've also booted into the firmware and I have set to boot from usb first, then OS. (I don't see Linux/Windows choices there, only OS). And yes I disabled secure and fast boot.
P.S.:This is my first Arch installation, I come from Lubuntu/Manjaro and I bought this hardware for the purpose of learning Arch Linux (so I really, really, really want to install Arch on it).
Thanks for any help!
Last edited by linux_dream (2015-05-17 22:43:29)

JeromeDGDG wrote:Hello linux_dream.
First, archlinux is for boot exactly the same than other linux distributions. It mount by a boot manager first (grub for exemple).
So, first of all, you absolutly need to creat a /boot partition with some required tools (have some differents) and then, mount it on /boot. This partition need to be FAT32 with around 512MB (mine is 256MB and works fine) and be gpt/UEFI and bootable. There is specific parameters to pass to the tool at format partition time (but if you followed the wiki, all of this is ok now...).
Hello Jérome,
I do have an uefi partition (FAT32) thanks to Windows. It is on /dev/sda2, so I mounted it as /mnt/boot/efi where I had mounted /mnt as root.
JeromeDGDG wrote:
Then...
you have to see the /boot partition you created on your BIOS. The bios, is the first thinks the computer run at boot time (before everythings). Then go inside your bios and check options around boot and see boot list (sometimes, when change config, you have to reboot again the bios for see the changes on boot list appears). Then on your boot list from BIOS, you have to see your grub /boot partition (mine is named égrub_archlinux" viewed by the boot list of my bios) and make it boot first (or just after usb and cdrom if you prefer...). If not, this grub will never been mounted and windows will start first.
Also, if you are confused with command tools on linux systems and you not sure your partition boot is not well created, you can easily used gparted gui tools (do a bootable cdrom and use it for partitions or check...).
In the BIOS I don't see anything related to grub nor Arch. However in the uefi settings, I do. To access these settings is tedious, I need to boot Windows, click on reboot while maintaining the Shift key, selecting "troubleshooting", go to uefi settings, reboot and then press F9 to enter there. There I can see grub, Arch and Windows and I can enter in Arch from there. So I don't need the arch.iso flash drive anymore, I prefer to boot from my hard disk.
head_on_a_stick wrote:
That doesn't make much sense -- you say you have "installed gummiboot" but also that "Windows was in front of grub [sic]" in your NVRAM entries -- which did you install, GRUB or gummiboot?
Also, installing a desktop environment (LXDE) is mentioned nowhere in the Beginner's Guide.
I installed both Grub and gummiboot (in that order). Yeah I installed LXDE because I thought everything went fine (grub recognized Arch when it generated the .cfg file), I only saw the problems when I rebooted: grub doesn't show up.
head_on_a_stick wrote:
The actual command you should use is:
# grub-install --target=x86_64-efi --efi-directory=$esp --bootloader-id=grub --recheck
I did that command too, where I took care to replace $esp by /mnt/boot/efi if I remember well. The command worked.
head_on_a_stick wrote:
Again, the command should be:
# grub-mkconfig -o /boot/grub/grub.cfg
As stated in the ArchWiki page I have linked above.
Make sure you have mounted all your partitions and used `arch-chroot` before running these commands.
I did that command, it generated files and recognized 3 images (linux, initramfs and another thing I don't remember). Again, if I remember well.
head_on_a_stick wrote:
Please post the content of /boot/loader/loader.conf & /boot/loader/entries/arch.conf (if that is what you've called it) and the output of:
lsblk -f
ls -R /boot
# parted -l
# efibootmgr -v
Again, run all these commands after you have mounted all your partitions and used `arch-chroot` from the live Arch ISO.
You can use sprunge to generate a link to their pastebin for the command output:
<command> | curl -F 'sprunge=<-' http://sprunge.us
https://wiki.archlinux.org/index.php/Li … in_clients
Unfortunately I'm having a very hard time to make the curl command work, I think that it's due to my keyboard layout and I can't seem to write the correct apostrophes (mines seem curvy) nor the correct " sign. Here's the error that I get (manually copied):
returned Warning: Illegally formatted input field!
curl: option -F: is badly used here.
curl: try 'curl --help' or 'curl --manual' for more information
. I've been seeking help for around 20 minutes on #archlinux (IRC) to no avail thus far.
So I entered some of the commands you mentionned and I took some photos of them. See the 5 photos at https://imgur.com/QN8FBZ1,RLbSe2u,73o1w … ,aBTxNNF#0
Of course it would be much better if I could find a way to make the curl command work.

GRUB doesn't detect NTFS partition

Similar Messages

Maybe you are looking for