BOOTMGR is missing

By jtobgen ·
My friend's company have a IBM X3500 7977 92M and it happens that last month went down. They're using Windows 2003 server installed in it. He ask me to help him to solve there problem regards to this. And now, am trying to boot from the OS installer, which is the Win 2003 server, sometimes the machine hangs-up in the selection if you want to repair it or not. But sometimes it will go through but it prompt me that no drive detected.

I tried to boot it without the OS installer then the screens says, bootmgr is missing.

Can someone help me to solve this problem.

Any advice will be appreciated. Thanks a lot. :-)

This conversation is currently closed to new comments.

Thread display: Collapse - | Expand +

All Answers

Collapse -

Recovery CD

by Mohammad Oweis In reply to BOOTMGR is missing

Use the original recovery CD (Server Guide) from IBM website, if you don't have it.
Booting from the Win-2003 CD will not work, because you have a RAID controller and windows can not detect the HDD without a driver.

So, you have two options:
1- Wipe the server with Server Guide and have a fresh installation.
2- Get a driver for the RAID controller from IBM and hit F6 at the initial screen of the setup, and supply the driver.
You will need a floppy disk :)

Good Look.

Collapse -

Recovery CD

by jtobgen In reply to Recovery CD

Hi Sir Mohammad,

I already did run the ServeGuide which is inlcuded with the IBM server machine. I successfully finished what the guide's want me to do so and ask me to insert the Win-2003 Installation disk and successfully finished to input all the information, the machine automatically turned-off.

The option two is not possible to the machine. because it doesn't have a floppy drive installed in it.

For now, I'm downloading the IBM UpdateXpress CD 4.05a - System x from IBM support website.

Anyways, thank you so much for the thread.

Collapse -


by Mohammad Oweis In reply to Recovery CD

UpdateXpress can help, you can update the firmware for the RAID controller, HDD and all other hardware.

maybe this will solve the problem.

I had a problem with one of my IBM server in the past, server could not boot and hanged at Windows logo, i disabled hyper-threading from BIOS then it worked like a charm.
Even though it was working before with hyper-threading.

Collapse -

hyper-threading from BIOS

by jtobgen In reply to UpdateXpress

Same problem encountered after the update using the UpdateXpress. :-(

How can I do disabling the hyper-threading from BIOS? Can you explain me how please? :-)

Collapse -


by Mohammad Oweis In reply to hyper-threading from BIOS

If the new firmware failed for one of the devices, you can use an older version of UpdateXpress and re-install the old firmware for that device.

Once You reboot the server, you will have "press F1 to enter BIOS configuration".
Hit F1, then search in the menus.
Sorry i can't remember where to find it.
It should be somewhere "Hyper-Threading = Enable/Disable"

Collapse -


by jtobgen In reply to Hyper-threading

Hi sir,

I already tried the UpdateXpress which I downloaded from IBM site. It doesn't work for me. Same problem encountered. Is there any ways to update the system BIOS, SAS, RAID controller without installed OS? Because, I think the real problem is the firmware. Firmware is really outdated. Last update is 2006. In which so many critical updates are already release by IBM. But my problem is, I don't know how to update the firmware without installed OS. Is it possible to update firmwares without OS installed, or the "Hyper-Threading" that you were saying is already the answer to my question? :-)

Collapse -


by Mohammad Oweis In reply to UpdateXpress

Boot from the UpdateXpress CD.
This way you can update the firmware for all hardware; BIOS, RAID, SAS, HDD,...

Running the CD from the OS will update the drivers and some firmwares like Ethernet.

Good Luck.

Collapse -

may be failing HDD

by oldbaritone In reply to BOOTMGR is missing

Sounds like the HDD could be on the way down. If you can, get another drive, shut the whole system down for a couple of hours and let it cool, then use a disk-clone package like Partition Manager to resurrect whatever you can. If it still won't boot, try "repair" on the new drive..

Collapse -

Failing HDD

by jtobgen In reply to may be failing HDD

Hi Sir oldbaritone,

Sounds good. Bwt, how can I do the repair?

Collapse -

3rd party recovery software

by oldbaritone In reply to Failing HDD

I have been through this a couple of times. If you're lucky, give the old drive a rest for a couple of days, and while it's resting, buy a new drive as large or larger (capacity) than the old one.

Do you have an old junker machine in the boneyard? Or is the current machine dead until this is fixed? It's best to do this on a machine you can start and forget it for a while - maybe as long as a week.

Put both the new drive and old drive in the machine, and boot whatever OS the recovery software needs. (Some of them even run DOS, so it usually doesn't take much. You can usually use a Live CD to boot.)

Start the recovery software, and tell it to copy everything it can salvage from the old drive to the new drive, including the partition table, MBR, and everything you can get.

Make sure it has started, and then walk away. If there are many bad sectors, I've had this process take as long as a week days on a large drive. "Hard" sector errors often take 10-15 seconds per sector for the recycle and reread. You'll hear the old drive clunking and moaning.

After the data is moved to the new drive, remove the old drive and boot the system from the new drive if you can. If not, boot from the install CD and try to repair/recover.

Most times, I have gotten more than 95% of the data back. System files are often lost, but so what. They can be re-installed or repaired. (System files get many hits; user data is accessed much less frequently. That's why the user data is often OK when the system files are corrupt.)

So good luck. It's a hassle. I just went through it two weeks ago when a system drive failed.

Been there, done that, got a tee-shirt, don't need another tee-shirt.


Related Discussions

Related Forums