Discuss, seek assistance, and report issues related to hardware components, such as hardware platforms, memory, network ports, power supplies, UPS systems, and so on.
I've suffered a couple of power cuts today due to works from the electric company.
Unfortunately, my F-423 unit doesn't want to boot any more. On coming back home I've found it powered on, but stuck on the BIOS banner.
I've dismounted the unit, removed all the RAM modules, the two NVME drives. I remove also the battery (I checked it with a meter, the voltage is correct) and shortened the battery holder contacts to force the CMOS reset.
Nothing has worked: the unit does regularly beep and displays the BIOS banner, but I can't get into the BIOS, nor it tries to boot from my disks. Removing the two disks produces the exact same effect. I am at lost, I seem to remember that something similar occurred some months go due to an involuntary power cord (I pulled the wrong power cable), but after having done the reset etc the system decided to restart after a while.
This time seems to be different, and I don't know what else to do. I am attaching the photo I've taken to the display showing the BIOS banner, and no, the unit is surely out of warranty (more than 2 years since I purchased it).
Hi thanks for you answer. I'll do it later when I am back home.
Just to be sure: when you write "press power button", do you mean maintaining it pressed until I hear the three beeps? I tried to boot with no M.2 disks, but I didn't remove the disks from the slots (they have not OS onboard), and the system booted with the single beep and then stopped at the banner as I wrote.
On clearing the CMOS the first boot takes quite some time before emitting the first beep and then trying to enter the BIOS, I assume also this behavior is normal.
I'll tell you later if your trick solves the issue, thanks again.
You don't need to hold down the power button continuously; simply press the power button to start normally. Under normal circumstances, when all hard drives are removed and you turn on the computer, you will first hear one beep, followed by three beeps. Looking forward to your feedback.
To contact our team, please send email to following addresses, remember to replace (at) with @
I had the unit unplugged from the power brick the whole day, and I don't know if this sole fact has made the difference. Matter of fact, I proceeded as you've indicated, removing all the disks (M2 and SSD), and I powered on the unit. After the usual beep, this time the <DEL>... <ESC> message was finally visualized, and after the configured wait time the boot process jumped into the EFI BIOS, as there were no disks to boot from. Great (but no three expected beeps)!
I've rebooted and I've entered the BIOS settings. Strangely enough, I was asked to enter the BIOS password I did set previously, and the BIOS settings were exactly the same I left configured. Puzzling, as I did remove the backup battery for half an hour, short circuited the battery holder contacts for way over 10 seconds, and still all the settings were there. The only thing that was not up to date was the BIOS time, reset to beginning of 2020.
I then shut down one more time the unit and put back all the disks. Power on, boot, the OS loaded like nothing occurred. And so yes, the unit is back online! Which is great, but still leaves open a number of questions:
1) As I wrote initially, the issue arose after two short power failures due to the electric company. I've had recently (a couple months ago) another power accident, this time it was me pulling the wrong power chord. Is the F-423 particularly sensible to unexpected power losses? Does it get confused to the point only a inducted hard reset (pulling away all the disks, the battery, etc.) is able to cure the unit? Granted, the first time I was able (incidentally) to recover just because I did remove all the disks. This time I thought it was not necessary to remove the disks from the bays, but you've proven me wrong.
2) I've never heard the expected three beeps: the unit beeped once as expected, and then continued directly to BIOS boot.
3) Pulling the battery and shortening its holder's contacts eventually does not fully reset the CMOS. I can't otherwise understand why the BIOS settings (and the BIOS password) were still in effect after many hours of being powered down.
Finally, unless you've already done so (and please forgive me if you did), it would be nice to have a troubleshooting guide resumed in a pinned post.
Thank you so much again.
PS: I do have an UPS protecting the devices, but either it did not last long enough, or its battery failed miserably.
When turning on, you can only hear a single beep sound, which is usually a boot system failure. You can refer to this post to recreate the boot system: viewtopic.php?t=6433
To contact our team, please send email to following addresses, remember to replace (at) with @
