In article <ra0phr$s56$
1...@dont-email.me>,
Joe Beanfish <joebe...@nospam.duh> wrote:
>> report that the
>> target filesystem is read-only, and then a few attempted copies after
>> that, the files will disappear, and it appears that the mount point
>> has no drive mounted there if an ls -a is run, but df still lists the
>> drive in its output.
>Flaky USB port?
>Not enough power on the port (if you're not using external power
>for the drives)?
Not enough reliable power from the *external* power supply if you *are*
using one :)
Having had an external USB/network NAS with a switchmode powerbrick
slowly go out of spec, such that the drive would work ok until you wrote
wrote wrote wrote wrote at it, and then it would suddenly decide to
spin down/up the drive and get confused ...
Can you hear what the drive is doing? Can you see the activity light
misbehaving (unusual loss of activity, or active light coming on
FULL and staying on ... )
Filesystems going read-only is often a defence mechanism when other
things are going wrong, so it's a symptom (not a cause).
Definitely check the output of dmesg (or /var/log/messages or syslog)
from the point where you connected the drive, until the failure happens.
--
--------------------------------------+------------------------------------
Mike Brown: mjb[-at-]
signal11.org.uk |
http://www.signal11.org.uk