BOOTMDR missing, only happens when a slave HDD is installed with no OS

[LookatmeABC123]

I started up my computer as always, and I notice that my E: drive (80GB WD IDE HD) is not showing up under My Computer. I restart my computer and get an error message that BOOTMDR is missing. I unplugged the WD drive, and then started up and the computer booted up no problem.

The thing is, this hard drive does not have an OS on it...it is just a slave drive.

Also, it would not work when I connected it to an IDE to USB adapter and tried to connect it to the computer via USB 2. The hard drive is around 4-5 years old. I have ALOT of important files on there that I desperately need...what can I do???

I thought about disconnecting my master hard drive, and booting off the Vista CD and trying to do a boot repair of that drive, but that doesn't really make sense since it doesn't even have an OS on it, but I'm desperate at this point...

 

[mechBgon]

Welcome to the Forums Begin by confirming that the jumper cap has been removed from the 80GB drive's master/slave/cable-select pins, if it is the only drive on its cable. With the cap removed, that's the special Single Master setting that WD drives often like best.

Any good?


Also, if you get ACCESS DENIED when trying to get into certain folders, you will probably need this info: http://support.microsoft.com/kb/308421

 

[robisbell]

exact model number of the HDD at issue?
has it ever had a OS installed on it?

 

[LookatmeABC123]

The exact model number is WD800JB - 00ETA0

It used to have windows XP on it if memory serves, pretty sure it never had vista, 99% positive.

 

[robisbell]

bootldr isn't a vista thing, it's been around long before then, I would suggest you fdisk that drive and do a thorough reformat. I had a feeling it was aleftover from when a XP was on it, but wanted to make sure. make sure you remove any partitions on it.

 

[vanvock]

It's not LDR It's MDR that's his prob & he needs the data on the disk. If you re-format it will be lost. You might check in BIOS to see if the boot order has changed.

 

[robisbell]

no, his system boots up fine when the 80GB is disconnected and runs fine. when the 80Gb is connected then the old bootldr on the 80 tries to boot a non existant OS that is not on it anymore.

 

[vanvock]

I had the impression that it had been in the system. Could he not edit the boot.ini & make it not try to load that OS?

 

[robisbell]

it's not on the main drive. it's on the old. he just needs to fdisk the drive, and reformat it.

 

[Old Hippie]

it's not on the main drive. it's on the old. he just needs to fdisk the drive, and reformat it.

Yep, but he still needs the data on the disc. OP, have you tried to set the boot drive in your BIOS to your Vista drive?

Also, it would not work when I connected it to an IDE to USB adapter and tried to connect it to the computer via USB 2

This would be an easy way to get the files. Does your adaptor include a power cable for the HDD?

 

[robisbell]

why would he need anything off the old, it's not had a OS on it a a while he stated. there's nothing on the old drive that is necessary for the current OS to run.

 

[Old Hippie]

Originally posted by: robisbell
why would he need anything off the old, it's not had a OS on it a a while he stated. there's nothing on the old drive that is necessary for the current OS to run.

I have ALOT of important files on there that I desperately need...what can I do???

Glasses?

 

[robisbell]

thanks. I was focusing on the bootldr trying to run from it, and forgot that issue.

I'd recommend putting the drive in a use case and hooking it up after the pc has booted and copying the files off it and then fdisking the drive.

 

[Old Hippie]

Originally posted by: robisbell
thanks. I was focusing on the bootldr trying to run from it, and forgot that issue.

I'd recommend putting the drive in a use case and hooking it up after the pc has booted and copying the files off it and then fdisking the drive.

Also, it would not work when I connected it to an IDE to USB adapter and tried to connect it to the computer via USB 2.

I'm gonna suggest putting your glasses on when you start to read, or maybe concentrate on a few problems instead of every problem. :laugh:

 

[robisbell]

re-read what I typed.
"I'd recommend putting the drive in a USB case and hooking it up after the pc has booted and copying the files off it and then fdisking the drive."
he tried booting with the drive on and connected. I'm saying let the system boot and once up, hook it up and turn it on.

 

[Old Hippie]

You're right! He probably doesn't even know what a "use" case is.

 

[mechBgon]

I wonder if he's checked his jumper setting yet...

 

[robisbell]

OP. I would suggest you put the drive in the USB enclosure, start up your pc, and once it's up and running, connect the USB enclosure and copy off what you need and then fdisk the drive.

 

[sonoma1993]

I think the OP hd is gone. He said in his op, that he hooked up his hdd to an ide to usb hdd adapter and it wouldn't work in that either.

 

[robisbell]

it was connected when he started up the PC, that's why the errors.