Re: Fallo de disco
Buenas,
Ya ha termindao el ddrescue:
# ddrescue -f -n -v /dev/sdb1 /mnt/2TBUSB/sdb1.img /root/recovery.log
GNU ddrescue 1.21
About to copy 1000 GBytes from /dev/sdb1 to /mnt/2TBUSB/sdb1.img.
Starting positions: infile = 0 B, outfile = 0 B
Copy block size: 128 sectors Initial skip size: 128 sectors
Sector size: 512 Bytes
Press Ctrl-C to interrupt
ipos: 852551 MB, non-trimmed: 0 B, current rate: 57344 B/s
opos: 852551 MB, non-scraped: 3072 B, average rate: 28167 kB/s
non-tried: 0 B, errsize: 1024 B, run time: 9h 51m 49s
rescued: 1000 GB, errors: 2, remaining time: 1s
percent rescued: 99.99% time since last successful read: 0s
Finished
En principio no ha encontrado ningun error, pero desde que he puesto
el "ddrescue" han saltado estos mensajes en el dmesg:
https://paste.debian.net/1005046/
Mañana cuando cambie el disco, ejecutare el proceso inverso: dd
if=/mnt/2TBUSB/sdb1.img of=/dev/sdb
¿Tengo que añadir algo mas? ¿Alguna recomendación para el volcado?
Gracias por todo.
Un saludo.
El día 13 de enero de 2018, 10:47, Josu Lazkano
<josu.lazkano@gmail.com> escribió:
> Gracias a todos,
>
> El servidor esta en remoto y ahora mismo no puedo ir fisicamente a
> pincha otro disco, pero tengo un disco de 2TB por USB conectado con
> espacio suficiente.
>
> He ejecutado esto dentro de una consola virtual (screen):
>
> # ddrescue -f -n -v /dev/sdb1 /mnt/2TBUSB/sdb1.img /root/recovery.log
> GNU ddrescue 1.21
> About to copy 1000 GBytes from /dev/sdb1 to /mnt/2TBUSB/sdb1.img.
> Starting positions: infile = 0 B, outfile = 0 B
> Copy block size: 128 sectors Initial skip size: 128 sectors
> Sector size: 512 Bytes
>
> Press Ctrl-C to interrupt
> ipos: 1149 MB, non-trimmed: 0 B, current rate: 27656 kB/s
> opos: 1149 MB, non-scraped: 0 B, average rate: 39622 kB/s
> non-tried: 999054 MB, errsize: 0 B, run time: 29s
> rescued: 1149 MB, errors: 0, remaining time: 7h
> percent rescued: 0.11% time since last successful read: 0s
> Copying non-tried blocks... Pass 1 (forwards)
>
> Me he guiado de esta guia:
> https://datarecovery.com/rd/how-to-clone-hard-disks-with-ddrescue/
>
> Si me da algun fallo tendre que añadir mas parametros como "-r3". Ojala no.
>
> Quedan 7 horas a que termine, así que toca esperar.
>
> Gracias de nuevo, os mantengo informado.
>
> Un saludo.
>
> El día 12 de enero de 2018, 18:07, asanchezm@e-compugraf.com
> <asanchezm@e-compugraf.com> escribió:
>>
>>
>> El 12/01/18 a las 08:58, Josu Lazkano escribió:
>>> Buenas,
>>>
>>> Tengo un servidor Debian Stretch con varios discos, y uno de ellos
>>> esta dando este error en el "dmesg":
>>>
>>> [97558.405283] ata2.00: configured for UDMA/133
>>> [97558.405307] sd 1:0:0:0: [sdb] tag#1 FAILED Result: hostbyte=DID_OK
>>> driverbyte=DRIVER_SENSE
>>> [97558.405310] sd 1:0:0:0: [sdb] tag#1 Sense Key : Medium Error [current]
>>> [97558.405314] sd 1:0:0:0: [sdb] tag#1 Add. Sense: Unrecovered read
>>> error - auto reallocate failed
>>> [97558.405318] sd 1:0:0:0: [sdb] tag#1 CDB: Read(10) 28 00 63 40 0d 08
>>> 00 00 08 00
>>> [97558.405320] blk_update_request: I/O error, dev sdb, sector 1665142027
>>> [97558.408269] EXT4-fs error (device sdb1): __ext4_get_inode_loc:4355:
>>> inode #52037649: block 208142497: comm rsync: unable to read itable
>>> block
>>> [97558.408271] ata2: EH complete
>>> [97559.398608] ata2.00: exception Emask 0x0 SAct 0x100 SErr 0x0 action 0x0
>>> [97559.402026] ata2.00: irq_stat 0x40000008
>>> [97559.405410] ata2.00: failed command: READ FPDMA QUEUED
>>> [97559.408805] ata2.00: cmd 60/08:40:08:0d:40/00:00:63:00:00/40 tag 8
>>> ncq dma 4096 in
>>> res 41/40:08:0b:0d:40/00:00:63:00:00/00 Emask
>>> 0x409 (media error) <F>
>>> [97559.415557] ata2.00: status: { DRDY ERR }
>>> [97559.418935] ata2.00: error: { UNC }
>>>
>>> Se repite muchas veces: https://paste.debian.net/1004844/
>>>
>>> Veo que es en el disco sdb1.
>>>
>>> # fdisk -l /dev/sdb
>>> Disco /dev/sdb: 931,5 GiB, 1000204886016 bytes, 1953525168 sectores
>>> Unidades: sectores de 1 * 512 = 512 bytes
>>> Tamaño de sector (lógico/físico): 512 bytes / 512 bytes
>>> Tamaño de E/S (mínimo/óptimo): 512 bytes / 512 bytes
>>> Tipo de etiqueta de disco: dos
>>> Identificador del disco: 0x2fc1b76a
>>>
>>> Disposit. Inicio Comienzo Final Sectores Tamaño Id Tipo
>>> /dev/sdb1 2048 1953525167 1953523120 931,5G 83 Linux
>>>
>>> ¿Que puedo hacer?
>>>
>>> Veo en los logs que el error es siempre en el mismo "block" y diferente "inode":
>>>
>>> # dmesg | grep inode
>>> [ 316.370044] EXT4-fs (sdb1): initial error at time 1515460519:
>>> __ext4_get_inode_loc:4355: inode 52037653: block 208142497
>>> [ 316.370052] EXT4-fs (sdb1): last error at time 1515460545:
>>> __ext4_get_inode_loc:4355: inode 52038675: block 208142561
>>> [ 6851.109227] EXT4-fs error (device sdb1): __ext4_get_inode_loc:4355:
>>> inode #52037653: block 208142497: comm rsync: unable to read itable
>>> block
>>> [ 6852.146499] EXT4-fs error (device sdb1): __ext4_get_inode_loc:4355:
>>> inode #52037654: block 208142497: comm rsync: unable to read itable
>>> block
>>> [ 6853.128782] EXT4-fs error (device sdb1): __ext4_get_inode_loc:4355:
>>> inode #52037650: block 208142497: comm rsync: unable to read itable
>>> block
>>> [ 6853.961676] EXT4-fs error (device sdb1): __ext4_get_inode_loc:4355:
>>> inode #52037649: block 208142497: comm rsync: unable to read itable
>>> block
>>> [ 6854.919324] EXT4-fs error (device sdb1): __ext4_get_inode_loc:4355:
>>> inode #52037652: block 208142497: comm rsync: unable to read itable
>>> block
>>> [ 6855.979335] EXT4-fs error (device sdb1): __ext4_get_inode_loc:4355:
>>> inode #52037651: block 208142497: comm rsync: unable to read itable
>>> block
>>> [ 6856.874282] EXT4-fs error (device sdb1): __ext4_get_inode_loc:4355:
>>> inode #52037655: block 208142497: comm rsync: unable to read itable
>>> block
>>> [ 6858.007035] EXT4-fs error (device sdb1): __ext4_get_inode_loc:4355:
>>> inode #52037656: block 208142497: comm rsync: unable to read itable
>>> block
>>> [ 6859.064576] EXT4-fs error (device sdb1): __ext4_get_inode_loc:4355:
>>> inode #52037661: block 208142497: comm rsync: unable to read itable
>>> block
>>> [ 6860.037469] EXT4-fs error (device sdb1): __ext4_get_inode_loc:4355:
>>> inode #52037659: block 208142497: comm rsync: unable to read itable
>>> block
>>>
>>> ¿Podría identificar el bloque y saber que tengo guardado?
>>>
>>> Agradezco cualquier ayuda.
>>>
>>> Un saludo.
>>>
>> Ya te comentaron varias soluciones, en resumen, ve compra otro HD
>> clonalo deja el nuevo y listo, no te quiebres la cabeza.
>>
>
>
>
> --
> Josu Lazkano
--
Josu Lazkano
Reply to: