UEFI update stupidity
Printed From: ASRock.com
Category: Technical Support
Forum Name: Intel Motherboards
Forum Description: Question about ASRock Intel Motherboards
URL: https://forum.asrock.com/forum_posts.asp?TID=1894
Printed Date: 26 Dec 2024 at 11:52am Software Version: Web Wiz Forums 12.04 - http://www.webwizforums.com
Topic: UEFI update stupidity
Posted By: pixel42
Subject: UEFI update stupidity
Date Posted: 01 Feb 2016 at 6:14pm
Dear
ASRock, I'm owner of one of your motherboards (Z97 Pro3) and I'm really angry.
It is out of my understanding that even in the latest version of the UEFI (2.10)
you are not able to store/restore the UEFI settings on update
or AT LEAST give out a warning that the settings will be reset and have to be restored
again. So thanks to this now I'm one of a lot of pissed off people out there that have
lost their RAID system, because you reset the SATA mode from RAID to AHCI,
which makes the RAID controller lose all its settings, changing all RAID drives
to "non-raid" after the next boot. It would take how much time for one
of your programmers to change this completely stupid behavior?! An hour maybe?
Come on.
|
Replies:
Posted By: wardog
Date Posted: 01 Feb 2016 at 8:42pm
Last I knew Gigabyte, EVGA, ASUS, MSI, and a host of other manufacturers do this, or have, in their implementation also.
While true, and disconcertingly so I'll add, sadly it does also wipe the Saved Settings.
|
Posted By: pixel42
Date Posted: 02 Feb 2016 at 8:24pm
A simple big fat warning sign telling you that settings will get lost and especially that SATA mode must set back to RAID _before_ reboot. That would have been enough...
|
Posted By: Xaltar
Date Posted: 02 Feb 2016 at 10:28pm
You can save your BIOS settings to disk and restore them post flash. When updating on a board connected to a RAID array it is advisable to disconnect the drives from the system then flash, restore your settings and only then reconnect them. I only mention this to avoid further irritation later on down the line.
-------------
|
Posted By: parsec
Date Posted: 02 Feb 2016 at 11:46pm
As a RAID user for many years, I'm sorry to say but it's RAID 101 material that after a UEFI/BIOS update, the FIRST thing you must do is get into the UEFI/BIOS and set the SATA mode to RAID.
When the PC restarts after an update to the UEFI/BIOS, a screen appears that DOES say the UEFI/BIOS settings have been reset to default values. This message is not in a large or colorful font, but it is displayed.
When the PC restarts after a UEFI/BIOS clear (Not an update but a simple clear), the same message as described above appears, warning the user that all the UEFI/BIOS options have been reset to their default values. You can easily test that yourself.
In BOTH of these cases, there is a timer running on the screen that gives us 15 seconds to press the Del or F2 keys, so we can go into the UEFI/BIOS UI and set any options we require, such as the SATA mode to RAID. Otherwise when the timer expires, the PC will then start booting, which the message on the screen clearly states.
So I must say that it is not true that there is no warning given about the options being reset to defaults after a UEFI/BIOS update or a UEFI/BIOS clear. There is the warning I described above, which we can see displayed if we simply clear the UEFI/BIOS.
To be fair to both sides of this question, the message displayed is in a small, un-warning like font that is obviously missed by some users. For those users that are not accustomed to the requirement of setting one or more UEFI/BIOS options after an update or clear, the current format of the warning message could be improved. This message has been in its current format for years, so it has not been made smaller or changed recently.
Personally, I use several non-default UEFI/BIOS option settings that I must reset after an update or clear. I'm not referring to OC option settings at all. I use non-default settings of the CSM option, the SATA drive type, and disable several hardware options, for example. For me, resetting options is standard work after an update or clear.
The discussion about what options should or can be left set to the users choice, can be argued from many perspectives, including that of UEFI/BIOS programmers. The old standard of setting all options to their default values may have its basis in realities of firmware programming that is still valid today.
------------- http://valid.x86.fr/48rujh" rel="nofollow">
|
Posted By: wardog
Date Posted: 03 Feb 2016 at 10:49am
parsec wrote:
The discussion about what options should or can be left set to the users choice, can be argued from many perspectives, including that of UEFI/BIOS programmers. The old standard of setting all options to their default values may have its basis in realities of firmware programming that is still valid today.
|
Agree. It's 101.
And to the above, considering resetting all back to Defaults, back in the day when you called into PAID Tech Support that going back to Defaults gave the Tech a place from where to begin. ie: as it left the factory
|
Posted By: LuckyStiff63
Date Posted: 09 Feb 2016 at 12:51am
@Pixel: I think lots of us have had things like this happen. I know I have created MANY problems for myself over the years, and when that happens, it definitely sucks! But hopefully the following things are true: 1. You had good backups so you didn't lose any data. 2. You have a better understanding of what to do (or not to do?) next time. 3. This thread might save someone else from the same fate, so thanks for posting.
I hope that array doesn't rake to long to restore...
- Lucky
------------- "I was just pondering the immortal last words of Socrates, who said: "I drank **WHAT?**" - Val Kilmer, as Chris Knight in "Real Genius"
|
|