I am trying ddrescue on my valuable 500GB SATA and this is the output I had:

knoppix@Microknoppix:~$ ddrescue -f -r1 -R /dev/sda /dev/sdc /home/knoppix/Desktop/log2.log
GNU ddrescue 1.21
Press Ctrl-C to interrupt
ipos: 495735 MB, non-trimmed: 4826 MB, current rate: 0 B/s
opos: 495735 MB, non-scraped: 0 B, average rate: 0 B/s
non-tried: 495281 MB, errsize: 0 B, run time: 1h 38m 53s
rescued: 0 B, errors: 0, remaining time: n/a
percent rescued: 0.00% time since last successful read: 1h 38m 53s
Copying non-tried blocks... Pass 3 (backwards)

Here is the logfile:

# Mapfile. Created by GNU ddrescue version 1.21
# Command line: ddrescue -f -r1 -R /dev/sda /dev/sdc /home/knoppix/Desktop/log2.log
# Start time: 2017-01-18 09:34:51
# Current time: 2017-01-18 11:19:33
# Copying non-tried blocks... Pass 3 (backwards)
# current_pos current_status
0x735B320000 ?
# pos size status
0x00000000 0x00010000 *
0x00010000 0x00010000 ?
0x00020000 0x00010000 *
0x00030000 0x00020000 ?
0x00050000 0x00010000 *
0x00060000 0x00040000 ?
0x000A0000 0x00010000 *
0x000B0000 0x00080000 ?
0x00130000 0x00010000 *
0x00140000 0x00100000 ?
0x00240000 0x00010000 *

Please is there any hope? If not what can I do? PLEASE HELP

How far does it get? Is any data written to /dev/sdc? Its probably easier to output to a file instead of a device to work with the data later.

1 members found this post helpful.

It appears that ddrescue was unable to read even a single sector from that drive. Not a good sign. Is the disk even spinning?

1 members found this post helpful.

Thanks for the replies. Yes the disk is spinning alright; no odd noise from it.
So far no data written to /dev/sdc.

This is the latest output:
knoppix@Microknoppix:~$ ddrescue -f -r1 -R /dev/sda /dev/sdc /home/knoppix/Desktop/log2.log
GNU ddrescue 1.21
Press Ctrl-C to interrupt
ipos: 431269 MB, non-trimmed: 69233 MB, current rate: 0 B/s
opos: 431269 MB, non-scraped: 0 B, average rate: 0 B/s
non-tried: 430874 MB, errsize: 0 B, run time: 23h 36m 59s
rescued: 0 B, errors: 0, remaining time: n/a
percent rescued: 0.00% time since last successful read: 23h 36m 59s
Copying non-tried blocks... Pass 3 (backwards)

clemenceau,

Welcome to LQ.

As you probably know, it is a good idea if possible to make a copy of the existing drive to another one.
You appear to be trying to do that!

Have you also tried PhotoRec as well as ddrescue:
http://www.cgsecurity.org/wiki/PhotoRec

PhotoRec Step by Step:
http://www.cgsecurity.org/wiki/PhotoRec_Step_By_Step

Useful link (refers to Windows, but procedure is similar):
https://dottech.org/10756/testdisk-p...will-ever-use/

Have you tried connecting the HDD to another functioning Linux/Windows computer using a USB to SATA adapter such as this:
https://www.amazon.co.uk/StarTech-co.../dp/B00HJZJI84

1 members found this post helpful.

clemenceau,

Have you made any progress?

Using dcfldd instead of dd may be of use:
https://www.obsidianforensics.com/bl...g-using-dcfldd

Warning:

It is important to write protect the drive to be imaged as soon as possible after it has been attached to the computer. While a properly configured forensic Linux machine will not write to the evidence disk, it is good to take precautions to block write attempts, both from the system and the user.

Also:
http://stefanoprenna.com/blog/2014/0...instead-of-dd/

1 members found this post helpful.

Hello beachboy2
I was ill for a while. I tried dcfldd on the dead disk but still no good result! Below is the output:

knoppix@Microknoppix:~$ dd if=/dev/sda of=/dev/sdc
dd: error reading '/dev/sda': Input/output error
0+0 records in
0+0 records out
0 bytes copied, 0.158943 s, 0.0 kB/s
knoppix@Microknoppix:~$

What do you suggest? still help please.

Does Knoppix run as root by default, or allow access to raw devices by default?

1 members found this post helpful.

Hi 273
I'm actually a Newbie in Linux, I can't really tell if Knoppix run as root by default or allow access to raw devices by default.
Need a guideline, please.

Knoppix appears to include the user in the "disk" group, which allows read access to raw disk devices. If you did not have permission to read the drive, you would get a "Permission denied" error and never get to the point of doing anything that would cause an I/O error.

When you get the I/O error, immediately run the "dmesg" command. Near the end of the output you should see some messages related to the disk device. Those would give a better idea about what is going wrong.

1 members found this post helpful.

Hi rknicholsm
Thanks for your interest. Below is the output I had with the "dmesg" command, but I can't interpret it. Once again need your help.
(only a portion of the output is shown)

[ 38.117441] ata1.00: status: { DRDY ERR }
[ 38.117442] ata1.00: error: { ABRT }
[ 38.120986] ata1.00: configured for UDMA/133 (device error ignored)
[ 38.120999] ata1: EH complete
[ 38.130762] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[ 38.130764] ata1.00: irq_stat 0x40000001
[ 38.130769] ata1.00: failed command: READ DMA
[ 38.130776] ata1.00: cmd c8/00:08:00:00:00/00:00:00:00:00/e0 tag 22 dma 4096 in
res 51/04:08:00:00:00/00:00:00:00:00/e0 Emask 0x1 (device error)
[ 38.130779] ata1.00: status: { DRDY ERR }
[ 38.130781] ata1.00: error: { ABRT }
[ 38.134369] ata1.00: configured for UDMA/133 (device error ignored)
[ 38.134389] sd 0:0:0:0: [sda] tag#22 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[ 38.134394] sd 0:0:0:0: [sda] tag#22 Sense Key : Illegal Request [current]
[ 38.134398] sd 0:0:0:0: [sda] tag#22 Add. Sense: Unaligned write command
[ 38.134403] sd 0:0:0:0: [sda] tag#22 CDB: Read(10) 28 00 00 00 00 00 00 00 08 00
[ 38.134406] blk_update_request: I/O error, dev sda, sector 0
[ 38.134421] ata1: EH complete
[ 38.144102] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[ 38.144105] ata1.00: irq_stat 0x40000001
[ 38.144113] ata1.00: failed command: READ DMA
[ 38.144118] ata1.00: cmd c8/00:08:00:00:00/00:00:00:00:00/e0 tag 25 dma 4096 in
res 51/04:08:00:00:00/00:00:00:00:00/e0 Emask 0x1 (device error)
[ 38.144121] ata1.00: status: { DRDY ERR }
[ 38.144122] ata1.00: error: { ABRT }
[ 38.147664] ata1.00: configured for UDMA/133 (device error ignored)
[ 38.147685] ata1: EH complete
[ 38.157442] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[ 38.157447] ata1.00: irq_stat 0x40000001
[ 38.157455] ata1.00: failed command: READ DMA
[ 38.157463] ata1.00: cmd c8/00:08:00:00:00/00:00:00:00:00/e0 tag 27 dma 4096 in
res 51/04:08:00:00:00/00:00:00:00:00/e0 Emask 0x1 (device error)
[ 38.157468] ata1.00: status: { DRDY ERR }
[ 38.157471] ata1.00: error: { ABRT }
[ 38.159958] kvm: disabled by bios
[ 38.161054] ata1.00: configured for UDMA/133 (device error ignored)
[ 38.161073] ata1: EH complete
[ 38.170774] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[ 38.170779] ata1.00: irq_stat 0x40000001
[ 38.170786] ata1.00: failed command: READ DMA
[ 38.170794] ata1.00: cmd c8/00:08:00:00:00/00:00:00:00:00/e0 tag 29 dma 4096 in
res 51/04:08:00:00:00/00:00:00:00:00/e0 Emask 0x1 (device error)
[ 38.170797] ata1.00: status: { DRDY ERR }
[ 38.170800] ata1.00: error: { ABRT }
[ 38.174455] ata1.00: configured for UDMA/133 (device error ignored)
[ 38.174480] ata1: EH complete
[ 38.184105] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[ 38.184110] ata1.00: irq_stat 0x40000001
[ 38.184114] ata1.00: failed command: READ DMA
[ 38.184122] ata1.00: cmd c8/00:08:00:00:00/00:00:00:00:00/e0 tag 0 dma 4096 in
res 51/04:08:00:00:00/00:00:00:00:00/e0 Emask 0x1 (device error)
[ 38.184126] ata1.00: status: { DRDY ERR }
[ 38.184129] ata1.00: error: { ABRT }
[ 38.185225] kvm: disabled by bios
[ 38.187693] ata1.00: configured for UDMA/133 (device error ignored)
[ 38.187710] ata1: EH complete
[ 38.197433] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[ 38.197436] ata1.00: irq_stat 0x40000001
[ 38.197439] ata1.00: failed command: READ DMA
[ 38.197444] ata1.00: cmd c8/00:08:00:00:00/00:00:00:00:00/e0 tag 1 dma 4096 in
res 51/04:08:00:00:00/00:00:00:00:00/e0 Emask 0x1 (device error)
[ 38.197446] ata1.00: status: { DRDY ERR }
[ 38.197448] ata1.00: error: { ABRT }
[ 38.200994] ata1.00: configured for UDMA/133 (device error ignored)
[ 38.201012] ata1: EH complete
[ 38.210770] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[ 38.210775] ata1.00: irq_stat 0x40000001
[ 38.210780] ata1.00: failed command: READ DMA
[ 38.210788] ata1.00: cmd c8/00:08:00:00:00/00:00:00:00:00/e0 tag 3 dma 4096 in
res 51/04:08:00:00:00/00:00:00:00:00/e0 Emask 0x1 (device error)
[ 38.210792] ata1.00: status: { DRDY ERR }
[ 38.210794] ata1.00: error: { ABRT }
[ 38.214446] ata1.00: configured for UDMA/133 (device error ignored)
[ 38.214466] sd 0:0:0:0: [sda] tag#3 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[ 38.214471] sd 0:0:0:0: [sda] tag#3 Sense Key : Illegal Request [current]
[ 38.214475] sd 0:0:0:0: [sda] tag#3 Add. Sense: Unaligned write command
[ 38.214480] sd 0:0:0:0: [sda] tag#3 CDB: Read(10) 28 00 00 00 00 00 00 00 08 00
[ 38.214484] blk_update_request: I/O error, dev sda, sector 0
[ 38.214487] Buffer I/O error on dev sda, logical block 0, async page read
[ 38.214500] ata1: EH complete
[ 38.215217] kvm: disabled by bios
[ 38.224100] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[ 38.224105] ata1.00: irq_stat 0x40000001
[ 38.224110] ata1.00: failed command: READ DMA
[ 38.224118] ata1.00: cmd c8/00:08:00:00:00/00:00:00:00:00/e0 tag 6 dma 4096 in
res 51/04:08:00:00:00/00:00:00:00:00/e0 Emask 0x1 (device error)
[ 38.224122] ata1.00: status: { DRDY ERR }
[ 38.224125] ata1.00: error: { ABRT }
[ 38.227673] ata1.00: configured for UDMA/133 (device error ignored)
[ 38.227699] ata1: EH complete
[ 38.237437] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[ 38.237442] ata1.00: irq_stat 0x40000001
[ 38.237447] ata1.00: failed command: READ DMA
[ 38.237455] ata1.00: cmd c8/00:08:00:00:00/00:00:00:00:00/e0 tag 8 dma 4096 in
res 51/04:08:00:00:00/00:00:00:00:00/e0 Emask 0x1 (device error)
[ 38.237459] ata1.00: status: { DRDY ERR }
[ 38.237462] ata1.00: error: { ABRT }
[ 38.241032] ata1.00: configured for UDMA/133 (device error ignored)
[ 38.241052] ata1: EH complete
[ 38.250778] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[ 38.250783] ata1.00: irq_stat 0x40000001
[ 38.250788] ata1.00: failed command: READ DMA
[ 38.250796] ata1.00: cmd c8/00:08:00:00:00/00:00:00:00:00/e0 tag 10 dma 4096 in
res 51/04:08:00:00:00/00:00:00:00:00/e0 Emask 0x1 (device error)
[ 38.250800] ata1.00: status: { DRDY ERR }
[ 38.250802] ata1.00: error: { ABRT }
[ 38.254344] ata1.00: configured for UDMA/133 (device error ignored)
[ 38.254366] ata1: EH complete
[ 38.264098] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[ 38.264102] ata1.00: irq_stat 0x40000001
[ 38.264105] ata1.00: failed command: READ DMA
[ 38.264110] ata1.00: cmd c8/00:08:00:00:00/00:00:00:00:00/e0 tag 12 dma 4096 in
res 51/04:08:00:00:00/00:00:00:00:00/e0 Emask 0x1 (device error)
[ 38.264113] ata1.00: status: { DRDY ERR }
[ 38.264114] ata1.00: error: { ABRT }
[ 38.267653] ata1.00: configured for UDMA/133 (device error ignored)
[ 38.267673] ata1: EH complete
[ 38.277453] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[ 38.277458] ata1.00: irq_stat 0x40000001
[ 38.277464] ata1.00: failed command: READ DMA
[ 38.277471] ata1.00: cmd c8/00:08:00:00:00/00:00:00:00:00/e0 tag 14 dma 4096 in
res 51/04:08:00:00:00/00:00:00:00:00/e0 Emask 0x1 (device error)
[ 38.277475] ata1.00: status: { DRDY ERR }
[ 38.277477] ata1.00: error: { ABRT }
[ 38.281020] ata1.00: configured for UDMA/133 (device error ignored)
[ 38.281049] ata1: EH complete
[ 38.290767] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[ 38.290771] ata1.00: irq_stat 0x40000001
[ 38.290775] ata1.00: failed command: READ DMA
[ 38.290779] ata1.00: cmd c8/00:08:00:00:00/00:00:00:00:00/e0 tag 16 dma 4096 in
res 51/04:08:00:00:00/00:00:00:00:00/e0 Emask 0x1 (device error)
[ 38.290782] ata1.00: status: { DRDY ERR }
[ 38.290783] ata1.00: error: { ABRT }
[ 38.294319] ata1.00: configured for UDMA/133 (device error ignored)
[ 38.294333] sd 0:0:0:0: [sda] tag#16 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[ 38.294335] sd 0:0:0:0: [sda] tag#16 Sense Key : Illegal Request [current]
[ 38.294337] sd 0:0:0:0: [sda] tag#16 Add. Sense: Unaligned write command
[ 38.294340] sd 0:0:0:0: [sda] tag#16 CDB: Read(10) 28 00 00 00 00 00 00 00 08 00
[ 38.294341] blk_update_request: I/O error, dev sda, sector 0
[ 38.294344] Buffer I/O error on dev sda, logical block 0, async page read
[ 38.294357] ata1: EH complete

The drive is reporting "device error" on every operation. That suggests an error in the control logic rather than a problem with the platters themselves. You won't be able to recover anything from that disk. Professional data recovery might be able to substitute another control card and make the drive readable again. That's probably not something you would want to try yourself even if you could obtain another drive of that same model.

1 members found this post helpful.

Hi again rknichols!
Thanks for your valuable suggestions.
I'll try to see to that.
Best Regards