Nowe posty

Autor Wątek: problem z obrazem partycji za pomocą dd  (Przeczytany 3750 razy)

freerider

  • Gość
problem z obrazem partycji za pomocą dd
« dnia: 2011-02-26, 18:30:55 »
Witam.
Mam następujący problem ze zrobieniem obrazu partycji za pomocą dd.

po wykonaniu dd if=/dev/sda2 of=/home/freerider/obraz.img zwraca następujący błąd:

Cytuj
root@niewinny:~# dd if=/dev/sda2 of=/home/freerider/obraz.img
dd: czytanie `/dev/sda2': Błąd wejścia/wyjścia
6302728+0 przeczytanych recordów
6302728+0 zapisanych recordów
skopiowane 3226996736 bajtów (3,2 GB), 207,391 s, 15,6 MB/s
jakim narzędziem bym nie próbował dd czy gzipem
gzip -c /dev/sda2 > /home/freerider/obraz.gz
zawsze 3,2 GB i przerywa

partycja źródłowa 50GB miejsca na docelowej na obraz ponad 100GB (ReiserFS) więc nie jest to wina braku miejsca.

Dodam że problem występuje zarówno na 32 jak i 64 bitowym systemie.

Partycję źródłową formatowałem z różnym systemem plików (ext3,reiserfs,ntfs) i zawsze jest to samo.

Ma ktoś jakiś pomysł ?

arctgx

  • Gość
problem z obrazem partycji za pomocą dd
« Odpowiedź #1 dnia: 2011-02-26, 19:04:47 »
Dmesg lub inne narzędzia (smart*) nie sugerują uszkodzenia samego dysku?

freerider

  • Gość
problem z obrazem partycji za pomocą dd
« Odpowiedź #2 dnia: 2011-02-26, 20:13:01 »
Logi:

syslog:
Cytuj
Feb 26 20:00:48 niewinny kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Feb 26 20:00:48 niewinny kernel: ata1.00: BMDMA stat 0x24
Feb 26 20:00:48 niewinny kernel: ata1.00: failed command: READ DMA
Feb 26 20:00:48 niewinny kernel: ata1.00: cmd c8/00:00:1f:60:e0/00:00:00:00:00/ec tag 0 dma 131072 in
Feb 26 20:00:48 niewinny kernel:          res 51/40:00:4b:60:e0/00:00:00:00:00/0c Emask 0x9 (media error)
Feb 26 20:00:48 niewinny kernel: ata1.00: status: { DRDY ERR }
Feb 26 20:00:48 niewinny kernel: ata1.00: error: { UNC }
Feb 26 20:00:51 niewinny kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Feb 26 20:00:51 niewinny kernel: ata1.00: BMDMA stat 0x24
Feb 26 20:00:51 niewinny kernel: ata1.00: failed command: READ DMA
Feb 26 20:00:51 niewinny kernel: ata1.00: cmd c8/00:00:1f:60:e0/00:00:00:00:00/ec tag 0 dma 131072 in
Feb 26 20:00:51 niewinny kernel:          res 51/40:00:4b:60:e0/00:00:00:00:00/0c Emask 0x9 (media error)
Feb 26 20:00:51 niewinny kernel: ata1.00: status: { DRDY ERR }
Feb 26 20:00:51 niewinny kernel: ata1.00: error: { UNC }
Feb 26 20:00:54 niewinny kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Feb 26 20:00:54 niewinny kernel: ata1.00: BMDMA stat 0x24
Feb 26 20:00:54 niewinny kernel: ata1.00: failed command: READ DMA
Feb 26 20:00:54 niewinny kernel: ata1.00: cmd c8/00:00:1f:60:e0/00:00:00:00:00/ec tag 0 dma 131072 in
Feb 26 20:00:54 niewinny kernel:          res 51/40:00:4b:60:e0/00:00:00:00:00/0c Emask 0x9 (media error)
Feb 26 20:00:54 niewinny kernel: ata1.00: status: { DRDY ERR }
Feb 26 20:00:54 niewinny kernel: ata1.00: error: { UNC }
Feb 26 20:00:56 niewinny kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Feb 26 20:00:56 niewinny kernel: ata1.00: BMDMA stat 0x24
Feb 26 20:00:56 niewinny kernel: ata1.00: failed command: READ DMA
Feb 26 20:00:56 niewinny kernel: ata1.00: cmd c8/00:00:1f:60:e0/00:00:00:00:00/ec tag 0 dma 131072 in
Feb 26 20:00:56 niewinny kernel:          res 51/40:00:4b:60:e0/00:00:00:00:00/0c Emask 0x9 (media error)
Feb 26 20:00:56 niewinny kernel: ata1.00: status: { DRDY ERR }
Feb 26 20:00:56 niewinny kernel: ata1.00: error: { UNC }
Feb 26 20:00:59 niewinny kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Feb 26 20:00:59 niewinny kernel: ata1.00: BMDMA stat 0x24
Feb 26 20:00:59 niewinny kernel: ata1.00: failed command: READ DMA
Feb 26 20:00:59 niewinny kernel: ata1.00: cmd c8/00:00:1f:60:e0/00:00:00:00:00/ec tag 0 dma 131072 in
Feb 26 20:00:59 niewinny kernel:          res 51/40:00:4b:60:e0/00:00:00:00:00/0c Emask 0x9 (media error)
Feb 26 20:00:59 niewinny kernel: ata1.00: status: { DRDY ERR }
Feb 26 20:00:59 niewinny kernel: ata1.00: error: { UNC }
Feb 26 20:01:02 niewinny kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Feb 26 20:01:02 niewinny kernel: ata1.00: BMDMA stat 0x24
Feb 26 20:01:02 niewinny kernel: ata1.00: failed command: READ DMA
Feb 26 20:01:02 niewinny kernel: ata1.00: cmd c8/00:00:1f:60:e0/00:00:00:00:00/ec tag 0 dma 131072 in
Feb 26 20:01:02 niewinny kernel:          res 51/40:00:4b:60:e0/00:00:00:00:00/0c Emask 0x9 (media error)
Feb 26 20:01:02 niewinny kernel: ata1.00: status: { DRDY ERR }
Feb 26 20:01:02 niewinny kernel: ata1.00: error: { UNC }
messages:
Cytuj
Feb 26 20:00:48 niewinny kernel: ata1.00: configured for UDMA/133
Feb 26 20:00:48 niewinny kernel: ata1: EH complete
Feb 26 20:00:51 niewinny kernel: ata1.00: configured for UDMA/133
Feb 26 20:00:51 niewinny kernel: ata1: EH complete
Feb 26 20:00:54 niewinny kernel: ata1.00: configured for UDMA/133
Feb 26 20:00:54 niewinny kernel: ata1: EH complete
Feb 26 20:00:57 niewinny kernel: ata1.00: configured for UDMA/133
Feb 26 20:00:57 niewinny kernel: ata1: EH complete
Feb 26 20:00:59 niewinny kernel: ata1.00: configured for UDMA/133
Feb 26 20:00:59 niewinny kernel: ata1: EH complete
Feb 26 20:01:02 niewinny kernel: ata1.00: configured for UDMA/133
Feb 26 20:01:02 niewinny kernel: sd 2:0:0:0: [sda] Unhandled sense code
Feb 26 20:01:02 niewinny kernel: sd 2:0:0:0: [sda]  Result: hostbyte=0x00 driverbyte=0x08
Feb 26 20:01:02 niewinny kernel: sd 2:0:0:0: [sda]  Sense Key : 0x3 [current] [descriptor]
Feb 26 20:01:02 niewinny kernel:         72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00
Feb 26 20:01:02 niewinny kernel:         0c e0 60 4b
Feb 26 20:01:02 niewinny kernel: sd 2:0:0:0: [sda]  ASC=0x11 ASCQ=0x4
Feb 26 20:01:02 niewinny kernel: sd 2:0:0:0: [sda] CDB: cdb[0]=0x28: 28 00 0c e0 60 1f 00 01 00 00
Feb 26 20:01:02 niewinny kernel: ata1: EH complete
Feb 26 20:01:05 niewinny kernel: ata1.00: configured for UDMA/133
Feb 26 20:01:05 niewinny kernel: ata1: EH complete
Feb 26 20:01:08 niewinny kernel: ata1.00: configured for UDMA/133
Feb 26 20:01:08 niewinny kernel: ata1: EH complete
Feb 26 20:01:11 niewinny kernel: ata1.00: configured for UDMA/133
Feb 26 20:01:11 niewinny kernel: ata1: EH complete
Feb 26 20:01:13 niewinny kernel: ata1.00: configured for UDMA/133
Feb 26 20:01:13 niewinny kernel: ata1: EH complete
Feb 26 20:01:16 niewinny kernel: ata1.00: configured for UDMA/133
Feb 26 20:01:16 niewinny kernel: ata1: EH complete
Feb 26 20:01:19 niewinny kernel: ata1.00: configured for UDMA/133
Feb 26 20:01:19 niewinny kernel: sd 2:0:0:0: [sda] Unhandled sense code
Feb 26 20:01:19 niewinny kernel: sd 2:0:0:0: [sda]  Result: hostbyte=0x00 driverbyte=0x08
Feb 26 20:01:19 niewinny kernel: sd 2:0:0:0: [sda]  Sense Key : 0x3 [current] [descriptor]
Feb 26 20:01:19 niewinny kernel:         72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00
Feb 26 20:01:19 niewinny kernel:         0c e0 60 4b
Feb 26 20:01:19 niewinny kernel: sd 2:0:0:0: [sda]  ASC=0x11 ASCQ=0x4
Feb 26 20:01:19 niewinny kernel: sd 2:0:0:0: [sda] CDB: cdb[0]=0x28: 28 00 0c e0 60 4b 00 00 04 00
Feb 26 20:01:19 niewinny kernel: ata1: EH complete
dmesg:
Cytuj
end_request: I/O error, dev sda, sector 216031307
Buffer I/O error on device sda2, logical block 3151366
Buffer I/O error on device sda2, logical block 3151367
Buffer I/O error on device sda2, logical block 3151368
Buffer I/O error on device sda2, logical block 3151369
Buffer I/O error on device sda2, logical block 3151370
Buffer I/O error on device sda2, logical block 3151371
Buffer I/O error on device sda2, logical block 3151372
Buffer I/O error on device sda2, logical block 3151373
Buffer I/O error on device sda2, logical block 3151374
Buffer I/O error on device sda2, logical block 3151375
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata1.00: BMDMA stat 0x25
ata1.00: failed command: READ DMA
ata1.00: cmd c8/00:04:4b:60:e0/00:00:00:00:00/ec tag 0 dma 2048 in
         res 51/40:00:4b:60:e0/00:00:00:00:00/0c Emask 0x9 (media error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { UNC }
ata1.00: configured for UDMA/133
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata1.00: BMDMA stat 0x25
ata1.00: failed command: READ DMA
ata1.00: cmd c8/00:04:4b:60:e0/00:00:00:00:00/ec tag 0 dma 2048 in
         res 51/40:00:4b:60:e0/00:00:00:00:00/0c Emask 0x9 (media error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { UNC }
ata1.00: configured for UDMA/133
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata1.00: BMDMA stat 0x25
ata1.00: failed command: READ DMA
ata1.00: cmd c8/00:04:4b:60:e0/00:00:00:00:00/ec tag 0 dma 2048 in
         res 51/40:00:4b:60:e0/00:00:00:00:00/0c Emask 0x9 (media error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { UNC }
ata1.00: configured for UDMA/133
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata1.00: BMDMA stat 0x25
ata1.00: failed command: READ DMA
ata1.00: cmd c8/00:04:4b:60:e0/00:00:00:00:00/ec tag 0 dma 2048 in
         res 51/40:00:4b:60:e0/00:00:00:00:00/0c Emask 0x9 (media error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { UNC }
ata1.00: configured for UDMA/133
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata1.00: BMDMA stat 0x25
ata1.00: failed command: READ DMA
ata1.00: cmd c8/00:04:4b:60:e0/00:00:00:00:00/ec tag 0 dma 2048 in
         res 51/40:00:4b:60:e0/00:00:00:00:00/0c Emask 0x9 (media error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { UNC }
ata1.00: configured for UDMA/133
ata1: EH complete
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata1.00: BMDMA stat 0x25
ata1.00: failed command: READ DMA
ata1.00: cmd c8/00:04:4b:60:e0/00:00:00:00:00/ec tag 0 dma 2048 in
         res 51/40:00:4b:60:e0/00:00:00:00:00/0c Emask 0x9 (media error)
ata1.00: status: { DRDY ERR }
ata1.00: error: { UNC }
ata1.00: configured for UDMA/133
sd 2:0:0:0: [sda] Unhandled sense code
sd 2:0:0:0: [sda]  Result: hostbyte=0x00 driverbyte=0x08
sd 2:0:0:0: [sda]  Sense Key : 0x3 [current] [descriptor]
Descriptor sense data with sense descriptors (in hex):
        72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00
        0c e0 60 4b
sd 2:0:0:0: [sda]  ASC=0x11 ASCQ=0x4
sd 2:0:0:0: [sda] CDB: cdb[0]=0x28: 28 00 0c e0 60 4b 00 00 04 00
end_request: I/O error, dev sda, sector 216031307
quiet_error: 96 callbacks suppressed
Buffer I/O error on device sda2, logical block 3151366
Buffer I/O error on device sda2, logical block 3151367
ata1: EH complete
logi ze smarta:
Cytuj
Complete error log:

SMART Error Log Version: 1
ATA Error Count: 216 (device log contains only the most recent five errors)
   CR = Command Register [HEX]
   FR = Features Register [HEX]
   SC = Sector Count Register [HEX]
   SN = Sector Number Register [HEX]
   CL = Cylinder Low Register [HEX]
   CH = Cylinder High Register [HEX]
   DH = Device/Head Register [HEX]
   DC = Device Command Register [HEX]
   ER = Error register [HEX]
   ST = Status register [HEX]
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.

Error 216 occurred at disk power-on lifetime: 1528 hours (63 days + 16 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 00 4b 60 e0 0c

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 00 04 4b 60 e0 4c 00      05:45:29.368  READ FPDMA QUEUED
  27 00 00 00 00 00 e0 00      05:45:29.367  READ NATIVE MAX ADDRESS EXT
  ec 00 00 00 00 00 a0 00      05:45:29.366  IDENTIFY DEVICE
  ef 03 46 00 00 00 a0 00      05:45:29.366  SET FEATURES [Set transfer mode]
  27 00 00 00 00 00 e0 00      05:45:29.365  READ NATIVE MAX ADDRESS EXT

Error 215 occurred at disk power-on lifetime: 1528 hours (63 days + 16 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 00 4b 60 e0 0c

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 00 04 4b 60 e0 4c 00      05:45:26.703  READ FPDMA QUEUED
  27 00 00 00 00 00 e0 00      05:45:26.702  READ NATIVE MAX ADDRESS EXT
  ec 00 00 00 00 00 a0 00      05:45:26.701  IDENTIFY DEVICE
  ef 03 46 00 00 00 a0 00      05:45:26.701  SET FEATURES [Set transfer mode]
  27 00 00 00 00 00 e0 00      05:45:26.700  READ NATIVE MAX ADDRESS EXT

Error 214 occurred at disk power-on lifetime: 1528 hours (63 days + 16 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 00 4b 60 e0 0c

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 00 04 4b 60 e0 4c 00      05:45:18.698  READ FPDMA QUEUED
  27 00 00 00 00 00 e0 00      05:45:18.697  READ NATIVE MAX ADDRESS EXT
  ec 00 00 00 00 00 a0 00      05:45:18.696  IDENTIFY DEVICE
  ef 03 46 00 00 00 a0 00      05:45:18.696  SET FEATURES [Set transfer mode]
  27 00 00 00 00 00 e0 00      05:45:18.695  READ NATIVE MAX ADDRESS EXT

Error 213 occurred at disk power-on lifetime: 1528 hours (63 days + 16 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 00 4b 60 e0 0c

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 00 04 4b 60 e0 4c 00      05:45:16.064  READ FPDMA QUEUED
  60 00 00 c8 3b 4f 40 00      05:45:16.059  READ FPDMA QUEUED
  60 00 00 c8 37 4f 40 00      05:45:16.054  READ FPDMA QUEUED
  60 00 10 b8 35 4f 40 00      05:45:16.052  READ FPDMA QUEUED
  60 00 00 b8 31 4f 40 00      05:45:16.046  READ FPDMA QUEUED

Error 212 occurred at disk power-on lifetime: 1528 hours (63 days + 16 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 00 4b 60 e0 0c

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 00 00 1f 60 e0 4c 00      05:45:09.993  READ FPDMA QUEUED
  27 00 00 00 00 00 e0 00      05:45:09.992  READ NATIVE MAX ADDRESS EXT
  ec 00 00 00 00 00 a0 00      05:45:09.991  IDENTIFY DEVICE
  ef 03 46 00 00 00 a0 00      05:45:09.991  SET FEATURES [Set transfer mode]
  27 00 00 00 00 00 e0 00      05:45:09.990  READ NATIVE MAX ADDRESS EXT

chmooreck

  • Gość
problem z obrazem partycji za pomocą dd
« Odpowiedź #3 dnia: 2011-02-26, 20:40:07 »
spróbuj ddrescue

freerider

  • Gość
problem z obrazem partycji za pomocą dd
« Odpowiedź #4 dnia: 2011-02-26, 20:57:45 »
Cytat: chmooreck
spróbuj ddrescue
ddrescue poszło z tym że na wysokości 3,2GB dało informacje że jest jakiś błąd dysku.
Dzięki za pomoc