Seagate USB enclosure Linux trouble

Index, feed.

[	Date	\|	2013-07-02 23:17 -0400	]
[	Mod.	\|	2016-05-19 11:23 -0400	]

I got a Seagate external drive (4TB drive attached to a USB3 / SATA bridge, called "Backup Plus Desk"). It would not initially be recognized by my (Debian) Linux (boring leading part of each line elided):

sd 9:0:0:0: [sdb] Attached SCSI disk
usb 1-2: USB disconnect, device number 69
usb 1-2: new high speed USB device number 70 using ehci_hcd
usb 1-2: New USB device found, idVendor=0bc2, idProduct=a0a4
usb 1-2: New USB device strings: Mfr=2, Product=3, SerialNumber=1
usb 1-2: Product: Backup+ Desk
usb 1-2: Manufacturer: Seagate
usb 1-2: SerialNumber: (elided)
scsi10 : uas

As far as I can tell, it's the "uas" part that's the wrong decision there.

Then some more noise:

mtp-probe: checking bus 1, device 70: "/sys/devices/pci0000:00/0000:00:12.2/usb1/1-2"
scsi 10:0:0:0: Direct-Access     Seagate  Backup+ Desk     050B PQ: 0 ANSI: 6
mtp-probe: bus: 1, device: 70 was not an MTP device
scsi 10:0:0:0: uas_eh_abort_handler tag 0
scsi 10:0:0:0: uas_eh_device_reset_handler tag 0
scsi 10:0:0:0: uas_eh_target_reset_handler tag 0
scsi 10:0:0:0: uas_eh_bus_reset_handler tag 0
usb 1-2: reset high speed USB device number 70 using ehci_hcd
scsi 10:0:0:0: Device offlined - not ready after error recovery
scsi 10:0:0:1: Direct-Access     Seagate  Backup+ Desk     050B PQ: 0 ANSI: 6
scsi 10:0:0:2: Direct-Access     Seagate  Backup+ Desk     050B PQ: 0 ANSI: 6
scsi 10:0:0:3: Direct-Access     Seagate  Backup+ Desk     050B PQ: 0 ANSI: 6
scsi 10:0:0:4: Direct-Access     Seagate  Backup+ Desk     050B PQ: 0 ANSI: 6
scsi 10:0:0:5: Direct-Access     Seagate  Backup+ Desk     050B PQ: 0 ANSI: 6
scsi 10:0:0:6: Direct-Access     Seagate  Backup+ Desk     050B PQ: 0 ANSI: 6
scsi 10:0:0:7: Direct-Access     Seagate  Backup+ Desk     050B PQ: 0 ANSI: 6
sd 10:0:0:0: Attached scsi generic sg2 type 0
sd 10:0:0:1: Attached scsi generic sg3 type 0
sd 10:0:0:2: Attached scsi generic sg4 type 0
sd 10:0:0:3: Attached scsi generic sg5 type 0
sd 10:0:0:4: Attached scsi generic sg6 type 0
sd 10:0:0:5: Attached scsi generic sg7 type 0
sd 10:0:0:6: Attached scsi generic sg8 type 0
sd 10:0:0:7: Attached scsi generic sg9 type 0
sd 10:0:0:4: uas_eh_abort_handler tag 0
sd 10:0:0:6: uas_eh_abort_handler tag 0
sd 10:0:0:1: uas_eh_abort_handler tag 0
sd 10:0:0:7: uas_eh_abort_handler tag 0
sd 10:0:0:2: uas_eh_abort_handler tag 0
sd 10:0:0:3: uas_eh_abort_handler tag 0
sd 10:0:0:5: uas_eh_abort_handler tag 0
sd 10:0:0:0: uas_eh_abort_handler tag 0
sd 10:0:0:0: uas_eh_device_reset_handler tag 0
sd 10:0:0:1: uas_eh_device_reset_handler tag 0
sd 10:0:0:2: uas_eh_device_reset_handler tag 0
sd 10:0:0:3: uas_eh_device_reset_handler tag 0
sd 10:0:0:4: uas_eh_device_reset_handler tag 0
sd 10:0:0:5: uas_eh_device_reset_handler tag 0
sd 10:0:0:6: uas_eh_device_reset_handler tag 0
sd 10:0:0:7: uas_eh_device_reset_handler tag 0
sd 10:0:0:4: uas_eh_target_reset_handler tag 0
sd 10:0:0:0: uas_eh_bus_reset_handler tag 0
usb 1-2: reset high speed USB device number 70 using ehci_hcd

Then some serious bullshit:

sd 10:0:0:0: Device offlined - not ready after error recovery
sd 10:0:0:5: Device offlined - not ready after error recovery
sd 10:0:0:3: Device offlined - not ready after error recovery
sd 10:0:0:2: Device offlined - not ready after error recovery
sd 10:0:0:7: Device offlined - not ready after error recovery
sd 10:0:0:1: Device offlined - not ready after error recovery
sd 10:0:0:6: Device offlined - not ready after error recovery
sd 10:0:0:4: Device offlined - not ready after error recovery
sd 10:0:0:5: [sdg] READ CAPACITY(16) failed
sd 10:0:0:5: [sdg]  
sd 10:0:0:0: [sdb] READ CAPACITY(16) failed

At this point, I would have eight /dev/sd? devices created, but none of them readable.

Since I don't think I need module uas (USB-attached SCSI) for anything, I just unloaded it (rmmod uas) and also blacklisted it for good measure (by creating a file /etc/modprobe.d/blacklist-uas.conf with contents blacklist uas; untested, details will vary by distribution).

Now things appear to be alright, and I can actually access my block device.

usb 2-1.3: new high speed USB device number 20 using ehci_hcd
usb 2-1.3: New USB device found, idVendor=0bc2, idProduct=a0a4
usb 2-1.3: New USB device strings: Mfr=2, Product=3, SerialNumber=1
usb 2-1.3: Product: Backup+ Desk
usb 2-1.3: Manufacturer: Seagate
usb 2-1.3: SerialNumber: (elided)
scsi18 : usb-storage 2-1.3:1.0
scsi 18:0:0:0: Direct-Access     Seagate  Backup+ Desk     050B PQ: 0 ANSI: 6
sd 18:0:0:0: [sdh] Spinning up disk...........ready
sd 18:0:0:0: [sdh] 976754645 4096-byte logical blocks: (4.00 TB/3.63 TiB)
sd 18:0:0:0: [sdh] Write Protect is off
sd 18:0:0:0: [sdh] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sd 18:0:0:0: [sdh] 976754645 4096-byte logical blocks: (4.00 TB/3.63 TiB)
 sdh: sdh1
sd 18:0:0:0: [sdh] 976754645 4096-byte logical blocks: (4.00 TB/3.63 TiB)
sd 18:0:0:0: [sdh] Attached SCSI disk

Other relevant models

On 2016-01-28, a reader mentioned that the same steps applied to some ioSafe SoloPRO fireproof and waterproof external drives on Debian Squeeze. Thanks, Mikhaël Sayegh!

On 2016-05-18, I applied the same fix to use a "LaCie Porsche Desktop" external drive. The SMART data indicates that the disk is made by Seagate.

www.kurokatta.org

Quick links:

Photos: Montréal; Oregon; Paris; Camp info 2007; Camp Faécum 2007; --more--
Doc: Jussieu; Japanese adjectives; Muttrc; Bcc; Montréal; Couleurs LTP; French English words; Petites arnaques; --more--
Hacks: Statmail; DSC-W17 patch; Scarab: dictionnaire de Scrabble; Sigpue
Recipes: Omelette soufflée au sirop d'érable; Camembert fondu au sirop d'érable; La Mona de Tata Zineb; Cake aux bananes, au beurre de cacahuètes et aux pépites de chocolat