Not enough space on /boot partition?
Not enough space on /boot partition?
Hello,
I have been using Mx Linux for months now and for the most part the system has met all expectations of a stable and usable system. However recently I have been receiving error messages viewed as a pop up on the bottom right hand corner of my screen. It says: "Not enough space on /boot partition". I did not know what to do about this so ignored it but it came to the point where I could not update my system any longer. I ran MX Cleanup and that seem to help but only for a short period of time. I presume that MX Linux is writing and saving some sort of logs somewhere that is filling up my computer however as Windows did not do that I am not sure what action to take. Below is what I have in my drives when running the df command.
$ df -h
Filesystem Size Used Avail Use% Mounted on
udev 7.8G 0 7.8G 0% /dev
tmpfs 1.6G 2.8M 1.6G 1% /run
/dev/sda1 220G 208G 62M 100% /
tmpfs 5.0M 12K 5.0M 1% /run/lock
tmpfs 3.2G 154M 3.0G 5% /dev/shm
cgroup 12K 0 12K 0% /sys/fs/cgroup
tmpfs 1.6G 1.5M 1.6G 1% /run/user/1000
/dev/sr0 7.3G 7.3G 0 100% /media/Saskguy/DVD
/dev/sdb1 932G 761G 171G 82% /media/Saskguy/My Passport
/dev/sdc1 466G 457G 9.6G 98% /media/Saskguy/Elements
Does anyone have suggestions how to resolve this?
I have been using Mx Linux for months now and for the most part the system has met all expectations of a stable and usable system. However recently I have been receiving error messages viewed as a pop up on the bottom right hand corner of my screen. It says: "Not enough space on /boot partition". I did not know what to do about this so ignored it but it came to the point where I could not update my system any longer. I ran MX Cleanup and that seem to help but only for a short period of time. I presume that MX Linux is writing and saving some sort of logs somewhere that is filling up my computer however as Windows did not do that I am not sure what action to take. Below is what I have in my drives when running the df command.
$ df -h
Filesystem Size Used Avail Use% Mounted on
udev 7.8G 0 7.8G 0% /dev
tmpfs 1.6G 2.8M 1.6G 1% /run
/dev/sda1 220G 208G 62M 100% /
tmpfs 5.0M 12K 5.0M 1% /run/lock
tmpfs 3.2G 154M 3.0G 5% /dev/shm
cgroup 12K 0 12K 0% /sys/fs/cgroup
tmpfs 1.6G 1.5M 1.6G 1% /run/user/1000
/dev/sr0 7.3G 7.3G 0 100% /media/Saskguy/DVD
/dev/sdb1 932G 761G 171G 82% /media/Saskguy/My Passport
/dev/sdc1 466G 457G 9.6G 98% /media/Saskguy/Elements
Does anyone have suggestions how to resolve this?
- Eadwine Rose
- Administrator
- Posts: 14639
- Joined: Wed Jul 12, 2006 2:10 am
Re: Not enough space on /boot partition?
With all help requests, please share your full Quick System Info, found in the menu under Favorites. Press the Copy for forum button, then click paste in a reply. If need be, you can do this with the LiveUSB, thanks.
MX-23.6_x64 July 31 2023 * 6.1.0-37amd64 ext4 Xfce 4.20.0 * 8-core AMD Ryzen 7 2700
Asus TUF B450-Plus Gaming UEFI * Asus GTX 1050 Ti Nvidia 535.247.01 * 2x16Gb DDR4 2666 Kingston HyperX Predator
Samsung 870EVO * Samsung S24D330 & P2250 * HP Envy 5030
Asus TUF B450-Plus Gaming UEFI * Asus GTX 1050 Ti Nvidia 535.247.01 * 2x16Gb DDR4 2666 Kingston HyperX Predator
Samsung 870EVO * Samsung S24D330 & P2250 * HP Envy 5030
Re: Not enough space on /boot partition?
I am sorry, I presumed the info I pasted was sufficient. Here is what I have from the Quick System Info:
Code: Select all
System:
Kernel: 6.1.0-22-amd64 [6.1.94-1] arch: x86_64 bits: 64 compiler: gcc v: 12.2.0
parameters: BOOT_IMAGE=/boot/vmlinuz-6.1.0-22-amd64 root=UUID=<filter> ro quiet splash
resume=UUID=<filter> resume_offset=45172736
Desktop: Xfce v: 4.18.1 tk: Gtk v: 3.24.36 info: xfce4-panel wm: xfwm v: 4.18.0 vt: 7
dm: LightDM v: 1.26.0 Distro: MX-23.3_x64 Libretto October 15 2023 base: Debian GNU/Linux 12
(bookworm)
Machine:
Type: Desktop System: Dell product: OptiPlex 3050 v: N/A serial: <superuser required> Chassis:
type: 3 serial: <superuser required>
Mobo: Dell model: 08NPPY v: A00 serial: <superuser required> UEFI-[Legacy]: Dell v: 1.2.0
date: 12/22/2016
CPU:
Info: model: Intel Core i5-7500 bits: 64 type: MCP arch: Kaby Lake gen: core 7 level: v3
note: check built: 2018 process: Intel 14nm family: 6 model-id: 0x9E (158) stepping: 9
microcode: 0xF8
Topology: cpus: 1x cores: 4 smt: <unsupported> cache: L1: 256 KiB desc: d-4x32 KiB; i-4x32 KiB
L2: 1024 KiB desc: 4x256 KiB L3: 6 MiB desc: 1x6 MiB
Speed (MHz): avg: 800 min/max: 800/3800 scaling: driver: intel_pstate governor: powersave
cores: 1: 800 2: 800 3: 800 4: 800 bogomips: 27199
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Vulnerabilities:
Type: gather_data_sampling mitigation: Microcode
Type: itlb_multihit status: KVM: VMX disabled
Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT disabled
Type: mds mitigation: Clear CPU buffers; SMT disabled
Type: meltdown mitigation: PTI
Type: mmio_stale_data mitigation: Clear CPU buffers; SMT disabled
Type: reg_file_data_sampling status: Not affected
Type: retbleed mitigation: IBRS
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: IBRS; IBPB: conditional; STIBP: disabled; RSB filling;
PBRSB-eIBRS: Not affected; BHI: Not affected
Type: srbds mitigation: Microcode
Type: tsx_async_abort mitigation: TSX disabled
Graphics:
Device-1: Intel HD Graphics 630 vendor: Dell driver: i915 v: kernel arch: Gen-9.5
process: Intel 14nm built: 2016-20 ports: active: HDMI-A-1 empty: DP-1,DP-2,HDMI-A-2
bus-ID: 00:02.0 chip-ID: 8086:5912 class-ID: 0300
Display: x11 server: X.Org v: 1.21.1.7 compositor: xfwm v: 4.18.0 driver: X:
loaded: modesetting unloaded: fbdev,vesa dri: iris gpu: i915 display-ID: :0.0 screens: 1
Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.00x11.22") s-diag: 582mm (22.93")
Monitor-1: HDMI-A-1 mapped: HDMI-1 model: Samsung S24C570 serial: <filter> built: 2014
res: 1920x1080 hz: 60 dpi: 94 gamma: 1.2 size: 521x293mm (20.51x11.54") diag: 598mm (23.5")
ratio: 16:9 modes: max: 1920x1080 min: 720x400
API: OpenGL v: 4.6 Mesa 22.3.6 renderer: Mesa Intel HD Graphics 630 (KBL GT2)
direct-render: Yes
Audio:
Device-1: Intel 200 Series PCH HD Audio vendor: Dell driver: snd_hda_intel v: kernel
bus-ID: 00:1f.3 chip-ID: 8086:a2f0 class-ID: 0403
API: ALSA v: k6.1.0-22-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: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Dell driver: r8169
v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: e000 bus-ID: 02:00.0 chip-ID: 10ec:8168
class-ID: 0200
IF: eth0 state: down mac: <filter>
Device-2: Intel Wireless 7265 driver: iwlwifi v: kernel modules: wl pcie: gen: 1
speed: 2.5 GT/s lanes: 1 bus-ID: 03:00.0 chip-ID: 8086:095a class-ID: 0280
IF: wlan0 state: up mac: <filter>
IF-ID-1: tun0 state: unknown speed: 10 Mbps duplex: full mac: N/A
Bluetooth:
Device-1: Intel Bluetooth wireless interface type: USB driver: btusb v: 0.8 bus-ID: 1-3:2
chip-ID: 8087:0a2a class-ID: e001
Report: hciconfig ID: hci0 rfk-id: 1 state: up address: <filter> bt-v: 2.1 lmp-v: 4.2
sub-v: 1000 hci-v: 4.2 rev: 1000
Info: acl-mtu: 1021:5 sco-mtu: 96:6 link-policy: rswitch hold sniff
link-mode: peripheral accept service-classes: rendering, capturing, object transfer, audio,
telephony
RAID:
Hardware-1: Intel SATA Controller [RAID mode] driver: ahci v: 3.0 port: f060 bus-ID: 00:17.0
chip-ID: 8086:2822 rev: class-ID: 0104
Drives:
Local Storage: total: 1.58 TiB used: 1.39 TiB (87.9%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/sda maj-min: 8:0 vendor: SanDisk model: TEAM T253X1240G size: 223.57 GiB block-size:
physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: 6AK3 scheme: MBR
ID-2: /dev/sdb maj-min: 8:16 type: USB vendor: Western Digital model: WD My Passport 0748
size: 931.48 GiB block-size: physical: 512 B logical: 512 B type: N/A serial: <filter> rev: 1015
scheme: MBR
ID-3: /dev/sdc maj-min: 8:32 type: USB vendor: Western Digital model: WD5000BPVT-22HXZT1
size: 465.76 GiB block-size: physical: 512 B logical: 512 B type: HDD rpm: 5400 serial: <filter>
rev: 1.75 scheme: MBR
Partition:
ID-1: / raw-size: 223.57 GiB size: 219 GiB (97.96%) used: 207.76 GiB (94.9%) fs: ext4
dev: /dev/sda1 maj-min: 8:1
Swap:
Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: file size: 19.5 GiB used: 831 MiB (4.2%) priority: -2 file: /swap/swap
Sensors:
System Temperatures: cpu: 35.0 C mobo: N/A
Fan Speeds (RPM): N/A
Repos:
Packages: 2744 pm: dpkg pkgs: 2697 libs: 1534 tools: apt,apt-get,aptitude,nala,synaptic pm: rpm
pkgs: 0 pm: flatpak pkgs: 47
No active apt repos in: /etc/apt/sources.list
Active apt repos in: /etc/apt/sources.list.d/brave-browser-release.list
1: deb [arch=amd64] https://brave-browser-apt-release.s3.brave.com/ stable main
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/google-earth-pro.list
1: deb [arch=amd64] http://dl.google.com/linux/earth/deb/ stable main
Active apt repos in: /etc/apt/sources.list.d/megasync.list
1: deb [signed-by=/usr/share/keyrings/meganz-archive-keyring.gpg] https://mega.nz/linux/repo/Debian_12/ ./
Active apt repos in: /etc/apt/sources.list.d/mx.list
1: deb http://mxrepo.com/mx/repo/ bookworm main non-free
Active apt repos in: /etc/apt/sources.list.d/tradingview-desktop.list
1: deb [arch=amd64 signed-by=/usr/share/keyrings/tradingview-desktop-archive-keyring.gpg] https://tvd-packages.tradingview.com/ubuntu/stable jammy multiverse
Info:
Processes: 327 Uptime: 22d 19h 40m wakeups: 1 Memory: 15.51 GiB used: 8.58 GiB (55.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: BIOS (legacy, CSM, MBR)
Re: Not enough space on /boot partition?
I would start with MX Cleanup and look at how many Kernels you might be able to remove.
Keep both the current one, and either the previous one, or the very first one.
After that, I would install Stacer and see where you can clean / clear up. (Logs, cache, trash, etc )
Keep both the current one, and either the previous one, or the very first one.
After that, I would install Stacer and see where you can clean / clear up. (Logs, cache, trash, etc )
*QSI = Quick System Info from menu (Copy for Forum)
*MXPI = MX Package Installer
*Please check the solved checkbox on the post that solved it.
*Linux -This is the way!
*MXPI = MX Package Installer
*Please check the solved checkbox on the post that solved it.
*Linux -This is the way!
Re: Not enough space on /boot partition?
Why Stacer? MX Cleanup can clean old logs,trash, etc. Is Stacer more inclusive?CharlesV wrote: Sat Aug 17, 2024 3:40 pm I would start with MX Cleanup and look at how many Kernels you might be able to remove.
Keep both the current one, and either the previous one, or the very first one.
After that, I would install Stacer and see where you can clean / clear up. (Logs, cache, trash, etc )
Forum Rules
Guide - How to Ask for Help
richb Administrator
System: MX 23 KDE
AMD A8 7600 FM2+ CPU R7 Graphics, 16 GIG Mem. Three Samsung EVO SSD's 250 GB
Guide - How to Ask for Help
richb Administrator
System: MX 23 KDE
AMD A8 7600 FM2+ CPU R7 Graphics, 16 GIG Mem. Three Samsung EVO SSD's 250 GB
- DukeComposed
- Posts: 1396
- Joined: Thu Mar 16, 2023 1:57 pm
Re: Not enough space on /boot partition?
Don't presume. You can run Disk Usage Analyzer from the menu and it will tell you where all of your disk space is being used.saskguy wrote: Sat Aug 17, 2024 3:16 pm I presume that MX Linux is writing and saving some sort of logs somewhere that is filling up my computer
You can put text output from the terminal in a code block to improve formatting and readability. In this case it looks like your /dev/sda1 partition is full, so you should probably use a combination of Disk Usage Analyzer and du to find where all of your free space went.saskguy wrote: Sat Aug 17, 2024 3:16 pmDoes anyone have suggestions how to resolve this?Code: Select all
$ df -h Filesystem Size Used Avail Use% Mounted on /dev/sda1 220G 208G 62M 100% /
Re: Not enough space on /boot partition?
Yes, two:
Change with BIOS from SATA/RAID to SATA/AHCI:
Code: Select all
RAID:
Hardware-1: Intel SATA Controller [RAID mode] driver: ahci v: 3.0 port: f060 bus-ID: 00:17.0
chip-ID: 8086:2822 rev: class-ID: 0104
Code: Select all
Partition:
ID-1: / raw-size: 223.57 GiB size: 219 GiB (97.96%) used: 207.76 GiB (94.9%) fs: ext4
dev: /dev/sda1 maj-min: 8:1
Re: Not enough space on /boot partition?
Thanks for the reply. I did run the clean up tool and removed an unused kernel (6.1.0-23-amd64) which is newer than the one I am currently using oddly enough (6.1.0-22-amd64) and also old wifi drivers that together freed up around 500mb of space. However I don't understand why I am receiving this error in the first place, according to the clean up tool I have 12.7GB available on the hard drive where Mx Linux is installed in.
I can't seem to find the program "Stacer", it is not available in the package installer or on flathub, any suggestions on where to find this?
I can't seem to find the program "Stacer", it is not available in the package installer or on flathub, any suggestions on where to find this?
Re: Not enough space on /boot partition?
Stacer has two things that are of interest:richb wrote: Sat Aug 17, 2024 3:52 pmWhy Stacer? MX Cleanup can clean old logs,trash, etc. Is Stacer more inclusive?CharlesV wrote: Sat Aug 17, 2024 3:40 pm I would start with MX Cleanup and look at how many Kernels you might be able to remove.
Keep both the current one, and either the previous one, or the very first one.
After that, I would install Stacer and see where you can clean / clear up. (Logs, cache, trash, etc )
- First, you can *see* which / what is taking up how much space.
- Second, you can *select* an exact thing - so for example you can clear only a large cache or log file.
MX Cleanup is very good - and *really* useful for both quick cleanup as well as removing unused kernels easily. Shines right there! And you have the graphical usage as well.
I think both are great, and I use both slightly differently on their strengths.


*QSI = Quick System Info from menu (Copy for Forum)
*MXPI = MX Package Installer
*Please check the solved checkbox on the post that solved it.
*Linux -This is the way!
*MXPI = MX Package Installer
*Please check the solved checkbox on the post that solved it.
*Linux -This is the way!
Re: Not enough space on /boot partition?
Do you still get to popup, after cleaning?saskguy wrote: Sat Aug 17, 2024 4:09 pm Thanks for the reply. I did run the clean up tool and removed an unused kernel (6.1.0-23-amd64) which is newer than the one I am currently using oddly enough (6.1.0-22-amd64) and also old wifi drivers that together freed up around 500mb of space. However I don't understand why I am receiving this error in the first place, according to the clean up tool I have 12.7GB available on the hard drive where Mx Linux is installed in.
I can't seem to find the program "Stacer", it is not available in the package installer or on flathub, any suggestions on where to find this?
If yes, please open terminal as normal user and run:
Code: Select all
cleanup-notifier-mx
and if yes is that the same popup you have seen?
(Also as mentioned do get rid of the intels RAID stuff, this can create lot of confusion. )