- Jan 5, 2005
- 52
- 0
- 0
Hello everyone,
An important client came into the computer store I work at today and dropped off his rig for an upgrade. I built him a new sysem and then tried to boot into windows to set everything up. I got that stupid "NTLDR is missing" message so I popped in the WindowsXP CD and went to recovery console.
It took about a full minute after the keyboard thing finished before it displayed C:\>. I typed "dir" just as a test and it paused. The screen went black for about another minute before it displayed a message; something to the effect of the directory or drive is unreadable.
I typed chkdsk and got just about the same result, with a slightly different message; something to the effect of "the specificed drive contains unrecoverable errors and cannot be read".
Soooo I took it to another computer and attached it as a master on the secondary IDE channel. I turned the machine on and (despite the fact that this drive was not even somewhat affiliated with the boot drive) got an INVALID BOOT DISK error.
So I attached it as a master to the IDE controller card on the machine and it booted. Once in windows the disk was not recognized and did not show up in the drive list. The entire time it was connected to this machine (this is just FYI) it was the only disk on the cable, and all jumper settings and cabling was properly configured - so you don't have to worry about that.
Anyway, I shut it down and attempted to do a clone using Symantec Ghost 2002 (the only version I have). Synamtec said that the drive contained errors - no big surprise.
So I told enabled CRC32 Ignore and Force Cloning, and tried again. This time it recognized the errors in the bar along the bottom but allowed me to continue to chose my destination drive. This is where it gets really strange.
Synamtec reported the source and destination drives to be of identitical size - 120gb, but whenever I finished with the source/destination selection it prompted me with this error:
"The destination drive is too small."
OK, fine. So I went and grabbed a 200Gb drive - should be plenty of room for a 120Gb drive right? Apparently not. I got the same exact error. Figuring it was a motherboard error - since the particular motherboard was not one we really trusted, I tried it on another machine. Same error. So far I have not been able to make ghost recognize the 200Gb drive as sufficiently large enough to clone a 120gb drive.
The reason I was trying to clone the drive was so that (a) I have a working backup of the drive because it contains extremely important information that belongs to the customer, and because I wanted to see if perhaps the cloned drive would be workable enough for some program to recover it - perhaps just a lemon drive.
If anyone has any suggestions of (preferably free) software that will perform a miracle and save this poor guys data, or some procedure I'm not aware of that I could follow to save his drive, I would be very very happy to hear them. I'm open to suggestions!
Thanks for your time...
An important client came into the computer store I work at today and dropped off his rig for an upgrade. I built him a new sysem and then tried to boot into windows to set everything up. I got that stupid "NTLDR is missing" message so I popped in the WindowsXP CD and went to recovery console.
It took about a full minute after the keyboard thing finished before it displayed C:\>. I typed "dir" just as a test and it paused. The screen went black for about another minute before it displayed a message; something to the effect of the directory or drive is unreadable.
I typed chkdsk and got just about the same result, with a slightly different message; something to the effect of "the specificed drive contains unrecoverable errors and cannot be read".
Soooo I took it to another computer and attached it as a master on the secondary IDE channel. I turned the machine on and (despite the fact that this drive was not even somewhat affiliated with the boot drive) got an INVALID BOOT DISK error.
So I attached it as a master to the IDE controller card on the machine and it booted. Once in windows the disk was not recognized and did not show up in the drive list. The entire time it was connected to this machine (this is just FYI) it was the only disk on the cable, and all jumper settings and cabling was properly configured - so you don't have to worry about that.
Anyway, I shut it down and attempted to do a clone using Symantec Ghost 2002 (the only version I have). Synamtec said that the drive contained errors - no big surprise.
So I told enabled CRC32 Ignore and Force Cloning, and tried again. This time it recognized the errors in the bar along the bottom but allowed me to continue to chose my destination drive. This is where it gets really strange.
Synamtec reported the source and destination drives to be of identitical size - 120gb, but whenever I finished with the source/destination selection it prompted me with this error:
"The destination drive is too small."
OK, fine. So I went and grabbed a 200Gb drive - should be plenty of room for a 120Gb drive right? Apparently not. I got the same exact error. Figuring it was a motherboard error - since the particular motherboard was not one we really trusted, I tried it on another machine. Same error. So far I have not been able to make ghost recognize the 200Gb drive as sufficiently large enough to clone a 120gb drive.
The reason I was trying to clone the drive was so that (a) I have a working backup of the drive because it contains extremely important information that belongs to the customer, and because I wanted to see if perhaps the cloned drive would be workable enough for some program to recover it - perhaps just a lemon drive.
If anyone has any suggestions of (preferably free) software that will perform a miracle and save this poor guys data, or some procedure I'm not aware of that I could follow to save his drive, I would be very very happy to hear them. I'm open to suggestions!
Thanks for your time...
