[SOLVED] Upgrade 2.4 - 3.1 - Grub Rescue Error - Symbol 'grub_disk_native_sectors' not found - Truenas Core BHYVE

[stompro]

I attempted to upgrade my Proxmox Backup Server 2.4.x to 3.1 yesterday, and after the reboot it just comes up with the grub rescue prompt, with the error.

error: symbol 'grub_disk_native_sectors' not found.

I'm running it on a VM on a Trunas Mini - running Trunas Core (TrueNAS-13.0-U6.1), so using Bhyve to run the VM.

I've looked at https://pve.proxmox.com/wiki/Recover_From_Grub_Failure and tried various steps with no luck.

There are a few threads that reference that error that have suggestions, and I've tried those also.

Advanced Options - Rescue boot Errors out with
"error: no such device: rpool.
ERROR: unable to find boot disk automatically.
Press any key to continue...
"
and will not boot with rescue boot using the following ISOs,

• proxmox-backup-server_2.1-1.iso
• proxmox-backup-server_3.1-1.iso
• proxmox-ve_7.4-1.iso
• proxmox-ve_8.1-1.iso

I can get in doing a debug install boot, and using the second , which let me try the steps from https://pve.proxmox.com/wiki/Recover_From_Grub_Failure

I mounted the drives, chrooted and updated and installed grub to sda

I don't think I did anything strange when I setup the device, but my memory may just be faulty.

I'll add in the disk setup info when I have a chance.

Any suggestions of where to look next?

 

[stompro]

Another Note, I purchased a community subscription for Proxmox Backup Server and enabled it at the same time I upgraded. I upgraded to the latest 2.4.4 first.

But I didn't reboot after upgrading to 2.4.4, just went on to the 3.1 upgrade steps at
https://pbs.proxmox.com/wiki/index.php/Upgrade_from_2_to_3

 

[stompro]

The error message seems to be because a function was renamed in grub in December 2020.
https://git.savannah.gnu.org/cgit/grub.git/log/?qt=grep&q=grub_disk_native_sectors

So something must be out of date.... or the wrong library is being used.

 

[stompro]

Resolved, I found a nice guide for Debian guests on freenas / Bhyve and common issues.

https://prezu.ca/post/2021-07-28-debian-on-truenas/

Copying solution here in case that goes away.

1. Download the Debian Minimal NetInst IOS - I used debian-12.4.0-amd64-netinst.iso
2. Adjust VM VNC device to 800x600 res to fix a display issue. You can change that back later.
3. Boot into Rescue mode using the debian iso.
4. Use the option "Force GRUB installation to the EFI removable media path:" - That seems like it fixed the issue.

So the EFI removable media path must have had the old version of grub.

I really hope this helps someone else.

 

[Twibby]

Resolved, I found a nice guide for Debian guests on freenas / Bhyve and common issues.

https://prezu.ca/post/2021-07-28-debian-on-truenas/

Copying solution here in case that goes away.

1. Download the Debian Minimal NetInst IOS - I used debian-12.4.0-amd64-netinst.iso
2. Adjust VM VNC device to 800x600 res to fix a display issue. You can change that back later.
3. Boot into Rescue mode using the debian iso.
4. Use the option "Force GRUB installation to the EFI removable media path:" - That seems like it fixed the issue.

So the EFI removable media path must have had the old version of grub.

I really hope this helps someone else.

THANK YOU
After 2 days searching this saved me

 

[Kelu]

Resolved, I found a nice guide for Debian guests on freenas / Bhyve and common issues.

https://prezu.ca/post/2021-07-28-debian-on-truenas/

Copying solution here in case that goes away.

1. Download the Debian Minimal NetInst IOS - I used debian-12.4.0-amd64-netinst.iso
2. Adjust VM VNC device to 800x600 res to fix a display issue. You can change that back later.
3. Boot into Rescue mode using the debian iso.
4. Use the option "Force GRUB installation to the EFI removable media path:" - That seems like it fixed the issue.

So the EFI removable media path must have had the old version of grub.

I really hope this helps someone else.

Thanks a lot, this workaround fixed the issue for me as well. I experienced the issue after upgrading from Proxmox 7 to Proxmox 8, following the wiki step-by-step - but even with no warnings or errors in the status report, the system failed to boot after doing the major apt dist-upgrade followed by a reboot.