I tried updating my Proxmox / Debian to 13, due to Proxmox 8 losing support in August, but the machine fails to start.
I can chroot into the system, but not sure what I need to change.
Or should I do a clean Debian 13 installation then Proxmox?
Do you know what stage of the boot is failing?
Does it get past GRUB and boot the kernel? If not, you probably need to update your board firmware version (specifically U-Boot).
The older 2020.X U-Boot’s that we shipped on launch simply don’t work with more recent GRUB’s and kernels. You can try the “v0.9.1” testing version or the more recent development version. I’m planning to do a new formal release in July or August.
Besides that, Debian 13 (trixie) works fine by itself. I can’t recall the details 100%, but I did run into issues doing upgrades from 12 to 13.
It’s an sychronous abort after grub.
I’ve re-installed grub but it still persists.
Happy to grab the output.
I’m on v0.9.1, as I had the issue with pass-through and had to use that testing version.
Autoboot in 10 seconds, press 's' to stop and bring up boot menu
e7e[re[999;999He[6ne8Card did not respond to voltage select! : -110
mmc_init: -95, time 22
Missing TPMv2 device for EFI_TCG_PROTOCOL
e[?25le[2Je[1;1He[1;1He[2Ke[2;3H*** U-Boot Boot Menu ***e[0Ke[3;1He[2Ke[11;1He[2Ke[12;3HPress UP/DOWN to move, ENTER to select, ESC to quite[0Ke[13;1He[2Ke[4;7He[7mContinue standard boote[0me[5;7HBoot into recoverye[6;7HBoot OpenWrt from NANDe[7;7Hnvme 0:1e[8;7Hnvme 0:15e[9;7HU-Boot consolee[?25he[2Je[1;1HScanning for bootflows in all bootdevs
Seq Method State Uclass Part Name Filename
--- ----------- ------ -------- ---- ------------------------ ----------------
Scanning global bootmeth 'efi_mgr':
Hunting with: simple_bus
Found 0 extension board(s).
Scanning bootdev 'nvme#0.blk#1.bootdev':
0 efi ready nvme f nvme#0.blk#1.bootdev.part efi/boot/bootaa64.efi
** Booting bootflow 'nvme#0.blk#1.bootdev.part_f' with efi
Working FDT set to 90000000
TEN64: Using legacy fan device tree overlay
INFO: RNG Desc SUCCESS with status 0
INFO: result b947569645721828
Booting /efi\boot\bootaa64.efi
e[0;30;47me[?25hWelcome to GRUB!
e[0;37;40me[0;37;40me[0;37;40m"Synchronous Abort" handler, esr 0x8600000e, far 0x0
elr: ffffffff86368000 lr : 00000087663175f0 (reloc)
elr: 0000000000000000 lr : 00000087dffaf5f0
x0 : 00000087dfeff940 x1 : 00000000fb80f7bf
x2 : 0000000000000001 x3 : 0000000000000000
x4 : 0000000000000127 x5 : 000000877bf9f000
x6 : 000000000000012a x7 : 0000000000000002
x8 : 0000000000001000 x9 : 00000087dffc15d8
x10: 0000000000000ff8 x11: 00000000080a1840
x12: 0000000000000001 x13: 00000087dffb5338
x14: 00000000ffffffff x15: 00000000fb80f4ef
x16: 00000087dffa7030 x17: 0000000000000000
x18: 0000000000000000 x19: 00000087dfeff940
x20: 0000000000000000 x21: 0000000000000000
x22: 00000087dfeff940 x23: 00000087dfeff940
x24: 00000087dfd5a000 x25: 0000000000000000
x26: 00000087dfd5a000 x27: 0000000000000000
x28: 00000000fb911690 x29: 00000000fb80f740
Code: "Synchronous Abort" handler, esr 0x96000004, far 0xfffffffffffffff0
elr: 0000000082005bb8 lr : 0000000082005b98 (reloc)
elr: 00000000fbc9dbb8 lr : 00000000fbc9db98
x0 : 00000000fbd849bf x1 : 0000000000000000
x2 : 0000000000000020 x3 : 00000000021c0500
x4 : 00000000021c0500 x5 : fffffffffffffff8
x6 : 00000000ffffffc8 x7 : 00000000fb80f5d0
x8 : 0000000000000001 x9 : 00000000ffffffe8
x10: 0000000000000006 x11: 000000000001869f
x12: 0000000000000001 x13: 00000087dffb5338
x14: 0000000000000010 x15: 00000000fb80f34b
x16: 00000087dffa7030 x17: 0000000000000000
x18: 00000000fb817d70 x19: fffffffffffffff0
x20: 00000000fbd93000 x21: 00000000fffffffc
x22: 00000000fbd95efd x23: 00000000fbd849bf
x24: 00000087dfd5a000 x25: 0000000000000000
x26: 00000087dfd5a000 x27: 0000000000000000
x28: 00000000fb911690 x29: 00000000fb80f5d0
Code: d1004273 913bf6d6 aa0003f7 12800075 (b9400261)
UEFI image [0x00000087dffa6000:0x00000087dffc9fff] '/efi\boot\bootaa64.efi'
Resetting CPU ...
### ERROR ### Please RESET the board ###
Hmm, that is a weird one.
A couple of things to try:
1. Check that the partition table (primary and backup GPT)'s on your disk match.
You can use parted or a similar tool to do this.
I have seen similar fault traces before that were resolved by fixing the GPTs. This often happens if disk is cloned directly from a smaller to larger disk.
2. Wipe and Reinstall GRUB
It is possible that the ‘default’ GRUB version and Debian’s GRUB version are out of sync.
Normally Debian will install GRUB into /boot/efi/EFI/debian and use EFI variables to point the system there.
As Ten64 does not support EFI variables, GRUB needs to be installed in the “default” location at /boot/efi/EFI/BOOT
I think this is the most likely issue/solution, especially if you have upgraded in-place from an older Debian.
mkdir /mnt/root
mount /dev/nvme0n1p1 /mnt/root/
mount /dev/nvme0n1p15 /mnt/root/boot/efi
mount --bind /dev /mnt/root/dev
mount --bind /sys /mnt/root/sys
mount --bind /proc /mnt/root/proc
chroot /mnt/root
mv /boot/efi/EFI /boot/efi/_EFI # move the old versions aside
apt-get install --reinstall grub-efi-arm64
grub-install --removable
As a sanity check, you should have these files in /boot/efi before rebooting:
root@recovery000afa2424fd:/# ls -la /boot/efi/EFI/BOOT/
-rwxr-xr-x 1 root root 110 Jun 7 02:09 BOOTAA64.CSV
-rwxr-xr-x 1 root root 987432 Jun 7 02:09 BOOTAA64.EFI
-rwxr-xr-x 1 root root 117 Jun 7 02:09 grub.cfg
-rwxr-xr-x 1 root root 2856384 Jun 7 02:09 grubaa64.efi
-rwxr-xr-x 1 root root 887472 Jun 7 02:09 mmaa64.efi
3. Wipe the u-boot variables/settings
The output just before the GRUB handover looks slightly different to what I get, so I think this is worth a try:
# From the recovery environment
mtd erase ubootenv
reboot
What I normally see is this:
Scanning bootdev 'nvme#0.blk#1.bootdev':
0 efi ready nvme f nvme#0.blk#1.bootdev.part efi/boot/bootaa64.efi
** Booting bootflow 'nvme#0.blk#1.bootdev.part_f' with efi
Working FDT set to 90000000
TEN64: Using legacy fan device tree overlay
Card did not respond to voltage select! : -110
mmc_init: -95, time 21
Missing TPMv2 device for EFI_TCG_PROTOCOL
INFO: RNG Desc SUCCESS with status 0
INFO: result e73f500e47e6d347
Booting /efi\boot\bootaa64.efi
Failed to open efi\boot\console=ttyS0,115200 - Not Found
Failed to load image ?�: Not Found
start_image() returned Not Found, falling back to default loader
Welcome to GRUB!
DPMAC7@qsgmii Waiting for PHY auto negotiation to complete......... TIMEOUT !
DPMAC7@qsgmii: Could not initialize
....
GNU GRUB version 2.06-13+deb12u1