Continuing the discussion from Fwupd fails to update Dell firmware:
Update does not work with this message related to space on /run
/run/media/root/ESP does not have sufficient space, required 87.6 MB, got 60.4 MB.
Continuing the discussion from Fwupd fails to update Dell firmware:
Update does not work with this message related to space on /run
/run/media/root/ESP does not have sufficient space, required 87.6 MB, got 60.4 MB.
Unfortunately, all I can say is “me too!” I’m having a similar issue with my ThinkPad. There’s a “system update” and an EC update and neither one can install because there’s “not enough space”, even though lsblk
indicates there should be more than enough room.
I am not sure why you are seeing that. /run/media is the usual location where udev creates a subdir for the user and mounts a removable disk. It is not normally a place where any updates would need space for writing.
If you are doing a bios update from usb then maybe that is appropriate, but normally not. Possibly the update is compressed and needs to be extracted before installation which could require the additional space.
Please show us the output of mount
, lsblk -f
and df -h
so we can see what is actually happening with drive space. Please use preformatted text to show that data (paste the text, highlight it, then click the </>
button)
NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS
zram0 [SWAP]
nvme0n1
├─nvme0n1p1 vfat FAT32 ESP F200-DFD9
├─nvme0n1p2
├─nvme0n1p3 ntfs 846EAD3E6EAD2A3E
├─nvme0n1p4 ext4 1.0 41a23861-4881-4d26-a0cf-4e0dd1bb7e61 444.7M 47% /boot
├─nvme0n1p5 btrfs fedora_localhost-live ece8fdd6-d645-4eee-ac93-61cda1253ef4 22.2G 93% /home
│ /
├─nvme0n1p6 ntfs 5270B81D70B809AD
├─nvme0n1p7 ntfs Image 6416BD8A16BD5E2C
└─nvme0n1p8 ntfs DELLSUPPORT F2662C88662C5021
Filesystem Size Used Avail Use% Mounted on
/dev/nvme0n1p5 343G 320G 23G 94% /
devtmpfs 4.0M 0 4.0M 0% /dev
tmpfs 7.7G 68M 7.6G 1% /dev/shm
efivarfs 374K 222K 148K 61% /sys/firmware/efi/efivars
tmpfs 3.1G 2.6M 3.1G 1% /run
/dev/nvme0n1p5 343G 320G 23G 94% /home
tmpfs 7.7G 759M 7.0G 10% /tmp
/dev/nvme0n1p4 974M 462M 445M 51% /boot
tmpfs 1.6G 264K 1.6G 1% /run/user/1001
revokefs-fuse 343G 320G 23G 94% /var/tmp/flatpak-cache-8IEMV2/org.freedesktop.Platform-F919U2
and mount :
/dev/nvme0n1p5 on / type btrfs (rw,relatime,compress=zstd:1,ssd,discard=async,space_cache=v2,subvolid=257,subvol=/root)
devtmpfs on /dev type devtmpfs (rw,nosuid,size=4096k,nr_inodes=2003464,mode=755,inode64)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev,inode64)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime)
cgroup2 on /sys/fs/cgroup type cgroup2 (rw,nosuid,nodev,noexec,relatime,nsdelegate,memory_recursiveprot)
pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)
efivarfs on /sys/firmware/efi/efivars type efivarfs (rw,nosuid,nodev,noexec,relatime)
bpf on /sys/fs/bpf type bpf (rw,nosuid,nodev,noexec,relatime,mode=700)
configfs on /sys/kernel/config type configfs (rw,nosuid,nodev,noexec,relatime)
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
tmpfs on /run type tmpfs (rw,nosuid,nodev,size=3214788k,nr_inodes=819200,mode=755,inode64)
systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=37,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=9535)
tracefs on /sys/kernel/tracing type tracefs (rw,nosuid,nodev,noexec,relatime)
fusectl on /sys/fs/fuse/connections type fusectl (rw,nosuid,nodev,noexec,relatime)
/dev/nvme0n1p5 on /home type btrfs (rw,relatime,compress=zstd:1,ssd,discard=async,space_cache=v2,subvolid=256,subvol=/home)
tmpfs on /tmp type tmpfs (rw,nosuid,nodev,size=8036972k,nr_inodes=1048576,inode64)
/dev/nvme0n1p4 on /boot type ext4 (rw,relatime)
binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,nosuid,nodev,noexec,relatime)
sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw,relatime)
tmpfs on /run/user/1001 type tmpfs (rw,nosuid,nodev,relatime,size=1607392k,nr_inodes=401848,mode=700,uid=1001,gid=1001,inode64)
gvfsd-fuse on /run/user/1001/gvfs type fuse.gvfsd-fuse (rw,nosuid,nodev,relatime,user_id=1001,group_id=1001)
overlay on /var/lib/docker/overlay2/47c8306f7c59a6f59b60073cb4ffd74d279adef21f99d71cfb3ba6041fcc03d8/merged type overlay (rw,relatime,lowerdir=/var/lib/docker/overlay2/l/IHIWWJKFRAQRRZ4KW3GNKRZWZF:/var/lib/docker/overlay2/l/7ZL6TNMBC5MNFWKUW4CQEEU2BR:/var/lib/docker/overlay2/l/SJAF5N2YOALNVFYDJUKQ2IAGXL:/var/lib/docker/overlay2/l/BIQM4CNOQP5UGQTQVQ4EHVC3PK:/var/lib/docker/overlay2/l/AVHWNEE5FIEBK3IBGCN2CY6TRI:/var/lib/docker/overlay2/l/U2Q6NOOMCSO7NWO4US7NQK7SFZ:/var/lib/docker/overlay2/l/PTB7BXELXT6GHG7KZMLK4AWYU7:/var/lib/docker/overlay2/l/PGIS7HERRO4PGC4ZCDKPBXP53E:/var/lib/docker/overlay2/l/ZFZYVXBX2SQLNYAW4OENVEOLMP:/var/lib/docker/overlay2/l/4ZCFTUKCOODOBOLG74KSRVLI2I:/var/lib/docker/overlay2/l/NZB6NEP3X2LRXRO6X2GQLNK2O7:/var/lib/docker/overlay2/l/SNHUDUDWCLIDWCHW7QNAPMAKOB:/var/lib/docker/overlay2/l/QWAPMOSFYPDTVWSQUYBQGYUZ4N,upperdir=/var/lib/docker/overlay2/47c8306f7c59a6f59b60073cb4ffd74d279adef21f99d71cfb3ba6041fcc03d8/diff,workdir=/var/lib/docker/overlay2/47c8306f7c59a6f59b60073cb4ffd74d279adef21f99d71cfb3ba6041fcc03d8/work)
nsfs on /run/docker/netns/dc9f01e171bd type nsfs (rw)
portal on /run/user/1001/doc type fuse.portal (rw,nosuid,nodev,relatime,user_id=1001,group_id=1001)
revokefs-fuse on /var/tmp/flatpak-cache-8IEMV2/com.bitwarden.desktop-7EB6U2 type fuse.revokefs-fuse (rw,nosuid,nodev,relatime,user_id=1001,group_id=1001)
It might me that the ESP is mounted on /run/media/root/ESP, perhaps temporarily. There is no evidence that the ESP is mounted elsewhere, and not even on /boot/efi, where it is expected to be mounted.
If that is the case,the ESP may be too small or filled with files that shouldn’t be there.
I took the liberty of editing both posts to add the preformatted text tags so the display is now as seen on-screen.
Please use those tags when posting by highlighting the pasted text then click the </>
button on the toolbar so it maintains the same formatting.
I see 1 major problem on your system and it shows with the ‘df -h’ output.
Your main btrfs file system which contains both / and /home is 94% full which quickly causes errors on btrfs as well as most other file system types.
An additional issue, which may or may not be a factor, is that it seems there is no efi partition mounted or used by fedora. Fedora appears to have been installed in UEFI boot mode and the efi partition would normally be mounted at /boot/efi, but is not presently mounted in what you show.
I note that the ‘df -h’ output shows the directory /sys/firmware/efi/efivars exists which indicates UEFI boot, so something must have caused the /boot/efi directory to be dismounted (intentionally or otherwise) and could easily cause your problems.
Please now show the content of cat /etc/fstab
so we may analyze why the efi partition is not mounted at /boot/efi.