How Update BIOS?

If you are currently already on bios 1.22, but have trouble updating to 23, I suggest you stay on 22.  the new updated features on 23 may have no relevance to you.  what is worse is that latest bios may have bugs and could potentially brick your motherboard.  Update bios only when absolutely necessary, such as a new microcode released after the last version in order to support a new cpu.  Bios 22 already has all you need. No need to heed Dell recommendation of urgent bios update.  Many users had gone there and bricked their PCs.

I am on BIOS 1.4.9.  This is a used box.  Looking back into Journalctl -xb, I found that my BIOS is bad anyway:

Jul 06 18:30:24 server_f.project33.ca kernel: MAR: [Firnuare Bug]: No firnuare reserved region can cover this RMRR [0x00000000dd800000-0x00000000dfffffffl, contact By
Jul 06 18:30:24 server_f.project33.ca kernel: DMAR: [Firmware Bug]: Your BIOS is broken: bad RuRR (0x0000000OdaB00000-0x0000000OdfffffffI
                                        BIOS vendor: Dell Inc.: Ver: 1.4.9: Product Version:
Jul 06 18:30:24 server_f.project33.ca kernel: DMAR-IR: IOAPIC id 2 under DRHD base Oxfed91000 IOMMU 1
Jul 06 18:30:24 server_f.project33.ca kernel: DMAR-IR: HET id 0 under DRHD base Oxfed91000
Jul 06 18:30:24 server_f.project33.ca kernel: DMAR-IR: Queued invalidation will be enabled to support »Zapic and Intr-remapping.
Jul 06 18:30:24 server_f.project33.ca kernel: DMAR-IR: Enabled IRQ remapping in xZapic mode
Jul 06 18:30:24 server_f.project33.ca kernel: x86/cpu: SGX disabled bu BIOS.
Jul 06 18:30:25 server_f.project33.ca kernel: sd 0:0:0:0: Lsdb] Mo Caching mode page found
Jul 06 18:30:25 server_f.project33.ca kernel: sd 0:0:0:0: Lsdb] Assuming drive cache: write through
Jul 06 18:30:26 server_f.project33.ca systemdl11: Failed to mount /boot.
Jul 06 18:30:26 server_f.project33.ca systemd1]: Failed to start Crash recovery kernel arming.
Jul 06 18:30:26 server_f. project33.ca kernel: device-mapper: core: Cannot calculate initial queue limits
Jul 06 18:30:26 server_f.project33.ca systemdl1l: Failed to start LUM event activation on device 8:2

So now I literally cannot boot and need to get a new BIOS in there.  Can you recommend a version that's stable?

Well I flashed 1.23.0, which worked.  Same OS problem though.  

Cheers

do you think it is not a bios version issue but motherboard?  can you still use the pc?

Helps to have a little more detail if booting from OS isn't working.

• What OS is being attempted?
• Does PC past POST or does screen stay black, or are you getting BSOD?
• Booting from HDD, SSD, or flash drive?  If SSD, please mention type.
• Does the power light stay white or flash a sequence in amber?

The feedback was about BIOS but I'm still facing similar issues.  Not had time to investigate.  Will post when I know.  I will say that the onboard NVME M.2 drive has me seeing speeds I've never seen before.  This is on a headless server (AlmaLinux), which is fantastic. 

Again, will report more soon.  Seems more questions as well.  

Answers:

AlmaLinux 8.6, not a month old, minimal scripts, nginx and postgres (non-db)/psql.  

I'm getting an LMU error.  Past other OS-level stuff...

Here is my Stack post on the matter: https://unix.stackexchange.com/questions/708904/linux-boot-problem 

Booting from wonderfully working NVME M.2 drive.  But, I must say, I've upgraded BIOS version from 1.4.9 to 1.23.latest. Still no difference even after Dell forums warnings about bricking.  No brick.  

The NVME is a Samsung VV1.  Brand spanking new.  

Power light green.  Been non-indicative.  Also, it's broken with regards to startup and/or shutdown/reboot.  

Got it working.  Format the USB drive to FAT32 not exFAT.