[SOLVED] TestDisk Partition Recovery Issue [Developer - Mr.Christophe Grenier]

unSpawn · 11-10-2011, 08:37 AM

Quote:

Originally Posted by rajeefmk

Yes. The live CD worked earlier. I think The added hardware is creating the problem.

What would be helpful in case a system doesn't boot or displays odd behaviour is diagnose the reasons why. Sometimes this requires booting into the single or 1 runlevel and running 'dmesg' to see what goes on and sometimes you need to coax the system into booting using a combination of kernel parameters like for example "nosoftlockup nosync nohalt acpi=off noapic nolapic libata.noacpi libata.dma=0 libata.ignore_hpa=1"...

Quote:

Originally Posted by rajeefmk

From the release notes, systemrescuecd has ddrescue instead of dd_rescue. Are the command lines same for both ?

Different named applications usually have different command line switches. 'man ddrecue' and 'man dd_rescue' (if the latter exists) should show. What they have in common is specifying the input device name and output file name to use and the position at which the backup should start.

Quote:

Originally Posted by rng

Use only dd_rescue as instructed by unSpawn.

Actually either one would be good to use.

Quote:

Originally Posted by rng

This thread is in software section, where most users are not looking for recovery problems. You may put a new thread in general section, giving link to this thread- so that more users/experts can see and help you.

Next time instead suggest the OP asks a moderator to move the thread using the "report" button on the topmost post.

Quote:

Originally Posted by rajeefmk

It is only showing sda and its partitions. Knoppix did not detect sdb.

Always post actual error messages and 'dmesg' output. If you can't save nfo then even a phone cam screen shot would be better than nothing.

Quote:

Originally Posted by rajeefmk

shall I proceed with dd_rescue ?

As you already did there's nothing left but wish you good luck. From what you have posted there is no way for me to determine which device was loaded where (sometimes a CDROM may take up a SCSI-ish device name like /dev/sda) and the transfer rate definitely is not encouraging. If everything fails (and at your transfer rate this may take days) dd_rescue allows you to reverse the direction with "-r". However I don't know if it will still honor the "-s 90G" so you should at least have 400GB free space.

Quote:

Originally Posted by rng

Once image file is made:

That's a bit premature.

Quote:

Originally Posted by rng

to check: sudo fsck -y /mnt/hdb1/hda1_rescue.img

As any attempt to correct a corrupted file system, even if that would work due to the master having disk and consequently file system errors, could skew file contents even more I consider that really bad advice. Since it's not the first time in this thread posts of yours give me the shakes I urge you to please, please read (and practice) before you post advice like that.

Quote:

Originally Posted by rng

to mount recovered file: sudo mount -o loop /mnt/hdb1/hda1_rescue.img /mnt/rescued

This isn't necessary. Photorec, Foremost and other recovery tools read disk images fine.

Quote:

Originally Posted by rajeefmk

I´m atttaching the latest update from the dd_rescue which has been running for more than 17 hours. It has onlz processed 483k size files out of which all are error and no success.

Bummer.

Quote:

Originally Posted by rajeefmk

Anz suggestions on my next step ?

Please post output of various syslog files (ls /var/log/) like messages, boot and or kernel log and 'dmesg' before doing anything else.

rajeefmk · 11-10-2011, 09:11 AM

Quote:

Originally Posted by unSpawn

Please post output of various syslog files (ls /var/log/) like messages, boot and or kernel log and 'dmesg' before doing anything else.

Iäm posting the outputs as I cannot attach the files as they exceed the forum limit. Request you verify and give your valuable opinion.

Output of dmesg

0b 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00
[78866.248956] 0b 40 03 c0
[78866.248961] sd 3:0:0:0: [sdb] Add. Sense: No additional sense information
[78866.248967] sd 3:0:0:0: [sdb] CDB: Read(10): 28 00 0b 40 03 c0 00 00 08 00
[78866.248982] end_request: I/O error, dev sdb, sector 188744640
[78866.248985] Buffer I/O error on device sdb, logical block 23593080
[78866.249001] ata4: EH complete
[78870.417601] ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[78870.417605] ata4.00: BMDMA stat 0x25
[78870.417610] ata4.00: failed command: READ DMA
[78870.417617] ata4.00: cmd c8/00:08:c0:03:40/00:00:00:00:00/eb tag 0 dma 4096 in
[78870.417619] res 51/04:08:c0:03:40/04:00:3a:00:00/eb Emask 0x1 (device error)
[78870.417623] ata4.00: status: { DRDY ERR }
[78870.417626] ata4.00: error: { ABRT }
[78877.645574] ata4.00: configured for UDMA/100 (device error ignored)
[78877.645588] ata4: EH complete
[78881.396204] ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[78881.396208] ata4.00: BMDMA stat 0x25
[78881.396212] ata4.00: failed command: READ DMA
[78881.396220] ata4.00: cmd c8/00:08:c0:03:40/00:00:00:00:00/eb tag 0 dma 4096 in
[78881.396221] res 51/04:08:c0:03:40/04:00:3a:00:00/eb Emask 0x1 (device error)
[78881.396225] ata4.00: status: { DRDY ERR }
[78881.396228] ata4.00: error: { ABRT }
[78889.658910] ata4.00: configured for UDMA/100 (device error ignored)
[78889.658925] ata4: EH complete
[78893.430436] ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[78893.430440] ata4.00: BMDMA stat 0x25
[78893.430444] ata4.00: failed command: READ DMA
[78893.430452] ata4.00: cmd c8/00:08:c0:03:40/00:00:00:00:00/eb tag 0 dma 4096 in
[78893.430453] res 51/04:08:c0:03:40/04:00:3a:00:00/eb Emask 0x1 (device error)
[78893.430457] ata4.00: status: { DRDY ERR }
[78893.430460] ata4.00: error: { ABRT }
[78901.462242] ata4.00: configured for UDMA/100 (device error ignored)
[78901.462256] ata4: EH complete
[78905.320225] ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[78905.320229] ata4.00: BMDMA stat 0x25
[78905.320233] ata4.00: failed command: READ DMA
[78905.320241] ata4.00: cmd c8/00:08:c0:03:40/00:00:00:00:00/eb tag 0 dma 4096 in
[78905.320243] res 51/04:08:c0:03:40/04:00:3a:00:00/eb Emask 0x1 (device error)
[78905.320246] ata4.00: status: { DRDY ERR }
[78905.320249] ata4.00: error: { ABRT }
[78913.102248] ata4.00: configured for UDMA/100 (device error ignored)
[78913.102267] ata4: EH complete
[78916.597825] ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[78916.597827] ata4.00: BMDMA stat 0x25
[78916.597830] ata4.00: failed command: READ DMA
[78916.597835] ata4.00: cmd c8/00:08:c0:03:40/00:00:00:00:00/eb tag 0 dma 4096 in
[78916.597836] res 51/04:08:c0:03:40/04:00:3a:00:00/eb Emask 0x1 (device error)
[78916.597838] ata4.00: status: { DRDY ERR }
[78916.597839] ata4.00: error: { ABRT }
[78924.372239] ata4.00: configured for UDMA/100 (device error ignored)
[78924.372253] ata4: EH complete
[78929.110892] ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[78929.110896] ata4.00: BMDMA stat 0x25
[78929.110901] ata4.00: failed command: READ DMA
[78929.110908] ata4.00: cmd c8/00:08:c0:03:40/00:00:00:00:00/eb tag 0 dma 4096 in
[78929.110910] res 51/04:08:c0:03:40/04:00:3a:00:00/eb Emask 0x1 (device error)
[78929.110914] ata4.00: status: { DRDY ERR }
[78929.110917] ata4.00: error: { ABRT }
[78936.605557] ata4.00: configured for UDMA/100 (device error ignored)
[78936.605570] sd 3:0:0:0: [sdb] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[78936.605572] sd 3:0:0:0: [sdb] Sense Key : Aborted Command [current] [descriptor]
[78936.605576] Descriptor sense data with sense descriptors (in hex):
[78936.605577] 72 0b 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00
[78936.605584] 0b 40 03 c0
[78936.605586] sd 3:0:0:0: [sdb] Add. Sense: No additional sense information
[78936.605590] sd 3:0:0:0: [sdb] CDB: Read(10): 28 00 0b 40 03 c0 00 00 08 00
[78936.605596] end_request: I/O error, dev sdb, sector 188744640
[78936.605599] Buffer I/O error on device sdb, logical block 23593080
[78936.605618] ata4: EH complete
[78940.378410] ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[78940.378414] ata4.00: BMDMA stat 0x25
[78940.378418] ata4.00: failed command: READ DMA
[78940.378425] ata4.00: cmd c8/00:08:c0:03:40/00:00:00:00:00/eb tag 0 dma 4096 in
[78940.378427] res 51/04:08:c0:03:40/04:00:3a:00:00/eb Emask 0x1 (device error)
[78940.378431] ata4.00: status: { DRDY ERR }
[78940.378434] ata4.00: error: { ABRT }
[78947.825572] ata4.00: configured for UDMA/100 (device error ignored)
[78947.825587] ata4: EH complete
[78951.411551] ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[78951.411555] ata4.00: BMDMA stat 0x25
[78951.411559] ata4.00: failed command: READ DMA
[78951.411567] ata4.00: cmd c8/00:08:c0:03:40/00:00:00:00:00/eb tag 0 dma 4096 in
[78951.411568] res 51/04:08:c0:03:40/04:00:3a:00:00/eb Emask 0x1 (device error)
[78951.411572] ata4.00: status: { DRDY ERR }
[78951.411575] ata4.00: error: { ABRT }
[78959.232233] ata4.00: configured for UDMA/100 (device error ignored)
[78959.232247] ata4: EH complete
[78964.224635] ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[78964.224639] ata4.00: BMDMA stat 0x25
[78964.224643] ata4.00: failed command: READ DMA
[78964.224651] ata4.00: cmd c8/00:08:c0:03:40/00:00:00:00:00/eb tag 0 dma 4096 in
[78964.224652] res 51/04:08:c0:03:40/04:00:3a:00:00/eb Emask 0x1 (device error)
[78964.224656] ata4.00: status: { DRDY ERR }
[78964.224659] ata4.00: error: { ABRT }
[78972.352234] ata4.00: configured for UDMA/100 (device error ignored)
[78972.352248] ata4: EH complete
[78976.058852] ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[78976.058856] ata4.00: BMDMA stat 0x25
[78976.058860] ata4.00: failed command: READ DMA
[78976.058867] ata4.00: cmd c8/00:08:c0:03:40/00:00:00:00:00/eb tag 0 dma 4096 in
[78976.058869] res 51/04:08:c0:03:40/04:00:3a:00:00/eb Emask 0x1 (device error)
[78976.058873] ata4.00: status: { DRDY ERR }
[78976.058876] ata4.00: error: { ABRT }
[78984.435564] ata4.00: configured for UDMA/100 (device error ignored)
[78984.435578] ata4: EH complete
[78988.615343] ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[78988.615346] ata4.00: BMDMA stat 0x25
[78988.615348] ata4.00: failed command: READ DMA
[78988.615352] ata4.00: cmd c8/00:08:c0:03:40/00:00:00:00:00/eb tag 0 dma 4096 in
[78988.615353] res 51/04:08:c0:03:40/04:00:3a:00:00/eb Emask 0x1 (device error)
[78988.615355] ata4.00: status: { DRDY ERR }
[78988.615357] ata4.00: error: { ABRT }
[78996.515577] ata4.00: configured for UDMA/100 (device error ignored)
[78996.515597] ata4: EH complete
[79000.126309] ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[79000.126313] ata4.00: BMDMA stat 0x25
[79000.126317] ata4.00: failed command: READ DMA
[79000.126324] ata4.00: cmd c8/00:08:c0:03:40/00:00:00:00:00/eb tag 0 dma 4096 in
[79000.126326] res 51/04:08:c0:03:40/04:00:3a:00:00/eb Emask 0x1 (device error)
[79000.126330] ata4.00: status: { DRDY ERR }
[79000.126333] ata4.00: error: { ABRT }
[79008.065558] ata4.00: configured for UDMA/100 (device error ignored)
[79008.065572] sd 3:0:0:0: [sdb] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[79008.065574] sd 3:0:0:0: [sdb] Sense Key : Aborted Command [current] [descriptor]
[79008.065578] Descriptor sense data with sense descriptors (in hex):
[79008.065580] 72 0b 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00
[79008.065586] 0b 40 03 c0
[79008.065589] sd 3:0:0:0: [sdb] Add. Sense: No additional sense information
[79008.065592] sd 3:0:0:0: [sdb] CDB: Read(10): 28 00 0b 40 03 c0 00 00 08 00
[79008.065599] end_request: I/O error, dev sdb, sector 188744640
[79008.065602] Buffer I/O error on device sdb, logical block 23593080
[79008.065620] ata4: EH complete
[79011.538272] ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[79011.538276] ata4.00: BMDMA stat 0x25
[79011.538281] ata4.00: failed command: READ DMA
[79011.538288] ata4.00: cmd c8/00:08:c0:03:40/00:00:00:00:00/eb tag 0 dma 4096 in
[79011.538290] res 51/04:08:c0:03:40/04:00:3a:00:00/eb Emask 0x1 (device error)
[79011.538294] ata4.00: status: { DRDY ERR }
[79011.538296] ata4.00: error: { ABRT }
[79020.455567] ata4.00: configured for UDMA/100 (device error ignored)
[79020.455582] ata4: EH complete
[79024.218015] ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[79024.218019] ata4.00: BMDMA stat 0x25
[79024.218024] ata4.00: failed command: READ DMA
[79024.218031] ata4.00: cmd c8/00:08:c0:03:40/00:00:00:00:00/eb tag 0 dma 4096 in
[79024.218033] res 51/04:08:c0:03:40/04:00:3a:00:00/eb Emask 0x1 (device error)
[79024.218037] ata4.00: status: { DRDY ERR }
[79024.218040] ata4.00: error: { ABRT }
[79032.248900] ata4.00: configured for UDMA/100 (device error ignored)
[79032.248915] ata4: EH complete
[79036.063344] ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[79036.063348] ata4.00: BMDMA stat 0x25
[79036.063352] ata4.00: failed command: READ DMA
[79036.063360] ata4.00: cmd c8/00:08:c0:03:40/00:00:00:00:00/eb tag 0 dma 4096 in
[79036.063361] res 51/04:08:c0:03:40/04:00:3a:00:00/eb Emask 0x1 (device error)
[79036.063365] ata4.00: status: { DRDY ERR }
[79036.063368] ata4.00: error: { ABRT }
[79043.622224] ata4.00: configured for UDMA/100 (device error ignored)
[79043.622238] ata4: EH complete
[79047.518740] ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[79047.518744] ata4.00: BMDMA stat 0x25
[79047.518748] ata4.00: failed command: READ DMA
[79047.518756] ata4.00: cmd c8/00:08:c0:03:40/00:00:00:00:00/eb tag 0 dma 4096 in
[79047.518758] res 51/04:08:c0:03:40/04:00:3a:00:00/eb Emask 0x1 (device error)
[79047.518763] ata4.00: status: { DRDY ERR }
[79047.518776] ata4.00: error: { ABRT }
[79054.968894] ata4.00: configured for UDMA/100 (device error ignored)
[79054.968908] ata4: EH complete
[79058.464017] ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[79058.464021] ata4.00: BMDMA stat 0x25
[79058.464025] ata4.00: failed command: READ DMA
[79058.464033] ata4.00: cmd c8/00:08:c0:03:40/00:00:00:00:00/eb tag 0 dma 4096 in
[79058.464034] res 51/04:08:c0:03:40/04:00:3a:00:00/eb Emask 0x1 (device error)
[79058.464038] ata4.00: status: { DRDY ERR }
[79058.464041] ata4.00: error: { ABRT }
[79066.638891] ata4.00: configured for UDMA/100 (device error ignored)
[79066.638907] ata4: EH complete
[79070.077017] ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[79070.077021] ata4.00: BMDMA stat 0x25
[79070.077026] ata4.00: failed command: READ DMA
[79070.077033] ata4.00: cmd c8/00:08:c0:03:40/00:00:00:00:00/eb tag 0 dma 4096 in
[79070.077035] res 51/04:08:c0:03:40/04:00:3a:00:00/eb Emask 0x1 (device error)
[79070.077039] ata4.00: status: { DRDY ERR }
[79070.077042] ata4.00: error: { ABRT }
[79078.505547] ata4.00: configured for UDMA/100 (device error ignored)
[79078.505561] sd 3:0:0:0: [sdb] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[79078.505564] sd 3:0:0:0: [sdb] Sense Key : Aborted Command [current] [descriptor]
[79078.505567] Descriptor sense data with sense descriptors (in hex):
[79078.505569] 72 0b 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00
[79078.505575] 0b 40 03 c0
[79078.505578] sd 3:0:0:0: [sdb] Add. Sense: No additional sense information
[79078.505582] sd 3:0:0:0: [sdb] CDB: Read(10): 28 00 0b 40 03 c0 00 00 08 00
[79078.505588] end_request: I/O error, dev sdb, sector 188744640
[79078.505591] Buffer I/O error on device sdb, logical block 23593080
[79078.505613] ata4: EH complete
[79082.799166] ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[79082.799170] ata4.00: BMDMA stat 0x25
[79082.799174] ata4.00: failed command: READ DMA
[79082.799182] ata4.00: cmd c8/00:08:c0:03:40/00:00:00:00:00/eb tag 0 dma 4096 in
[79082.799184] res 51/04:08:c0:03:40/04:00:3a:00:00/eb Emask 0x1 (device error)
[79082.799188] ata4.00: status: { DRDY ERR }
[79082.799190] ata4.00: error: { ABRT }
[79090.755566] ata4.00: configured for UDMA/100 (device error ignored)
[79090.755581] ata4: EH complete
[79094.945537] ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[79094.945541] ata4.00: BMDMA stat 0x25
[79094.945545] ata4.00: failed command: READ DMA
[79094.945553] ata4.00: cmd c8/00:08:c0:03:40/00:00:00:00:00/eb tag 0 dma 4096 in
[79094.945555] res 51/04:08:c0:03:40/04:00:3a:00:00/eb Emask 0x1 (device error)
[79094.945559] ata4.00: status: { DRDY ERR }
[79094.945561] ata4.00: error: { ABRT }
[79102.918888] ata4.00: configured for UDMA/100 (device error ignored)
[79102.918902] ata4: EH complete
[79106.624193] ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[79106.624197] ata4.00: BMDMA stat 0x25
[79106.624201] ata4.00: failed command: READ DMA
[79106.624209] ata4.00: cmd c8/00:08:c0:03:40/00:00:00:00:00/eb tag 0 dma 4096 in
[79106.624210] res 51/04:08:c0:03:40/04:00:3a:00:00/eb Emask 0x1 (device error)
[79106.624214] ata4.00: status: { DRDY ERR }
[79106.624217] ata4.00: error: { ABRT }
[79114.372223] ata4.00: configured for UDMA/100 (device error ignored)
[79114.372237] ata4: EH complete
[79118.001815] ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[79118.001819] ata4.00: BMDMA stat 0x25
[79118.001824] ata4.00: failed command: READ DMA
[79118.001831] ata4.00: cmd c8/00:08:c0:03:40/00:00:00:00:00/eb tag 0 dma 4096 in
[79118.001833] res 51/04:08:c0:03:40/04:00:3a:00:00/eb Emask 0x1 (device error)
[79118.001837] ata4.00: status: { DRDY ERR }
[79118.001840] ata4.00: error: { ABRT }
[79125.932222] ata4.00: configured for UDMA/100 (device error ignored)
[79125.932237] ata4: EH complete
[79129.824907] ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[79129.824911] ata4.00: BMDMA stat 0x25
[79129.824916] ata4.00: failed command: READ DMA
[79129.824923] ata4.00: cmd c8/00:08:c0:03:40/00:00:00:00:00/eb tag 0 dma 4096 in
[79129.824925] res 51/04:08:c0:03:40/04:00:3a:00:00/eb Emask 0x1 (device error)
[79129.824929] ata4.00: status: { DRDY ERR }
[79129.824931] ata4.00: error: { ABRT }
[79137.628881] ata4.00: configured for UDMA/100 (device error ignored)
[79137.628896] ata4: EH complete
[79142.371305] ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[79142.371309] ata4.00: BMDMA stat 0x25
[79142.371313] ata4.00: failed command: READ DMA
[79142.371320] ata4.00: cmd c8/00:08:c0:03:40/00:00:00:00:00/eb tag 0 dma 4096 in
[79142.371322] res 51/04:08:c0:03:40/04:00:3a:00:00/eb Emask 0x1 (device error)
[79142.371326] ata4.00: status: { DRDY ERR }
[79142.371329] ata4.00: error: { ABRT }
[79150.245548] ata4.00: configured for UDMA/100 (device error ignored)
[79150.245564] sd 3:0:0:0: [sdb] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[79150.245569] sd 3:0:0:0: [sdb] Sense Key : Aborted Command [current] [descriptor]
[79150.245575] Descriptor sense data with sense descriptors (in hex):
[79150.245578] 72 0b 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00
[79150.245589] 0b 40 03 c0
[79150.245594] sd 3:0:0:0: [sdb] Add. Sense: No additional sense information
[79150.245601] sd 3:0:0:0: [sdb] CDB: Read(10): 28 00 0b 40 03 c0 00 00 08 00
[79150.245616] end_request: I/O error, dev sdb, sector 188744640
[79150.245619] Buffer I/O error on device sdb, logical block 23593080
[79150.245634] ata4: EH complete
[79188.178069] pcmanfm[5092]: segfault at fffffffe ip b6ecc3ac sp bffc4860 error 4 in libgobject-2.0.so.0.2800.6[b6e98000+47000]

rajeefmk · 11-10-2011, 09:15 AM

Cannot post output of dd_rescue.log, progress.log and badblocks.log as their character count exceeds forum limit.

unSpawn · 11-10-2011, 09:27 AM

Quote:

Originally Posted by rajeefmk

Cannot post output of dd_rescue.log, progress.log and badblocks.log as their character count exceeds forum limit.

I'll send you an email now.

rajeefmk · 11-10-2011, 09:43 AM

I have sent the mail.

rajeefmk · 11-10-2011, 10:20 AM

Quote:

Originally Posted by unSpawn

Actually either one would be good to use.

Putting across a humble question - Can dd_rhelp do anything in this case ? I was reading the following link posted by rng and thought that this was similar to my case ie. dd_rescue has slowed down after hitting many bad sectors.So If we can bypass these sectors it would be helpful. At the same time, if bypassed it might got well beyond our scope of interest .Hence I´mm confused.

http://codeidol.com/unix/knoppix/Rep...d-Hard-Drives/

unSpawn · 11-10-2011, 10:31 AM

Received files. Looking now.

unSpawn · 11-10-2011, 11:39 AM

Quote:

Originally Posted by rajeefmk

Putting across a humble question - Can dd_rhelp do anything in this case ? I was reading the following link posted by rng and thought that this was similar to my case ie. dd_rescue has slowed down after hitting many bad sectors.So If we can bypass these sectors it would be helpful. At the same time, if bypassed it might got well beyond our scope of interest .Hence I´mm confused.

If you want to try dd_rhelp go right ahead. But 'dmesg' and dd_rescue.log show the machine doesn't recognize the device at the hardware level. I'd rather try dd_rescue with O_DIRECT in reverse copy mode or rng's ddrescue example from http://www.forensicswiki.org/wiki/Ddrescue first.

rng · 11-11-2011, 07:31 AM

@rajeefmk: Any progress?

rajeefmk · 11-12-2011, 05:52 AM

[QUOTE=unSpawn;4520839]

Quote:

If you want to try dd_rhelp go right ahead.

I'm not familiar with the software.Was just putting across a suggestion.

Quote:

'dmesg' and dd_rescue.log show the machine doesn't recognize the device at the hardware level.

I booted again and checked in the BIOS.The hard disk seems to be detected by the BIOS as slave.

Quote:

I'd rather try dd_rescue with O_DIRECT in reverse copy mode or rng's ddrescue example from http://www.forensicswiki.org/wiki/Ddrescue first.

Could you elaborate on running dd_rescue in reverse mode ? i tried a few command aand got the whole thing messed up.

rajeefmk · 11-12-2011, 05:54 AM

Quote:

Originally Posted by rng

@rajeefmk: Any progress?

Thank you rng for the concern. I have no progress yet other than the warnings and command error.I'm trying to learn and apply the commands of ddrescue and dd_rhelp.

Shall update immediately when i get a progress.

rajeefmk · 11-12-2011, 05:58 AM

@unspawn : (the moderator)

I have my university xams round the corner and will get over by 17th december. I can only continue with process after that as i'm now leaving to college. (after bunking 4 days for the purpose of recovery alone.)..

Can I contiue reporting back to the thread after that or will this thread be terminated/closed ?

unSpawn · 11-12-2011, 06:21 AM

Quote:

Originally Posted by rajeefmk

I booted again and checked in the BIOS.The hard disk seems to be detected by the BIOS as slave.

Nice.

Quote:

Originally Posted by rajeefmk

Could you elaborate on running dd_rescue in reverse mode ?

That's just adding the "-d" and "-r" switches:

Code:

dd_rescue -d -r -l /recovery/dd_rescue.log -o /recovery/badblocks.log /dev/sdb /recovery/image.dd 2>&1 | tee /recovery/progress.log

* One thing I'm not certain about is if reverse copying honors "-s 90G" and if it does in which way and the author hasn't responded to my email yet.

If you OTOH would want to try rng's suggestion (be my guest) be careful to adapt it to your situation. Since both tools output may fill the disk ensure you don't run both at the same time and first move existing image.dd (if it has a reasonable size that is) to your backup disk:

Code:

ddrescue -d -v /dev/sdb /recovery/ddrescue.dd /recovery/ddrescue.log
ddrescue -d -v -r 1 /dev/sdb /recovery/ddrescue.dd /recovery/ddrescue.log

See 'man ddrescue' for explanation.

rng · 11-12-2011, 09:25 AM

One more application for your consideration: myrescue

Its description in synaptic package manager of ubuntu: myrescue is a program to rescue the still-readable data from a damaged harddisk. It is similar in purpose to dd_rescue, but it tries to quickly get out of damaged areas to first handle the not yet damaged part of the disk.

link: https://www.linux.com/learn/docs/ldp...rescue-utility

unSpawn · 11-16-2011, 03:58 PM

Quote:

Originally Posted by rajeefmk

I have my university xams round the corner and will get over by 17th december. I can only continue with process after that as i'm now leaving to college. (after bunking 4 days for the purpose of recovery alone.).. Can I contiue reporting back to the thread after that or will this thread be terminated/closed ?

No problem. Good luck with the exams. Just ping this thread when you get back.