Search results

Hi, You are trying to upgrade PVE not using ALL right repository. Have you recently changed your subscription from community to enterprise? you have to update ALL repository in these file (for ENTERPRISE REPOSITORY) /etc/apt/sources.list /etc/apt/sources.list.d/pve-enterprise.list...

Hi, before rebooting the node, you can change the weight of the node. For example, if you have pve1 (weight=1) and pve2 (weight=1) you can change in pve1 (weight=2) and pve2 (weight=1) in the corosync.conf file in order to avoid and you can loss the quorum during the reboot proces MM

Be careful when you will add more disks. In my past experience in adding disk in ceph storage, I can do these considerations: After adding a disk and including the OSD, we had to wait for the PG realignment. The graph was mostly yellow, but there was no impact on customer service. Since it...

First of all, try accessing via the web all the nodes to understand where the cluster split occurred. This usually happens when Corosync experiences communication issues. If you see a red dot with an "X," and your server is powered on, it means that Corosync is having problems. Also, check the...

May you paste zpool status output? You can try to cleare ZFS error by using this command MM

Here an example for the zpool attach command: Find your pool with zpool status - probably your pool is rpool Note: be sure the new disk is clean (or formatted) I do not know with NVME, but you have to find your disk. For example with wwn lsblk -o +MODEL,SERIAL,WWN find the new disk and the...

seem that right now you do not have a mirror. You have to create a mirror from existing drive prepare the new disk! And then something like sudo zpool attach YourPool /path/to/your/existingdisk /path/to/your/newdisk

you have to create multiple virtual NICs on the VM

the UUID is not changed, are y sure? blkid

Sorry, yes you have to do the replace command. Probably if you list your zfs raid you will see the broken nvme like not present (in the examples sdc). ps. I do a mistake: replace grub-install /dev/sdc with grub-install /dev/sda For example: wwn-0x50014ee2b8c15f36 = code/PATH of the NEW DISK...

you have to change /dev/sdc and /dev/sda with your drives. Find the exact path of you drive. The /dev/sdc and /dev/sda are only an exaples.

Hello everyone, while upgrading from Proxmox 7 to 8, we encountered a significant issue during the migration from kernel 5.15 to 6.2 and vice versa. All the machines were frozen. Furthermore, when attempting to migrate from kernel 6.2 to 6.2, but with QEMU from 8 to 7, Proxmox became upset...

for zfs raid boot device the coplet sequence : Replace the physical failed/offline drive i.e. /dev/sdc with new i.e. /dev/sda wipefs --all --force /dev/sda* (clean operation) sgdisk --replicate=/dev/sdb /dev/sda (replicate operation) grub-install /dev/sdc (only if bootable) zpool replace mypool...

try sgdisk --replicate=/dev/sdb /dev/sda the size must be the same.

nomaly you do not have to do nothing. It could be an hardware problem

You can see the content of the storage nfs?

1. You can select vlan_aware on the vmbr interface on the PVE (no tag on the fisical interface) , then you can create one or more vmbr interface to your vm with the vlan tag you need.(this work for you, right?) Or You can also make linux vlan on the pve and then create vmbr bridge with this...

Humm, I do not know, mabe you can configure 2 or more vlan on proxmox and see 2 or more network on your VM?

the switch is configured to accept all vlan you need?

be sure you have the lines bridge-vlan-aware yes bridge-vids 2-4094 in your /etc/network/interface on proxmox for the bridge you use then you can try tu put the vlan tag (one or more) in the network configuratin in your VM and do not use tag on OS of the VM