[linux-lvm] Unable to find device with UUID XXX.

Brian McCullough bdmc at bdmcc-us.com
Wed May 18 19:44:03 UTC 2016


This is not looking good.

I have tried to re-attach the old ( probably failing ) drive to the test
machine, and I see this in dmesg:

[ 4566.743139] usb 1-5: new high-speed USB device number 27 using
ehci_hcd
[ 4566.861622] usb 1-5: New USB device found, idVendor=0bc2,
idProduct=3320
[ 4566.861625] usb 1-5: New USB device strings: Mfr=2, Product=3,
SerialNumber=1
[ 4566.861627] usb 1-5: Product: Expansion Desk
[ 4566.861628] usb 1-5: Manufacturer: Seagate
[ 4566.861629] usb 1-5: SerialNumber: 2HC015KJ
[ 4566.862054] scsi8 : usb-storage 1-5:1.0
[ 4567.865494] scsi 8:0:0:0: Direct-Access     Seagate  Expansion Desk
0711 PQ: 0 ANSI: 6
[ 4567.866036] sd 8:0:0:0: Attached scsi generic sg4 type 0
[ 4567.869533] sd 8:0:0:0: [sdd] Spinning up disk..............ready
[ 4578.911055] sd 8:0:0:0: [sdd] 732566645 4096-byte logical blocks:
(3.00 TB/2.72 TiB)
[ 4609.862126] usb 1-5: reset high-speed USB device number 27 using
ehci_hcd
[ 4624.964140] usb 1-5: device descriptor read/64, error -110
[ 4640.167241] usb 1-5: device descriptor read/64, error -110
[ 4640.370138] usb 1-5: reset high-speed USB device number 27 using
ehci_hcd
[ 4655.472298] usb 1-5: device descriptor read/64, error -110
[ 4665.690010] sd 8:0:0:0: [sdd] Test WP failed, assume Write Enabled
[ 4672.640209] sd 8:0:0:0: [sdd] Asking for cache data failed
[ 4672.640211] sd 8:0:0:0: [sdd] Assuming drive cache: write through
[ 4672.643323] sd 8:0:0:0: [sdd] Spinning up
disk.......................................................................................................not
responding...
[ 4773.042814] sd 8:0:0:0: [sdd] 732566645 4096-byte logical blocks:
(3.00 TB/2.72 TiB)
[ 4779.990875] sd 8:0:0:0: [sdd] Test WP failed, assume Write Enabled
[ 4786.941084] sd 8:0:0:0: [sdd] Asking for cache data failed
[ 4786.941086] sd 8:0:0:0: [sdd] Assuming drive cache: write through


This is a Seagate ( as you can see ) packaged USB external drive.

With these errors, would it be worthwhile trying to extract the drive
from the case and try it either internally or in another case?


Thank you,
Brian





More information about the linux-lvm mailing list