I have got a issue with my system It won’t reboot. My system got turned off by someone turned the system off at the plug rather the shutting it down properly and now it won’t reboot. It just says No bootable device. Strike F1 to reboot, F2 enter setup menu, F5 enter PSA.
I don’t understand it nothing has changed.
Anyone have any ideas? Am i going to have to reinstall the whole system?
If you press F2, then browse the BIOS screens, do you see your boot device?
I have experienced this. It was corruption of the GPT Partition Table.
Boot from a Linux Live flash drive, sudo gdisk /dev/sdx (where sdx is your boot drive) and see what it says about the partition table.
The backup partition table is likely OK and you can easily recover the master table from the backup one and save. Then try booting again.
P.S. The GPT partition table should only be written when changes are made, so I have no idea why it would get corrupted, but it has happened a couple of times on a hard power off.
Is there a video on how to do this please? I’m a novice when it comes to NAS and IT stuff.
Cheers
Not sure about videos, maybe, I’ve never looked for one.
But before you go about manually modifying the GPT table or similar, do you have a backup of any important data you may have on the NAS? Do you at least have a backup of the configuration file from TrueNAS?
If you encrypted your data pool and now accidentally lose the contents of your boot-pool you may permanently lose access to your encrypted data unless you have a full copy of the configuration-files or separately saved the encryption key(s) somewhere else.
If you didn’t encrypt your data it’s more of a nuisance to restore the settings manually but the data should be safe at least.
@Andrew_O_Keeffe has already lost access to the boot drive, so at this point it is impossible to backup your system configuration file. But @neofusion does have a point - once you have access back, you should implement @joeschmuck 's Multi-Report script so that you get an emailed copy of your configuration file once per week.
I was suggesting that you use gdisk to see whether the master GPT Partition table had been corrupted and if so to recover the master GPT Partition table from the backup GPT Partition table. I was NOT suggesting that they should “go about manually modifying the GPT table”.
If it is not a problem with GPT, then you may need to rebuild your boot drive and if you need to do this then it will be VERY helpful to have a backup of your system configuration to hand.
I understand that the boot-pool is unusable in it’s current state so it’s too late to make a backup at this point. The intent of my post was to put light on what’s at stake.
If it is the GPT master table that is corrupt, then recovering it from the backup table using gdisk is straight forward and unlikely to get screwed up (because the backup table should be an exact copy of the master table - so no need to enter the partition sector extents manually) - so not much at stake.
If it is NOT the partition table that is the problem, then likely to be much harder to recover.
@Andrew_O_Keeffe Since you have posted Log in issues at main screen can we assume that your boot drive is now working again?
And if so, it would be nice if you:
No I have not fixed this issue on this machine. I have two NAZ. The log in issue was with the another machine and I will always say thank you to people that have help me.
In answer to neofusion’s message no I don’t have a backup of either the data or the config. Am I right in thinking then that all my data is lost and I will have to reinstall trunas from the beginning again.
If it is not a GPT issue then it is possible that the boot disk is lost and you may have to reinstall - but in that case all other pools on other drives will still be useable.
If your system configuration was NOT stored on the boot drive, then you can probably import the old pool, and restore the system configuration from there.
But if you have to reinstall and you don’t have a system configuration backup, once you have imported the old pools, you will need to recreate all the other configurations (e.g. SMART, Cron, Snapshots, replications, shares, apps etc.).
