Proxmox server not booting -- I'm lost

Firav

Member
Feb 28, 2022
5
0
6
25
Tennessee, USA
Howdy y'all.
I've had a debian 8 Proxmox server set up for a while and hosted on a Kimsufi machine. Recently (yesterday) the Proxmox web UI was no longer accessible after a reboot. I've tried booting into a rescue OS within Kimsufi to see if I can see into the lvs filesystem, but I can only seem to find the raw vm image. I'm at a loss on how to find what the issue is that is preventing the Proxmox OS from booting properly. Any of y'all have some insight? I'm able to provide as much information as possible!
 
Just following up on this post, I've been able to reboot into a recovery OS and this is about as far as I can get:
MobaXterm_2023-06-08_22-21-04.png

I can't mount any other drive except the dev/vg/data, which looks like it has the .raw for the VM I was running.
Heres an outlook on drive configuration:
MobaXterm_2023-06-08_22-25-56.png

I can get the system to come "online", but the UI isnt accessable. I try to SSH into the root account, and receive "connection refused" on port 22, which is the known SSH port for the install.
 
Hi!

Tell me more about the storage hardware/layout ( mdadm -> lvm -> ext4 ? )

First guess, the Bios boot order problem ( not every disk has boot loader installed ).
If not, you boot up a Debian Live ISO, exact version as was your system based on.

https://cdimage.debian.org/cdimage/
https://cdimage.debian.org/cdimage/archive/

After you manged to Debian Live boot up, install the necessary packages:

Code:
$> apt-get install mdadm lvm2 grub2 grub2-common chroot

Try to assemble the raid storage:

$(Live)> mdadm --assemble --scan
$(Live)> pvscan
$(Live)> vgscan
$(Live)> lvscan
$(Live)> vgs
$(Live)> vgchange -ay <vgs>

Try to mount on the LVM volumes:
$(Live)> mkdir /media/pveroot/
$(Live)> mkdir /media/pvedata/
$(Live)> mount /dev/mapper/pve-root  /media/pveroot/
# $(Live)> mount /dev/mapper/pve-data  /media/pvedata/     # no need to mount

OK, try to repair your system:
$(Live)> chroot /media/pveroot/ /bin/bash

$(chroot)> apt-get clean all
$(chroot)> apt-get autoclean
$(chroot)> apt-get update
$(chroot)> apt-get install -f
$(chroot)> apt-get install mdadm
$(chroot)> apt-get install lvm2
$(chroot)> apt-get install openssh-server
$(chroot)> update-initramfs -c -d -u
$(chroot)> grub-mkconfig > /boot/grub/grub.cfg
$(chroot)> exit

$(Live)> mdadm --detail --scan > /media/pveroot/etc/mdadm/mdadm.conf
$(Live)> grub-install --boot-directory=/media/pveroot/boot /dev/sda
$(Live)> grub-install --boot-directory=/media/pveroot/boot /dev/sdb
$(Live)> grub-install --boot-directory=/media/pveroot/boot /dev/sdc
$(Live)> grub-install --boot-directory=/media/pveroot/boot /dev/sdd

$(Live)> chroot /media/pveroot/ /bin/bash
$(chroot)> update-initramfs -c -d -u
$(chroot)> update-grub
$(chroot)> exit

Reboot the system.
 
Last edited:
So I can confirm two of my kimsufi proxmox servers failed similarly, recently. I have another OVH SYS server that run everything for me. If that fails I am done. Do we know what's going on here?
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!