Do you have a PC with an IDE controller? If so, try it on that as a slave.
Remember you need to set a jumper and position the drive to the center position on the cable. I suspect it would help if you knew the cable you were using was a IDE cable rather than a Cable Select IDE cable. Cable select and XP's support for it simplified things, but older drives (like yours) were before widespread adoption of CS (or USB). Try it by itself on the cable, and on the end too if the center position fails, also try it with the master position jumpered if not already done so, or with other cables or IDE controllers if available.
said the surface may be deteriorated. And any capacitors on the hard drive circuit board may have failed. But you know the firmware can communicate with your BIOS in recognizing the drive and it spins up---that is huge. Good luck.
User Configuration Jumper block
| 9 7 5 3 1 |
|10 8 6 4 2 |
1- 2 Life Test
3- 4 Master
5- 6 Slave Present
7- 8 RESERVED
9-10 Remote LED
presumably this diagram is on your drive
You can also boot up a LiveCD version of Linux and see if it can see the files on the drive. I'd recommend SystemRescueDisk
. I would be read-only with this program. Anything else can result in data loss. If it can see files and open some up then I would quickly copy the drive or at least those areas of interest to a storage drive.
The final last resort would be a surface write. You'd need 130Mb free. ddrescue
Found on SystemRescueCD (sudo or ./ not needed, just the command)
ddrescue [-options] bad_disk good_disk (should be equal or greater size) log_file
logfile should be used as it checks log file for already recovered files and goes from there...saves time which will already be hours
fdisk -l [list hard drives detected and names... sd_ for SATA drives, hd_ for IDE drives]
ddrescue -n -f /dev/sdb /dev/sdc resq.log
This will retrieve all non-damaged files and file structures first from sdb and transfer to sdc and note them in the log file. I recommend trying to transfer (backup) all files rescued at this point to another drive. Then,
ddrescue -r3 -f /dev/sdb /dev/sdc resq.log
This example will attempt to recover the damaged files three times before moving on and use the resq.log to find their location and not waste time looking.