I have a FAT32 partition that I use as my /boot directory. It ran out of capacity while I was trying to install new kernels.
So I expanded the boot partition from 256 MB to 512 MB. But this didn’t help. Even though the partition is 512 MB in size, it runs out of capacity with only 117.4 MB of files. In Dolphin it says “0 B free”.
Why is it that the full capacity can’t be accessed?
Might have become corrupt.
You can start to check it passively with fsck.vfat -n /dev/sdxx and see what that returns to start with.
Be careful and read up what you are doing before pressing anything, choose “no action” if in doubt.
Worst case scenario you have to reformat the partition and reinstall grub from a live usb.
Not as bad as it sounds though.
Edit
Question: since you mount it on /boot, I assume you are not using efi boot?
Thank you. But it didn’t give me any options.
[liam@Liam-Manjaro-Desktop ~]$ sudo fsck.vfat -n /dev/nvme0n1p5
fsck.fat 4.2 (2021-01-31)
There are differences between boot sector and its backup.
This is mostly harmless. Differences: (offset:original/backup)
65:01/00
Not automatically fixing this.
Dirty bit is set. Fs was not properly unmounted and some data may be corrupt.
Automatically removing dirty bit.
Leaving filesystem unchanged.
/dev/nvme0n1p5: 343 files, 258078/258078 clusters
Probably ok, but there is something.
You didn’t repond to my question about your bios and how you boot…
How old is your computer?
Output of inxi -Fazy please
And the log from the failed installation please. Dolphin probably just has no rights to read the capacity.
Because you need to format it too. And don’t forget to reinstall all kernels and microcode you’re using.
I have an Intel Haswell processor. Here’s the output of that command:
[liam@Liam-Manjaro-Desktop ~]$ inxi -Fazy
System:
Kernel: 5.10.187-1-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 13.1.1
parameters: BOOT_IMAGE=/vmlinuz-5.10-x86_64
root=UUID=933ff9e4-53cb-40d5-9717-8d2f94674fda rw quiet apparmor=1
security=apparmor udev.log_priority=3 nvidia-drm.modeset=1
Desktop: KDE Plasma v: 5.27.6 tk: Qt v: 5.15.10 wm: kwin_wayland vt: 1
dm: SDDM Distro: Manjaro Linux base: Arch Linux
Machine:
Type: Desktop Mobo: Gigabyte model: B85M-D3H v: x.x
serial: <superuser required> UEFI: American Megatrends v: F15
date: 08/20/2015
CPU:
Info: model: Intel Core i7-4790 bits: 64 type: MT MCP arch: Haswell
gen: core 4 level: v3 note: check built: 2013-15 process: Intel 22nm
family: 6 model-id: 0x3C (60) stepping: 3 microcode: 0x28
Topology: cpus: 1x cores: 4 tpc: 2 threads: 8 smt: enabled cache:
L1: 256 KiB desc: d-4x32 KiB; i-4x32 KiB L2: 1024 KiB desc: 4x256 KiB
L3: 8 MiB desc: 1x8 MiB
Speed (MHz): avg: 3492 high: 3744 min/max: 800/4000 scaling:
driver: intel_cpufreq governor: schedutil cores: 1: 3013 2: 3622 3: 3744
4: 3462 5: 3289 6: 3589 7: 3637 8: 3585 bogomips: 57491
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Vulnerabilities:
Type: itlb_multihit status: KVM: VMX disabled
Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT
vulnerable
Type: mds mitigation: Clear CPU buffers; SMT vulnerable
Type: meltdown mitigation: PTI
Type: mmio_stale_data status: Unknown: No mitigations
Type: retbleed status: Not affected
Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via
prctl and seccomp
Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer
sanitization
Type: spectre_v2 mitigation: Retpolines, IBPB: conditional, IBRS_FW,
STIBP: conditional, RSB filling, PBRSB-eIBRS: Not affected
Type: srbds mitigation: Microcode
Type: tsx_async_abort status: Not affected
Graphics:
Device-1: NVIDIA GM206 [GeForce GTX 960] vendor: eVga.com. driver: nvidia
v: 535.86.05 alternate: nouveau,nvidia_drm non-free: 535.xx+
status: current (as of 2023-07) arch: Maxwell code: GMxxx
process: TSMC 28nm built: 2014-19 pcie: gen: 3 speed: 8 GT/s lanes: 16
ports: active: none off: DP-3,HDMI-A-1 empty: DP-1,DP-2,DVI-I-1
bus-ID: 01:00.0 chip-ID: 10de:1401 class-ID: 0300
Display: wayland server: X.org v: 1.21.1.8 with: Xwayland v: 23.1.2
compositor: kwin_wayland driver: X: loaded: nvidia gpu: nvidia display-ID: 0
Monitor-1: DP-3 res: 1920x1200 size: N/A modes: N/A
API: OpenGL v: 4.6.0 NVIDIA 535.86.05 renderer: NVIDIA GeForce GTX
960/PCIe/SSE2 direct-render: Yes
Audio:
Device-1: Intel 8 Series/C220 Series High Definition Audio vendor: Gigabyte 8
driver: snd_hda_intel v: kernel bus-ID: 00:1b.0 chip-ID: 8086:8c20
class-ID: 0403
Device-2: Logitech QuickCam Communicate STX
driver: gspca_zc3xx,snd-usb-audio type: USB rev: 1.1 speed: 12 Mb/s lanes: 1
mode: 1.1 bus-ID: 3-4:3 chip-ID: 046d:08d7 class-ID: 0102
API: ALSA v: k5.10.187-1-MANJARO status: kernel-api with: aoss
type: oss-emulator tools: alsactl,alsamixer,amixer
Server-1: JACK v: 1.9.22 status: off with: a2jmidid status: off
tools: jack_control,qjackctl
Server-2: PipeWire v: 0.3.75 status: off with: pipewire-media-session
status: active tools: pw-cli
Server-3: PulseAudio v: 16.1 status: active with: 1: pulseaudio-alsa
type: plugin 2: pulseaudio-jack type: module tools: pacat,pactl
Network:
Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
vendor: Gigabyte driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s
lanes: 1 port: d000 bus-ID: 03:00.0 chip-ID: 10ec:8168 class-ID: 0200
IF: enp3s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Bluetooth:
Device-1: Broadcom BCM20702A0 Bluetooth 4.0 driver: btusb v: 0.8 type: USB
rev: 2.0 speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 3-10:7 chip-ID: 0a5c:21e8
class-ID: fe01 serial: <filter>
Report: rfkill ID: hci0 rfk-id: 0 state: up address: see --recommends
Drives:
Local Storage: total: 2.45 TiB used: 390.3 GiB (15.6%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Western Digital
model: WDS500G3X0C-00SJG0 size: 465.76 GiB block-size: physical: 512 B
logical: 512 B speed: 31.6 Gb/s lanes: 4 tech: SSD serial: <filter>
fw-rev: 111110WD temp: 43.9 C scheme: GPT
ID-2: /dev/sda maj-min: 8:0 vendor: A-Data model: SU800 size: 119.24 GiB
block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s tech: SSD
serial: <filter> fw-rev: 1C scheme: GPT
ID-3: /dev/sdb maj-min: 8:16 vendor: Western Digital
model: WD10EZRX-00D8PB0 size: 931.51 GiB block-size: physical: 4096 B
logical: 512 B speed: 6.0 Gb/s tech: HDD rpm: 5400 serial: <filter>
fw-rev: 0A80 scheme: GPT
ID-4: /dev/sdc maj-min: 8:32 vendor: Seagate model: ST1000DX001-1CM162
size: 931.51 GiB block-size: physical: 4096 B logical: 512 B speed: 3.0 Gb/s
tech: HDD rpm: 7200 serial: <filter> fw-rev: CC43 scheme: GPT
ID-5: /dev/sdd maj-min: 8:48 vendor: SanDisk model: Ultra USB 3.0
size: 28.64 GiB block-size: physical: 512 B logical: 512 B type: USB rev: 3.0
spd: 5 Gb/s lanes: 1 mode: 3.2 gen-1x1 tech: N/A serial: <filter>
fw-rev: 1.00 scheme: GPT
SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
ID-6: /dev/sde maj-min: 8:64 model: N/A size: 29.3 GiB block-size:
physical: 512 B logical: 512 B type: USB rev: 2.0 spd: 480 Mb/s lanes: 1
mode: 2.0 tech: N/A serial: <filter> fw-rev: 2.00 scheme: MBR
SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
Partition:
ID-1: / raw-size: 58.4 GiB size: 58.38 GiB (99.96%) used: 42.06 GiB (72.1%)
fs: xfs dev: /dev/nvme0n1p2 maj-min: 259:2
ID-2: /boot raw-size: 512 MiB size: 126 MiB (24.61%) used: 126 MiB (100.0%)
fs: vfat dev: /dev/nvme0n1p5 maj-min: 259:5
ID-3: /home raw-size: 360 GiB size: 360 GiB (100.00%)
used: 348.11 GiB (96.7%) fs: f2fs dev: /dev/nvme0n1p3 maj-min: 259:3
Swap:
Alert: No swap data was found.
Sensors:
System Temperatures: cpu: 32.0 C mobo: N/A
Fan Speeds (RPM): N/A
Info:
Processes: 308 Uptime: 2h 32m wakeups: 0 Memory: total: 16 GiB
available: 15.58 GiB used: 4.76 GiB (30.5%) Init: systemd v: 253
default: graphical tool: systemctl Compilers: gcc: 13.1.1 alt: 11/12
clang: 15.0.7 Packages: 1677 pm: pacman pkgs: 1666 libs: 443 tools: pamac
pm: flatpak pkgs: 0 pm: snap pkgs: 11 Shell: Bash v: 5.1.16
running-in: konsole inxi: 3.3.28
I should note that GParted gave an error when I resized the boot partition. However, it was already double the capacity that’s accessible, so the problem was probably already there.
I think your boot should be mounted at /boot/efi, not /boot, so there might be something really strange going on.
If your boot is mounted at /boot/efi almost no space is used and kernels reside on the root partition (since /boot is still on the root partition, not boot) instead and this problem would most likely never occur in the first place.
You are running a very old kernel, maybe efi was installed like that back then, I hope someone can help you with this, because to me something seems off.
No. It certainly wasn’t like that by default back then. It was a deliberate choice to mount it on /boot, though I don’t remember what was the reason.
Sorry, outside my comfort zone if you have gone and change boot procedures like that.
Maybe you can just boot into a live env and reformat it and reinstall grub, will probably MAYBE work, but since you have changed things in combination with boot, I can not advice more. Sorry!
can we have a output of;
$ lsblk -f
i’m getting vibes that the OP has confused the EFI partition with /boot directory. unless explicitly created /boot is part of “rootfs” and in most manjaro setups EFI partition is system mounted at /boot/efi/EFI/ or /boot/efi/
Well if he has the kernel there it will be a bit more complicated. I guess he will have to mount somewhere else, and reinstall the kernel and grub…before rebooting. The whole procedure to move the /boot
What I mean is he could boot into a live env, reformat the partition (If he wanted he could backup the kernels in /boot I guess), manually mounting root and boot (at /boot/efi this time) and whatnot. chroot into the system and reinstall kernels and efi grub. Should be doable.
mhwd-kernels should take care of it all… I think…
But at the same time, I have no idea if he has changed OTHER things to point to the boot partition at /boot and not /boot/efi, therefore I say MAYBE.
Yes exactly. But i have never done it and cannot help with the steps.
Too late. I already backed up and deleted the /boot partition to try to solve this. I didn’t think it would get more replies so quickly.
But the EFI directory was directly inside /boot, so it was /boot/EFI instead of /boot/efi/EFI.
Now I’m struggling to copy the files over to the new boot partition I created with the correct ownership.
Ok, so you have reformated, it, lets see if we can figure this out, are you in a live or still on your system?
What you need to do is copy everything EXCEPT the efi into your /boot, then mount the newly partitioned fat32 partition to /boot/efi (create the directory if it is not there).
Then install grub:
sudo grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=manjaro --recheck
sudo grub-mkconfig -o /boot/grub/grub.cfg
After that it might work, but as I stated earlier, I do not know what you did when you moved your boot.
If you are in a live env, you need to chroot into your system AFTER you mounted both root and boot and then do the grub stuff.
Edit
Since we are not reinstalling kernels here, you also have to make sure your fstab is correct with the new uuid and that its being mounted at /boot/efi and not at /boot
Edit 2
If you want to, you can also be sure that at least one kernel gets installed, I would recommend the latest lts kernel:
sudo mhwd-kernels -i linux61
Just to be clear - you are using systemd-boot?
I ended up just making a new /boot partition and copying the files over. I then reinstalled GRUB. It now boots fine and I have more capacity.
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.