Search results

i fully agree that the main problem resides between the chair & the keyboard. Still, enabling the service made the difference between containers starting at boot or not starting at boot.

hello everyone, having some kind of issue starting a LXC, I am having trouble analyzing the logs to pinpoint exactly what is happening here ? Any thoughts ? Mucho Gracias in advance ! lxc-start -n 103 -F -l DEBUG -o /tmp/lxc-103.log https://paste.ubuntu.com/p/P8sFVG2jQF/

I know that now...i didn't when I first created the pool, and the tutorial I was following didn't use long aliases for drives / partitions. On the bright side, the issue seems solved through help from the ZoL mailing list. fwiw, and for posterity, here's the thread ...

errr... given that i know that I put the zfs cache into a partition of the SSD , and given : root@pve:/etc/default# zpool history History for 'zfs-pool': 2018-10-10.16:41:27 zpool create -f -o ashift=12 zfs-pool raidz /dev/sda /dev/sdb /dev/sdc /dev/sdd cache /dev/sde5 log /dev/sde4 and...

but both must be related, surely ? Since doing "zfs mount -a" allows pve-container@100.service to start without errors.

from the journalctl output (https://paste.ubuntu.com/p/QGZzdt7PQb/) i did see this : -- The job identifier is 49. Aug 11 15:48:52 pve kernel: EXT4-fs (sde1): mounted filesystem with ordered data mode. Opts: (null) Aug 11 15:48:53 pve zpool[822]: invalid or corrupt cache file contents: invalid...

root@pve:~# systemctl status pve-container@100.service ● pve-container@100.service - PVE LXC Container: 100 Loaded: loaded (/lib/systemd/system/pve-container@.service; static; vendor preset: enabled) Active: failed (Result: exit-code) since Sun 2019-08-11 16:32:26 CEST; 20s ago Docs...

after i do a "zfs mount -a" , there is no output to the start commands, and the VM/LXC start normal. After a reboot & prior to "zfs mount -a", nothing starts & I end up with errors like Job for pve-container@100.service failed because the control process exited with error code. See "systemctl...

root@pve:/# zpool list NAME SIZE ALLOC FREE CKPOINT EXPANDSZ FRAG CAP DEDUP HEALTH ALTROOT zfs-pool 928G 638G 290G - - 33% 68% 1.00x ONLINE - root@pve:/# zfs list NAME USED AVAIL REFER...

one final question : the mount point for the pool is "/zfs-pool", should that directory actually exist or is "zfs mount -a" supposed to create that directory ? oops, our messages crossed eachother : https://paste.ubuntu.com/p/Gz9wgkcP9x/

from the below...I would conclude that "zpool import zfs-pool" is trying to import the pool twice ????? root@pve:/etc/default# zpool export zfs-pool root@pve:/etc/default# root@pve:/etc/default# root@pve:/etc/default# zpool status pool: zfs-pool state: ONLINE status: Some supported...

indeed there was 1 VM that had a CDrom device with that iso. I "ejected" the cdrom. root@pve:/etc/default# zpool export zfs-pool root@pve:/etc/default# zpool import zfs-pool cannot import 'zfs-pool': a pool with that name already exists use the form 'zpool import <pool | id> <newpool>' to give...

root@pve:/etc/default# zpool export zfs-pool umount: /zfs-pool/iso: target is busy. cannot unmount '/zfs-pool/iso': umount failed root@pve:/etc/default# lsof +D /zfs-pool/iso COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME kvm 3669 root 15r REG 0,56 350224384 11...

all the pool details are specified in the link to my original post. ( https://forum.proxmox.com/threads/zfs-mounting-problems.23680/#post-261750 ) dmesg : https://paste.ubuntu.com/p/dPC85Yp5QR/

I'm not sure if i understand what you mean... The host boots fully. PVE starts up properly. Containers/VM's do not start, because zfs pool does not mount automatically. The zfs pool is not an rpool, root is not mounted on the zfs pool. The console just displays the usual welcome banner, telling...

Thank you very much for helping out. Some people are saying i should just hose the server & reinstall proxmox from scratch. I really hate doing that, it will not deliver any knowledge about what is actually going wrong with this machine.

@RobFantini : any hints for those of us who have made sure the mount point is _empty_ but zfs still will not mount at boot ?

@Duckdave What is the mount point for your zfs pool ? Is there anything inside that mount point ?

Hello all, I really would love to get to the bottom of this. I had posted in another thread, but the symptoms no longer match, creating a separate thread seems the proper way to ask for help troubleshooting. This is my detailed post in the other thread ...

no, i didn't... but my issue has evolved. I cleaned up the zfs moint point, and it is now empty. Unfortunately & strangely, the pool _still_ won't mount at reboot. However, it now _does_ mount with a manual issue of command "zfs mount -a" (without the Overlay parameter) ...go figure...