[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Recuperar un disck



hola,

el primer que es fa en aquests casos es fer una imatge del disc defectuós i després treballar sobre la imatge, no sobre el disc original. és a dir: fer un "dd" i després utilitzar eines com el testdik sobre el fitxer que ha generat el dd.

"ddrescue" va molt bé per llegir sectors defectuosos i generar una imatge del disc. el paquet debian es diu "gddrescue". seria algo així:

 ddrescue /dev/sdb imatge-de-sdb.dd

on /dev/sdb es el dispositiu del disc vell.

d.


On 07/19/2013 05:25 PM, Griera wrote:
Hola:

Has prova amb "testdisk" que està a debian? És molt lent, però a mi m'ha recuperat el disc dur en dos ocasions.

Salut!


On Fri, 19 Jul 2013 10:34:29 +0000
Pere Nubiola Radigales<pere@nubiola.cat>  wrote:

Fa uns dies s'em va espatllar el disc. Donat que el ordinador era una mica
vell en vaig compraun de nou , al que vaig installar el el disc vell per
intentar recuperar dades.
Quant uintento montar el disc vell em dona els eguent dmesg

[22611.547157] ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[22611.547162] ata4.00: BMDMA stat 0x24
[22611.547166] ata4.00: failed command: READ DMA EXT
[22611.547172] ata4.00: cmd 25/00:08:8a:8a:b1/00:00:3a:00:00/e0 tag 0 dma
4096 in
[22611.547172]          res 71/04:04:9d:00:32/04:00:00:00:00/e0 Emask 0x1
(device error)
[22611.547175] ata4.00: status: { DRDY DF ERR }
[22611.547177] ata4.00: error: { ABRT }
[22611.600951] ata4.00: both IDENTIFYs aborted, assuming NODEV
[22611.600956] ata4.00: revalidation failed (errno=-2)
[22611.600966] ata4: soft resetting link
[22611.772763] ata4.00: both IDENTIFYs aborted, assuming NODEV
[22611.772776] ata4.00: revalidation failed (errno=-2)
[22616.751914] ata4: soft resetting link
[22616.939780] ata4.00: both IDENTIFYs aborted, assuming NODEV
[22616.939793] ata4.00: revalidation failed (errno=-2)
[22616.939797] ata4.00: disabled
[22616.939814] ata4: EH complete
[22616.939836] sd 3:0:0:0: [sdb] Unhandled error code
[22616.939839] sd 3:0:0:0: [sdb]
[22616.939841] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[22616.939843] sd 3:0:0:0: [sdb] CDB:
[22616.939845] Read(10): 28 00 3a b1 8a 8a 00 00 08 00
[22616.939854] end_request: I/O error, dev sdb, sector 984713866
[22616.939870] sd 3:0:0:0: [sdb] Unhandled error code
[22616.939872] sd 3:0:0:0: [sdb]
[22616.939874] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[22616.939876] sd 3:0:0:0: [sdb] CDB:
[22616.939877] Read(10): 28 00 3a b1 8a 92 00 00 f0 00
[22616.939884] end_request: I/O error, dev sdb, sector 984713874
[22616.939887] JBD: Failed to read block at offset 93
[22616.939929] JBD: recovery failed
[22616.939931] EXT3-fs (sdb3): error loading journal

La commanda smartctl --all -T verypermissive /dev/sdb em torna

smartctl 6.2 2013-04-20 r3812 [x86_64-linux-3.9-1-amd64] (local build)
Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Vendor:               /3:0:0:0
Product:
User Capacity:        600,332,565,813,390,450 bytes [600 PB]
Logical block size:   774843950 bytes
scsiModePageOffset: response length too short, resp_len=47 offset=50
bd_len=46
scsiModePageOffset: response length too short, resp_len=47 offset=50
bd_len=46
Terminate command early due to bad response to IEC mode page
=== START OF READ SMART DATA SECTION ===
Log Sense failed, IE page [scsi response fails sanity test]
Error Counter logging not supported

scsiModePageOffset: response length too short, resp_len=47 offset=50
bd_len=46
Device does not support Self Test logging


He trobat aixo:
https://groups.google.com/forum/#!msg/de.comp.os.unix.linux.hardware/okXwhnwvxQs/gQafyYebquQJ

Pero está en Aleman. veig que fa un dd peró no veig d'on obté les dades

Algú em pot ajudar




Pere Nubiola Radigales
Telf: +34 656316974
e-mail: pere@nubiola.cat
            pnubiola@fsfe.org
            pere.nubiola@gmail.com



Reply to: