[SOLVED] after upgrade to PVE9 one Node stuck on Loading initial ramdisk

U

udo

Distinguished Member
Proxmox Subscriber
Apr 22, 2009
5,988
206
163
Ahrensburg; Germany
[EDIT]
My fault! There was still an "root=ZFS=rpool/ROOT/pve-1 boot=zfs" in the default-grub file due an prior installation on other Hardware without boss-card.
[/EDIT]


Hi,
this mornig I've upgrade 3 Nodes of an Cluster to proxmox-ve: 9.2.0 (running kernel: 7.0.14-8-pve).
On a Dell R6615 with Boss-Card (NVMe Raid-1) proxmox stuck at Loading initial ramdisk - even with the 7.0.14-8 kernel also with 6.8.12-39.
The Server had installed the actual BIOS during the upgrade process.

Rescue Boot with the pve 9.2 iso work fortunately.

I've tried :
update-grub
proxmox-boot-tool refresh (No /etc/kernel/proxmox-boot-uuids found, skipping ESP sync.)
grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=Proxmox --recheck

but without success.

Found a similiar issue, which was solved by downgrading grub to 2.06 from bookworm, but i think it's should work with the actual grub too.
I have some pve-nodes for upgrading left - also some with boss-card, so is very important for me that the issue was solved.

Some more Info about the disks:
1 Boot-Raid-1 with LVM, 4 NVMEs for zfs and one NVMe as ceph-osd
Code: 
lsblk /dev/nvme2n1
NAME               MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
nvme2n1            259:1    0 447.1G  0 disk
├─nvme2n1p1        259:2    0  1007K  0 part
├─nvme2n1p2        259:3    0     1G  0 part /boot/efi
└─nvme2n1p3        259:4    0   399G  0 part
  ├─pve-swap       252:0    0    64G  0 lvm  [SWAP]
  ├─pve-root       252:1    0    30G  0 lvm  /
  ├─pve-data_tmeta 252:2    0   2.8G  0 lvm 
  │ └─pve-data     252:5    0 279.3G  0 lvm 
  └─pve-data_tdata 252:3    0 279.3G  0 lvm 
    └─pve-data     252:5    0 279.3G  0 lvm 

# zfs
lsblk /dev/nvme0n1 
NAME        MAJ:MIN RM  SIZE RO TYPE MOUNTPOINTS
nvme0n1     259:13   0  2.9T  0 disk
├─nvme0n1p1 259:14   0  2.9T  0 part
└─nvme0n1p9 259:15   0    8M  0 part
lsblk /dev/nvme1n1 
NAME        MAJ:MIN RM  SIZE RO TYPE MOUNTPOINTS
nvme1n1     259:12   0  2.9T  0 disk
├─nvme1n1p1 259:16   0  2.9T  0 part
└─nvme1n1p9 259:17   0    8M  0 part
lsblk /dev/nvme3n1 
NAME        MAJ:MIN RM  SIZE RO TYPE MOUNTPOINTS
nvme3n1     259:6    0  2.9T  0 disk
├─nvme3n1p1 259:7    0  2.9T  0 part
└─nvme3n1p9 259:8    0    8M  0 part
lsblk /dev/nvme4n1 
NAME        MAJ:MIN RM  SIZE RO TYPE MOUNTPOINTS
nvme4n1     259:5    0  2.9T  0 disk
├─nvme4n1p1 259:9    0  2.9T  0 part
└─nvme4n1p9 259:10   0    8M  0 part

# osd
NAME                                                                                                  MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
nvme5n1                                                                                               259:11   0   7T  0 disk
└─ceph--85f34230--4ab7--4700--b04d--e2aed2172a45-osd--block--092ed71c--c3ce--4a2e--9570--c75239ca46ec 252:4    0   7T  0 lvm
Any help is welcome

Udo
 
Last edited:
longer said:
Could you share:
~# efibootmgr -v

Could it be related to:
https://pve.proxmox.com/wiki/Upgrade_from_8_to_9#GRUB_Might_Fail_To_Boot_From_LVM_in_UEFI_Mode
?
From which version you upgraded?
Click to expand...
Hi,
of course
Code: 
efibootmgr -v
BootCurrent: 0001
Timeout: 0 seconds
BootOrder: 0004,0003,0000,0001
Boot0000  Virtual Floppy        PciRoot(0x3)/Pci(0x7,0x1)/Pci(0x0,0x4)/USB(0,0)/USB(3,0)/USB(0,0)/Unit(1)
      dp: 02 01 0c 00 d0 41 03 0a 03 00 00 00 / 01 01 06 00 01 07 / 01 01 06 00 04 00 / 03 05 06 00 00 00 / 03 05 06 00 03 00 / 03 05 06 00 00 00 / 03 11 05 00 01 / 7f ff 04 00
Boot0001* Virtual CD/DVD        PciRoot(0x3)/Pci(0x7,0x1)/Pci(0x0,0x4)/USB(0,0)/USB(3,0)/USB(0,0)/Unit(0)
      dp: 02 01 0c 00 d0 41 03 0a 03 00 00 00 / 01 01 06 00 01 07 / 01 01 06 00 04 00 / 03 05 06 00 00 00 / 03 05 06 00 03 00 / 03 05 06 00 00 00 / 03 11 05 00 00 / 7f ff 04 00
Boot0003  PXE Device 1: Integrated NIC 1 Port 1 Partition 1 - Intel(R) Ethernet 25G 2P E810-XXV OCP - 30:3E:A7:18:73:4E - IPv4  VenHw(3a191845-5f86-4e78-8fce-c4cff59f9daa)
      dp: 01 04 14 00 45 18 19 3a 86 5f 78 4e 8f ce c4 cf f5 9f 9d aa / 7f ff 04 00
Boot0004* Proxmox       HD(2,GPT,8487b536-0321-4f8c-9729-436910ad3418,0x800,0x200000)/File(\EFI\Proxmox\shimx64.efi)
      dp: 04 01 2a 00 02 00 00 00 00 08 00 00 00 00 00 00 00 00 20 00 00 00 00 00 36 b5 87 84 21 03 8c 4f 97 29 43 69 10 ad 34 18 02 02 / 04 04 36 00 5c 00 45 00 46 00 49 00 5c 00 50
00 72 00 6f 00 78 00 6d 00 6f 00 78 00 5c 00 73 00 68 00 69 00 6d 00 78 00 36 00 34 00 2e 00 65 00 66 00 69 00 00 00 / 7f ff 04 00
The grub-packages are installed
Code: 
dpkg -l | grep grub
ii  grub-common                          2.12-9+pmx2                             amd64        GRand Unified Bootloader (common files)
ii  grub-efi-amd64                       2.12-9+pmx2                             amd64        GRand Unified Bootloader, version 2 (EFI-AMD64 version)
ii  grub-efi-amd64-bin                   2.12-9+pmx2                             amd64        GRand Unified Bootloader, version 2 (EFI-AMD64 modules)
ii  grub-efi-amd64-signed                1+2.12+9+pmx2                           amd64        GRand Unified Bootloader, version 2 (amd64 UEFI signed by Debian)
ii  grub-efi-amd64-unsigned              2.12-9+pmx2                             amd64        GRand Unified Bootloader, version 2 (EFI-AMD64 images)
ii  grub-pc-bin                          2.12-9+pmx2                             amd64        GRand Unified Bootloader, version 2 (PC/BIOS modules)
ii  grub2-common                         2.12-9+pmx2                             amd64        GRand Unified Bootloader (common files for version 2)
ii  proxmox-grub                         2.12-9+pmx2                             amd64        Empty package to ensure Proxmox Grub packages are installed
The server was installed the first time 2 years ago (with pve 8.2 if I'm right).
 
Did you run apt remove systemd-boot on the upgrade?

I'm planning a similar upgrade and have on my notes:
apt install --reinstall grub-efi-amd64
 
  • Like
Reactions: udo
longer said:
If not already done, test to disable secure boot in BIOS and try if it can boot
Click to expand...
Hi,
secure boot is disabled in the bios. Strange, then efibootmgr shows \EFI\Proxmox\shimx64.efi

I updated another Node this morning, also on a R6615 with Boss-Raid-1-Card, which runs well. On this Node Secure Boot is also disabled and efibootmgr shows \EFI\proxmox\grubx64.efi
First I try to recreate initrd.img-7.0.14-8-pve - no change.

So I create an new efi boot entry
Code: 
efibootmgr -o 0000,0001
BootCurrent: 0001
Timeout: 0 seconds
BootOrder: 0000,0001
Boot0000* Proxmox       HD(2,GPT,8487b536-0321-4f8c-9729-436910ad3418,0x800,0x200000)/File(\EFI\proxmox\grubx64.efi)
Boot0001* Virtual CD/DVD        PciRoot(0x3)/Pci(0x7,0x1)/Pci(0x0,0x4)/USB(0,0)/USB(3,0)/USB(0,0)/Unit(0)
Boot0004  Proxmox       HD(2,GPT,8487b536-0321-4f8c-9729-436910ad3418,0x800,0x200000)/File(\EFI\Proxmox\shimx64.efi)
But the server still stuck on Loading initial ramdisk…

Udo
 
miguelsousa said:
Did you run apt remove systemd-boot on the upgrade?

I'm planning a similar upgrade and have on my notes:
apt install --reinstall grub-efi-amd64
Click to expand...
Hi,
perhaps that has something to do with the issue. On another similiar R6615 which I upgrade this morning, the packages are not installed.

On the node with the issue, was systemd-boot removed, but systemd-boot-efi installed…
Code: 
dpkg -l | grep systemd-boot
rc  systemd-boot                         252.39-1~deb12u2                        amd64        simple UEFI boot manager - tools and services
ii  systemd-boot-efi:amd64               257.13-1~deb13u1                        amd64        simple UEFI boot manager - EFI binaries

Have removed systemd-boot-efi and purged systemd-boot and will try an new reboot.
 
You must log in or register to reply here.
Top Bottom
Back