03-11-2014 05:09 PM
I've got a sas3 hardware raid controller card so I'm not using the onboard raid 300, which takes FOR-EV-ERRRRR to get through POST. Is there a way I can disable that? I even tried attaching drives to it to see if I could change controller settings, but no...
Also, I'm booting the os (lmde) to another pcie card so I'm not using the onboard raid at all.
Solved! Go to Solution.
03-13-2014 08:34 AM
03-17-2014 12:50 AM
Thank you for your reply, it worked, the software SLI MegaRaid bios is no longer interrupting the boot process.
Sadly, after this, the server wouldn't boot. As it turns out, something about this one change cased a shift in the UEFI nvram and my system wouldn't restart. And then the OS would not reinstall using the same methods I had successfully used before.
This post helped me get going: http://forums.debian.net/viewtopic.php?f=16&t=81120
Quite interesting, this UEFI stuff...
03-19-2014 05:53 PM
I_am_Nivek, in the future, you should probably ask what bios version people are on. On the RD430, version 2.12 seems to me to not handle non Windows operating systems very well. As I detail on this post, nearly any change I make to the RD430 (including update-grub) would cause the uefi boot entry menu to be corrupted.
That includes making your one change in the bios.
After reinstalling the OS 10+ times, I next turned to a ThinkServer TS140 we have. I put a raid controller on it and installed the same linux OS as on the RD430 and the TS140 was completely stable, including after running update-grub. I updated the RD430 to V8.10 bios and it has now been stable through a couple of small configuration changes, but notably is the first time I was able to recover to the installation once UEFI had lost it.
03-20-2014 04:10 AM
03-20-2014 02:44 PM
Nivek, no worries. Your answer wasn't the cause of everything else. I wasn't yet aware of the "Patsburg SCU" option's function in the bios and you got me on the right path.
And I wasn't understanding the various aspects of my problem well enough yet to ask for help.
I mentioned in the uefi thread that I would love if there was a bios-independent efi program that could reset and validate the boot menu in the nvram.