Search results

To be clear, I've not declined to do anything. I simply have an incredible load of work and this is just adding to it and I'm trying to make the time to fix proxmox instead of suggesting we move away from it. We've never had any such issues with vmware and we're not ready to buy a license right...

It seems ssh is now not working between nodes. And other problems are starting to creep in. I tried installing a rocky Linux instance but it would not start on any node so I gave up. This for example makes no sense. I even tried to add the known_hosts but it would not even see the file...

Did you read what I've posted? I've been sharing a LOT of information :). I explain that all nodes but this one are able to see the storage but I also confirmed since that all nodes can upload to the iso storage above but this one node. I was able to use the uploaded .ISO to install a guest on...

Seems ok. Like I shared earlier, all of the NFS shares are there. # cat /etc/pve/storage.cfg dir: local path /var/lib/vz content backup,iso,vztmpl zfspool: local-zfs pool rpool/data content rootdir,images sparse 1 nfs: nfs_vmstore export...

What would I be looking for?

All nodes can see the files in the NFS storage. Only I cannot upload anything suddenly as I'm getting the above error.

Yes, I mean something different but since I'm not sure what's going on, I'm also not sure what to include for info, details etc. The storage was created at the cluster level and is shared across all nodes.

What in the world does this mean? Error 500: can't activate storage 'nfs-iso' on node 'pro07': command '/usr/bin/ssh -o 'BatchMode=yes' 10.0.0.76 -- /usr/sbin/pvesm status --storage nfs-iso' failed: exit code 255 I recently lost three guests because something happened to the storage in a...

# ls -la /rpool/ drwxr-xr-x 2 root root 2 May 9 18:41 data drwxr-xr-x 3 root root 3 May 9 18:41 ROOT # ls -la /rpool/data/ drwxr-xr-x 2 root root 2 May 9 18:41 . drwxr-xr-x 4 root root 4 May 9 18:41 .. I mean I went to move the storage to NFS for example but as I already know, there is...

I tried moving the storage to another device but it shows 'no content'. # find /dev | grep 152 /dev/shm/qb-2589-3152932-30-EgKM9V /dev/shm/qb-2589-3152932-30-EgKM9V/qb-event-pve2-data /dev/shm/qb-2589-3152932-30-EgKM9V/qb-event-pve2-header...

I think I'm not seeing the full command you want me to run. 152 is one of the guests. ~# for i in $(ls -1 /dev/zd* |grep -v '/dev/zd[0-9]*p[0-9]*'); do echo $i; /lib/udev/zvol_id $i ; done |grep -B1 myzpool/vm-152-disk-0 /dev/zd0 myzpool/vm-152-disk-0 grep: /dev/zd0: No such file or directory...

Hi, thanks for helping. You want me to try this in the other post? >for i in $(ls -1 /dev/zd* |grep -v '/dev/zd[0-9]*p[0-9]*'); do echo $i; /lib/udev/zvol_id $i ; done |grep -B1 <name of missing zvol> >(replace <name of missing zvol> by the name of a zvol which has the problem (in your...

I know this is old but I seem to be experiencing something similar. https://forum.proxmox.com/threads/cannot-migrate-guests.114340/

Solved: This was solved by giving up and rebuilding the entire cluster. I wanted to upgrade all of my 7.1.7 to 7.2 but one node is not allowing migration. I tried while it was still 7.1.7 and got the errors so I upgraded to 7.2 with the guests on it and no difference after a reboot...

Thank you for the help everyone.

I see what's happening. If I log into any other node, I see it's version in the datacenter since it becomes my control node if you will. When I log into the node I upgraded, then it shows me the node is 7.2.7. The only weird thing is that it shows me the original message about subscribing which...

Can you tell from the result I posted if it upgraded? It certainly is still showing 7.1.7 no matter if I clear the browser cache.

In terms of nodes, I migrated everything away from this node before starting this so while it's part of the cluster, it's not essential.

Oh, that's interesting. the GUI says 7.1.7 but... # pveversion -v proxmox-ve: 7.2-1 (running kernel: 5.15.39-4-pve) pve-manager: 7.2-7 (running version: 7.2-7/d0dd0e85) pve-kernel-5.15: 7.2-9 pve-kernel-helper: 7.2-9 pve-kernel-5.13: 7.1-9 pve-kernel-5.15.39-4-pve: 5.15.39-4...

No difference. # apt update Hit:1 http://security.debian.org bullseye-security InRelease Hit:2 http://ftp.us.debian.org/debian bullseye InRelease Get:3 http://ftp.us.debian.org/debian bullseye-updates InRelease [44.1 kB] Hit:4 http://download.proxmox.com/debian/pve bullseye InRelease Fetched...