Boot errors (UEFI unauthorized changes, or not boot disk)

TrueNAS General
,
1

I’m getting the “the system found unauthorized changes on the firmware, operating system or UEFI drivers” when I attempt to boot.

Forcing my way into the BIOS, I find all the drives I expect (6 6TB data drives, two SSD drives one of what is boot and one of which was intended to be a cache drive but that never quite happened).

Booting from either of the SSD drives I get “This is a FreeNAS data disk and can not boot system. System Halted.”

My latest config backup says it’s of TrueNAS-13.0-U5.3. I’m reasonably sure that’s essentially current, haven’t added users or changed pools in some time.

I can of course try booting truenas or other OS from USB, and just try reinstalling (since I have the config backuip).

Is that likely to be my smart course? Is the motherboard config RAM battery likely to be the problem? Can I maybe reinstall in place and preserve the config info? What are my big dangers when I start clumsily poking my fingers into things?

My usual problem – I only run this one TrueNAS server, and it runs flawlessly for so long that I forget the details, not practicing them every week or month.

No reason to suspect any damage to the data set so far, at least. It’s annoying but not really serious for it to be out of service for days or even a few weeks (home environment).

2

Is secure boot enabled? Disable it in that case.

1 Like
3

Might have gotten enabled as the default config. I did try resetting BIOS to default, was thinking about maybe having lost the data due to the battery wearing out.

That’s easily checked, thanks for suggesting it.

4

I think that was the main problem, in fact – the default setting that I reset to included secure boot.

Weird stuff happened after that, but I’m fairly sure the weird stuff was unrelated to secure boot or BIOS parameters at all – it was video resolution issues, for video from a separate VGA card (no video on this motherboard). I resolved those by reinstalling TrueNAS, which worked fine (and that seems to me to confirm that whatever was going on with video resolution, it was not related to BIOS settings).

Anyway, the server is back up and running and I’m on to the next issue, updating my backup scheme and getting current backups.

(I lost most of a year to medical issues, during which I wasn’t lifting server boxes or crouching down on the floor or really doing much of anything. That’s resolved decently in my favor so I’m back to deferred maintenance catch-up!)