[SOLVED] External USB hard drives no longer mounting read/write -- now read only
PuppyThis forum is for the discussion of Puppy Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
External USB hard drives no longer mounting read/write -- now read only
I have 2 laptops, both running identically configured Precise Puppy 5.4.2, one a Toshiba, the other a Compaq. I also use 2 identical external 2 TB USB-docked hard drives formatted as NTFS in RAID 1 array (mirroring each other.) I've had no problems at all using the hard drives with either laptop until recently, using the Compaq, suffered a power outage. Now when I try to mount the drives on the Compaq, which appear as usual on the desktop, I get this warning message in a red box:
"The ntfs-3g driver was unable to mount the NTFS
partition and returned this error message:
fuse: mountpoint is not empty
fuse: if you are sure this is safe, use the 'nonempty' mount option
So, the inbuilt kernel NTFS driver has been used
to mount the partition read-only."
I checked the fstab file in both computers, and they are identical, the contents of which is:
The drives still mount fine (read-write) on the Toshiba, but read only on the Compaq. Does anyone know anything I can do to remedy this situation, i.e. be able to mount read-write on the Compaq? Sincere thanks for any help! I've installed Puppy on both computers' internal hard drives, so they are both dual boot with Windows XP (which I never use anymore now that I can do whatever I want with the apps I have installed on Puppy, which I love.
Thanks for the advice, but the actual solution was so simple, I feel kind of stupid! The folder that was the supposed mount point was not empty when I checked it, so I just deleted the folders there (they contained nothing anyway) and .... problem solved! It was just like the warning message said about the mount point not being empty, duh! I do appreciate the response though.