?
Solved

BOOTMGR is MISSING after SAS Expansion card change URGENT!

Posted on 2010-01-09
8
Medium Priority
?
754 Views
Last Modified: 2013-11-16
HI,

Our IBM Blade Server HS12 SAS Connection Expansion card broke and I had to change it. After changing it I activated the Raid Array and it was fine. After reboot, Windows 2008 says: BOOTMGR is MISSING. I tried to repair many times but no help. All the files are readable from the disks. I have tried to rebuild BCD, fixboot, fixmbr and so on, but it does not get fixed. I get the Bootmgr error at every boot. First the OS was not visible at Repair option but I managed to get it visible. Still no success in getting it boot.

For instance I get this error when trying bcdedit:
bcdedit /set {default} device partition=c:
An error occurred while attempting to reference the specified entry.
The system cannot find the file specified.

The same error comes with bcdedit /set {default} osdevice partition=c:
But command bcdedit /set {bootmgr} device partition=c: is successful.

Is there anything else to try or have I lost the game?
0
Comment
Question by:JKalliola
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 4
  • 4
8 Comments
 
LVL 47

Expert Comment

by:David
ID: 26273099
What, exactly, did you do to "activate" the array.  My concern is that the array was reassembled out of order.  If that happened, then your actions, rebuilding BCD, fixing bootmgr, and anything else you did basically destroyed any chance of recovery.

Also, if it was reassembled out of order, the controller wouldn't care, and it would pass all consistency checks.  It could even appear as if all files are readable, especially if you had a large enough stripe size, and you got the FIRST disk in the right slot, but any of the subsequent disks were out of order.

The way to tell if you did get the disks in the correct order is to boot windows and mount the logical drive.  Find some really large files that would be expected to span all of the disks in the array, and type them out or copy them and visually inspect them.  A chkdsk (but not a chkdsk/f) will not always detect this.

If you did reassemble out of order, then yes, you did do a lot of damage, any file you wrote is going to be at the wrong spot, but it won't be end of the world, and  you could still get a large amount back, just as long as you did not do a chkdsk /f and it did a repair.
0
 
LVL 47

Expert Comment

by:David
ID: 26273266
It also could be that the Array is no longer an "array", and you are just seeing a single disk drive, the first disk drive in the array, that happens to have the partitioning and the directory entries.  Did you notice any disk drive activity lights on any drive other than the first one?   Look at the RAID configuration and make sure it is same RAID level, size, number of drives that you had before.
0
 

Author Comment

by:JKalliola
ID: 26273339
Thanks for the comment.

What I did was just activate the array after controller replacement. Before activating it was reported as Inactive/optimal during boot sequence. It is not striped, it's mirrored.

I have not done any chkdsk's, I have only tried to fix BOOTMGR problem.

Any other suggestions?
0
Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
LVL 47

Expert Comment

by:David
ID: 26273870
well ... very unlikely it I raid related, unless this particular raid controller was running different firmware rev, and there is metadata issue that might have necessitated some sort of conversion step. just to be able to 100 percent eliminate the raid, I would contact the controller support email and run by a whatif you swap controller with degraded raid that was running different firmware.
0
 

Author Comment

by:JKalliola
ID: 26276513
The raid was functional before changing the controller. It just rebooted once a while and with IBM support we decided to change the controller. So the server was functional and the OS was fully functional but it rebooted continiously. There was no BOOTMGR error before the change. The firmware is same in both controllers.
0
 
LVL 47

Expert Comment

by:David
ID: 26278031
True JKalliola, but it will only "work" if the RAID controller is presenting the exact same LUN with same config as before.  IF it is now confused on where the starting block of the RAID is, or chunk size, or RAID level or something else related.  When you change RAID controllers you have to make 100% sure the new controller is configured with same settings as old one, in every respect.
0
 

Accepted Solution

by:
JKalliola earned 0 total points
ID: 26311165
I think that in this IBM system the configuration is not on the card as it was with the same configuration as with old controller card. I only had to change boot order, ohterwise it was 100% same configuration. I have made a restore from backups as I did not manage to get BOOTMGR working.
0
 

Author Comment

by:JKalliola
ID: 26311174
Closed.
0

Featured Post

On Demand Webinar: Networking for the Cloud Era

Ready to improve network connectivity? Watch this webinar to learn how SD-WANs and a one-click instant connect tool can boost provisions, deployment, and management of your cloud connection.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

After seeing many questions for JRNL_WRAP_ERROR for replication failure, I thought it would be useful to write this article.
This article shows how to get a list of available printers for display in a drop-down list, and then to use the selected printer to print an Access report or a Word document filled with Access data, using different syntax as needed for working with …
To efficiently enable the rotation of USB drives for backups, storage pools need to be created. This way no matter which USB drive is installed, the backups will successfully write without any administrative intervention. Multiple USB devices need t…
This tutorial will walk an individual through the steps necessary to join and promote the first Windows Server 2012 domain controller into an Active Directory environment running on Windows Server 2008. Determine the location of the FSMO roles by lo…

762 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question