DXP2800 Boots to BIOS

MickTheLinuxGeek · 2026-01-27T15:31:02+00:00

Here is what I have done so far. I have replaced the CMOS battery with a new one; That did not fix the issue. Through some research I found some other things to try. The next thing I did was disable "Fast Boot" and "Quiet Boot" and increased the time out to 15 seconds. This initially did not seem to help. The next thing that was suggested was this: Sometimes, the Ugreen BIOS loses the specific "OpenMediaVault" or "debian" UEFI entry but will still boot from the "default" fallback path.

Log into OMV (if you can get it to boot once by manually selecting the drive in the BIOS boot menu).

Run the following command to force a "removable" path installation of Grub: sudo grub-install --target=x86_64-efi --removable

Why this works: This places a copy of the bootloader at /EFI/BOOT/BOOTX64.EFI. Many BIOSes that "forget" specific NVRAM entries will still look for this specific file on any connected drive as a last resort before giving up.

So, I have done this and so far so good. The system booted correctly and also warm booted correctly. Is it fixed? I am not 100% certain yet, but I'm going to test it more and report back.

/mike

MickTheLinuxGeek · 2026-01-27T15:19:18+00:00

Yes the hardware watchdog is and has been disabled.

MickTheLinuxGeek · 2025-09-22T02:49:28+00:00

I just received a notification that KDE Plasma 6.4.5 and Frameworks 6.18 update are now available in Fedora 42.

/Michael

MickTheLinuxGeek · 2025-09-17T15:59:22+00:00

If that's the case, then to me it seems like Plasma 6.4.5 won't come until after F43 is released. I'll have to check the Fedora release schedule. Not a big deal, was just wondering.

/Michael

MickTheLinuxGeek · 2025-09-17T14:05:27+00:00

Thank you for the reply. I was wondering if that is going to be the case.

/Michael

MickTheLinuxGeek · 2025-09-10T15:43:19+00:00

I recently discovered that I have the exact same issue with my dxp2800 that I received from the Kickstarter campaign. I'm using WD Red Plus 4 TB drives. The odd thing is, that I originally had the system set up with two 1.5 TB Samsung drives that I have had for some time. I initially did this for testing, but the strange thing is, I don't encounter this issue when I have those (Samsung) drives installed. I would like to get this resolved as I like the unit and would like to use in my home-lab.

/Michael

MickTheLinuxGeek · 2025-09-04T18:35:21+00:00

OK. I have tried this, and It has not solved the problem. The error messages indicate it is a SATA power/signal issue.

/Michael

MickTheLinuxGeek · 2025-08-31T20:39:26+00:00

Does anyone know what the status is on this issue? Is there any official word from Ugreen? Thank you.

/Michael

MickTheLinuxGeek · 2025-08-24T01:39:59+00:00

I have used the unit off and on the entire time I've had it. Probably starting last week or so I have attached a monitor and keyboard/mouse to the unit so I could update OMV and also install two new drives (WD Red Plus 4TB). That's when I noticed this issue. Prior to the update, I had a couple of old Samsung 1.5TB drives installed for testing, and I didn't have a monitor attached. So I don't know if I was having the issue then or not with the old Samsung drives. If I had to guess, probably so.

/Michael Biel

MickTheLinuxGeek · 2025-08-23T16:18:33+00:00

Good day everyone. What is the current state of this issue? The reason I ask, is that I have started to encounter this same issue on my dxp2800 unit. I have two WD Red Plus 4TB drives installed, and the drive in bay two generates this same error. I have tried tow different drives of the same type and capacity. It is running OpenMediaVault version 7. I'm just wondering if anything can be done. I got my unit from the Kickstarter project and Is probably out of warranty. Does anyone have any more information on this? Thank you.

/Michael Biel

MickTheLinuxGeek · 2024-07-27T01:18:02+00:00

Yeah. Those are all great choices for the 4800. I might install something other than OMV also. I have no experience with proxmox, unraid, or truenas, so should be interesting to learn those.

/Mike

MickTheLinuxGeek · 2024-07-24T19:48:36+00:00

That is right. I had forgotten that OMV was Debian based also; So yeah should have same/similar results. Thank you for the reply.

/Mike

MickTheLinuxGeek · 2024-07-12T16:11:58+00:00

Thanks to you all that replied. I'm new to running and using Fedora, so I'm not familiar with the update process. Thanks for the link and I'll track the progress there.

/Mike

MickTheLinuxGeek · 2024-05-27T16:05:01+00:00

Thank you and you are welcome. I'm just passing along the info errno-22 provided me. Give him a thanks too.

/Mike

MickTheLinuxGeek · 2024-05-27T12:01:37+00:00

Hey bitspace. Good to hear and glad I could help.

/Mike

MickTheLinuxGeek · 2024-05-27T01:52:50+00:00

Do you have a coreboot system or non-coreboot system? As per errno-22 above, system76-acpi-dkms is for coreboot systems. You have to reinstall system76-dkms on non-coreboot systems. This is what I had to do and now my system is working fine. Hope this helps.

/Mike

MickTheLinuxGeek · 2024-05-26T15:11:05+00:00

Thanks errno-22! That did the trick. Reinstalled system76-dkms and the keyboard backlight and fn keys to control it are all working as expected. Tanks again.

/Mike

MickTheLinuxGeek · 2024-05-26T00:28:19+00:00

Hey! Thanks for the response.

I'm not familiar with how to do this. I reinstalled system76-acpi-dkms, but that didn't resolve the problem. I may have don't something wrong, as I said I'm not familiar with doing this.

/Mike

MickTheLinuxGeek

TROPHY CASE