I am trying to copy a file from a Windows partition.
linux-h4i8:/home/ion # mount /dev/sdc2 /mnt/hd
The disk contains an unclean file system (0, 0).
Metadata kept in Windows cache, refused to mount.
Failed to mount '/dev/sdc2': Operation not permitted
The NTFS partition is in an unsafe state. Please resume and shutdown
Windows fully (no hibernation or fast restarting),or mount the volume
read-only with the 'ro' mount option.
Focusing on the “or mount the volume read-only with the ‘ro’ mount option”…
linux-h4i8:/home/ion # mount -ro /dev/sdc2 /mnt/hd
mount: /mnt/hd: can't find in /etc/fstab.
What does /etc/fstab have to do with what I was instructed to do? Thanks for any suggestion or explanation.
I booted Win 10 and this time when I shut down I waited till I heard the fan stop to insure it was a proper shutdown. But the problem repeated when I tried to mount the file system.
Hi
There is shutdown and there is full shutdown… in WinX select shutdown in the menu and before you select it hold the shift key and select ‘shutdown’ for a ‘full’ shutdown or I use a shortcut;
Apart from that: My experience is with Windows 8.1.
I turned off “fast boot” in Windows. And it worked fine – until it stopped working.
So then I disable hibernation in Windows, and it started working again. It seems that Microsoft doesn’t like turning off fast boot, so it partially ignores that.
My current strategy – when rebooting from Windows, I use: SHIFT restart
That is supposed to cause Windows to fully shutdown. But I’m no longer sure that anything from Microsoft can be fully trusted.
linux-h4i8:/home/ion # mount -ro /dev/sdc2 /mnt/hd
mount: /mnt/hd: can't find in /etc/fstab.
What does /etc/fstab have to do with what I was instructed to do? Thanks for any suggestion or explanation.[/QUOTE]
Well, /etc/fstab is the configuration file for the mount program. As soon as mount has not enough information to do a mount as asked for, it will go to /etc/fstab to find out if there is an entry for /dev/sdc2 to gather the failing information. As there isn’t such entry (I assume, because you failed to show /etc/fstab), it complains. In this case, the failing information could be the fstype. When this information fails, mount tries to find out what the fstype is by looking inside the partition if it can make an intelllegent guess, but when that fails …
This is rather at the top of
man mount
If only the directory or the device is given, for example:
mount /dir
then mount looks for a mountpoint (and if not found then for a device) in the /etc/fstab file.