Tekkie

While I have no data to challenge that, I don't understand how everything works fine, an update is processed, then it doesn't boot correctly. The self-checks (POST) are successful and it can boot to other operating systems, so I can't see a hardware issue. The point in which it hangs is when the bootloader should appear and count down for a few seconds before loading Unraid normally. The fact it works if I go through a boot menu in BIOS does suggest it's not software, but the fact other operating systems work and even Unraid worked prior to an update suggests it is software. It's a weird conundrum. I do use Firefox and also experienced the 'resend data' popup previously mentioned by @humpe. I clicked cancel per their recommendation and all is now stable again.

Since the normal boot cycle didn't work, I went into the BIOS to make sure that still worked. It did, so I went over to the bootable devices it sees and selected the 'Boot Menu' option and then pushed enter on the flash drive with Unraid (the only device listed). I was then taken to the bootloader menu where I selected to load Unraid OS (normal option). It then booted up just fine. I'm too scared to restart it and try booting normally because it doesn't make sense that it would work that way but halt the system when booting normally. I wanted to share my findings in hopes that it may help someone in the future, but also in case someone has any ideas regarding what's happening here. The hardware is all new and high-end; it was running for about a month without any issues at all. I will also note that @JorgeB was correct that a reboot would fix it (after breaking it), as the 'Main' page now correctly shows usage per disk:

I turned the server off, let it sit for a moment, then turned it back on. The ASUS logo displays as it POSTs and then the screen goes black. NumLock is unresponsive. The server hangs immediately now! 😳😵 Concerned is an understatement. What do we do when all we get is a black screen? This is embarrassing and frustrating downtime.

That did not work for me and rendered the server unbootable, though I've still not gotten back to having physical access to it to investigate further. The restart after the update worked, but the subsequent restart did not. I also had this issue and found that if I clicked cancel, it appeared as if nothing happened. I click resend and then saw changes on the page and thought that's what made it go through. I'll test this when I get the server back up, as it was taken offline by restarting the second time. I do hope it's nothing major preventing it from booting. Everything was stable and working well prior to the update. The only reason I updated was because of the banner at the top that persistently told me there was an update to apply. Don't fix what isn't broken!

Thank you for your time on this. I was very excited to hear that this was such a quick fix. Unfortunately, I restarted the server and it did not come back up. I am told there is a solid bright white LED displaying on the motherboard, so I suspect something is now wrong and preventing it from booting. I am not at the machine, so I will have to investigate later. I was able to restart it just fine after the update recently, so I'm not sure why it won't boot now.

Thanks in advance for reading this. I'm hoping it's a quick fix. After restarting the server following an update from 6.11.5 to 6.12, I manually started the array as it doesn't come back automatically. I then started all of the docker containers again, as they didn't start automatically. No worries with that. I noticed, however, on the "Main" page that I can no longer see the usage per disk. I now see "Unmountable: Unsupported or no file system" for my drives. It's worth noting that the Docker containers are running and I can play media through Plex, so it appears to be working. The only difference is the error that has taken the place of the used/free space for each drive. Diagnostics are attached, as well as screenshots showing the before and after of the array, the array status showing all is well, and the array operation area. Before: After: Array Status: Array Operation: Diagnostics: unraid-diagnostics-20230618-1610.zip