| Forum Home | ||||
| Press F1 | ||||
| Thread ID: 97275 | 2009-02-10 04:10:00 | Trying to read an extraneous HDD | Bryan (147) | Press F1 |
| Post ID | Timestamp | Content | User | ||
| 746489 | 2009-02-10 04:10:00 | My daughter's HP Pavillion has karked it! I have an older PC and have installed XP on it. I then found out that daughter's HDD, with XP, was NTFS, mine was FAT 32. I converted mine to NTFS and connected her HDD as a slave to my PC. All I get is "DISK READ ERROR". I do see that the message has been a big problem worldwide with XP but I cannot find a solution. I have checked the cables etc and all is fine. When I disconnect her HDD and just leave my XP, the system boots fine. What I want to do is to access her HDD and recover some of her data (didn't believe in backing up!). Problem with her HDD is that coming out of the HP Pavillion the HHD had everything installed as OEM. Anyone got any ideas? Should I get a bootable Linux and do it that way? |
Bryan (147) | ||
| 746490 | 2009-02-10 05:00:00 | When you connected hers as a slave, did you boot from yours then scan her hdd for errors? Not boot from hers? It may come up with the screen that scans / checks / fixes the errors I wouldnt boot from hers as it may crash, if it does boot into windows, because of the difference in hardware |
Speedy Gonzales (78) | ||
| 746491 | 2009-02-10 06:15:00 | I then found out that daughter's HDD, with XP, was NTFS, mine was FAT 32. I converted mine to NTFS and connected her HDD as a slave to my PC. All I get is "DISK READ ERROR". You didn't need to do that. XP Fat32 will read NTFS drives. Its probably giving the error cause her drive is stuffed. |
pctek (84) | ||
| 746492 | 2009-02-10 06:21:00 | If XP can't see it then yes try a bootable linux CD sometimes it can see what windows cannot | gary67 (56) | ||
| 746493 | 2009-02-10 06:27:00 | Hi Speedy. I booted from mine but that was when I got the "Disk read error". No chance of scaning hers and mine did not boot. Thanks pctek. I did have a tech look at her system. He claims that although the motherboard and the CPU had been compromised, the HDD had not been affected, but then again I do not know how thorough he was. |
Bryan (147) | ||
| 1 | |||||