Proxmox no loger start - recover files from a Linux Container


New Member
Dec 12, 2022
I have/had proxmox running on a raspberry pi 4 on an micro SD card.
All was working fine until a run a update form the proxmox ui now the pi is stuck in a reboot loop.
I need to get the data from my LXC if that is possible.
I have managed to get the vm-100-disk-0.raw, vm-101-disk-0.raw, vm-102-disk-0.raw files from the SD card.
Are this the right files?
How can I mount / load them on a other Linux / windows machine, in order to get some file from within the container?
note that Proxmox doesn't support the raspberry pi, you probably used some third party port?

the raw files should be mountable using pretty much any modern linux system, if they were created by PVE they will just contain an ext4 file system (no partitions or anything else).
i know i have tryed al lot of thing to mount the raw file but no luck so far:
vm-101-disk-0.raw: UUID="94fe9e26-829c-4c37-98de-5017e6defb9d" BLOCK_SIZE="4096" TYPE="ext4"

sudo fdisk -l -u=sectors /home/pi/vm-101-disk-0.raw
Disk /home/pi/vm-101-disk-0.raw: 4.08 MiB, 4280320 bytes, 8360 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

sudo losetup -f --show -P /home/pi/vm-101-disk-0.raw

sudo mount -o loop,offset=9437184 /work/loop_test/disk_image.img /mnt/ntfs_partition

sudo mount -t ext4 ro,noload /home/pi/vm-101-disk-0.raw /media/101

sudo mount -t ext4 ro,noload /dev/loop2 /media/101

sudo mount /dev/loop3 -t ext4 -o ro,loop,offset=0x100000 /media/101

sudo mount -t ext4 -o ro /home/pi/vm-101-disk-0.raw /media/101

sudo mount /home/pi/vm-101-disk-0.raw -t ext4 -o ro,loop,offset=0x100000 /media/101/

sudo losetup --offset 48234496 /dev/loop3 /home/pi/vm-101-disk-0.raw

Create = sudo losetup --offset 48234496 /dev/loop3 /home/pi/vm-101-disk-0.raw
Remove = sudo losetup -d /dev/loop0

Any suggestions to get it to work?
Are you sure that this is the correct disk and not just some EFI / TPM state disk - since it is only 4 MiB large
if i create a LCX container what is the default path where the container disk is placed?
Depends on your used storage.
Ext4: /var/lib/vz
LVM/LVMThin: there are no image files, LVs are used
ZFS: there are no image files, datasets/zvols are used
can i get that info from the config file:
lxc.cgroup.relative = 0
lxc.cgroup.dir.monitor = lxc.monitor/101
lxc.cgroup.dir.container = lxc/101
lxc.cgroup.dir.container.inner = ns
lxc.arch = arm64
lxc.include = /usr/share/lxc/config/ubuntu.common.conf
lxc.apparmor.profile = generated
lxc.apparmor.raw = deny mount -> /proc/,
lxc.apparmor.raw = deny mount -> /sys/,
lxc.monitor.unshare = 1
lxc.tty.max = 2
lxc.environment = TERM=linux = Domoticz
lxc.cgroup2.memory.max = 268435456
lxc.cgroup2.memory.swap.max = 268435456
lxc.rootfs.path = /var/lib/lxc/101/rootfs = veth = veth101i0 = 66:5C:17:C7:28:BF = eth0 = /usr/share/lxc/lxcnetaddbr
lxc.cgroup2.devices.allow = c 189:* rwm
lxc.mount.entry = usb-FTDI_FT232R_USB_UART_AC3KU7OK-if00-port0 dev/serial/by-id/usb-FTDI_FT232R_USB_UART_AC3KU7OK-if00-port0 none bind,optional,create=file
lxc.cgroup2.devices.allow = c 188:* rwm
lxc.mount.entry = /var/lib/lxc/101/devices/ttyUSB0 dev/ttyUSB0 none bind,optional,create=file
lxc.cgroup2.cpuset.cpus = 3


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!