Recent content by jsterr

Nothing has changed regarding this afaik. You need switchport with multiple vlans on it (vlan trunk), then create a vmbr0 with a bridged port (that connects to your switchport that(s) with the vlans on it). Then USE the sdn, as its the most simple way to do vlans for vm-access. If you also want...

Crimson is not included in pveceph yet.

I personally would look for journalctl -u pveproxy.service limiting with --since to the time-frame where you had that error. If it was 5 minutes ago for example it is: journalctl -u pveproxy.service --since "5 minutes ago"

Will ZFS 2.4 will come with a update within the 9.1.x window or is it planned for 9.2 (april?) https://git.proxmox.com/?p=zfsonlinux.git;a=summary

Yeah the customer thought it is needed and forgot about it. Setting it to 1 did the job :-)

multipath_component_detection = 0 needed to be set to 1 in /etc/lvm/lvm.conf - customer set the parameter, which caused this error. Thank you all for your help, I learned alot about iSCSI. Even created my own iSCSI-Target in a debian-vm to test it out myself (where it did work on first try)

I tried it again with aliases, everything looks correct until I need to create the pv and vg. I opened a proxmox subscription ticket.

Quincy is already EOL upgrade to Reef and then maybe even to squid. The Bug you mentioned is only shown for ceph 18 at least on clysos side. But there are other for ceph 19. I personally dont have any issues with 19.x so far.

https://pve.proxmox.com/wiki/Ceph_Quincy_to_Reef thats the one. (17 to 18) https://pve.proxmox.com/wiki/Ceph_Reef_to_Squid (18 to 19)

We also did 15 upgrades from ceph 19 to 20 in nested pve-environments (all clean installs from training) all went fine without issues. The only thing which was not 100% clear howto check what mds-services are standby via cli: We looked at the webui to find out. Adding a cli command might be...

You could also boot the debug mode from the installer and try to capture the logs, the debugging mode also helps to identify on which step exactly in the installer the reboot will be triggerd.

Can you try on a identical machine to see if its hardware related (as it sounds like?)

Geht nur wenn die VMs nicht im HA sind, aber wenn man HA hat, macht man eher eh ne Live-Migration bei ner Wartung ;-)

Someone has a idea to further troubleshoot this? The lvm filter should not be needed - the steps I took match with the guide from proxmox. Is my storage.cfg correct with the 4 iscsi-entries? iscsi: iscsi portal 10.10.1.71 target...

Hello check: https://pve.proxmox.com/wiki/Migrate_to_Proxmox_VE https://pve.proxmox.com/wiki/Advanced_Migration_Techniques_to_Proxmox_VE 7 hours sounds wrong but depends on the network you use and how much data you can transfer. But post a thread in english section of the forum if you need...