Announcement

Collapse
No announcement yet.

Windows update completed and reboot - Now cant see RAID so no OS

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Windows update completed and reboot - Now cant see RAID so no OS

    Hi Forum,

    We just recently set up a new Lenovo Server and it has been working fantastic, however yesterday it completed some windows updates. (Only Important Updates) and when we rebooted it to complete this updates is came up with NO OS found error. What is happening is it seems like the OS has lost the Drivers to the RAID Array so it can not see the mirrored hard drives or any partitions etc.

    I started a Server 2012 installation and got to the point where you Load Drivers for the RAID and then it see's all my original partitions, from here I can back out to "Repair your PC" so from this command prompt I tried to reinstall the drivers using PNPUtlil /a /i driver.inf which said it was successful in loading the drivers into the Driver Store but was unable to apply to any hardware.

    So what I think my underlying issue is, is that the server OS has lost (or they have been overwritten by windows update) the Drivers to load the see the raid, windows update is a suspect but I can not definitively say that caused this issue.

    Does anyone have any ideas on how I can resolve this with out rebuilding the entire OS? My concern is even if i do that and I have not determined why this has happened how can i prevent it from re-occurring.

    Thanks so much for any advice,

    Stacy


  • #2
    Is that the literal error message? "No OS found?" If so, it doesn't come from Windows, but from either the BIOS bootstrap or the very early stages of the OS loader.

    If the storage driver in Windows had been missing or damaged, you'd get a blue screen error at boot. I believe the error code for that particular scenario is 0x0000007b, also known as "inaccessible_boot_device". If you're not getting that error message, something else is wrong.

    You could try rebuilding the boot loader from the command prompt in the recovery environment with "bootrec /fixmbr" and "bootrec /fixboot".You may want to do a chkdsk first (without /f), just to rule out disk/controller issues.

    Comment

    Working...
    X