last year when I went back to Arch from Manjaro, I made a critical error. I’m not sure if I was just tired when partitioning things off or what. but I made my root only 20GB instead of the 50 that I had intended. I know in a lot use cases that’ll be fine, but in mine, not so much. with steam compat taking up 1-2gb and keeping one version of pacman cache, I’m constantly getting the redline warning.

Tonight I plan on booting to live and resize my luks drive and hopefully not fuck it. and if I do? oh well…Timeshift will hopefully save me.

  • ShortN0te@lemmy.ml
    0·
    9 months ago

    Remember to make sure that all the boot configs are updated correctly after the resize. It could happen that your boot manager does not find the partition to unlock after a resize

    • lemmyvore@feddit.nlEnglish
      0·
      9 months ago

      If you resize the partition? No, the UUID gets allocated when the partition is created and stays the same for the lifetime of the partition. It only changes if you explicitly change it manually. Which is something that’s only needed very rarely.

      For example I had to do it when I migrated my root disk to a larger SSD by cat-ing the entire disk to the new one and I wanted to keep both connected for a while (so I can boot into the old one in case anything went wrong). I had to change the UUID of the partition on the new disk but I still ran into some obscure grub issues and had to boot a system rescue live stick into the new disk to update grub properly. Overall it’s not a very good idea, in the future I think I’ll stick to rsync -avx root into the new partition.

      • ShortN0te@lemmy.ml
        0·
        9 months ago

        In my case it actually changed after i resized it. It was unexpected and broke my system. After i adjusted the UUID in the boot config it worked again.

        • lemmyvore@feddit.nlEnglish
          0·
          9 months ago

          That’s really unusual and yeah I can see how that would surprise you. What tool did you use to resize it?

          • ShortN0te@lemmy.ml
            0·
            9 months ago

            Thinking about what i did (already a few weeks ago) i think it makes sense now. A lot of sources suggested it would be easiest to delete the partition and simply create a new bigger one at the same start blocks. And then resize the FS. Then it actually makes sense why i ended up with another UUID.

            • lemmyvore@feddit.nlEnglish
              0·
              9 months ago

              Ahhhh I see now, that explains it. 😃 Yeah it’s not a bad method if you need to resize a partition in place, but you need to be super careful to restore all the partition parameters like sector size etc. exactly the same. And ofc to restore the previous UUID from inside the partition editor (fdisk or gpt) or with tune2fs -U.

              For future reference it’s best to use parted instead, which will take care of everything for you. Best to boot into a GParted live stick for any operations on essential partitions, not to do it on the live system. Same thing for copying partitions, use a Clonezilla live stick. With Ventoy you can make a USB stick with several such tools on it, you just install Ventoy and then drop ISO files on the stick.

  • epyon22@programming.dev
    0·
    9 months ago

    Highly recommend using lvm in the future. You can undersize your partitions and when whichever one you need more space on it’s easy to grow. Also really easy to live migrate to other drives as needed. Good luck.

  • CMDR_Horn@lemmy.mlOP
    0·
    9 months ago

    UPDATE

    Booted to live and used gparted. had to fiddle with un-encrypting/re-encrypting the partitions in order to move everything around correctly, but everything was successful.

    nothing ended up needing to be updated in boot. systemd-boot is so basic that so long as the uuids don’t change, then it don’t care.

    All in all a good experience.