[CentOS-de] USB Festplatte hört plötzlich auf zu funktionieren

Di Nov 11 08:56:48 UTC 2014

Am 05.11.2014 um 16:00 schrieb Frank Büttner:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA512
>
> Huhu,
> spontan würde ich mal drauf tippen, das der USB Port oder sogar ein Teil
> vom USB Controller die Hufe hoch gerissen hat.
> Wie verhält sich denn die Platte an einem anderen System?
>
> Gruß
> Frank
> Am 05.11.2014 um 12:41 schrieb J. Echter:
>> Hallo,
>>
>> habe CentOS 6.5 x64, an diesem Rechner habe ich eine USB-Platte auf die
>> mein Backup Programm Sicherungen macht.
>>
>> Diese Platte hört plötzlich auf zu funktionieren und ist auch erst
>> wieder nach einem Reboot nutzbar.
>>
>> Wenn ich die Platte tausche und eine andere anschliesse dann wird diese
>> auch, bis zum Reboot, nicht erkannt.
>>
>> dmesg spuckt folgendes aus:
>>
>> usb 2-1.5: USB disconnect, device number 4
>> usb 2-1.5: new high speed USB device number 5 using ehci_hcd
>> usb 2-1.5: New USB device found, idVendor=1759, idProduct=5000
>> usb 2-1.5: New USB device strings: Mfr=1, Product=2, SerialNumber=3
>> usb 2-1.5: Product: MassStorage Device
>> usb 2-1.5: Manufacturer: USB 3.0
>> usb 2-1.5: SerialNumber:            73K4S4RGS
>> usb 2-1.5: configuration #1 chosen from 1 choice
>> scsi8 : SCSI emulation for USB Mass Storage devices
>> usb-storage: device found at 5
>> usb-storage: waiting for device to settle before scanning
>> usb-storage: device scan complete
>> scsi 8:0:0:0: Direct-Access     USB 3.0  LucidPort USB300 0100 PQ: 0
>> ANSI: 4
>> sd 8:0:0:0: Attached scsi generic sg3 type 0
>> sd 8:0:0:0: [sdc] 625142448 512-byte logical blocks: (320 GB/298 GiB)
>> sd 8:0:0:0: [sdc] Write Protect is off
>> sd 8:0:0:0: [sdc] Mode Sense: 03 00 00 00
>> sd 8:0:0:0: [sdc] Assuming drive cache: write through
>> sd 8:0:0:0: [sdc] Assuming drive cache: write through
>>   sdc: sdc1
>> sd 8:0:0:0: [sdc] Assuming drive cache: write through
>> sd 8:0:0:0: [sdc] Attached SCSI disk
>> EXT4-fs (sdc1): mounted filesystem with ordered data mode. Opts:
>> ...
>> ganz viel davon
>> ...
>> EXT4-fs (sdc1): mounted filesystem with ordered data mode. Opts:
>> usb 2-1.5: USB disconnect, device number 5
>> usb 2-1.5: new high speed USB device number 6 using ehci_hcd
>> usb 2-1.5: New USB device found, idVendor=1759, idProduct=5000
>> usb 2-1.5: New USB device strings: Mfr=1, Product=2, SerialNumber=3
>> usb 2-1.5: Product: MassStorage Device
>> usb 2-1.5: Manufacturer: USB 3.0
>> usb 2-1.5: SerialNumber:      WD-WX71A8295652
>> usb 2-1.5: configuration #1 chosen from 1 choice
>> scsi9 : SCSI emulation for USB Mass Storage devices
>> usb-storage: device found at 6
>> usb-storage: waiting for device to settle before scanning
>> usb-storage: device scan complete
>> scsi 9:0:0:0: Direct-Access     USB 3.0  LucidPort USB300 0100 PQ: 0
>> ANSI: 4
>> sd 9:0:0:0: Attached scsi generic sg3 type 0
>> sd 9:0:0:0: [sdc] 625142448 512-byte logical blocks: (320 GB/298 GiB)
>> sd 9:0:0:0: [sdc] Write Protect is off
>> sd 9:0:0:0: [sdc] Mode Sense: 03 00 00 00
>> sd 9:0:0:0: [sdc] Assuming drive cache: write through
>> sd 9:0:0:0: [sdc] Assuming drive cache: write through
>>   sdc: sdc1
>> sd 9:0:0:0: [sdc] Assuming drive cache: write through
>> sd 9:0:0:0: [sdc] Attached SCSI disk
>> EXT4-fs (sdc1): recovery complete
>> EXT4-fs (sdc1): mounted filesystem with ordered data mode. Opts:
>> EXT4-fs (sdc1): mounted filesystem with ordered data mode. Opts:
>> EXT4-fs (sdc1): mounted filesystem with ordered data mode. Opts:
>> EXT4-fs (sdc1): mounted filesystem with ordered data mode. Opts:
>> hub 2-1:1.0: cannot reset port 5 (err = -110)
>> hub 2-1:1.0: cannot reset port 5 (err = -110)
>> hub 2-1:1.0: cannot reset port 5 (err = -110)
>> hub 2-1:1.0: cannot reset port 5 (err = -110)
>> hub 2-1:1.0: cannot reset port 5 (err = -110)
>> hub 2-1:1.0: Cannot enable port 5.  Maybe the USB cable is bad?
>> hub 2-1:1.0: cannot disable port 5 (err = -110)
>> hub 2-1:1.0: cannot reset port 5 (err = -110)
>> usb 2-1.5: reset high speed USB device number 6 using ehci_hcd
>> ehci_hcd 0000:00:1d.0: fatal error
>> ehci_hcd 0000:00:1d.0: HC died; cleaning up
>> ehci_hcd 0000:00:1d.0: force halt; handhake ffffc9000306e024 00004000
>> 00004000 -> -110
>> ehci_hcd 0000:00:1d.0: HC died; cleaning up
>> usb 2-1: USB disconnect, device number 2
>> usb 2-1.2: USB disconnect, device number 3
>> usb 2-1.5: device descriptor read/all, error -19
>> hub 2-1:1.0: cannot disable port 5 (err = -19)
>> hub 2-1:1.0: cannot disable port 5 (err = -19)
>> sd 9:0:0:0: Device offlined - not ready after error recovery
>> sd 9:0:0:0: [sdc]  Result: hostbyte=DID_ABORT driverbyte=DRIVER_OK
>> sd 9:0:0:0: [sdc] CDB: Write(10): 2a 00 12 9e 3d 48 00 00 08 00
>> end_request: I/O error, dev sdc, sector 312360264
>> Buffer I/O error on device sdc1, logical block 39044777
>> lost page write due to I/O error on sdc1
>> sd 9:0:0:0: rejecting I/O to offline device
>> sd 9:0:0:0: [sdc] killing request
>> sd 9:0:0:0: rejecting I/O to offline device
>> ...
>> ganz viel davon
>> ...
>> sd 9:0:0:0: rejecting I/O to offline device
>> JBD2: Detected IO errors while flushing file data on sdc1-8
>> sd 9:0:0:0: rejecting I/O to offline device
>> sd 9:0:0:0: rejecting I/O to offline device
>> sd 9:0:0:0: rejecting I/O to offline device
>> sd 9:0:0:0: rejecting I/O to offline device
>> sd 9:0:0:0: rejecting I/O to offline device
>> sd 9:0:0:0: rejecting I/O to offline device
>> sd 9:0:0:0: rejecting I/O to offline device
>> sd 9:0:0:0: rejecting I/O to offline device
>> sd 9:0:0:0: rejecting I/O to offline device
>> sd 9:0:0:0: rejecting I/O to offline device
>> sd 9:0:0:0: rejecting I/O to offline device
>> sd 9:0:0:0: [sdc]  Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
>> sd 9:0:0:0: [sdc] CDB: Write(10): 2a 00 12 85 54 20 00 00 10 00
>> end_request: I/O error, dev sdc, sector 310727712
>> sd 9:0:0:0: rejecting I/O to offline device
>> ...
>> ganz viel davon
>> ...
>> sd 9:0:0:0: rejecting I/O to offline device
>> EXT4-fs (sdc1): delayed block allocation failed for inode 12 at logical
>> offset 36534272 with max blocks 2048 with error -5
>>
>> This should not happen!!  Data will be lost
>> sd 9:0:0:0: rejecting I/O to offline device
>> ...
>> extrem viel davon
>> ...
>> sd 9:0:0:0: rejecting I/O to offline device
>> Aborting journal on device sdc1-8.
>> sd 9:0:0:0: rejecting I/O to offline device
>> JBD2: I/O error detected when updating journal superblock for sdc1-8.
>> JBD2: Detected IO errors while flushing file data on sdc1-8
>> usb 2-1.5: USB disconnect, device number 6
>> EXT4-fs error (device sdc1): ext4_journal_start_sb: Detected aborted
>> journal
>> EXT4-fs (sdc1): Remounting filesystem read-only
>> EXT4-fs (sdc1): ext4_da_writepages: jbd2_start: 8192 pages, ino 12; err -30
>>
>> EXT4-fs error (device sdc1): ext4_read_block_bitmap: Cannot read block
>> bitmap - block_group = 2260, block_bitmap = 73924612
>> EXT4-fs error (device sdc1): ext4_discard_preallocations: Error reading
>> block bitmap for 2260
>> Buffer I/O error on device sdc1, logical block 0
>> lost page write due to I/O error on sdc1
>> EXT4-fs error (device sdc1): ext4_put_super: Couldn't clean up the journal
>>
>> kann mir da jemand auf die Sprünge helfen?
>>
>> Der Server läuft an sich durch, nur wenn die Platten wieder nicht
>> erkannt werden muss ich neu starten.
>>
>> Danke
>>
>> Jürgen
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2
>
> iQIcBAEBCgAGBQJUWjt1AAoJEPVbJZyTN5bNgr0P/3kpb7k0dNyIhMtaiwR9nf/X
> XFKmnqW0fdLkUmVxgJ5KgMtGLXrMdyoR3PPwUXEchEW8XwsOjOZMuTC/nPqZmzs3
> cg6hUAV/hxXKYwXt6DNwLh7L3T2gZyCeZhPdF4puSaec8MgphLvFEjL3Fw/V8GSe
> ufUUKT6/asScXdGiF5XYSjtRMbbBtFq46u0a+CykVMuTFOF18mKlCsCaZy9lA8nV
> fJrCBqb3uqZ8sIIGDUMlHpI98xKsymIr/rjLNip4ii8O6sxez9DU0Ai39lgdfhQ9
> uVDpPh6EBIgWy5G7W1aUHPyDEF6EwLEzRbw83R1vSWegl4OB+W1eKTefBcrfdPLv
> q0KydeVGgsORFUJXTRPYYo4G9pCUv8tEEdrUe+AjNV1WXryLQN61GbHtQQ6ATg0a
> 6AH+ISNHVX8Uk95g7tOqjjsfAq0KPxDC8Ova2tdoS5m6MIxdv7wFvt6eCo+qm0Qy
> rvYK3ZtPD4QNWiVjQyBp2EwUMNFCNlvhgDVIlt9xrs8nX+pqrfFW11ySG1q4p6w/
> wCxnzUv5d0wxOFDLNkj+4WvLDu6mzuCaC6ukxtIxnJUJMWmPUI74pjwyxDtjnteh
> 2kxKw8rhrRTj85TaATW7OXJYmFM1A8J+oPHgYLv2U0kdAmKfz4eYagPaDrI+LGA6
> bUfo5hjwK5EfLEkeIWfU
> =GkcB
> -----END PGP SIGNATURE-----

Hi,

also ich kann den USB Subsystem neu starten, dann ist meine Platte 
wieder verfügbar.

Beispiel:

|cd /sys/bus/pci/drivers/ehci_hcd
ls

0000:00:12.2  0000:00:13.2  bind  module  new_id  remove_id uevent  unbind

||echo -n "0000:00:12.2" > unbind|
|echo -n "0000:00:13.2" > unbind|
|echo -n "0000:00:12.2" > bind|
|echo -n "0000:00:13.2" > bind|

dann läuft das Teil wieder, evtl. hat nur das USB-Gehäuse ein Problem 
mit dem Treiber und vice versa?!?

Grüsse

Jürgen
-------------- nächster Teil --------------
Ein Dateianhang mit HTML-Daten wurde abgetrennt...
URL: <http://lists.centos.org/pipermail/centos-de/attachments/20141111/9a2a379c/attachment.html>