Re: Recuperar un disck

2013-07-20 Conversa David Escala 

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 +
Pere Nubiola Radigalesp...@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: p...@nubiola.cat
pnubi...@fsfe.org
pere.nubi...@gmail.com





--
To UNSUBSCRIBE, email to debian-user-catalan-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/51ea2f37.2010...@gmail.com

Re: Recuperar un disck

2013-07-20 Conversa Alex Muntada 
Després de fer la imatge amb el gddrescue pots provar a recuperar-ne les
dades amb el foremost.

És útil sobretot per recuperar fotos, documents, vídeos i altres tipus de
fitxers que tinguin patrons fàcils de detectar llegint les dades bloc a
bloc.

Salut i sort,
Alex

Re: Recuperar un disck

2013-07-20 Conversa hubble 
El Fri, 19 Jul 2013 10:34:29 +
Pere Nubiola Radigales p...@nubiola.cat va dir:

 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: p...@nubiola.cat
pnubi...@fsfe.org
pere.nubi...@gmail.com

Hola pere, ja saps que vaig contestar-te al teu correu personal i a lo que jo 
pensava que era la llista. desprès d'un dia sense que apareixes el missatge 
l'he buscat i he trobat que em vaig equivocar i el vaig enviar a la llista de 
debian sí, però a la llista de debian-user-spanish.
En comptes de rebre un flame com d'altres vegades, t'han contestat amb un 
consell, de part de camaleon, una usuària de la llista que fa una feina molt 
gran, i que aprofito i te la faig arribar. No crec que sigui la sol·lució, però 
es una resposta:

-

@Pere: Jo provaria amb l'aplicació de verificació d'errors del propi 
fabricant del disc dur, si el disc s'ha malograt malamanet i té sectors 
defectuosos és possible que puga recuperar·los, es a dir, que els marque 
com no legibles per a que al menys puga muntar el disc i extraure les 
dades.

Salut,

-- 
Camaleón

--

el missatge: 
https://lists.debian.org/debian-user-spanish/2013/07/msg00746.html


apa, sort!


-- 
To UNSUBSCRIBE, email to debian-user-catalan-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/20130720211005.e8f0eac760ca021d5c7c1...@telefonica.net

Recuperar un disck

2013-07-19 Conversa Pere Nubiola Radigales 
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: p...@nubiola.cat
   pnubi...@fsfe.org
   pere.nubi...@gmail.com

Re: Recuperar un disck

2013-07-19 Conversa Griera 
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 +
Pere Nubiola Radigales p...@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: p...@nubiola.cat
pnubi...@fsfe.org
pere.nubi...@gmail.com


--
To UNSUBSCRIBE, email to debian-user-catalan-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/20130719172553.2f908...@epigpbn01.ad-hugtip.local

Re: Recuperar un disck

2013-07-19 Conversa Jordi Mallach 
El dv 19 de 07 de 2013 a les 10:34 +, en/na Pere Nubiola Radigales
va escriure:
 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

Té molt mala pinta. Com anem de backups?

 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

Doncs el paio veu que smartctl diu que al block 175035952 hi ha
problemes. Segons google translate:

és a dir l'auto-prova ha trobat un error en un bloc,
que ni tan sols existeix. I el bloc defectuós 175035952 té
el Selbssttest no ser criticat.

Què tampoc és que entenguem massa, però almenys sabem que el bloc està
xungo.

Amb el dd el que fa és intentar posar-ho a zero per veure si això fa
revifar el disc, imagine. No sembla funcionar.

Bona sort amb el disc, tot i que jo no tinc gaires esperances.

Jordi

-- 
Jordi Mallach Pérez  --  Debian developer http://www.debian.org/
jo...@sindominio.net jo...@debian.org http://www.sindominio.net/
GnuPG public key information available at http://oskuro.net/


-- 
To UNSUBSCRIBE, email to debian-user-catalan-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/1374245904.7402.16.ca...@penyagolosa.oskuro.net