You are not logged in.
- Topics: Active | Unanswered
#1 2015-08-13 05:21:13
- mibadt
- Member
- Registered: 2009-09-25
- Posts: 396
Arch fails to mount NTFS partition after win10 upgrade
Hi,
I had a fully functional (BIOS/GRUB 2 based) dual boot Arch 64 (fully updated)/Win7 system.
Yesterday I upgraded the Win7 to Win 10 (no problems on the Win 10 and grub segments).
Afterwards, Arch failed to completely boot, and looking at the journal, I've found the problem was it couldn't mount NTFS partitions, claiming "windows has left those in hibernate state".
I've commented out the respective fstab entries (see below version) and, indeed, afterwards Arch fully booted again.
Has anybody an idea how to fix the problem with access to my NTFS partitions from within Linux?
Thanks upfront!
---------copy of modified fstab------------------
#
# /etc/fstab: static file system information
#
# <file system> <dir> <type> <options> <dump> <pass>
# /dev/sdb2 LABEL=Root
UUID=6ee857d9-95d1-47c4-ad47-18b979f49e74 / ext4 rw,relatime,data=ordered 0 1
# /dev/sda2
UUID=76af1051-313e-4736-a61c-7c6c8dbaf6ba /boot ext4 rw,relatime,data=ordered 0 2
# /dev/sdb3 LABEL=Var
UUID=f3d0d861-1faf-4f69-8aae-81c2974b15c1 /var ext4 rw,relatime,data=ordered 0 2
# /dev/sda3 LABEL=HOME
UUID=9d6eb8a2-be83-477b-976e-e6d1ad560f8d /home ext4 rw,relatime,data=ordered 0 2
# /dev/sdb4 LABEL=Lin_Back
UUID=827add8b-9051-409a-8ae8-cf23c7a27354 /lin_back ext2 rw,relatime 0 2
# /dev/sdb5 LABEL=Images
UUID=a520e020-5d7e-44f1-b125-ca171c60d1d0 /images ext2 rw,relatime 0 2
# /dev/sdb6 SWAP is auto mounted by systemd. Thus-no entry in fstab
#UUID=9f259b5f-dd18-4fdf-becf-3e62086bc059 none swap defaults 0 0
# /dev/sda1
#UUID=60EF627E1C378908 /windows ntfs-3g defaults 0 0
# /dev/sdc8
#UUID=24B39CB761075197 /photos ntfs-3g defaults 0 0
# /dev/sdb3
##UUID=71AF0020700759D6 /oldphotos ntfs-3g defaults 0 0Best regards,
Michael Badt
Offline
#2 2015-08-13 05:30:56
- ayekat
- Member
- Registered: 2011-01-17
- Posts: 1,590
Re: Arch fails to mount NTFS partition after win10 upgrade
You may need to configure Windows such that it completely shuts down the system instead of hibernating (which seems to be Windows-standard in the modern days).
Apart from that, if you wish that your boot continues after a failed attempt to mount a Windows-NTFS, you may want to pass the nofail option.
Offline
#3 2015-08-13 08:45:07
- mibadt
- Member
- Registered: 2009-09-25
- Posts: 396
Re: Arch fails to mount NTFS partition after win10 upgrade
Thanks a lot!
Best regards,
Michael Badt
Offline
#4 2015-08-13 10:39:15
- Silkworm205
- Member
- From: UK
- Registered: 2012-05-21
- Posts: 267
Re: Arch fails to mount NTFS partition after win10 upgrade
Hybrid/Fast-boot is responsible for causing this in both Windows 8 and 10. There's an article here about how to turn it off, which would allow you read/write access from Arch after each reboot. But it will make Windows take longer to load.
Otherwise, if Windows Hybrid-shutsdown and you just want to read files, you can mount it manually with the read only flag to access you data.
I think I know enough to know I don't know enough.
Offline
#5 2015-08-13 14:01:08
- mibadt
- Member
- Registered: 2009-09-25
- Posts: 396
Re: Arch fails to mount NTFS partition after win10 upgrade
Thanks again, that indeed caused my problem!
Best regards,
Michael Badt
Offline