Problem after 5.2 upgrade

[Saroop P V]

I have upgraded a production server from 5.1 to 5.2 on yesterday.
I had 7 active containers.
after the upgrade and reboot kernel changed from 4.15.3-1 to 4.15.17-1
Since then I couldn't start 6 of my 7 containers.
Survived one was on first drive local-zfs.
6 failed containers were on the second drive which is SSD.
I checked disk directories of all failed containers. It seems all directories went missing except /dev
Is there any solution to fix this?


NAME USED AVAIL REFER MOUNTPOINT
pool0 33.8G 416G 96K /pool0
pool0/xtemplates 33.7G 416G 304K /pool0/xtemplates
pool0/xtemplates/subvol-100-disk-1 7.98G 92.0G 7.98G /pool0/xtemplates/subvol-100-disk-1
pool0/xtemplates/subvol-101-disk-1 2.38G 97.6G 2.38G /pool0/xtemplates/subvol-101-disk-1
pool0/xtemplates/subvol-102-disk-1 10.2G 89.8G 10.2G /pool0/xtemplates/subvol-102-disk-1
pool0/xtemplates/subvol-106-disk-1 7.80G 92.2G 7.80G /pool0/xtemplates/subvol-106-disk-1
pool0/xtemplates/subvol-107-disk-1 5.41G 94.6G 5.41G /pool0/xtemplates/subvol-107-disk-1

 

[Saroop P V]

@Alwin Any possible fix for this issue?

 

[Alwin]

What are the error message, when starting the container, what can you find in the syslog/dmesg.
https://pve.proxmox.com/pve-docs/pv...ontainers_with_span_class_monospaced_pct_span

Containers don't use a mapped device on zfs, the use the subvol feature. When you create a VM on the other hand, there you should see a mapped zvol device.

 

[Saroop P V]

All the 6 failed containers give the same error

Job for pve-container@107.service failed because the control process exited with error code.
See "systemctl status pve-container@107.service" and "journalctl -xe" for details.
TASK ERROR: command 'systemctl start pve-container@107' failed: exit code 1


root@T050:~# ls /pool0/xtemplates/subvol-107-disk-1/
dev
root@T050:~#

 

[Alwin]

What are the error message, when starting the container, what can you find in the syslog/dmesg.
https://pve.proxmox.com/pve-docs/pv...ontainers_with_span_class_monospaced_pct_span

You need to do debugging.

 

[nitrosito]

Finally you can fix it?
I have the same issue

Thanks and regards