Hello I would boot a sysrescuelinux or sth like that and then move all partitions after /dev/sda2 "to the right" with "sfdisk --move-data" until enough space exists for /boot to grow. But only with a solid backup of all my data. regards //chriss On 06.04.23 13:21, Fons Adriaensen wrote:

Hello all,

I'm having a problem with updating a laptop: the /boot partition is too small for the new ramfs images.

The system uses GPT partioning and BIOS boot using syslinux.

/dev/sda1 1M Type = BIOS Boot /dev/sda2 /boot 95M Attributes: LegacyBIOSBootable /dev/sda3 / 93G (others for /home, /data and SWAP)

One solution would be to move the /boot directory to / instead of giving it its own partition.

The syslinux wiki page tells me that the absolute sector address of /boot/syslinux/ldlinux.sys plays a role in the boot sequence, so I suspect that just moving the boot directory and removing /dev/sda2 from /etc/fstab won't be enough. Would re-installing syslinux after that do the trick (and also take care of the LegacyBIOSBootable attribute) ?

If not, what would be the correct and safe way to do this ?

TIA,

On Thu, Apr 06, 2023 at 03:41:15PM +0000, u34@net9.ga wrote:

As far as I remember, what you wrote, including reinstalling syslinux, does the trick.

It's what I did, and it did the trick.

Aren't there wiki articles about these subjects?

There are, but they can be confusing. The information is spread over multiple pages, and exploring these quickly feels like entering a never-ending rabbit hole. You basically never know if you've seen all of it and if the info you have is complete. Which is why I asked. It's of course a complicated subject, just consider MBR or GUID BIOS or UEFI GRUB or Syslinux Which already leads to (in theory) 8 possible combinations, and then we are ingnoring LVM, RAID, encryption, and probably a lot of other variations which interact in not always very clear ways. Ciao, -- FA