Update dom0 error

I am trying to solve, update problem, when i update sudo qubes-dom0-update it gives me,

python3-xen.x86_64 2001:4.14.5-5.fc32 qubes-dom0-cached
xen.x86_64 2001:4.14.5-5.fc32 qubes-dom0-cached
xen-hypervisor.x86_64 2001:4.14.5-5.fc32 qubes-dom0-cached
xen-libs.x86_64 2001:4.14.5-5.fc32 qubes-dom0-cached
xen-licenses.x86_64 2001:4.14.5-5.fc32 qubes-dom0-cached
xen-runtime.x86_64 2001:4.14.5-5.fc32 qubes-dom0-cached
Dependencies resolved.

# Package Architecture Version Repository Size

pgrading:
python3-xen x86_64 2001:4.14.5-5.fc32 qubes-dom0-cached 60 k
xen x86_64 2001:4.14.5-5.fc32 qubes-dom0-cached 20 k
xen-hypervisor x86_64 2001:4.14.5-5.fc32 qubes-dom0-cached 7.7 M
xen-libs x86_64 2001:4.14.5-5.fc32 qubes-dom0-cached 624 k
xen-licenses x86_64 2001:4.14.5-5.fc32 qubes-dom0-cached 32 k
xen-runtime x86_64 2001:4.14.5-5.fc32 qubes-dom0-cached 19 M

# Transaction Summary

Upgrade 6 Packages

Total size: 27 M

Total size: 27 M
Is this ok [y/N]: y
Downloading Packages:
Running transaction check
Transaction check succeeded.
Running transaction test
Error: Transaction test error:
installing package xen-hypervisor-2001:4.14.5-5.fc32.x86_64 needs 236KB on the /boot/efi filesystem

## Error Summary

Disk Requirements:
At least 1MB more space needed on the /boot/efi filesystem.

I spent a whole day looking for the solution, I can’t find it

Edit from @ludovic : I fixed the very ugly syntax

[love@dom0 ~]$ df -h

Filesystem Size Used Avail Use% Mounted on
devtmpfs 1.9G 0 1.9G 0% /dev
tmpfs 2.0G 0 2.0G 0% /dev/shm
tmpfs 2.0G 3.0M 2.0G 1% /run
/dev/dm-1 20G 4.1G 15G 22% /
tmpfs 2.0G 8.0K 2.0G 1% /tmp
xenstore 2.0G 448K 2.0G 1% /var/lib/xenstored
/dev/nvme0n1p5 976M 107M 803M 12% /boot
/dev/nvme0n1p1 96M 94M 2.4M 98% /boot/efi
/dev/dm-2 90G 78G 13G 87% /var/lib/qubes
tmpfs 391M 32K 391M 1% /run/user/1000
[dex@dom0 ~]$ df -h
Filesystem Size Used Avail Use% Mounted on
devtmpfs 1.9G 0 1.9G 0% /dev
tmpfs 2.0G 0 2.0G 0% /dev/shm
tmpfs 2.0G 3.0M 2.0G 1% /run
/dev/dm-1 20G 4.1G 15G 22% /
tmpfs 2.0G 8.0K 2.0G 1% /tmp
xenstore 2.0G 448K 2.0G 1% /var/lib/xenstored
/dev/nvme0n1p5 976M 107M 803M 12% /boot
/dev/nvme0n1p1 96M 94M 2.4M 98% /boot/efi
/dev/dm-2 90G 78G 13G 87% /var/lib/qubes
tmpfs 391M 32K 391M 1% /run/user/1000

can someone help me i’m an ass in the field, i’m learning thank you

You need to free up the space in EFI partition /boot/efi/ before you can apply updates.
What’s the output of this command in dom0?

sudo bash -c "du -sh /boot/efi/*/*/*"

hi tzwcfq

723K /boot/efi/EFI/Boot/BOOTIA32.EFI
136K /boot/efi/EFI/Boot/bootx64.efi
67K /boot/efi/EFI/Boot/fbia32.efi
86K /boot/efi/EFI/Boot/fbx64.efi
837K /boot/efi/EFI/Boot/mmx64.efi
8.1M /boot/efi/EFI/HP/BIOS
2.6M /boot/efi/EFI/HP/BIOSUpdate
29M /boot/efi/EFI/Microsoft/Boot
61K /boot/efi/EFI/Microsoft/Recovery
1.0K /boot/efi/EFI/fedora/BOOTIA32.CSV
1.0K /boot/efi/EFI/fedora/BOOTX64.CSV
1.6M /boot/efi/EFI/fedora/gcdia32.efi
2.5M /boot/efi/EFI/fedora/gcdx64.efi
1.0K /boot/efi/EFI/fedora/grub.cfg
1.6M /boot/efi/EFI/fedora/grubia32.efi
2.5M /boot/efi/EFI/fedora/grubx64.efi
661K /boot/efi/EFI/fedora/mmia32.efi
831K /boot/efi/EFI/fedora/mmx64.efi
907K /boot/efi/EFI/fedora/shim.efi
723K /boot/efi/EFI/fedora/shimia32.efi
907K /boot/efi/EFI/fedora/shimx64.efi
1.0K /boot/efi/EFI/qubes/fonts
12K /boot/efi/EFI/qubes/grub.cfg
1.8M /boot/efi/EFI/qubes/grubx64.efi
29M /boot/efi/EFI/qubes/initramfs-5.10.90-1.fc32.qubes.x86_64.img
2.5M /boot/efi/EFI/qubes/xen-4.14.5.efi
2.5M /boot/efi/EFI/qubes/xen.efi
1.0K /boot/efi/EFI/ubuntu/BOOTX64.CSV
1.0K /boot/efi/EFI/ubuntu/grub.cfg
1.7M /boot/efi/EFI/ubuntu/grubx64.efi
837K /boot/efi/EFI/ubuntu/mmx64.efi
934K /boot/efi/EFI/ubuntu/shimx64.efi
2.0K /boot/efi/System/Library/CoreServices

I have these in return, and I see that there are remnants of an old system, note I only have windows in dualboot with qubes os,

If you don’t have fedora or ubuntu installed in dualboot then you can safely remove them to free up the space:
sudo rm -rf /boot/efi/EFI/fedora /boot/efi/EFI/ubuntu
And then try to update dom0 again.

1 Like

hi tzwcfq I don’t know how thank you thank you very much, the update problem solved thnx thnx thnx