[ImoLUG] Lo butto ?

Paride Balestri paridebalestri@gmail.com
Gio 24 Nov 2016 05:57:14 CET


Prova cambiando adattatore usb/sata. Io ne avevo uno che faceva così è
stavo x buttare i dischi sarà del server esxi...
Se puoi attaccalo direttamente ad una porta sarà su un PC e prova. Se anche
li fa uguale allora è colpa del disco.

-bale

Il 24/nov/2016 00:27, "Stefano Ballardini" <stefano.ballardini@gmail.com>
ha scritto:

> Ciao a tutti,
> per farla breve, attacco il disco esterno via usb al pc, comincio a
> copiare files grossi, uso mc, dopo poco tempo la copia si blocca, un
> po' di dmesg:
>
> 25001.120393] usb 3-2: USB disconnect, device number 7
> [25001.120398] sd 11:0:0:0: Device offlined - not ready after error
> recovery
> [25001.120408] sd 11:0:0:0: [sdb] Unhandled error code
> [25001.120410] sd 11:0:0:0: [sdb]
> [25001.120412] Result: hostbyte=DID_ABORT driverbyte=DRIVER_OK
> [25001.120415] sd 11:0:0:0: [sdb] CDB:
> [25001.120416] Write(10): 2a 00 00 04 8e 90 00 00 f0 00
> [25001.120424] end_request: I/O error, dev sdb, sector 298640
> [25001.120430] EXT4-fs warning (device sdb1): ext4_end_bio:317: I/O
> error -5 writing to inode 86769666 (offset 8388608 size 8388608
> starting block 37360)
> [25001.120433] buffer_io_error: 6318 callbacks suppressed
> [25001.120435] Buffer I/O error on device sdb1, logical block 37074
> [25001.120441] Buffer I/O error on device sdb1, logical block 37075
> [25001.120443] Buffer I/O error on device sdb1, logical block 37076
> [25001.120446] Buffer I/O error on device sdb1, logical block 37077
> [25001.120448] Buffer I/O error on device sdb1, logical block 37078
> [25001.120451] Buffer I/O error on device sdb1, logical block 37079
> [25001.120453] Buffer I/O error on device sdb1, logical block 37080
> [25001.120455] Buffer I/O error on device sdb1, logical block 37081
> [25001.120457] Buffer I/O error on device sdb1, logical block 37082
> [25001.120460] Buffer I/O error on device sdb1, logical block 37083
> [25001.120504] EXT4-fs warning (device sdb1): ext4_end_bio:317: I/O
> error -5 writing to inode 86769666 (offset 8388608 size 8388608
> starting block 37420)
> [25001.120533] EXT4-fs warning (device sdb1): ext4_end_bio:317: I/O
> error -5 writing to inode 86769666 (offset 8388608 size 8388608
> starting block 37450)
> [25001.120561] EXT4-fs warning (device sdb1): ext4_end_bio:317: I/O
> error -5 writing to inode 86769666 (offset 8388608 size 8388608
> starting block 37480)
> [25001.120593] EXT4-fs warning (device sdb1): ext4_end_bio:317: I/O
> error -5 writing to inode 86769666 (offset 8388608 size 8388608
> starting block 37510)
> [25001.120619] EXT4-fs warning (device sdb1): ext4_end_bio:317: I/O
> error -5 writing to inode 86769666 (offset 8388608 size 8388608
> starting block 37540)
> [25001.120643] EXT4-fs warning (device sdb1): ext4_end_bio:317: I/O
> error -5 writing to inode 86769666 (offset 8388608 size 8388608
> starting block 37570)
> [25001.120669] EXT4-fs warning (device sdb1): ext4_end_bio:317: I/O
> error -5 writing to inode 86769666 (offset 8388608 size 8388608
> starting block 37600)
> [25001.120694] EXT4-fs warning (device sdb1): ext4_end_bio:317: I/O
> error -5 writing to inode 86769666 (offset 8388608 size 8388608
> starting block 37630)
> [25001.120719] EXT4-fs warning (device sdb1): ext4_end_bio:317: I/O
> error -5 writing to inode 86769666 (offset 8388608 size 8388608
> starting block 37660)
> [25001.123569] sd 11:0:0:0: [sdb] Unhandled error code
> [25001.123572] sd 11:0:0:0: [sdb]
> [25001.123575] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
> [25001.123577] sd 11:0:0:0: [sdb] CDB:
> [25001.123578] Write(10): 2a 00 00 04 8f 80 00 00 f0 00
> [25001.123585] end_request: I/O error, dev sdb, sector 298880
> [25001.127289] Aborting journal on device sdb1-8.
> [25001.127304] JBD2: Error -5 detected when updating journal
> superblock for sdb1-8.
> [25001.128217] EXT4-fs (sdb1): Delayed block allocation failed for
> inode 86769666 at logical offset 8192 with max blocks 2048 with error
> 30
> [25001.128221] EXT4-fs (sdb1): This should not happen!! Data will be lost
>
> [25001.128227] EXT4-fs error (device sdb1) in ext4_writepages:2608:
> Journal has aborted
> [25001.136064] EXT4-fs error (device sdb1):
> ext4_journal_check_start:56: Detected aborted journal
> [25001.136070] EXT4-fs (sdb1): Remounting filesystem read-only
> [25001.136074] EXT4-fs (sdb1): previous I/O error to superblock detected
> [25059.338556] EXT4-fs warning: 190 callbacks suppressed
> [25059.338568] EXT4-fs warning (device sdb1):
> __ext4_read_dirblock:902: error reading directory block (ino 2, block
> 0)
>
>
> Lo posso torturare ?
> O lo butto direttamente?
>
>
> pippersss
> _______________________________________________
> ImoLUG mailing list
> www.imolug.org
> imolug@lists.linux.it
> http://lists.linux.it/listinfo/imolug
> Regolamento ML - http://www.imolug.org/faq/Regolamento_MailingList
> Server e connettivit offerti da Ehiweb - www.ehiweb.it
>
> Facebook: https://www.facebook.com/ImoLUG
-------------- parte successiva --------------
Un allegato HTML è stato rimosso...
URL: <http://lists.linux.it/pipermail/imolug/attachments/20161124/194516b2/attachment.html>


Maggiori informazioni sulla lista ImoLUG