Is it recoverable?
-
I'm not in such a good mood right now, my HD has just burnt out on me :mad: Everything was working fine until I tried to install VS inside a VMware virtual machine located on that drive. With no warning at all, it dissapeared? Thinking it could be a bug in vista I tried a reboot, but then the BIOS froze at the "Detecting IDE drives" stage. So I can't even boot up while the drive is conected :mad: The drive is a Maxtor 80GB IDE 7200, only 3 years old. Does anybody know what may be wrong with it or how I could repair it? The drive itself is not that important, but there are a few files on it I would not like to lose if it can be helped.
-
I'm not in such a good mood right now, my HD has just burnt out on me :mad: Everything was working fine until I tried to install VS inside a VMware virtual machine located on that drive. With no warning at all, it dissapeared? Thinking it could be a bug in vista I tried a reboot, but then the BIOS froze at the "Detecting IDE drives" stage. So I can't even boot up while the drive is conected :mad: The drive is a Maxtor 80GB IDE 7200, only 3 years old. Does anybody know what may be wrong with it or how I could repair it? The drive itself is not that important, but there are a few files on it I would not like to lose if it can be helped.
If the system won't even POST with the drive connected, it's toast. There's pretty much nothing you can do with it, unless you want to spend a lot of money and send the drive to a data recovery company. Well, after a little more thought, you MIGHT be able to find an identical Maxtor drive and POSSIBLY swap the PCB out. That might get you back up and running...possibly...maybe...
Dave Kreskowiak Microsoft MVP - Visual Basic
-
If the system won't even POST with the drive connected, it's toast. There's pretty much nothing you can do with it, unless you want to spend a lot of money and send the drive to a data recovery company. Well, after a little more thought, you MIGHT be able to find an identical Maxtor drive and POSSIBLY swap the PCB out. That might get you back up and running...possibly...maybe...
Dave Kreskowiak Microsoft MVP - Visual Basic
Thanks. I don't know exactly what the problem is, but I placed it in a USB caddy. This allowed me access to the files but I keep getting random I/O error's. I recently upgraded my main board to an ASUS M2N-E, which only has one IDE channel. So I have been meaning to replace this drive anyway. Find an identical you say, funny, It does have a twin. I bought two of them, but the other has so far not shown any signs of problems. But then again that one sit's in the caddy and rarely get's used.
-
Thanks. I don't know exactly what the problem is, but I placed it in a USB caddy. This allowed me access to the files but I keep getting random I/O error's. I recently upgraded my main board to an ASUS M2N-E, which only has one IDE channel. So I have been meaning to replace this drive anyway. Find an identical you say, funny, It does have a twin. I bought two of them, but the other has so far not shown any signs of problems. But then again that one sit's in the caddy and rarely get's used.
-
Just be aware that by breaking the clean room seal to swap PCBs your second drive will be left in terminal condition as well. If you do this, make sure you've moved all the data off it first.
-- Rules of thumb should not be taken for the whole hand.
I understand. But for an 80GB maxtor it's not really worth it. I will just try part-ex'ing it for one of the latest models.
-
I'm not in such a good mood right now, my HD has just burnt out on me :mad: Everything was working fine until I tried to install VS inside a VMware virtual machine located on that drive. With no warning at all, it dissapeared? Thinking it could be a bug in vista I tried a reboot, but then the BIOS froze at the "Detecting IDE drives" stage. So I can't even boot up while the drive is conected :mad: The drive is a Maxtor 80GB IDE 7200, only 3 years old. Does anybody know what may be wrong with it or how I could repair it? The drive itself is not that important, but there are a few files on it I would not like to lose if it can be helped.
I hope you did NOT mount the drive into the VM. Never do that if the drive is also known to the host. It does not even have to be the System Drive in order to cause serious trouble. Your description (one IDE channel, other drive on USB) sound like it was the System Drive, though. If you mounted a disk-file, it SHOULD have worked. In order to see if its just a Windows problem, I would boot the PC using a Linux LiveCD (if one Windows flavour does not recognize it, BartPE probably will neither). Then try finding the device (i.e., start QParted, cfdisk or whatever partitioner your LiveCD offers). If it does not appear there, either, you could still try to low-level-format it from the BIOS, if it is listed there. Low-Level formatting will cost you your data, though. If it IS listed in your partition editor, watch if the partition table is listed correctly and if the BOOT-flag is set on the correct partition. Fix, if necessary, then try again. If all fails, scrap it.
Cheers, Sebastian -- Contra vim mortem non est medicamen in hortem.
-
I hope you did NOT mount the drive into the VM. Never do that if the drive is also known to the host. It does not even have to be the System Drive in order to cause serious trouble. Your description (one IDE channel, other drive on USB) sound like it was the System Drive, though. If you mounted a disk-file, it SHOULD have worked. In order to see if its just a Windows problem, I would boot the PC using a Linux LiveCD (if one Windows flavour does not recognize it, BartPE probably will neither). Then try finding the device (i.e., start QParted, cfdisk or whatever partitioner your LiveCD offers). If it does not appear there, either, you could still try to low-level-format it from the BIOS, if it is listed there. Low-Level formatting will cost you your data, though. If it IS listed in your partition editor, watch if the partition table is listed correctly and if the BOOT-flag is set on the correct partition. Fix, if necessary, then try again. If all fails, scrap it.
Cheers, Sebastian -- Contra vim mortem non est medicamen in hortem.
Yes, I mounted the drive into VM, but it was not the system drive. The drive in question was my old system drive before I changed my MainBoard. I used to have two IDE drives, but my new board only supports one IDE cable, with my DVD-RW I had to move one drive to a usb. At the same time as updating I also bought a SCSI to be used as the system drive. Anyway, that IDE drive was a spare. I have been using VM for a few years now and never had problems while mounting drives and sharing them between the host and client. But, I did recently upgrade to a newer version of VM, so that could very well be the problem. The drive seems to be working ok now, and while it is I'm going to sell it. I just got another SCSI, so really, it's of no use to me.