I’m stuck with this issue I’m struggling to find a solution for googling about it so I’d like to ask for some help, please.
So apparently the rpm-ostree upgrade fails due to “No space left on device” despite my system still having 62G of free disk space. The problem is temporary fixed when I delete some big files but keeps on coming back eventually - confirmed to immediately cause it when I try another ujust upgrade. /dev/sda3 465G 401G 62G 87% /sysroot
What’s interesting is that this “No space left on device” issue is also affecting my flatpaks, particularly Chrome and Steam:
Steam Logs
i386-linux-gnu-capsule-capture-libs: warning: cannot create symlink /proc/self/fd/18/lib/i386-linux-gnu/libGL.so.1: No space left on device
i386-linux-gnu-capsule-capture-libs: warning: cannot create symlink /proc/self/fd/18/lib/i386-linux-gnu/libunistring.so.5: No space left on device
i386-linux-gnu-capsule-capture-libs: warning: cannot create symlink /proc/self/fd/18/lib/i386-linux-gnu/libnss_compat.so.2: No space left on device
i386-linux-gnu-capsule-capture-libs: warning: cannot create symlink /proc/self/fd/18/lib/i386-linux-gnu/libnss_compat.so.2: No space left on device
i386-linux-gnu-capsule-capture-libs: warning: cannot create symlink /proc/self/fd/18/lib/i386-linux-gnu/libnss_compat.so.2: No space left on device
i386-linux-gnu-capsule-capture-libs: warning: cannot create symlink /proc/self/fd/18/lib/i386-linux-gnu/libnss_dns.so.2: No space left on device
i386-linux-gnu-capsule-capture-libs: warning: cannot create symlink /proc/self/fd/18/lib/i386-linux-gnu/libnss_dns.so.2: No space left on device
i386-linux-gnu-capsule-capture-libs: warning: cannot create symlink /proc/self/fd/18/lib/i386-linux-gnu/libnss_dns.so.2: No space left on device
i386-linux-gnu-capsule-capture-libs: warning: cannot create symlink /proc/self/fd/18/lib/i386-linux-gnu/libnss_files.so.2: No space left on device
i386-linux-gnu-capsule-capture-libs: warning: cannot create symlink /proc/self/fd/18/lib/i386-linux-gnu/libnss_files.so.2: No space left on device
i386-linux-gnu-capsule-capture-libs: warning: cannot create symlink /proc/self/fd/18/lib/i386-linux-gnu/libnss_files.so.2: No space left on device
pressure-vessel-wrap[23008]: E: Unable to create symlink "/var/home/ll/.local/share/Steam/ubuntu12_64/steam-runtime-sniper/var/tmp-DT4Z52//lib/ld-linux.so.2" -> "/run/host/usr/lib/ld-linux.so.2": No space left on device
Forgot to copy the flatpak Chrome logs but it was definitely complaining about having no space when I tried to run it from the terminal cause it refused to run using the GUI.
A reboot appears to temporarily fix the issue but it comes back shortly after. For now I’ve prevented rpm-ostree from automatically upgrading by adding a 0.0.0.0 hosts file entry for ghcr.io
Below are logs that I encounter when I use the ujust upgrade command:
── 20:55:33 - System update ────────────────────────────────────────────────────
Pulling manifest: ostree-image-signed:docker://ghcr.io/ublue-os/bazzite:stable
error: Preparing import: Fetching manifest: Writing cached pending manifest: Unable to write detached metadata: renameat(7e/tmp.5BVcNL, 7e/cd0af554328210e06aea8f051d4e2c38adb500d25de612125014d28795615e.commitmeta): No space left on device
System update failed:
0: Command failed: `/usr/bin/rpm-ostree upgrade`
1: `/usr/bin/rpm-ostree` failed: exit status: 1
Location:
src/steps/os/linux.rs:228
Retry? (y)es/(N)o/(s)hell/(q)uit
── 23:13:34 - System update ────────────────────────────────────────────────────
Pulling manifest: ostree-image-signed:docker://ghcr.io/ublue-os/bazzite:stable
Staging deployment... done
error: Staging deployment: Initializing deployment: Checking out deployment tree: Hardlinking bc/c06975f9552319ccf765680a88ca3f53afe40706108bf898b9c5f077a04654.file to QPdfOutputIntent: No space left on device
System update failed:
0: Command failed: `/usr/bin/rpm-ostree upgrade`
1: `/usr/bin/rpm-ostree` failed: exit status: 1
Location:
src/steps/os/linux.rs:228
Retry? (y)es/(N)o/(s)hell/(q)uit
Oh wait, yeah I do have pinned images.
Do I move the pin to the new one? iirc I pinned that because I originally did not have an intention to upgrade, and eventually I forgot about the pin.
/boot for you would likely be /dev/sda2. /dev/sda3 is your root partition.
Yepp. Likely the issue is that you have that pinned image. It is over 6 months old and likely doesn’t share anything with your other images at this point.
But you too have less than 30% available on /boot and likely the newest image just doesn’t fit.
Man, many thanks! I’ve unpinned the image which will hopefully fix the issue. Can’t reboot right now but I’ll see a few hours from now.
iirc I must’ve manually partitioned which caused me to have this size of /boot
What’s the recommended size for the /boot partition to serve as my reference in the future?