I am getting myself in a knot 
So pls forgive the what feels like a stupid situation.
I have an MS-01 - that has just come back from RMA. Previously it ran perfectly since about April when it was delivered (with the intel microcode) until it failed to power on after an unscheduled power outage. Prior to the outage, it was up to date (failed maybe 2-3 weeks ago)
I have the memory and SSDs and was expecting / hoping that I would simply be able to reinsert these and restart.
2x Samsung SSDs (no zfs)
BUT that is apparently not the case.
The machine boots up into GNU GRUB v 2.0.6-13+pmx2
Where, I am presented with a prompt.
grub>
If I use a proxmox bootable USB, and Advanced Options -> Rescue Boot everything seems “fine” but I have to manually select this every time.
I don’t know what “Rescue Boot” does.
Nor, what I should do once I have booted into what seems like the fully running system. When I reboot, it continues to go back to the grub menu
When I search - most of what I find is reference to the upgrade issue. which doesn’t seem applicable.
I have tried to look into what type of bootloader I am using (having booted with “Rescue Boot”)
Efibootmgr -v gives me.
though, when I use proxmox-boot-tools status, I get
So I am a bit (lot) confused (particularly for something that should have be a simple plug and go)
What am I missing?
So pls forgive the what feels like a stupid situation.
I have an MS-01 - that has just come back from RMA. Previously it ran perfectly since about April when it was delivered (with the intel microcode) until it failed to power on after an unscheduled power outage. Prior to the outage, it was up to date (failed maybe 2-3 weeks ago)
I have the memory and SSDs and was expecting / hoping that I would simply be able to reinsert these and restart.
2x Samsung SSDs (no zfs)
BUT that is apparently not the case.
The machine boots up into GNU GRUB v 2.0.6-13+pmx2
Where, I am presented with a prompt.
grub>
If I use a proxmox bootable USB, and Advanced Options -> Rescue Boot everything seems “fine” but I have to manually select this every time.
I don’t know what “Rescue Boot” does.
Nor, what I should do once I have booted into what seems like the fully running system. When I reboot, it continues to go back to the grub menu
When I search - most of what I find is reference to the upgrade issue. which doesn’t seem applicable.
I have tried to look into what type of bootloader I am using (having booted with “Rescue Boot”)
Efibootmgr -v gives me.
BootCurrent: 0003Timeout: 3 secondsBootOrder: 0003,0001,0002,0000Boot0000* proxmox HD(2,GPT,177037ab-7c7e-415b-a912-3abca8acda91,0x800,0x200000)/File(\EFI\proxmox\shimx64.efi)Boot0001* UEFI OS HD(2,GPT,177037ab-7c7e-415b-a912-3abca8acda91,0x800,0x200000)/File(\EFI\BOOT\BOOTX64.EFI)..BOBoot0002* UEFI OS HD(2,GPT,abd38b7d-4c7d-45ce-a54e-3798bcc945d0,0x800,0x200000)/File(\EFI\BOOT\BOOTX64.EFI)..BOBoot0003* UEFI: SanDisk, Partition 2 PciRoot(0x0)/Pci(0x14,0x0)/USB(14,0)/HD(2,GPT,2d393880-2f44-4f7d-9933-b55d6d0be33d,0x220,0x4000)..BOthough, when I use proxmox-boot-tools status, I get
Re-executing ‘/usr/sbin/proxmox-boot-tool’ in new private mount namespace…E: /etc/kernel/proxmox-boot-uuids does not existSo I am a bit (lot) confused (particularly for something that should have be a simple plug and go)
What am I missing?
lsblk -o +FSTYPENAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS FSTYPEsda 8:0 1 14.3G 0 disk iso9660├─sda1 8:1 1 240K 0 part ├─sda2 8:2 1 8M 0 part vfat├─sda3 8:3 1 1.3G 0 part hfsplus└─sda4 8:4 1 300K 0 part nvme0n1 259:0 0 3.5T 0 disk ├─nvme0n1p1 259:1 0 1007K 0 part ├─nvme0n1p2 259:3 0 1G 0 part vfat└─nvme0n1p3 259:4 0 3.5T 0 part /mnt/pve/nvme1 ext4nvme1n1 259:2 0 3.5T 0 disk ├─nvme1n1p1 259:5 0 1007K 0 part ├─nvme1n1p2 259:6 0 1G 0 part /boot/efi vfat└─nvme1n1p3 259:7 0 3.5T 0 part LVM2_member ├─pve-swap 252:0 0 8G 0 lvm [SWAP] swap ├─pve-root 252:1 0 904G 0 lvm / ext4 ├─pve-data_tmeta 252:2 0 10.2G 0 lvm │ └─pve-data-tpool 252:4 0 1003.5G 0 lvm │ ├─pve-data 252:5 0 1003.5G 1 lvm │ ├─pve-vm--107--disk--0 252:6 0 4M 0 lvm │ ├─pve-vm--107--disk--1 252:7 0 32G 0 lvm │ ├─pve-vm--109--disk--0 252:8 0 48G 0 lvm ext4 │ ├─pve-vm--106--disk--0 252:9 0 64G 0 lvm ext4 │ └─pve-vm--110--disk--0 252:10 0 64G 0 lvm ext4 ├─pve-data_tdata 252:3 0 1003.5G 0 lvm │ └─pve-data-tpool 252:4 0 1003.5G 0 lvm │ ├─pve-data 252:5 0 1003.5G 1 lvm │ ├─pve-vm--107--disk--0 252:6 0 4M 0 lvm │ ├─pve-vm--107--disk--1 252:7 0 32G 0 lvm │ ├─pve-vm--109--disk--0 252:8 0 48G 0 lvm ext4 │ ├─pve-vm--106--disk--0 252:9 0 64G 0 lvm ext4 │ └─pve-vm--110--disk--0 252:10 0 64G 0 lvm ext4 └─pve-grubtemp 252:11 0 4M 0 lvm
Last edited:
