monovergent 🛠️

  • 5 Posts
  • 37 Comments
Joined 2 years ago
cake
Cake day: November 27th, 2023

help-circle










  • Among the people I know in real life, some post (non-tech stuff) to Reddit, some write reviews on Yelp, and some have called customer support hotlines for tech products. But none have ever posted online to ask for tech help, at least not to my awareness. Neither did I back when I used Windows, and not for a couple years even after switching to Linux.

    I suspect most Ubuntu users are among that common crowd. They might look up an issue on the internet, but expect to ask for help from a dedicated support center. Or can’t be bothered to sign up for an account and post to the places that can answer their questions, which are usually very “techy” and possibly even intimidating to beginners.

    As for my setup, the upgrade from Debian 12 to 13 went very smoothly. I had to fix a few obscure config files, but nobody else really touches them, and it didn’t stop it from booting. Replaced a deprecated package with its Flatpak equivalent as well. Only unsolved issue is the xfce4-panel consuming all of one core on occasion for no apparent reason.








  • I got away with a 380 MB /boot during upgrade, though that assumes you aren’t dual booting another distro that also needs some room. Have you tried deleting old kernel versions?

    But if you want to future-proof, the issue is that shrinking a partition from its “top” is not a supported function. For ease of explanation, suppose we want a 1.5 GB /boot partition:

    1. Shrink nvme0n1p3 by 1.5 GB
    2. Create a new partition and format
    3. dd the old boot partition to the new partition
    4. Resize the new /boot partition to the full 1.5 GB
    5. Delete the old boot partition
    6. For good measure, reinstall GRUB to make sure it is aware of the new partition: https://wiki.debian.org/GrubEFIReinstall

    This assumes your fstab file mounts by UUID (default in recent versions of Debian). If not, update /etc/fstab to match the new partition. It’s been a while since I last did this, so definitely have your backup on hand and perhaps double check with other resources in case I left out any steps.

    More precisely, shrinking relies on the presence of empty blocks. A filesystem usually fills from “top” to “bottom”, so there would be no empty blocks to shave off the top of your nvme0n1p3, you can only shave off at the end. If you really don’t want /boot at the end, you’ll have to shrink nvme0n1p3, back it up, delete nvme0n1p3, expand /boot, re-create nvme0n1p3, and dd the backup back into its place.