Well, it happened again after doing some updates and rebooting today. My ZFS pool would not mount. I sure would like a solution to this other than having to edit the zfs-mount.service every time it happens.
After running a few more commands, it appears that the ZFS Pool is not actually mounting.
root@billx2:~# zfs get mounted
NAME PROPERTY VALUE SOURCE
storage mounted no -
storage/share mounted no -
storage/share/Files...
I can't seem to figure this out. Everything I know how to check seems to be setup properly, but neither my Turnkey File server, nor my Ubuntu container sees any of the files. When I check the containers in the Proxmox GUI, it shows the mountpoints in the Resources tab. Some output from Putty...
Well, it seem to be somewhat fixed. I can get GUI and my containers are running, but for some reason, my ZFS pool files are not showing. The ZFS Pool shows that 4.5TB is allocated, but the files are not showing up. I'll do some more digging and see if I can figure out what's going on there.
I think maybe because I didn't have the repository key. That step is not shown in the page here: https://pve.proxmox.com/wiki/Upgrade_from_5.x_to_6.0
I suppose it might help if that page was modified to show that. The page you linked is definitely more helpful to a no-subscription user like me...
Trying the process on the 'see also' link you posted. It seems to be working furiously after I did the apt full upgrade.
But then I get this again:
GRUB failed to install to the following devices: │...
Hello,
After a long time waiting, I finally tried to do an inplace upgrade from Proxmox 5.4 to 6.0. Why not, I have some time now that we are social distanced and under stay at home orders.
I followed the guide here: https://pve.proxmox.com/wiki/Upgrade_from_5.x_to_6.0.
I did all my updates...
OK, nevermind. I'm not entirely sure why, but the old disk would boot as BIOS boot (Legacy), but when I clone it, it only boots using UEFI boot. Shrug.
Well, tried clonezilla. Same result. I had both disks attached to a laptop with no other drives, I told it to do direct disk to disk copy. See attached for the result.
This was copying between two m.2 SSDs, both the same 128GB size. One was installed in the laptop, the other was in an adapter...
Hi,
I've been running a Proxmox server at my home for almost a year now. I originally set it up with a 128GB SSD as the boot drive and have a set of four mechanical drives in a ZFS pool for storage. I thought at the time this would offer the best setup.
I have issues of running out of space on...
Jacob, I'm not sure if was the absolute best thing to do, but I had the same problem as you. I solved it by clearing the apt list and re-running apt update/apt full-upgrade.
This is the command to remove the apt list:
rm /var/lib/apt/lists/*
After I did it, I 'might' have read that it wasn't...
Ok, I solved it on my own..not bad for a linux newb.
I had to clear the apt update list and start over.
rm /var/lib/apt/lists/*
After that, I ran apt update and apt full-upgrade and ended up with this:
proxmox-ve: 5.1-42 (running kernel: 4.13.16-1-pve)
pve-manager: 5.1-46 (running version...
Tried to update lxc-pve alone, this is what it says:
root@billx2:~# apt upgrade lxc-pve
Reading package lists... Done
Building dependency tree
Reading state information... Done
lxc-pve is already the newest version (2.1.1-2).
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove...
Unfortunately, I think I read this post from @fabian too late. I did run apt-get upgrade yesterday. Still learning...I will use apt commands from now on. Anyone know a way to fix my Proxmox VE host?
I've been wondering, is it normal to get this when doing apt update or apt-get update?
The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 0D9A1950E2EF0603
Reading package lists... Done
W: An error occurred during the signature verification. The...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.