Search results

I also get this error when trying to add a new zfs on the newly upgraded proxmox5 to the cluster: create storage failed: error during cfs-locked 'file-storage_cfg' operation: no quorum! (500) This still because all hosts must be same version?

Well the upgrade finally took hold. but now that host doesn't seem 100% compatible with the other ones in the cluster (all other hosts red X). and the shell window looks bizarre and is non-functional. Do I need to do the upgrade across all hosts in the cluster?

oh, I see that was just the upgrade "news", I had to page down many times (not very intuitive) to get to the line that says "Yes" to continue. Good grief Charlie Brown, can it be any more complicating?

I tried that and it just stops at this point and seems to do nothing: apt-listchanges: News --------------------- ebtables (2.0.10.4+snapshot20181205-1) unstable; urgency=medium All the ebtables binaries have been moved away from /sbin to /usr/sbin. Some compatibility symlinks have been...

The above steps does not work. I will have to do a clean re-install, sucks rejoining to cluster, and connecting to ISCSI targets, etc. but oh well, its junk.

Ran those and did a reboot, and this is what i get on the console screen

Is there a way to piecemeal upgrade/update each service individually? Clearly doing it all at once with apt-get upgrade command is not going to work.

That's the $64 question. I have 5 Proxmox boxes, all are or at least were 5.3 I have no clue how this one got half in and half out of an upgrade to 6. The good news is its the last one in the cluster and there are no VM's on it. So it can be wiped/changed/updated or whatever without production...

To be clear they are working now that the multipath was disabled for those 6 HDD's, but here's the output: root@proxmox3:~# lsscsi [0:0:6:0] disk SEAGATE ST1000NX0453 N0A3 /dev/sda [0:0:7:0] disk SEAGATE ST1000NX0453 N003 /dev/sdb [0:0:8:0] disk SEAGATE...

root@proxmox5:~# pveversion -v proxmox-ve: 6.2-1 (running kernel: 4.15.18-9-pve) pve-manager: 5.3-5 (running version: 5.3-5/97ae681d) pve-kernel-5.4: 6.2-2 pve-kernel-helper: 6.2-2 pve-kernel-5.4.41-1-pve: 5.4.41-1 pve-kernel-4.15: 5.2-12 pve-kernel-4.15.18-9-pve: 4.15.18-30 corosync: 2.4.4-pve1...

When I run the update portion, I get this error: Reading package lists... Error! W: The repository 'https://enterprise.proxmox.com/debian/pve stretch Release' does not have a Release file. N: Data from such a repository can't be authenticated and is therefore potentially dangerous to use. N...

If try to create a zfs pool in the cli, i get this: root@proxmox5:~# zpool create -f -o ashift=12 RAID10 /dev/sdb /dev/sdg /dev/sdh /dev/sdi /dev/sdj /dev/sdk zpool: symbol lookup error: /lib/libzfs.so.2: undefined symbol: efi_rescan If i click on the webGUI ZFS module, I get this: It would...

I get this error: root@proxmox3:~# lsscsi -bash: lsscsi: command not found

i got it, it was the multipath all along, sheez.

Is the "ID" the first part starting with 35000...? root@proxmox3:~# multipath -l 35000c5009f224cdf dm-3 SEAGATE,ST1000NX0453 size=932G features='1 retain_attached_hw_handler' hwhandler='0' wp=rw `-+- policy='service-time 0' prio=0 status=active `- 0:0:11:0 sdf 8:80 active undef running...

i have all my current VM's on a iscsi target using a HP Nimble. the "local" drives in question have nothing on them. I am configuring them as my backup actually. all VM's are thin client kiosk machines and clones of each other which are spread out over 4 other Proxmox boxes., only difference is...

Still nothing, wow this is crazy.

Rebooting now, none is using the VM's due to COVID and our center being off limits to public, so I cna make changes during day (4:15pm my time right now). We'll see in about 10 minutes...

luckily noone is using any of the VM's right now (thanks again to COVID) so reboot it is!

I did that, it makes no difference. Also, in the GUI they still show as Device Mapper under "Usage":