• @[email protected]OP
      link
      fedilink
      English
      93 days ago

      My “servers” are headless, in the basement, so even if I’m home, it’s still remote :D

    • @[email protected]
      link
      fedilink
      English
      3
      edit-2
      3 days ago

      I tell myself that every time, but I mean, I still end up doing it every time anyway lmao

      edit: Just did it, it went well.

    • @[email protected]
      link
      fedilink
      English
      23 days ago

      My work computer is Debian and I’m so looking forward to the upgrade. Just gotta contain myself for a free weeks until a 0.1 type update is released.

      • @[email protected]
        link
        fedilink
        English
        12 days ago

        There is no need ibthink. I did all 12 of my cluster at home plus all the work proxmox with no issues

        • @[email protected]
          link
          fedilink
          English
          12 days ago

          It might be safer to wait, one of my IRL friends ran into an issue, and I saw some others post about it on the Proxmox forums: TASK ERROR: activating LV 'pve/data' failed: Check of pool pve/data failed (status:64). Manual repair required!

          I think I didn’t run into that error because I flattened my LVM kinda, but if I hadn’t customized my setup maybe I would have run into that too.

          • @[email protected]
            link
            fedilink
            English
            12 days ago

            Its in the release upgrade notes. There isvone command to run if you are doing lvm. All my stuff is zfs or ceph so i never ran into it

                • @[email protected]
                  link
                  fedilink
                  English
                  1
                  edit-2
                  2 days ago

                  and the pve8to9 checklist script suggests to run this migration script if necessary

                  Ah, okay that makes more sense.

                  This is going to affect many more people who didn’t read it, then.

                  Although, that seems to only affect guests and not hosts?

                  The host machine becomes unbootable IIRC, so I think it’s something else?