Can you post the outcome - including what you did, what worked, what didn't, etc.? These types of threads are often helpful for future reference.
Sorry I was about to however I just got extremely busy in my personal life and ended up on a semi-vacation!
What happened was that I ran:
ddrescue -n -r3 /dev/sdd /dev/sdc logfile
eventually. As per before.
This coupled together with one thing I missed before which was the command:
The reason for the:
message previously was due to the fact that I didn't include the partition number:
e2fsck -p /dev/sdc1
....you would think out of nearly 10 years UNIX experience I wouldn't have missed that????
Anyway, due to what seemed to be a corrupted file system I needed to run:
e2fsck -y /dev/sdc1
This fixed a lot inode issues and I ended up with quite a few items in the: lost + found directory
I don't know yet what they were as the disk I used is a backup disk and currently disconnected from the machine due to lack of drive and power support within as it's an ancient pre-HT PIV with no SATA so I have an additional PCI based SATA card in there which is compatible with both BSD and Linux.
The crazy thing is however now that I managed to rescue this drive another much newer drive seems to be having I/O issues as through NFS when connected with my Ubuntu notebook I get system freeze on my BSD server.
Once I managed to catch a dmesg output on the TTY claiming:
however the next time I tried to read from the disk nothing was mentioned however the system just froze :-(
I just rebooted now and am waiting for the disk checks to go through even though last time it claimed the disk was clean....?
To be honest I really need to get the disk into a proper SATA port hardwired on a system board and see what happens then rather then Frankensteining as per what I have done.
Assumptions though is that if my hunch is correct and the disk is suffering from I/O issues then dd_rescue tool will be better as that caters for those kinds of errors much better then ddrescue which seems to cater for block errors better.
That will most likely have to be run through FreeBSD however, as my Gentoo based System Rescue CD may not like the UFS2 partition on it.
Will post more on my findings when I actually have achieved a recovery, will need to buy a new disk first though! :-)