Name: bigdaddyduff Date: December 25, 2007 at 18:20:53 Pacific Subject: out of the blue hard drive trouble OS: Windows Vista Home Premiu CPU/Ram: 120GB Model/Manufacturer: TOSHIBA Satellite P105
Comment:
I have a 120GB WD passport portable hard drive that I have used for years which is nearly full of important files. It has worked perfectly for years and has suffered no trauma. However, today when i plugged it into my computer, it didnt open in My Computer and was only visible in my device manager. It worked this morning, and i made no changes to anything between that time and when it wouldn't work. It is listed as unknown, unreadble, and unallocated in my disk manager, and labeled with EISA configuration. If it has always been EISA formatted, why does it not work now? And if it wasn't, how did it get that way since this morning? Any help would be greatly appreciated, thanks a lot!
The drive is USB. Right. I had the same problems with my USB HDD. I removed the drive from the external box and used a IDE 3.5 to 2.5 adapter and connected the drive to my HDD rack and it worked. I copied all the files and reformated. It works fine now. Why don't you do the same? If you don't have an HDD rack you can connect to the IDE cable in the board. If you only have SATA onboard you can use 2 converters SATA-TO-PATA-TO-2.5.
It is good advice, unfortunatley i don't have the technical know-how to pull it off, i'm mostly looking for a quick software or settings change fix, not to deconstruct my hard drive. Aegis, or dark666 or anyone, if you have any good programs in mind i'd love to hear, the cheaper or free-er the better, the fact that it happened so out of the blue makes me reticent to start taking things apart until its clear that's the only option.
The information on Computing.Net is the opinions of its users. Such
opinions may not be accurate and they are to be used at your own risk.
Computing.Net cannot verify the validity of the statements made on this site. Computing.Net and Computing.Net, LLC hereby disclaim all responsibility and liability for the content of Computing.Net and its accuracy.
PLEASE READ THE FULL DISCLAIMER AND LEGAL TERMS BY CLICKING HERE