No start after moving volume

[maenda]

Hi all,

I try to move a volume (disk) to another share on the storage (nfs to smb) but after the move, the vm does not start.

How can i find out what is going on?

thanks

 

[maenda]

Any thoughts?

 

[Dunuin]

Maybe some rights conflict? Different user/group file/folder mask used on NFS and SMB share?
Did you just copied the volume direcly from one share to another or did you used the Proxmox GUIs VM -> Hardware -> Harddisk -> "move disk" button to move the volume from one location to another?

 

[maenda]

Maybe some rights conflict? Different user/group file/folder mask used on NFS and SMB share?
Did you just copied the volume directly from one share to another or did you used the Proxmox GUIs VM -> Hardware -> Harddisk -> "move disk" button to move the volume from one location to another?

Thanks for your reply. I moved the volume with the move volume option in Proxmox itself.
The SMB share has the same user as the NFS does. So in theory it should work I guess?

 

[Dunuin]

Thanks for your reply. I moved the volume with the move volume option in Proxmox itself.
The SMB share has the same user as the NFS does. So in theory it should work I guess?

I'm also new to proxmox but I would look in the /var/log/syslog if there are some error messages which could give you hints whats going wrong.

 

[maenda]

It looks like it does not write the image correctly to it.

Sep 6 10:12:00 pve1 systemd[1]: Starting Proxmox VE replication runner...
Sep 6 10:12:00 pve1 kernel: [4834417.457835] EXT4-fs (loop0): mounted filesystem with ordered data mode. Opts: (null)
Sep 6 10:12:01 pve1 systemd[1]: pvesr.service: Succeeded.
Sep 6 10:12:01 pve1 systemd[1]: Started Proxmox VE replication runner.
Sep 6 10:12:11 pve1 systemd[1]: var-lib-lxc-103-rootfs.mount: Succeeded.
Sep 6 10:12:11 pve1 systemd[19502]: var-lib-lxc-103-rootfs.mount: Succeeded.
Sep 6 10:12:37 pve1 pvedaemon[21919]: starting CT 103: UPIDve1:0000559F:1CD08ABA:5F5499F5:vzstart:103:root@pam:
Sep 6 10:12:37 pve1 pvedaemon[21664]: <root@pam> starting task UPIDve1:0000559F:1CD08ABA:5F5499F5:vzstart:103:root@pam:
Sep 6 10:12:37 pve1 pvedaemon[16320]: <root@pam> end task UPIDve1:000054A0:1CD07BBA:5F5499CE:vzrestore:103:root@pam: OK
Sep 6 10:12:37 pve1 kernel: [4834455.008680] CIFS VFS: cifs_invalidate_mapping: could not invalidate inode 00000000705decea
Sep 6 10:12:37 pve1 pvedaemon[21919]: volume 'proxmox-images:103/vm-103-disk-0.raw' does not exist
Sep 6 10:13:00 pve1 systemd[1]: Starting Proxmox VE replication runner...
Sep 6 10:13:01 pve1 systemd[1]: pvesr.service: Succeeded.
Sep 6 10:13:01 pve1 systemd[1]: Started Proxmox VE replication runner.

Although the file is present on the storage. Not sure what is going on here
Even a new CT or VM does not start

 

[maenda]

I tried to mount it manually and it gives me an error the rootfs cannot be mounted.
Run a pct fsck 103 and now it starts. Looks like the container gets corrupt

Problem is when i create a new container, it is also corrupted.
It applies only to CT not to VM

What is wrong here?

proxmox-ve: 6.2-1 (running kernel: 5.4.60-1-pve)
pve-manager: 6.2-11 (running version: 6.2-11/22fb4983)
pve-kernel-5.4: 6.2-6
pve-kernel-helper: 6.2-6
pve-kernel-5.4.60-1-pve: 5.4.60-1
pve-kernel-5.4.55-1-pve: 5.4.55-1
pve-kernel-5.4.44-2-pve: 5.4.44-2
pve-kernel-5.4.34-1-pve: 5.4.34-2
ceph-fuse: 12.2.11+dfsg1-2.1+b1
corosync: 3.0.4-pve1
criu: 3.11-3
glusterfs-client: 5.5-3
ifupdown: residual config
ifupdown2: 3.0.0-1+pve2
ksm-control-daemon: 1.3-1
libjs-extjs: 6.0.1-10
libknet1: 1.16-pve1
libproxmox-acme-perl: 1.0.4
libpve-access-control: 6.1-2
libpve-apiclient-perl: 3.0-3
libpve-common-perl: 6.2-1
libpve-guest-common-perl: 3.1-3
libpve-http-server-perl: 3.0-6
libpve-storage-perl: 6.2-6
libqb0: 1.0.5-1
libspice-server1: 0.14.2-4~pve6+1
lvm2: 2.03.02-pve4
lxc-pve: 4.0.3-1
lxcfs: 4.0.3-pve3
novnc-pve: 1.1.0-1
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.2-10
pve-cluster: 6.1-8
pve-container: 3.1-13
pve-docs: 6.2-5
pve-edk2-firmware: 2.20200531-1
pve-firewall: 4.1-2
pve-firmware: 3.1-3
pve-ha-manager: 3.1-1
pve-i18n: 2.1-3
pve-qemu-kvm: 5.0.0-13
pve-xtermjs: 4.7.0-2
qemu-server: 6.2-14
smartmontools: 7.1-pve2
spiceterm: 3.1-1
vncterm: 1.6-2
zfsutils-linux: 0.8.4-pve1

root@pve1:~# cat /etc/pve/storage.cfg
dir: local
disable
path /var/lib/vz
content vztmpl,backup,iso
maxfiles 2
shared 0

lvmthin: local-lvm
disable
thinpool data
vgname pve
content rootdir,images

cifs: proxmox-isos
path /mnt/pve/proxmox-isos
server IP
share proxmox-isos
content iso,vztmpl
username proxmoxcluster

cifs: proxmox-backups
path /mnt/pve/proxmox-backups
server IP
share proxmox-backups
content snippets,backup
maxfiles 50
username proxmoxcluster

nfs: proxmox-images-nfs
export /mnt/user/proxmox-images-nfs
path /mnt/pve/proxmox-images-nfs
server IP
content rootdir,images
options vers=3

cifs: proxmox-images
path /mnt/pve/proxmox-images
server IP
share proxmox-images
content rootdir,images
username proxmoxcluster

 

[maenda]

Hope somebody can help me with this.