Search results

No @tom you are wrong. People do read the docs. But if the docs are disorganized or don't contain the "right" information you tend to gloss over them. As a person that has very poor sight (I'm legally blind); docs are great if they are: accurate terse discoverable cheers James

@tom You are right. This was my "fuck up". It appears (thank you to z_g on Freenode) that I once did an (incorrect) `apt-get upgrade` which apparently isn't the way you upgrade Proxmox VE due to the nature of Proxmox VE being a rolling release during stable Debian major versions and so the usual...

Please test live upgrades before pushing a new version of ProxmoxVE! Don't break us; we don't have time to be digging around in the bowls of Debian :/ -- Just make it work flawlessly!

So I guess I too solve this. TL;DR: Remove conflicting zfs deps; re-install zfs. Basically a bunch of manual dpkg -r removing crap until you can apt-get install zfsutils @tom Really not sure what your QA is over there for Proxmox with live upgrades but this is 2/2 where Proxmox VE upgrades...

@Ascent Could you share what your fix was in the end? I agree with you; the support provided in this thread has been less than useful. @tom You really need to pay attention to detail here. I just upgraded from Proxmox VE 5.0 to 5.1 (followed the instructions to the letter) have the expected...

Has there been an uptake on this feature by the ProxMox Dev team lately?