Thanks for pointing that out!
I checked my apt sources and found no proxmox (except the out-commented enterprise).
Added the PVE No-subscription repository, found 23 (!) new packages.
Shows ver. 6.0-8 in GUI now.
Obviously I missed manually adding the apt source (which IMHO should be installed...
BUG? Update needed?
Installed a new phresh Proxmox Server
downloaded template "Debian 10.0 (Standard) 10.0-1" through GUI
created new CT (ID 444)
entered new CT
new CT wont start
deep, deep in the logs:
"lxc-start 444 20191012123719.464 DEBUG...
o.k. solved :)
logs are written to be read ;)
in boot.log I spotted:
Oct 05 16:06:55 pve systemd: Starting Mount ZFS filesystems...
Oct 05 16:06:55 pve zfs: cannot mount '/rpool': directory is not empty
Oct 05 16:06:55 pve systemd: zfs-mount.service: Main process exited...
And for me :(
Upgrade seemd to go well, but after reboot no container will start...
Kinda stuck here - tried your script and got:
All packages are up to date.
different paths: as shown in zflist, mine were in rpool/subvol-xxx - script assumes rpool/data/subvol-xxx -...
did multiple re-boots since then - problem w. halt on boot never showed up again and is not reproducible (the 'purely cosmetic' thin target support missing from kernel messages still show though :°)
I have to correct my above post. I only had a report from our IT, didn't personally see the problem myself yet. Now saw, that boot stops due to a backup-directory on / which is not found:
[ TIME ] Timed out waiting for device dev-mapper-pve\x2dbackups.device.
[DEFEND] Dependency failed for...
I just suffered the same issue.
Box was set-up w. a clean install in March using a 5.x standard official release, downloaded from here.
Did an upgrade through GUI a couple of days ago and today finally rebooted (or rather tried to reboot) as recommended at the end of the upgrade-process.
I love you totalimpact! :)
That was exactly what I was looking for: -V (capital V instead of -v, as proposed by dear Miha ;°)
For noobs like me who come across this post:
When the LV is finally created, it must of course be formatted and mounted to show up in GUI:
Apparently proxmox resp. data stole the space - how do I get it back to use it for backups/dumps?
--- Logical volume ---
LV Name data
VG Name pve
LV UUID qOKuXk-Z0K7-BziW-1Uc7-qltl-Kbme-wTmcnZ
LV Write Access read/write
could you kindly elaborate on that?
What exactly did you type, what is the exact command?
I tried several variations but still get the same insufficient free space error.
Just trying to get my vzdumps to the 5TB 'empty space' on me lil server :)
I had the same problem: even though I don't have spaceship NCC Enterprise travelling in my /etc/apt/sources.list, PVE accessed the PAID repository and threw errors.
I solved this by commenting out the entry in...:
Obviously, by default, it is...