Not enough space on ⁄boot partition [Solved]

[artytux]

On Sunday upgraded Liquorix 6.9.12-2 up to Liquorix 6.10.6-2

After upgrade then reboot got message 'Not enough space on /boot partition' removed third kernel with MXPI.

Startup this morning that message reappears , Not enough space on /boot partition
MX Cleanup removed shade over 800Mb
The message is still showing after reboot later.

Code: Select all

Snapshot created on: 20240825_1517
System:
  Kernel: 6.10.6-2-liquorix-amd64 [6.10-6~mx23ahs] arch: x86_64 bits: 64 compiler: gcc v: 12.2.0 parameters: audit=0
    intel_pstate=disable BOOT_IMAGE=/vmlinuz-6.10.6-2-liquorix-amd64 root=UUID=<filter> ro quiet
    splash
  Desktop: KDE Plasma v: 5.27.5 wm: kwin_x11 vt: 7 dm: SDDM Distro: MX-23.3_KDE Libretto 2024 01
    21 base: Debian GNU/Linux 12 (bookworm)
Machine:
  Type: Desktop Mobo: ASRock model: B660M-HDV serial: <superuser required> UEFI: American
    Megatrends LLC. v: 17.01 date: 01/11/2024
CPU:
  Info: model: Intel Core i7-14700F bits: 64 type: MST AMCP arch: Raptor Lake gen: core 14
    level: v3 note: check built: 2022+ process: Intel 7 (10nm) family: 6 model-id: 0xB7 (183)
    stepping: 1 microcode: 0x123
  Topology: cpus: 1x cores: 20 mt: 8 tpc: 2 st: 12 threads: 28 smt: enabled cache: L1: 1.8 MiB
    desc: d-12x32 KiB, 8x48 KiB; i-8x32 KiB, 12x64 KiB L2: 28 MiB desc: 8x2 MiB, 3x4 MiB L3: 33 MiB
    desc: 1x33 MiB
  Speed (MHz): avg: 1063 high: 5303 min/max: 800/2101 boost: enabled scaling:
    driver: acpi-cpufreq governor: ondemand cores: 1: 1300 2: 1300 3: 967 4: 800 5: 5303 6: 800
    7: 800 8: 800 9: 800 10: 800 11: 800 12: 800 13: 800 14: 2101 15: 800 16: 800 17: 900 18: 900
    19: 800 20: 800 21: 900 22: 800 23: 900 24: 800 25: 816 26: 800 27: 800 28: 800
    bogomips: 118272
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Vulnerabilities:
  Type: gather_data_sampling status: Not affected
  Type: itlb_multihit status: Not affected
  Type: l1tf status: Not affected
  Type: mds status: Not affected
  Type: meltdown status: Not affected
  Type: mmio_stale_data status: Not affected
  Type: reg_file_data_sampling mitigation: Clear Register File
  Type: retbleed status: Not affected
  Type: spec_rstack_overflow status: Not affected
  Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
  Type: spectre_v2 mitigation: Enhanced / Automatic IBRS; IBPB: conditional; RSB filling;
    PBRSB-eIBRS: SW sequence; BHI: BHI_DIS_S
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: Intel DG2 [Arc A750] driver: i915 v: kernel alternate: xe arch: Gen-12.7
    code: Alchemist process: TSMC n6 (7nm) built: 2022+ pcie: gen: 1 speed: 2.5 GT/s lanes: 1 ports:
    active: DP-1,HDMI-A-1 empty: DP-2, DP-3, DP-4, HDMI-A-2, HDMI-A-3 bus-ID: 03:00.0
    chip-ID: 8086:56a1 class-ID: 0300
  Display: x11 server: X.Org v: 1.21.1.7 with: Xwayland v: 22.1.9 compositor: kwin_x11 driver: X:
    loaded: modesetting unloaded: fbdev,vesa dri: iris gpu: i915 display-ID: :0 screens: 1
  Screen-1: 0 s-res: 7680x2160 s-dpi: 96 s-size: 2032x571mm (80.00x22.48") s-diag: 2111mm (83.1")
  Monitor-1: DP-1 pos: primary,left model: Samsung built: 2021 res: 3840x2160 hz: 60 dpi: 52
    gamma: 1.2 size: 1872x1053mm (73.7x41.46") diag: 801mm (31.5") ratio: 16:9 modes: max: 3840x2160
    min: 640x480
  Monitor-2: HDMI-A-1 mapped: HDMI-1 pos: right model: Samsung built: 2021 res: 3840x2160 hz: 60
    dpi: 52 gamma: 1.2 size: 1872x1053mm (73.7x41.46") diag: 801mm (31.5") ratio: 16:9 modes:
    max: 3840x2160 min: 640x480
  API: OpenGL v: 4.6 Mesa 23.1.2-1~mx23ahs renderer: Mesa Intel Arc A750 Graphics (DG2)
    direct-render: Yes
Audio:
  Device-1: Intel Alder Lake-S HD Audio vendor: ASRock driver: snd_hda_intel v: kernel
    alternate: snd_soc_avs,snd_sof_pci_intel_tgl bus-ID: 00:1f.3 chip-ID: 8086:7ad0 class-ID: 0403
  Device-2: Intel DG2 Audio driver: snd_hda_intel v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1
    bus-ID: 04:00.0 chip-ID: 8086:4f90 class-ID: 0403
  API: ALSA v: k6.10.6-2-liquorix-amd64 status: kernel-api tools: alsamixer,amixer
  Server-1: PipeWire v: 1.0.0 status: active with: 1: pipewire-pulse status: active
    2: wireplumber status: active 3: pipewire-alsa type: plugin 4: pw-jack type: plugin
    tools: pactl,pw-cat,pw-cli,wpctl
Network:
  Device-1: Intel Ethernet I219-V vendor: ASRock driver: e1000e v: kernel port: N/A bus-ID: 00:1f.6
    chip-ID: 8086:1a1d class-ID: 0200
  IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Bluetooth:
  Device-1: Cambridge Silicon Radio Bluetooth Dongle (HCI mode) type: USB driver: btusb v: 0.8
    bus-ID: 1-10:12 chip-ID: 0a12:0001 class-ID: e001
  Report: hciconfig ID: hci0 rfk-id: 0 state: up address: <filter> bt-v: 2.1 lmp-v: 4.0
    sub-v: 22bb hci-v: 4.0 rev: 22bb
  Info: acl-mtu: 310:10 sco-mtu: 64:8 link-policy: rswitch hold sniff park
    link-mode: peripheral accept service-classes: rendering, capturing, object transfer, audio,
    telephony
Drives:
  Local Storage: total: 9.12 TiB used: 1.69 TiB (18.5%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: HP model: SSD EX900 Plus 512GB size: 476.94 GiB
    block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4 type: SSD serial: <filter>
    rev: 1.4.7.61 temp: 45.9 C scheme: GPT
  ID-2: /dev/sda maj-min: 8:0 vendor: Lexar model: SSD NS100 512GB size: 476.94 GiB block-size:
    physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: 357 scheme: GPT
  ID-3: /dev/sdb maj-min: 8:16 type: USB vendor: Toshiba model: External USB 3.0 size: 1.82 TiB
    block-size: physical: 512 B logical: 512 B type: N/A serial: <filter> rev: 5438 scheme: MBR
  ID-4: /dev/sdc maj-min: 8:32 type: USB vendor: Western Digital model: WD20SDRW-11VUUS0
    size: 1.82 TiB block-size: physical: 512 B logical: 512 B type: HDD rpm: 5400 serial: <filter>
    rev: 1026 scheme: GPT
  ID-5: /dev/sdd maj-min: 8:48 type: USB vendor: Western Digital model: WD50NDZW-11MR8S1
    size: 4.55 TiB block-size: physical: 4096 B logical: 512 B type: HDD rpm: 5400 serial: <filter>
    rev: 4010 scheme: GPT
Partition:
  ID-1: / raw-size: 50 GiB size: 48.91 GiB (97.83%) used: 14.74 GiB (30.1%) fs: ext4
    dev: /dev/nvme0n1p4 maj-min: 259:4
  ID-2: /boot raw-size: 612 MiB size: 585.5 MiB (95.67%) used: 398.5 MiB (68.1%) fs: ext4
    dev: /dev/nvme0n1p2 maj-min: 259:2
  ID-3: /boot/efi raw-size: 102 MiB size: 100.4 MiB (98.45%) used: 274 KiB (0.3%) fs: vfat
    dev: /dev/nvme0n1p1 maj-min: 259:1
  ID-4: /home raw-size: 100 GiB size: 97.87 GiB (97.87%) used: 4.01 GiB (4.1%) fs: ext4
    dev: /dev/nvme0n1p5 maj-min: 259:5
Swap:
  Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default)
  ID-1: swap-1 type: partition size: 1.25 GiB used: 0 KiB (0.0%) priority: -2 dev: /dev/nvme0n1p3
    maj-min: 259:3
Sensors:
  System Temperatures: cpu: 50.0 C mobo: N/A
  Fan Speeds (RPM): N/A
Repos:
  Packages: 2659 pm: dpkg pkgs: 2653 libs: 1397 tools: apt,apt-get,aptitude,nala,synaptic pm: rpm
    pkgs: 0 pm: flatpak pkgs: 6
  No active apt repos in: /etc/apt/sources.list
  Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
    1: deb http://deb.debian.org/debian bookworm-updates main contrib non-free non-free-firmware
  Active apt repos in: /etc/apt/sources.list.d/debian.list
    1: deb http://deb.debian.org/debian bookworm main contrib non-free non-free-firmware
    2: deb http://security.debian.org/debian-security bookworm-security main contrib non-free non-free-firmware
  Active apt repos in: /etc/apt/sources.list.d/mx.list
    1: deb http://mx.debian.nz/mx/repo/ bookworm main non-free
    2: deb http://mx.debian.nz/mx/repo/ bookworm ahs
Info:
  Processes: 518 Uptime: 1h 4m wakeups: 1 Memory: 62.64 GiB used: 5.27 GiB (8.4%) Init: SysVinit
  v: 3.06 runlevel: 5 default: graphical tool: systemctl Compilers: gcc: 12.2.0 alt: 12
  Client: shell wrapper v: 5.2.15-release inxi: 3.3.26
Boot Mode: UEFI

Isit possible the Linux-images marked with 'rc' cause this and how can they be removed ?

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
                                                                                                [/]─┐

I had the idea that had plenty enough room, this is with only two kernels have had upto three onboard with no problems

Code: Select all

└─> df
Filesystem      1K-blocks       Used  Available Use% Mounted on
udev             32705388          0   32705388   0% /dev
tmpfs             6568052       1752    6566300   1% /run
/dev/nvme0n1p4   51290592   15453844   33198924  32% /
efivarfs              192        110         78  59% /sys/firmware/efi/efivars
tmpfs                5120         12       5108   1% /run/lock
tmpfs            13398240          8   13398232   1% /dev/shm
/dev/nvme0n1p2     599528     408020     147644  74% /boot
/dev/nvme0n1p1     102825        274     102551   1% /boot/efi
/dev/nvme0n1p5  102626232    4208624   93158344   5% /home
cgroup                 12          0         12   0% /sys/fs/cgroup
tmpfs             6568048         28    6568020   1% /run/user/1000
/dev/sdc1      1921710580  381509388 1442510824  21% /media/fa/Paperport
/dev/sdb1      1921721536  315807592 1508222040  18% /media/fa/Musiclog
/dev/sdd1      4844093152 1092674000 3507215992  24% /media/fa/B.I.T.B.T.S.

Don't know is there something I have missed ? because inpast have had three Kernels sitting in with no problems, I realize the kernels get bigger over time cannot be that big thou.
Any help
Fully Appreciated

Thanks in advance.

[DukeComposed]

On Sunday upgraded Liquorix 6.9.12-2 up to Liquorix 6.10.6-2

After upgrade then reboot got message 'Not enough space on /boot partition' removed third kernel with MXPI.

Startup this morning that message reappears , Not enough space on /boot partition
MX Cleanup removed shade over 800Mb
The message is still showing after reboot later.

Your QSI is showing that you have a separate /boot partition with only about 180 MiB of free space. MX Cleanup will remove a lot of old files from your machine, things like old logs, but those logs don't live under /boot and removing them won't help you here.

Isit possible the Linux-images marked with 'rc' cause this and how can they be removed ?

These old kernel configs don't live under /boot, and removing them won't help you here.

I had the idea that had plenty enough room, this is with only two kernels have had upto three onboard with no problems

Code: Select all

└─> df
Filesystem      1K-blocks       Used  Available Use% Mounted on
/dev/nvme0n1p2     599528     408020     147644  74% /boot
/dev/nvme0n1p1     102825        274     102551   1% /boot/efi

Don't know is there something I have missed ? because inpast have had three Kernels sitting in with no problems, I realize the kernels get bigger over time cannot be that big thou.

Kernels can be that big. In fact, the recent 6.9 kernels' initramfs files have gotten huge. The one thing you missed is actually looking at what's taking up so much space underneath /boot. It's probably the initramfs files for your 6.9 and 6.10 Liquorix kernels.

[nosoynadie]

Hi

"rc" means that you have uninstalled the program but NOT its configuration files.
That may be the problem.

[artytux]

Hi

"rc" means that you have uninstalled the program but NOT its configuration files.
That may be the problem.

OK thanks for that.

[artytux]

@DukeComposed

It's probably the initramfs files for your 6.9 and 6.10 Liquorix kernels.

This is over my level so what has to be done ?

[artytux]

I'm reading up on initrd clear as mud. I'll keep reading ugh.

[dolphin_oracle]

long and short. the initramfs files for kernels generated with the latest firmware in ahs, and 6.9 kernels and up, will be over 250 mbs, rather than the 80ish mb prior. by default, the firmware for graphics is copied into the initramfs, and the nvidia package is particularly large.

there are a couple of ways to adjust this, but if you can't make your /boot larger and what 3 kernels, the easiest may be to remove a few firmware packages.

1. install mx-debian-firmware-compat (this will allow manual removal of firmware packages without removing the important mx-system package)
2. remove firmware-nvidia-graphics and firmware-amd-graphics (safe since you have intel graphics)
3. update the initramfs

Code: Select all

sudo update-initramfs -u -k all

The other less easy way is to revert to the firmware packages in stable rather than ahs, and then disable the ahs repo.

[artytux]

Thanks for the speedy reply only got to step 1

1. install mx-debian-firmware-compat (this will allow manual removal of firmware packages without removing the important mx-system package)

Got this

Problem detected while installing, please inspect the console output.

Code: Select all

Reading package lists...
Building dependency tree...
Reading state information...
The following packages will be REMOVED:
  mx-debian-firmware
The following NEW packages will be installed:
  mx-debian-firmware-compat
0 upgraded, 1 newly installed, 1 to remove and 0 not upgraded.
1 not fully installed or removed.
Need to get 1,792 B of archives.
After this operation, 1,024 B of additional disk space will be used.
Get:1 http://mx.debian.nz/mx/repo bookworm/main amd64 mx-debian-firmware-compat all 24.08.02 [1,792 B]
Fetched 1,792 B in 0s (16.5 kB/s)
dpkg: mx-debian-firmware: dependency problems, but removing anyway as you requested:
 mx-system depends on mx-debian-firmware | linux-firmware; however:
  Package mx-debian-firmware is to be removed.
  Package linux-firmware is not installed.

(Reading database ... 367023 files and directories currently installed.)
Removing mx-debian-firmware (24.08.10mx23) ...
Selecting previously unselected package mx-debian-firmware-compat.
(Reading database ... 367022 files and directories currently installed.)
Preparing to unpack .../mx-debian-firmware-compat_24.08.02_all.deb ...
Unpacking mx-debian-firmware-compat (24.08.02) ...
Setting up initramfs-tools (0.142) ...
update-initramfs: deferring update (trigger activated)
Setting up mx-debian-firmware-compat (24.08.02) ...
marking firmware package manually installed
Processing triggers for initramfs-tools (0.142) ...
update-initramfs: Generating /boot/initrd.img-6.10.6-2-liquorix-amd64
W: Possible missing firmware /lib/firmware/amd/amd_sev_fam19h_model1xh.sbin for module ccp
I: The initramfs will attempt to resume from /dev/nvme0n1p3
I: (UUID=e24ff749-9998-4424-9056-2405c82110c1)
I: Set the RESUME variable to override this.
zstd: error 70 : Write error : cannot write block : No space left on device 
E: mkinitramfs failure zstd -q -9 -T0 70
update-initramfs: failed for /boot/initrd.img-6.10.6-2-liquorix-amd64 with 1.
dpkg: error processing package initramfs-tools (--configure):
 installed initramfs-tools package post-installation script subprocess returned error exit status 1
Errors were encountered while processing:
 initramfs-tools
E: Sub-process /usr/bin/dpkg returned an error code (1)

[dolphin_oracle]

yeah cause the device is too full for the backup initramfs file. that error is still from a previous attempt, as mx-debian-firmware-compat doesn't actually trigger it. You may need to purge off a kernel until you get this resolved, as apt will continueing trying to finish installation everytime you use apt until it completes.

so now try purging off the two firmware packages I mentioned.

Code: Select all

sudo apt purge firmware-amd-graphics firmware-nvidia-graphics

[artytux]

results with this

Code: Select all

┌─[fa@fa]─[22:55:41_Mon_26 08 2024]─────────────────────────────────────────────────────────────────┘
└─> sudo apt purge firmware-amd-graphics firmware-nvidia-graphics
[sudo] password for fa:         
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following packages will be REMOVED:
  firmware-amd-graphics* firmware-linux* firmware-linux-nonfree* firmware-nvidia-graphics*
0 upgraded, 0 newly installed, 4 to remove and 0 not upgraded.
1 not fully installed or removed.
After this operation, 145 MB disk space will be freed.
Do you want to continue? [Y/n] y
(Reading database ... 367023 files and directories currently installed.)
Removing firmware-linux (20240709-1~mx23ahs) ...
Removing firmware-linux-nonfree (20240709-1~mx23ahs) ...
Removing firmware-amd-graphics (20240709-1~mx23ahs) ...
Removing firmware-nvidia-graphics (20240709-1~mx23ahs) ...
Setting up initramfs-tools (0.142) ...
update-initramfs: deferring update (trigger activated)
Processing triggers for initramfs-tools (0.142) ...
update-initramfs: Generating /boot/initrd.img-6.10.6-2-liquorix-amd64
W: Possible missing firmware /lib/firmware/amd/amd_sev_fam19h_model1xh.sbin for module ccp
I: The initramfs will attempt to resume from /dev/nvme0n1p3
I: (UUID=e24ff749-9998-4424-9056-2405c82110c1)
I: Set the RESUME variable to override this.