Page 1 of 1

[SOLVED!] problems mounting directories

PostPosted: Jan 8th, '16, 04:54
by lloyd
This might sound a little weird, but I have no clue about this...:-(
So here goes....
I have 3 drives...sda,sdb, and sdc. Mageia 5 is the only thing installed sdc. An ext4 and swap partition. It is a Samsung SSD.
sdb is a Western Digital HDD with a 1.9Tb partition (/home) and a 756Gb partition (/shared). The 1.9Tb /home partition is formatted ext4. It works fine.
The /shared partition was formatted was formatted with NTFS-3G so I could share it with Windows. It is now inaccesible from Linux. It won't mount.
sda is a Seagate HDD with Windows 10 Home on it and nothing else. I'm assuming Windows is formatted with NTFS. There is a 500Mb reserved partition. I don't care if that mounts. The main Windows partition is sda2. Windows runs fine by itself (booted from GRUB) This partition is also inaccesible from Linux.

Now come the error messages......

An error occurred while accessing '746.5 GiB Hard Drive', the system responded: The requested operation has failed: Error mounting system-managed device /dev/sdb5: Command-line `mount "/shared"' exited with non-zero exit status 14: The disk contains an unclean file system (0, 0). Metadata kept in Windows cache, refused to mount. Failed to mount '/dev/sdb5': 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.

Same error message for /media/win_d, except the partition numbers are different.

Windows 7 did NOT have this problem.



This is the original fstab file.....

Code: Select all
# Entry for /dev/sdc1 :
UUID=48ccc07c-c0b8-4c71-a002-7972530b6ff6 / ext4 noatime,acl 1 1
# Entry for /dev/sdb1 :
UUID=b22067d2-13e7-40e2-85d7-4cc6c34ce3e1 /home ext4 noatime,acl 1 2
# Entry for /dev/sda2 :
UUID=842EE71D2EE70750 /media/win_d ntfs-3g defaults,nofail,umask=000 0 0
none /proc proc defaults 0 0
# Entry for /dev/sdb5 :
UUID=3411D0BF0B2C1763 /shared ntfs-3g defaults,nofail,umask=000 0 0
# Entry for /dev/sda1 :
# UUID=66CEE3EFCEE3B589 /windows ntfs-3g defaults,nofail,umask=000 0 0
# Entry for /dev/sdc5 :
UUID=6ce6416d-2ccd-4d80-9133-1c6bc18b29a1 swap swap defaults 0 0


Any ideas on how to fix it? Any help is appreciated. Thank you!

Re: problems mounting directories

PostPosted: Jan 8th, '16, 06:54
by jiml8
Run chkdsk on it from Windows, then do a proper shutdown from Windows.

Not sure if there is an fsck option for NTFS; I think there is, but I have not used NTFS with Linux for many years and I don't recall exactly. You should try it though.

Re: problems mounting directories

PostPosted: Jan 8th, '16, 06:55
by jiml8
There is an ntfsfix command in Linux; try that.

Re: problems mounting directories

PostPosted: Jan 8th, '16, 10:54
by filip
Your "error" message clearly state:
lloyd wrote:
Code: Select all
Please resume and shutdown Windows fully (no hibernation or fast restarting), or mount the volume read-only with the 'ro' mount option.


So don't fix the NTFS FS before. It's not an error. It's a Windows feature.

Re: problems mounting directories

PostPosted: Jan 8th, '16, 11:13
by doktor5000
jiml8 wrote:There is an ntfsfix command in Linux; try that.

Better not, that's not for fixing. Only thing it does apart from some basic checks is it schedules an fsck for next windows boot. In short: Don't use it, and it won't fix the problem.

@lloyd: For windows 8 and above you should disable fast boot/ hybrid shutdown and also hibernation.
See also https://wiki.mageia.org/en/Mageia_in_du ... in_Windows

Re: problems mounting directories

PostPosted: Jan 8th, '16, 15:10
by lloyd
I followed your instructions about the powercfg file. That fixed the problem. Once again, the good Doktor cures the patient!
Thank you very much!

Lloyd

Re: problems mounting directories

PostPosted: Jan 8th, '16, 16:32
by isadora
Please lloyd, don't forget to mark the topic [SOLVED].
You can do so, by editing the subject/title in the first message in this topic.
Write [SOLVED] to the left of subject/title, thanks ahead. ;)