.raw does not exist after upgrade to Proxmox VE 8.0.4

zebisnaga

New Member
Feb 3, 2023
18
0
1
Hi guys,
I was using Proxmox VE version 7 and decided to upgrade to version 8 and for some reason now 2 of my LXC wont start having the following error

Code:
root@pve:~# pct start 101
volume 'Backups:104/vm-104-disk-0.raw' does not exist

This is my config for LXC 101

Code:
root@pve:~# cat /etc/pve/lxc/101.conf
arch: amd64
cores: 2
hostname: bot
memory: 1024
mp0: /mnt/pve/external,mp=/mnt/external,size=0T
net0: name=eth0,bridge=vmbr0,firewall=1,gw=192.168.30.1,hwaddr=86:9C:F6:C5:F3:B5,ip=192.168.30.171/24,type=veth
onboot: 1
ostype: ubuntu
rootfs: Backups:104/vm-104-disk-0.raw,size=120G
swap: 1024

And this is my storage.cfg

Code:
root@pve:~# cat /etc/pve/storage.cfg
dir: local
        path /var/lib/vz
        content backup,iso,vztmpl

zfspool: local-zfs
        pool rpool/data
        content rootdir,images
        sparse 1

dir: ISO
        path /storagepool/isos
        content iso,vztmpl
        prune-backups keep-all=1
        shared 0

dir: Backups
        path /storagepool/backups
        content snippets,rootdir,backup,iso,images,vztmpl
        prune-backups keep-all=1
        shared 0

dir: external
        path /mnt/pve/external
        content iso,snippets,rootdir,backup,vztmpl,images
        is_mountpoint 1
        nodes pve

I don't know how to fix this and after searching for a while I didn't found any good solution.
Can someone help? thanks
 
Is /mnt/pve/external actually mounted? Use "mount" from command line to see.
yes I mounted an hour ago

Code:
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
proc on /proc type proc (rw,relatime)
udev on /dev type devtmpfs (rw,nosuid,relatime,size=12250308k,nr_inodes=3062577,mode=755,inode64)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /run type tmpfs (rw,nosuid,nodev,noexec,relatime,size=2457012k,mode=755,inode64)
rpool/ROOT/pve-1 on / type zfs (rw,relatime,xattr,noacl)
securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev,inode64)
tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k,inode64)
cgroup2 on /sys/fs/cgroup type cgroup2 (rw,nosuid,nodev,noexec,relatime)
pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)
efivarfs on /sys/firmware/efi/efivars type efivarfs (rw,nosuid,nodev,noexec,relatime)
bpf on /sys/fs/bpf type bpf (rw,nosuid,nodev,noexec,relatime,mode=700)
systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=30,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=50533)
mqueue on /dev/mqueue type mqueue (rw,nosuid,nodev,noexec,relatime)
hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime,pagesize=2M)
debugfs on /sys/kernel/debug type debugfs (rw,nosuid,nodev,noexec,relatime)
tracefs on /sys/kernel/tracing type tracefs (rw,nosuid,nodev,noexec,relatime)
fusectl on /sys/fs/fuse/connections type fusectl (rw,nosuid,nodev,noexec,relatime)
configfs on /sys/kernel/config type configfs (rw,nosuid,nodev,noexec,relatime)
ramfs on /run/credentials/systemd-sysctl.service type ramfs (ro,nosuid,nodev,noexec,relatime,mode=700)
ramfs on /run/credentials/systemd-sysusers.service type ramfs (ro,nosuid,nodev,noexec,relatime,mode=700)
ramfs on /run/credentials/systemd-tmpfiles-setup-dev.service type ramfs (ro,nosuid,nodev,noexec,relatime,mode=700)
rpool on /rpool type zfs (rw,relatime,xattr,noacl)
rpool/ROOT on /rpool/ROOT type zfs (rw,relatime,xattr,noacl)
rpool/data on /rpool/data type zfs (rw,relatime,xattr,noacl)
rpool/data/subvol-103-disk-0 on /rpool/data/subvol-103-disk-0 type zfs (rw,relatime,xattr,posixacl)
rpool/data/subvol-102-disk-0 on /rpool/data/subvol-102-disk-0 type zfs (rw,relatime,xattr,posixacl)
rpool/data/subvol-100-disk-0 on /rpool/data/subvol-100-disk-0 type zfs (rw,relatime,xattr,posixacl)
rpool/data/subvol-106-disk-0 on /rpool/data/subvol-106-disk-0 type zfs (rw,relatime,xattr,posixacl)
storagepool on /storagepool type zfs (rw,xattr,noacl)
storagepool/backups on /storagepool/backups type zfs (rw,xattr,noacl)
storagepool/isos on /storagepool/isos type zfs (rw,xattr,noacl)
ramfs on /run/credentials/systemd-tmpfiles-setup.service type ramfs (ro,nosuid,nodev,noexec,relatime,mode=700)
binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,nosuid,nodev,noexec,relatime)
lxcfs on /var/lib/lxcfs type fuse.lxcfs (rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other)
sunrpc on /run/rpc_pipefs type rpc_pipefs (rw,relatime)
/dev/fuse on /etc/pve type fuse (rw,nosuid,nodev,relatime,user_id=0,group_id=0,default_permissions,allow_other)
tmpfs on /run/user/0 type tmpfs (rw,nosuid,nodev,relatime,size=2457012k,nr_inodes=614253,mode=700,inode64)
/dev/sdf1 on /mnt/pve/external type ext4 (rw,relatime)

using the lsblk

Code:
root@pve:~# lsblk
NAME     MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
sda        8:0    0 223.6G  0 disk
├─sda1     8:1    0  1007K  0 part
├─sda2     8:2    0     1G  0 part
└─sda3     8:3    0 222.6G  0 part
sdb        8:16   0 223.6G  0 disk
├─sdb1     8:17   0  1007K  0 part
├─sdb2     8:18   0     1G  0 part
└─sdb3     8:19   0 222.6G  0 part
sdc        8:32   0 465.8G  0 disk
├─sdc1     8:33   0 465.8G  0 part
└─sdc9     8:41   0     8M  0 part
sdd        8:48   0 465.8G  0 disk
├─sdd1     8:49   0 465.8G  0 part
└─sdd9     8:57   0     8M  0 part
sdf        8:80   0   1.8T  0 disk
└─sdf1     8:81   0   1.8T  0 part /mnt/pve/external
zd0      230:0    0     1M  0 disk
zd16     230:16   0    70G  0 disk
├─zd16p1 230:17   0   100M  0 part
├─zd16p2 230:18   0    16M  0 part
├─zd16p3 230:19   0  69.3G  0 part
└─zd16p4 230:20   0   625M  0 part
zd32     230:32   0     4M  0 disk
 
And why is container 101 using a virtual disk created for 104? Maybe rename the container to 104?
And is the (/storagepool/backups/vm-104-disk-0.raw file actually there?
 
yes I mounted an hour ago
perhaps the file was created in non-mounted directory, ie on root fileysystem prior to mount.
Or, because you have /storagepool as mount, and then you submount other things under /storagepool - the file could have ended up on the volume that is mounted as /storagepool.

The whole setup is really convoluted, I'd recommend peeling back and getting rid of some layers...



Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
 
And why is container 101 using a virtual disk created for 104? Maybe rename the container to 104?
And is the (/storagepool/backups/vm-104-disk-0.raw file actually there?
Thats a mistake I've made while copying to here ...
No , there is no .raw file in /storagepool/backups/
 
perhaps the file was created in non-mounted directory, ie on root fileysystem prior to mount.
Or, because you have /storagepool as mount, and then you submount other things under /storagepool - the file could have ended up on the volume that is mounted as /storagepool.

The whole setup is really convoluted, I'd recommend peeling back and getting rid of some layers...



Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
storagepool is a HDD inserted in pve.
This happened after a reboot after a dist-upgrade