Hang when booting from the other mirror

P

promoxer

Member
Apr 21, 2023
234
23
23
Code: 
  pool: rpool
 state: ONLINE
  scan: scrub repaired 0B in 00:08:47 with 0 errors on Sun Aug 10 00:32:48 2025
config:

        NAME                                                     STATE     READ WRITE CKSUM
        rpool                                                    ONLINE       0     0     0
          mirror-0                                               ONLINE       0     0     0
            ata-SAMSUNG_MZNTE256HMHP-000L7_S1KHNYAG111222-part3  ONLINE       0     0     0
            ata-SanDisk_SD8SN8U-256G-1006_174719800429-part3     ONLINE       0     0     0

Code: 
# proxmox-boot-tool refresh
Running hook script 'proxmox-auto-removal'..
Running hook script 'zz-proxmox-boot'..
Re-executing '/etc/kernel/postinst.d/zz-proxmox-boot' in new private mount namespace..
Copying and configuring kernels on /dev/disk/by-uuid/28F1-7863
        Copying kernel 6.5.13-6-pve
        Copying kernel 6.8.12-10-pve
        Copying kernel 6.8.12-11-pve
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-6.8.12-11-pve
Found initrd image: /boot/initrd.img-6.8.12-11-pve
Found linux image: /boot/vmlinuz-6.8.12-10-pve
Found initrd image: /boot/initrd.img-6.8.12-10-pve
Found linux image: /boot/vmlinuz-6.5.13-6-pve
Found initrd image: /boot/initrd.img-6.5.13-6-pve
Adding boot menu entry for UEFI Firmware Settings ...
done

1. My proxmox boots and stays stuck at init ramfs, somehow the web UI works and shows all VMs and LXCs refusing to boot and I could not make any sense. Most of them show the error kvm virtualisation configured, but not available. either disable in vm configuration or enable in bios.

2. https://www.reddit.com/r/Proxmox/comments/1cgxygg/new_proxmox_install_pve_822_containers_fail_to/ this link led me to force boot from SanDisk and VMs/LXCs booted as normal

3. proxmox-boot-tool refreshdid not fix the situation

4. How do I make Samsung work again?
 
Last edited:
Situation has worsened now:

1. SanDisk won't boot unless secured boot is disabled, and after booting, my LXCs won't start, but VMs can start
2. Samsung boots with secured mode, but again, after booting, LXCs won't start, but VMs can start

Code: 
# pct start 113
lxc_spawn: 1738 Operation not permitted - Failed to clone a new set of namespaces
__lxc_start: 2114 Failed to spawn container "113"
startup for container '113' failed
 
Last edited:
promoxer said:
Situation has worsened now:
Click to expand...
What changes did you make? What commands did you execute?
promoxer said:
Code: 
# pct start 113
lxc_spawn: 1738 Operation not permitted - Failed to clone a new set of namespaces
__lxc_start: 2114 Failed to spawn container "113"
startup for container '113' failed
Click to expand...
Sorry, but I have no idea how adding an ESP could cause containers to fail. Or maybe it now booted a newer kernel that was already installed but never used before (due to refreshing the ESPs)? Maybe try manually booting the previous kernel version as a work-around?
 
You must log in or register to reply here.
Top Bottom