Bios Settings Not Saving After Power Loss

[DaveEmb]

We had an issue with a defective UPS which caused a power outage. We have a 3 node cluster running 8.1. After the power loss, one of the nodes bios settings changed to the defaults. This enabled secure boot. When I disable secure boot and save the settings, the settings don't save when the node is power cycled. It's not the hardware because I put the nvme drive in a new identical server and the same issue occurred.


I suspect that one of the UEFI boot partitions may be corrupt after the power issue. Can the UEFI partitions be checked and repaired?

 

[gfngfn256]

When I disable secure boot and save the settings, the settings don't save when the node is power cycled

This looks like a BIOS issue. Do any (other) settings save themselves in BIOS when power-cycling?

I suspect the issue is the way you are making the change/s in the BIOS.
IDK what your HW/BIOS is but for example see here.

 

[gfngfn256]

Can the UEFI partitions be checked and repaired?

You can view the currently configured ESPs and their state by running:

proxmox-boot-tool status

Source PVE wiki. There you will also find all the info for repair/install of EFI System Partitions.

 

[DaveEmb]

Once you power cycle it, the settings change back to the defaults.

 

[_gabriel]

secure boot state is saved in the BIOS itself,
not on physical storage disk.

 

[gfngfn256]

Once you power cycle it, the settings change back to the defaults.

I assume you to mean ANY setting in the BIOS doesn't withstand a power-cycle (my question).
So you see this issue is BIOS related. As I've already pointed out (above) one of the most common issues is the method you are entering the BIOS from boot. (For instance on the above-mentioned HP you must enter the BIOS by hitting the F10 key, NOT the F12 to be able to correctly save settings). Other possibilities that may hinder saves include Secure Protected BIOSs , also check that there is a working CMOS BIOS battery present.

 

[leesteken]

After the power loss, one of the nodes bios settings changed to the defaults. This enabled secure boot. When I disable secure boot and save the settings, the settings don't save when the node is power cycled.

That's usually a empty CR2032 battery on the motherboard.

EDIT:

The new batteries resolved the issue.

 

[DaveEmb]

That's usually a empty CR2032 battery on the motherboard.

It's new hardware (3 months old). I also tried the nvme boot drive in a new box as well, and the results are the same. So not the battery..
I suspect there an issue with the boot partition.

Device Start End Sectors Size Type
/dev/nvme0n1p1 34 2047 2014 1007K BIOS boot
/dev/nvme0n1p2 2048 2099199 2097152 1G EFI System
/dev/nvme0n1p3 2099200 1000215182 998115983 475.9G Linux LVM

 

[gfngfn256]

I refer to my earlier post above, which I believe confirms that NO BIOS settings are retained, yet the OP insists that nothing is wrong with the server's BIOS HW. This I fail to understand at all. If you can't save ANY BIOS settings - first deal with that. I don't care how many "Boxes" you've tried with that NVME! If that "new box" is like the first one, they both probably have no CMOS battery installed! (Sometimes there is a battery present - but it has a plastic foil resistive material that needs removing to make contact - you better check). Get your multimeter out & check that battery for its correct voltage. Don't have a multimeter handy? Replace the battery with a NEW one!

Does the BIOS retain the time?

Using a different OS (find a disk lying around) - can you then make BIOS save its settings? (Wouldn't make sense - but if you don't trust help - & you shouldn't always - give it a try!)

You may also be dealing with a corrupted BIOS due to power-loss.

 

[DaveEmb]

I would like to thank everyone for their support and suggestions. Learned a few new things today, but still trying to figure out what is going on.
I tried the following:
1. Reformatted and installed Win 11.
2. Updated the BIOS.
3. Disabled Secure Boot and saved settings.
4. Went back into the BIOS before shutting down and removing power. Secure boot was still disabled.
5. Booted into windows, Shutdown The system, Removed Power Cord.
6. Connected the power, Started the system, Went into Bios Settings and Secure Boot is Enabled.
7. Stay tuned, Sent an email to the computer manufacturer. Minisforum NPB6

 

[DaveEmb]

I found that the bootmgr settings are different on the host (prx11) with issues. Not sure how to make changes so it is the same as prx12

prx11:
root@prx11:~# efibootmgr -v
BootCurrent: 0001
Timeout: 1 seconds
BootOrder: 0001
Boot0001* UEFI OS HD(2,GPT,f8fba1c0-f013-4034-b80c-40330c121549,0x800,0x200000)/File(\EFI\BOOT\BOOTX64.EFI)..BO

prx12:
root@prx10:~# efibootmgr -v
BootCurrent: 0002
Timeout: 1 seconds
BootOrder: 0002,0003
Boot0002* proxmox HD(2,GPT,ef808f61-9a0b-4a1e-b9f4-efbf8408131d,0x800,0x200000)/File(\EFI\proxmox\grubx64.efi)
Boot0003* UEFI OS HD(2,GPT,ef808f61-9a0b-4a1e-b9f4-efbf8408131d,0x800,0x200000)/File(\EFI\BOOT\BOOTX64.EFI)..BO

 

[DaveEmb]

These are new machines, but it looks like they had a bad batch of batteries. Support is sending out replacements. I was able to confirm that they only read 1.1 v on my Multimeter. So 2 out of the 4 machines have bad batteries. I will post an update once they are replaced.

 

[DaveEmb]

The new batteries resolved the issue.

 

[gfngfn256]

Good. Anyway looks like your issue is solved. Maybe tag mark the thread-title with [SOLVED], (upper right hand corner under title).