Well, this is a mess of a thread. To mount a NTFS partition
ntfs-3g -o rw /dev/sdb1 /media/Windows or
ntfs-3g -o ro /dev/sdb1 /media/Windows for read-only, if
rw fails. Just make sure the device and mount point correspond to what you're using on you're system. It's not likely everyone who reads this will have their Windows NTFS partition on /dev/sdb1.
Turning off fast start in Windows 8 and up is a necessity for lasting effect. But a good one-off is to hold the power button until the machine shuts down. It won't hibernate then. You can also disable 'fast boot' in the bios/uefi, which sometimes helps.
After quite a few of the listed solutions, Windows must be shut down, rebooted, and shut down again for them to work. Other times, with Linux solutions, Linux must be shut down and rebooted for the method to work.
sudo ntfs-3g -o remove_hiberfile /dev/sdb1 /path to mount point will remove the hibernation file preventing access to the NTFS volume, but afterward, the system should be shut down and rebooted, and THEN try to mount
rw, as above, or with
,rw appended to the mount options in
/etc/fstab for the NTFS volume.
If you want any file system to mount, regardless of what device the system gives it, which can change, you can find the UUID of the drive with
ls -al /dev/disk/by-uuid which gives something like this:
marky12@linuxxx:~$ ls -al /dev/disk/by-uuid total 0 drwxr-xr-x 2 root root 200 Sep 28 23:32 . drwxr-xr-x 6 root root 120 Sep 28 23:32 .. lrwxrwxrwx 1 root root 10 Sep 28 23:34 171aadc8-f84e-4011-9a57-XXXXXXXXXXXX -> ../../sda1 lrwxrwxrwx 1 root root 10 Sep 28 23:34 1aa1b978-565d-4430-a92a-XXXXXXXXXXXX -> ../../sda3 lrwxrwxrwx 1 root root 10 Sep 28 23:34 2353a9b0-8847-4541-87d8-XXXXXXXXXXXX -> ../../sda6 lrwxrwxrwx 1 root root 10 Sep 28 23:34 5aaa6253-fe3a-43cd-81b1-XXXXXXXXXXXX -> ../../sda7 lrwxrwxrwx 1 root root 10 Sep 28 23:34 XXXXXXXXXXXX -> ../../sda2 lrwxrwxrwx 1 root root 10 Sep 28 23:34 7ac1b3cb-0a73-4f30-bea2-XXXXXXXXXXXX -> ../../sda4 lrwxrwxrwx 1 root root 10 Sep 28 23:34 ac1d849d-7aed-40c2-b1d9-XXXXXXXXXXXX -> ../../sda8 lrwxrwxrwx 1 root root 10 Sep 28 23:34 fb2d05ee-21f9-4139-a216-XXXXXXXXXXXX -> ../../sda5 t
The big long numbers are UUIDs. which the system won't change. You can use them in
/etc/fstab like so
UUID=fb2d05ee-21f9-4139-a216-XXXXXXXXXXXX /media/drive ntfs defaults,user.auto,rw 0 0` Then, if you switch some drives around, and the device node changes from /dev/sdb1 to /dev/sdc1, the system will still know what drive you mean.
But if you make an identical image of a drive, it will have the same UUID. If you try to mount both on the same system, it won't work, even if you use device nodes, i.e. /dev/sdb1.
So, you have to use the mount option
no-uuid for one of them, and then you can mount both.
So, my impression is that if we all take a deep breath and relax a bit before tackling mysterious computer problems, no one will rush right past the solution.