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:

none /proc proc defaults 0 0
none /sys sysfs defaults 0 0
none /dev/pts devpts gid=2,mode=620 0 0
/dev/fd0 /mnt/floppy auto noauto,rw 0 0

_________________________________________________________

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.

I have a suspicion that your Compacq marked the drives as "faulty" in /etc/mdadm.conf. Try using the mdadm system (on the Compaq with the drives mounted) to see that's going on.

Note: I don't have "Puppy" installed on any of my systems, so the above is "generic" advice.

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.