On 10/03/2014 12:01 PM, Frank McCormick wrote:
I am running Fedora 20 (updated from 19) and have started having
problems with an external SATA disk. It's connected through a USB
adapter.
Smartd recognizes it but I see repeated errors in the journal about
not being able to update smart data on the disk.
A few days ago, (around the time I updated 19 to 20) the disk after
not being used for a while would become unresponsive with attempts to
access the directories on it resulting in hangs.
Yet if I reboot after turning the power to the disk off and on again
everything is fine for a while.
fsck reports the two partitions on the disk are fine and if I run
a SMART short test it passes.
This is the sort of error I get if I reboot without cycling the power
> Oct 03 11:09:54 localhost.localdomain systemd[1]: Job
> dev-disk-by\x2duuid-d8088c90\x2db24c\x2d483d\x2d8865\x2d4fdf6ac2b6a8.device/start
> Oct 03 11:09:54 localhost.localdomain systemd[1]: Timed out waiting
> for device dev-disk-by\x2duuid-d8088c90\x2db24c\x2d483d\x2d8865\x2d
> Oct 03 11:09:54 localhost.localdomain systemd[1]: Dependency failed
> for /home/frank/external.
> Oct 03 11:09:54 localhost.localdomain systemd[1]: Startup finished in
> 2.097s (kernel) + 1.926s (initrd) + 1min 31.930s (userspace) = 1m
> Oct 03 11:10:42 localhost.localdomain kernel: usb 2-6: USB
> disconnect, device number 4
> Oct 03 11:10:42 localhost.localdomain smartd[433]: Monitoring 1 ATA
> and 0 SCSI devices
> Oct 03 11:10:42 localhost.localdomain kernel: sd 4:0:0:0: [sdb]
> Unhandled error code
> Oct 03 11:10:42 localhost.localdomain kernel: sd 4:0:0:0: [sdb]
> Oct 03 11:10:42 localhost.localdomain kernel: Result:
> hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
> Oct 03 11:10:42 localhost.localdomain kernel: sd 4:0:0:0: [sdb] CDB:
> Oct 03 11:10:42 localhost.localdomain kernel: Read(10): 28 00 00 00
> 00 00 00 00 08 00
> Oct 03 11:10:42 localhost.localdomain kernel: end_request: I/O error,
> dev sdb, sector 0
> Oct 03 11:10:42 localhost.localdomain kernel: Buffer I/O error on
> device sdb, logical block 0
> Oct 03 11:10:42 localhost.localdomain kernel:
> ldm_validate_partition_table(): Disk read failed.
> Oct 03 11:10:42 localhost.localdomain kernel: Dev sdb: unable to read
> RDB block 0
> Oct 03 11:10:42 localhost.localdomain kernel: sdb: unable to read
> partition table
> Oct 03 11:10:42 localhost.localdomain kernel: sd 4:0:0:0: [sdb] READ
> CAPACITY failed
> Oct 03 11:10:42 localhost.localdomain kernel: sd 4:0:0:0: [sdb]
> Oct 03 11:10:42 localhost.localdomain kernel: Result:
> hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
> Oct 03 11:10:42 localhost.localdomain kernel: sd 4:0:0:0: [sdb] Sense
> not available.
> Oct 03 11:10:42 localhost.localdomain kernel: sd 4:0:0:0: [sdb]
> Attached SCSI disk
> Oct 03 11:10:42 localhost.localdomain systemd-udevd[1147]:
> inotify_add_watch(7, /dev/sdb, 10) failed: No such file or directory
>
>
Anyone has any ideas ?
Thanks
Been there and done that. I was pleagued
with this problem for many weeks until I
kicked the drives off of usb.
USB is the poorest type of connection for disk drives.
That's why I use an eSATA PcCard with 2 eSATA-3 ports
and connect the drive to the eSATA ports.
This of course requires that you have an enclosure which
provides eSATA ports.
After I did this, all such problems as you report totally disappeared.