TrueNAS 12.0 U8 no longer boots with "missing boot loader" error

TrueNAS General
1

I have a simple TrueNas 12.0 U8 server that boots from a NVME and then mounts several disks on an LSI controller for my data. Long story short, I decided to install an additional SSD for VM storage on one of the motherboard SATA ports. Well this disk had an existing windows 11 install on it. I failed to wipe it first and the system then decided to boot from that drive instead of my NVME. I shut down the mistaken booted win 11 desktop and changed the boot order and now I get “missing boot loader”. I even disconnected the SATA drive and still get this error. I have since created a 12.0 U8 USB drive and can boot to a console, but I don’t want to mess anything up since I think I just need to somehow recreate the UEFI boot. I would just reinstall the system, but my only config backup I can find is about 10 months old, and I have made quite a few changes in that time. Hoping someone knows what I need to type to get the system booting again. Thank you so much in advance for the help.

P.S. I took a picture of the console with a few commands ran to show partitions, but I can’t seem to post them here.

will try to attach a google drive shared picture if possible

2

Hopefully this will work for the picture I am looking at currently..

20260814_214359
20260814_2143591920×1440 671 KB

3

Browse some other threads and do the Tutorial by the Bot to get your forum trust level up and post images and links. I edited post above to add image

TrueNAS-Bot
Type this in a new reply and send to bring up the tutorial by Direct Message, if you haven’t done it already.
@TrueNAS-Bot start tutorial

4

@TrueNAS-Bot start tutorial

5

I am back up and running. I struggled a bit but was able to boot up an Ubuntu live USB/CD and mount the ZFS boot-pool on the NVME to copy the freenas-v1.db file out of the data folder. Then booting the TrueNAS 12 installer and running the upgrade option said it would recreate the bootup but failed saying my volume was corrupt. So the upgrade and then format option did the trick and everything looks like its back to normal. It even backed up my config and copied it back. Just had cold feet moving forward, but it was pretty easy. Thanks..

6

You really should not be running a system that is EOL since 2022.