Recovering data from SATA HDD with a ATAPI HDD
I have started something that I've since discovered is over my head. I have two desktop PCs. One is an older model that doesn't support SATA, the newer one has an SATA drive that has become nonfunctional. After running everything I could think of (chkdsk, fixboot, HDD diagnostic boot disk) without success, I had the brilliant idea that I could just pull the the ATAPI HDD out of my functional PC and run it as master on the SATA PC to see if I could salvage ANY data. I plugged it in and turned it on, then went into BIOS and changed the disk arrangement to have the ATAPI drive as primary and the SATA as secondary, however when I save and try to reboot, it just cycles through the "how would you like to start windows" screen continuously. I tried unplugging the SATA drive to see if I could just get the ATAPI drive to come on (and changed the appropriate BIOS settings) to no avail. I'm not sure what I'm doing wrong.
Does anyone have any ideas? I have a TON of pictures on the drive that I stupidly have not backed up anywhere else. Any help or ideas or even insults will be greatly appreciated. Thanks
Does anyone have any ideas? I have a TON of pictures on the drive that I stupidly have not backed up anywhere else. Any help or ideas or even insults will be greatly appreciated. Thanks
0
Comments
Your best bet right now is to put your working PATA drive back into your old computer, and get either an Adapter of some sort to hook your SATA drive as a slave to your working system to pull data off, or get a PCI SATA card for your old PC and hook it up natively to the working system.
Return the ATAPI drive to its working and original computer and then follow the steps outlined in this data recovery guide.
Thanks so much for your help
It helps that they were the same laptop... if they were old enough, it might also have helped that they were an older version of Windows or some other OS
The problem arises with newer (Win2K and later) versions of Windows that use a HAL - once the chipset-specific driver loads, if you move the drive to a machine with a different drive controller, the drive simply disappears, and you get the wonderfully enigmatic "INACCESSIBLE_BOOT_DEVICE" warning.
BTW, Microsoft does have a workaround for this, at least for PATA drives - you simply make sure the necessary "generic IDE" support is in place, and update the registry to tell Windows to use it. It may or may not work with a SATA system drive.
Back to your main problem: you can use a PATA/SATA adapter, or a PCI SATA card... but I really like having one of these around:
http://a-power.com/product-5442-251-3