F5F Stay Refreshed Hardware Desktop PC startup problems and BIOS configuration challenges

PC startup problems and BIOS configuration challenges

PC startup problems and BIOS configuration challenges

A
Azastias
Member
223
07-17-2025, 08:16 PM
#1
Here’s a rephrased version of your text:

I’ve built a case with the following components: Jonsbo N5 CPU, AMD Ryzen 5 5600G, 2x8GB DDR4 RAM, Corsair Vengeance MOBO, ROG Strix B550, a 750W PSU from Seasonic Prime, Titanium OS on Windows 11, WD Blue SN550 1TB NVMe SSD, PCI card (HP H220), and a 6Gbps SAS PCIe 3.0 HBA in IT mode. The setup includes ten 3.5” drives ranging from 14TB to 22TB, two SSDs with 12x 120mm Noctua fans, and an HP H220 with six Mini SAS 36P cables. All drives are standalone, not mirrored.

I’ve noticed similar discussions in forums about this setup, but I needed more clarity on my issue and to check the CMOS settings. When I boot up, the system shows connected devices like HDDs and SSDs, and at the bottom it prompts me to set up BIOS recovery. During RAID configuration, I made sure SATA mode was selected. After running SETUP (F1), no RAID was enabled. The two SSDs and eight hard drives are plugged into the motherboard’s SATA ports; the remaining drives connect via HP H220 and Mini SAS cables.

I’ve tried changing the CMOS battery, removed the old one, reinstalled it, but the message persists. I also let the battery sit for a while before reinserting it. The PC still displays the same warning when I exit BIOS. After a short period without power, the time displayed resets to 00:00 on January 1, 2019.

I used a new Duracell CR2032 battery, which had a limited lifespan. Without a multimeter, I can’t verify the motherboard’s condition. Someone who helped me install broadband yesterday suggested it might be due to insufficient power reaching the motherboard. My build has a 750W PSU, which should provide ample capacity.

If I keep ignoring this issue and just press F1 to boot normally, will a faulty or dead battery eventually harm my system?
A
Azastias
07-17-2025, 08:16 PM #1

Here’s a rephrased version of your text:

I’ve built a case with the following components: Jonsbo N5 CPU, AMD Ryzen 5 5600G, 2x8GB DDR4 RAM, Corsair Vengeance MOBO, ROG Strix B550, a 750W PSU from Seasonic Prime, Titanium OS on Windows 11, WD Blue SN550 1TB NVMe SSD, PCI card (HP H220), and a 6Gbps SAS PCIe 3.0 HBA in IT mode. The setup includes ten 3.5” drives ranging from 14TB to 22TB, two SSDs with 12x 120mm Noctua fans, and an HP H220 with six Mini SAS 36P cables. All drives are standalone, not mirrored.

I’ve noticed similar discussions in forums about this setup, but I needed more clarity on my issue and to check the CMOS settings. When I boot up, the system shows connected devices like HDDs and SSDs, and at the bottom it prompts me to set up BIOS recovery. During RAID configuration, I made sure SATA mode was selected. After running SETUP (F1), no RAID was enabled. The two SSDs and eight hard drives are plugged into the motherboard’s SATA ports; the remaining drives connect via HP H220 and Mini SAS cables.

I’ve tried changing the CMOS battery, removed the old one, reinstalled it, but the message persists. I also let the battery sit for a while before reinserting it. The PC still displays the same warning when I exit BIOS. After a short period without power, the time displayed resets to 00:00 on January 1, 2019.

I used a new Duracell CR2032 battery, which had a limited lifespan. Without a multimeter, I can’t verify the motherboard’s condition. Someone who helped me install broadband yesterday suggested it might be due to insufficient power reaching the motherboard. My build has a 750W PSU, which should provide ample capacity.

If I keep ignoring this issue and just press F1 to boot normally, will a faulty or dead battery eventually harm my system?

P
Petzku1618
Member
181
07-17-2025, 08:16 PM
#2
It seems like the system might have a minor issue with a bit flip in the BIOS. Have you considered updating the BIOS to a newer version?
P
Petzku1618
07-17-2025, 08:16 PM #2

It seems like the system might have a minor issue with a bit flip in the BIOS. Have you considered updating the BIOS to a newer version?

D
Dryb1998
Junior Member
5
07-17-2025, 08:16 PM
#3
I might consider rebooting and refreshing the BIOS since the current version could be unreliable or problematic.
D
Dryb1998
07-17-2025, 08:16 PM #3

I might consider rebooting and refreshing the BIOS since the current version could be unreliable or problematic.