Getting an 0xc0000001 on fresh install of WIndows 2012 r2 on an IBM blade HS23 with SSDs


I have a new HS23 (7875-E8U) blade with 2 mirrored 256G SSDs (90Y8643).   I have tried to load WIndows 2012 R2 on it twice.   Once without ServerGuide and once with ServerGuide.   Both complete the install without issue, but upon first boot, give me an 0xC0000001 missing boot device failure.   I have checked BIOS for boot order and the install saw the drives without issue.   All firmware is current and the HCL indicates that both are compatibile with 2012 R2.  

I also found this...

I am trying what looks like a very simple workaround at the bottom.   But I can not find the boot folder or the BCD file.  

Any suggestions would be REALLY appreciated.   This is a client project that is being hung up because of this.

Jon SnydermanAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Davis McCarnOwnerCommented:
1) Make sure you delete all of the partitions from your previous attempts before you try again.  Win 7,8,2K8, etc. all create a System partition and you want setup to create it on a blank HD.
2) They're a little vague about it; but, you may need to create a driver diskette and install the drivers during setup:
Downloads page:
 Note: You'll have to create an IBM id before they'll let you download the drivers.
Jon SnydermanAuthor Commented:
Thanks Davis.   Yes, I was deleting the partitions between the two loads.   As for drivers, the drivers are loaded as part of ServerGuide, however, the setup saw and allowed me to use the drive which usually indicates that the base or ServerGuide drivers are good.   I ended up calling IBM and we got it going, although it still seems a little unstable at boot.   The issue may be related to the attached multi-pathed SAN or the embedded optional hypervisor.  Neither are in use or in the boot order for this example, but they are attached.  So it still unclear.

If I come up with anything definitive, I will post back.

Davis McCarnOwnerCommented:

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

Jon SnydermanAuthor Commented:
It was updated at the disti but yes, we did check some.   I am going to go back and double check all that though.
Have you done an install on this blade successfully to other hard drive media?

I suspect the use of SSDs  may be a red herring in this case;  although the storage controller or SSDs might be faulty, I would back up and look at the entire blade configuration.  

Something related to the Hardware on the HS23 blade is allowing the Windows installer to complete but rendering a corrupt installation or other installation that cannot mount the new C: device or correctly boot the operating system.

If the storage controller drivers were not present,  the Windows installer should not even see your SSD device.

I strongly suggest running the IBM HS23 bladecenter diagnostics on the blade to fully test all the hardware, then
 disabling at BIOS level or removing any unnecessary hardware or "SAN Connections" from the blade,  for the install process.
Jon SnydermanAuthor Commented:
So we are not sure if the problem is resolved, but here is progress to date and I am going to close this out....

We ran a DSA and it came up clean.
We ran updates.   They were back level, but only one or two rev's.    
We set the onboard controller to only scan LUN 0 to try to avoid controller confusion.   But this is not really likely.
We  temporarily removed the SAN and the onboard hypervisor from the boot order.   But it was booting occasionally before this.

We seem to be booting reliably, but we have also re-engaged the SAN and the Hypervisor, although not in the boot order, but attached.

As I said, I am not sure what the final resolution was.   Maybe a combination of the three.  But for now, it seems to be stable.    BTW, setting the onboard controller to LUN 0 improves boot time dramatically, especially when a SAN is attached.

Thanks for your help
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Server Hardware

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.