Error: symbol 'grub_disk_native_sectors' not found

TrueNAS General
1

Hi,

i restarted my TrueNAS Scale Dragonfish-24.04.2 and i was met with the following error:

error: symbol ‘grub_disk_native_sectors’ not found

Fortunately this is my secondary Truenas server that i use for disaster recovery and snapshot replication target, so my main Truenas instance is still running.

I do not have a backup file for this secondary server so i cannot simply reinstall Truenas and restore pool.

But i have my main servers config and the servers should be almost identical in configuration, only the IP should be different, and of course “Periodic Snapshot Tasks” and “Replication Tasks” are different.

So question is, should i be able to use the main servers config to restore pool on 2ndary?

Any hope of fixing grub? Or should i just cut my losses and just reinstall and config everything from scratch?

2

You should be able to re-install the OS and then import the pool manually

3

I would not.

Now you know you should maintain one.

Fixing GRUB would be best done by reinstalling TrueNAS on a new boot drive or on the same boot drive.

If you can access the files on the old boot drive, see if you can recover /data/freenas-v1.db and /data/pwenc_secret as these are the configuration files.

It may be easier to just reconfigure from scratch, it depends. But your pool should be in-tact.

4

I booted from truena scale installation media, went to CLI

From commandline:

zpool import -f boot-pool
zfs list
mkdir /mnt/boot
mount -t zfs boot-pool/ROOT/24.04.2 /mnt/boot
cd /mnt/boot

I can see the folders, but unfortunately the /data folder seems to be empty, infact most folder seem empty, some files in var/log/

Guess i will just reinstall Truenas and go from there.

5 
zfs mount boot-pool/ROOT/24.04.2/data

Found em!

working via IDRAC so cant copy/paste, but files are:
crash
dhparam.pem
factory-v1.db
freenas-v1.db
manifest.json
pwenc_secret
eula…
user-services.json
zfs

ill try to figure out how to get these files via IDRAC…

6

You should only need the two files I specified

7

Alright, so i just reinstall to boot-pool and and replace those 2 files?

8

Reinstall TrueNAS and then have those two files somewhere and use Manage Configuration and Upload File to restore your configuration. I have never just copied them into the boot drive directory, that may work but the GUI is much easier.

9

Successfully restored system! Thank you!

I guess i really didn’t need the “pwenc_secret” file, since i don’t have encrypted data shares?

I only restored the .db file via GUI (did try adding the other file to there as well but only .db files were allowed) and everything seems to work, except some certificate issue so HTTPS isnt working ( Web UI HTTPS certificate setup failed.), looking into that next.

Also would like to find out why the boot-pool failed in the first place, since the disks seem fine, and i saw no issue before reboot.

10

Did you do anything with the system in the time leading up to the failure?
Update the zfs feature flags for example?

11

No, zero changes to server after i upgraded it to 24.04.2 form 23.10.2.

I actually did eventually find a backup file for this server which i took before upgrading to 24.04.2:

truenas02-TrueNAS-SCALE-23.10.2-20240729145752

After this i have done zero changes to the server, i just rebooted and was welcomed by error: symbol ‘grub_disk_native_sectors’ not found error.

12

That is normal as I am aware. If the files exists then it will load it. I’m not sure what happens if the file does not exist, I have not been willing to test that out.

Glad you were able to recover.

You may never know this answer but you have been asked a few questions, I seem to focus on the hardware so what exactly is the make/model of the boot drive? What is the connectivity of the drive to the machine? And what are the rest of the machine specs (Motherboard/RAM/CPU)?

Cheers

13
  • Dell PowerEdge R730
  • 2 x Intel(R) Xeon(R) CPU E5-2660 v3 @ 2.60GHz
  • 256.00 GB RAM (16x16GB, i believe it is some dell branded stuff)
  • Boot-pool:
  • disk1: SanDisk SSD SAS 372.61 GB (LT0400MO)
  • disk2: Seagate HDD SAS HDD 10K 600 GB (ST600MM0088)

Disks connected via: Dell HBA330 Mini it-flashed.

Funny enough, i just found out that the SSD drive in boot-pool has hand-written note on it “broken!” :smiley:

Still it seems to work… and has worked for 2 years now.

IDRAC:

Remaining Rated Write Endurance 91%
Failure Predicted No

Guess i will replace boot disks, just in case.

14

I’m not sure I comprehend what you wrote. Let me tell you what I think you wrote. Communications are key so it is best to make sure we understand each other.

You have a significant computer which has two CPUs and 256GB RAM (that is a lot).

Here it the part I do not comprehend: You have only two drives in the system, one is 400GB SSD, the other is 600GB.

Why am I confused? Those are very small drives for a system with so much memory. If these are the only two drives then it strikes me as odd.

Then you say “boot disks” which implies more than one disk.

Are you mixing drive types in a mirror boot-pool? It is not forbidden but it is different and I don’t know if it could be problematic.

But I did understand this. I too have held on to a drive that failed and then accidentally put it back into a system. But my failure would not allow the drive to be used at all.

15

The 2 disks mentioned are part of the “boot-pool” which is are mirrored for redundancy and only Truenas Scale is installed on those disk and nothing else. I didn’t mention my other disks/pools, since those i don’t have issues with.

In addition i do have:
6 x 1 TB WD Red SSD’s in 3-way mirror for “vm-data” dataset for fast storage
8 x 600 GB Seagate HDD SAS HDD 10K disks in RaidZ-2 for “backup” dataset.

I got the server from my work place when it was decommissioned. It was used for Virtual Desktop Infrastructre (VDI) setup previously, which is why it had so much RAM, which is now perfect for my ZFS cache :slight_smile:

The “boot-pool” did originally have 2xSanDisk SSD SAS 372.61 GB (LT0400MO) disks, but one of them broke over a year ago and i didn’t have any other spare 2.5" drives other than the 600GB SAS HDD to replace it with.