Not enough space on ⁄boot partition [Solved]

[artytux]

Had to go and read that link, Just finish up with saying to @dolphin_oracle and @DukeComposed and @nosoynadie , I appreciate your help, Thanks

[dolphin_oracle]

linux-image-amd64 and linux-headers-amd64 will pull in the most current debian stable kernel (6.1.0-23 I think is the debian versioning).

and you're welcome

[artytux]

linux-image-amd64 and linux-headers-amd64 will pull in the most current debian stable kernel (6.1.0-23 I think is the debian versioning).

and you're welcome

Instead of muddling this install any more than need to, I will get the iso-KDE MX-23.3_x64 KDE, with the 6.1 kernel and ahs repos enabled from the downloads page and work on/with that to see find if I was too hasty in picking up other kernel, have idea 6.1 kernel isn't up to Gen 14 and 6.10 is up to gen 14
MX-23.3_August_KDE.iso
only a test on live sess will confirm.

Thanks to all for your time and patience.

[jj 5117]

Same problem for me this morning. Same cause.
I used this thread as a template cure, keeping AMD drivers not NVIDIA.
It worked.
Thanks very much.

Questions:
Is 512MB the maximum size for /boot?
Is it OK to directly delete kernels from /boot, or is there a better method?

Edit: I don't mind living near the edge w/ AHS.

[Kermit the Frog]

... Is 512MB the maximum size for /boot?

Nope. No limits.

... Is it OK to directly delete kernels from /boot ... ?

When you tried everything and when only there is no other way.

... or is there a better method?

"Chroot Rescue Scan" with a live session or any other installed MX / antiX and start either MXPI or "MX Cleanup" or Synaptic :

Code: Select all

mx-packageinstaller

Code: Select all

mx-cleanup

Code: Select all

synaptic-pkexec

... or directly use commands (apt etc.) ...

[jj 5117]

@Kermit the Frog

Killer. Thanks Kermit.

[Kermit the Frog]

You're welcome. Forgot to say one thing:

With chroot way (no matter with the CRS or manually) you may need to mount the boot partition first to /boot cause when trying to remove them it won't be able to find that path . (Normally it gets mounted automatically when booting. But when it's on a separate partition and that system is not booted the /boot folder will be empty).

[jj 5117]

@Kermit the Frog

Cool. That explains prior problems I had w/ chrooting--And might also need to know that w/ the MX tool.

thx.

[fehlix]

You're welcome. Forgot to say one thing:

With chroot way (no matter with the CRS or manually) you may need to mount the boot partition first to /boot cause when trying to remove them it won't be able to find that path . (Normally it gets mounted automatically when booting. But when it's on a separate partition and that system is not booted the /boot folder will be empty).

Maybe you found a bug within chroot-rescue-scan (or you run an ancient version),
b/c chroot-rescue-scan is made such, when "visiting" a detected linux install,
you can run all normal operations like
update-grub
install or remove kernels used any apt-based tools, like apt-get, etc.
where always /boot would be involved.
This without the user to prepare further the chroot environment and without checking /etc/fstab
This was actually one goal of the tool, to make it simple, to rescue a system
or perform other normal tasks.

[artytux]

Same problem for me this morning. Same cause.
I used this thread as a template cure, keeping AMD drivers not NVIDIA.
It worked.
Thanks very much.

Questions:
Is 512MB the maximum size for /boot?
Is it OK to directly delete kernels from /boot, or is there a better method?

Edit: I don't mind living near the edge w/ AHS.

After @dolphin_oracle help clearing cleaning my install I set about clearing out the leftovers

Mxpi if only to remove just the kernels

found best for me to use Synaptic package manager to also remove rc = config files , here is what I did

to check e.g rc in kernels =

Code: Select all

 dpkg --list | egrep -i --color 'linux-image|linux-headers'

to check ALL of the unwanted configs on board

Code: Select all

 apt list '?config-files'

Click on the “Status” button at the bottom of the left pane. If the category “Not installed (residual config)” shows is there, select it and remove everything that shows up in the list of packages.
then you can check and/or double check before removing those old configs.

Now my system was

Code: Select all

┌─[fa@fa]─[21:01:39_Mon_26 08 2024]─────────────────────────────────────────────────────────────────┘
└─> dpkg --list | egrep -i --color 'linux-image|linux-headers'
ii  linux-headers-6.7.11-1-liquorix-amd64         6.7-17~mx23ahs                         amd64        Header files for Linux 6.7.11-1-liquorix-amd64
ii  linux-image-6.10.6-2-liquorix-amd64           6.10-6~mx23ahs                         amd64        Linux 6.10 for 64-bit PCs
rc  linux-image-6.7.10-1-liquorix-amd64           6.7-14~mx23ahs                         amd64        Linux 6.7 for 64-bit PCs
rc  linux-image-6.7.11-1-liquorix-amd64           6.7-17~mx23ahs                         amd64        Linux 6.7 for 64-bit PCs
rc  linux-image-6.7.12-1-liquorix-amd64           6.7-18~mx23ahs                         amd64        Linux 6.7 for 64-bit PCs
rc  linux-image-6.7.6-1-liquorix-amd64            6.7-11~mx23ahs                         amd64        Linux 6.7 for 64-bit PCs
rc  linux-image-6.7.9-1-liquorix-amd64            6.7-13~mx23ahs                         amd64        Linux 6.7 for 64-bit PCs
rc  linux-image-6.8.10-2-liquorix-amd64           6.8-16~mx23ahs                         amd64        Linux 6.8 for 64-bit PCs
rc  linux-image-6.8.12-1-liquorix-amd64           6.8-18~mx23ahs                         amd64        Linux 6.8 for 64-bit PCs
rc  linux-image-6.8.7-2-liquorix-amd64            6.8-8~mx23ahs                          amd64        Linux 6.8 for 64-bit PCs
rc  linux-image-6.8.8-1-liquorix-amd64            6.8-9~mx23ahs                          amd64        Linux 6.8 for 64-bit PCs
rc  linux-image-6.8.9-1-liquorix-amd64            6.8-10~mx23ahs                         amd64        Linux 6.8 for 64-bit PCs
rc  linux-image-6.8.9-3-liquorix-amd64            6.8-12~mx23ahs                         amd64        Linux 6.8 for 64-bit PCs
rc  linux-image-6.9.11-1-liquorix-amd64           6.9-10~mx23ahs                         amd64        Linux 6.9 for 64-bit PCs
rc  linux-image-6.9.12-1-liquorix-amd64           6.9-11~mx23ahs                         amd64        Linux 6.9 for 64-bit PCs
ii  linux-image-6.9.12-2-liquorix-amd64           6.9-12~mx23ahs                         amd64        Linux 6.9 for 64-bit PCs
rc  linux-image-amd64                             6.1.76-1                               amd64        Linux for 64-bit PCs (meta-package)
ii  linux-image-liquorix-amd64                    6.10-6~mx23ahs                         amd64        Linux image for liquorix on 64-bit PCs
                                                                                                [/]─┐

Now it

Code: Select all

┌─[fa@fa]─[09:06:40_Sun_01 09 2024]─────────────────────────────────────────────────────────────────────────────────┘
└─>  dpkg --list | egrep -i --color 'linux-image|linux-headers'
ii  linux-headers-6.7.11-1-liquorix-amd64         6.7-17~mx23ahs                         amd64        Header files for Linux 6.7.11-1-liquorix-amd64
ii  linux-image-6.10.6-2-liquorix-amd64           6.10-6~mx23ahs                         amd64        Linux 6.10 for 64-bit PCs
ii  linux-image-6.9.12-2-liquorix-amd64           6.9-12~mx23ahs                         amd64        Linux 6.9 for 64-bit PCs
ii  linux-image-liquorix-amd64                    6.10-6~mx23ahs                         amd64        Linux image for liquorix on 64-bit PCs
                                                                                                                [/]─┐
┌─[fa@fa]─[09:06:47_Sun_01 09 2024]─────────────────────────────────────────────────────────────────────────────────┘
└─>  apt list '?config-files'
Listing... Done