Your NAS has unexpectedly ceased functioning.
Your NAS has unexpectedly ceased functioning.
My server is acting up again after a restart. It was stable yesterday but now loops. I checked the monitor and saw the error image. I removed RAM until I had one stick left, tried all four sticks in each slot alone, and that fixed the issue every time it rebooted. After disconnecting and reconnecting all SATA/SAS and power cables, nothing changed. The BIOS is over 18 months old, so I updated it, but it still won’t boot to the Turanas Loader—it reboots before reaching the error screen. I’m unsure what’s causing the sudden failure now.
Disconnect every external storage except the operating system boot disk and check for startup. The quick search results indicate similar problems at https://github.com/openzfs/zfs/issues/13483.
Fun fact, I'm out now but just for fun—I'll get a new SSD for the boot drive. It might take about 30 minutes to get there.
I just installed a brand new 500gb SSD but it’s not working. After disconnecting power from all drives except the boot drive, I did another install and it still won’t boot. It shows up on a screen with repeated quick reboots. If I go to BIOS and enable boot override (since that’s the only drive), it jumps to this page and then back to BIOS in about two seconds.
Nothing seems to work, but I installed the original boot drive (M.2) in my gaming rig and it started up normally on Truenas. I’m going to try modifying it to see what’s faulty. Since my rig runs on hard water, I’ll begin with the power supply unit and hope that fixes the issue.
while working with vmware, i typically used compact usb drives about the size of a logitech bt mouse and keyboard. they offered 16gb storage, making it simple to boot and switch between them because the operating system’s location in memory doesn’t matter as long as it’s running.
I changed the boot drive and it didn't help. I also found another CPU in my storage area that I hadn't noticed before, but it didn't make a difference. That suggests the issue might be with the motherboard. I'm planning to test it again once I get some replacement parts to swap the CPU, because I don't want to take apart my main system without being able to reassemble it later. Since I've replaced the power supply and likely a good CPU, the remaining problem probably lies with the memory module.
It seems like the final step was skipped. I’d want to turn off certain settings in BIOS first, as they load the configuration file and then crash. There might have been recent updates that could trigger this issue—check for any patches or fixes related to boot stability. Also, verify that your clock is set correctly.
I attempted a BIOS update, but it didn’t work. It seems there’s no need to alter anything in the BIOS since it abruptly stopped functioning without any clear cause. I still went through the changes just to check for any random settings affecting it.