# CU 201: No space left on device **URL:** \ **Category:** Update Trouble\ **Created:** [6 May 2026 14:44 UTC](https://community.ipfire.org/t/cu-201-no-space-left-on-device/15760 "2026-05-06T14:44:04Z")\ **Posts on this page:** 15\ **Page:** 1
**Author:** ![larsen](https://community.ipfire.org/user_avatar/community.ipfire.org/larsen/32/15419_2.png) [@larsen](https://community.ipfire.org/u/larsen)\ **Post date:** [6 May 2026 14:44 UTC](https://community.ipfire.org/t/cu-201-no-space-left-on-device/15760/1 "2026-05-06T14:44:04Z")
On updating from CU 200 to CU 201, I got an error message in /var/log/pakfire/update-core-upgrade-201.log: ```auto dracut[I]: Executing: /usr/bin/dracut --kver=6.18.7-ipfire --force dracut[I]: ***Including module: modsign*** dracut[I]: ***Including module: i18n*** dracut[I]: ***Including module: btrfs*** dracut[I]: ***Including module: dm*** dracut[I]: ***Including module: fs-lib*** dracut[I]: ***Including module: kernel-modules*** dracut[I]: ***Including module: kernel-modules-extra*** dracut[I]: ***Including module: lvm*** dracut[I]: ***Including module: mdraid*** dracut[I]: ***Including module: qemu*** dracut[I]: ***Including module: rootfs-block*** dracut[I]: ***Including module: terminfo*** dracut[I]: ***Including module: udev-rules*** dracut[I]: ***Including module: initqueue*** dracut[I]: ***Including module: base*** dracut[I]: ***Including modules done*** dracut[I]: ***Installing kernel module dependencies*** dracut[I]: ***Installing kernel module dependencies done*** dracut[I]: ***Resolving executable dependencies*** dracut[I]: ***Resolving executable dependencies done*** dracut[I]: ***Generating early-microcode cpio image*** dracut[I]: ***Constructing AuthenticAMD.bin*** dracut[I]: ***Constructing GenuineIntel.bin*** dracut[I]: ***Store current command line parameters*** dracut[I]: ***Creating image file '/boot/initramfs-6.18.7-ipfire.img.tmp'*** dracut[I]: ***Hardlinking files*** dracut[I]: ***Hardlinking files done*** cp: error writing '/boot/initramfs-6.18.7-ipfire.img.tmp': No space left on device dracut[F]: Creation of /boot/initramfs-6.18.7-ipfire.img.tmp failed Generating grub configuration file ... Found background: /boot/grub/splash.png Found linux image: /boot/vmlinuz-6.18.7-ipfire Found initrd image: /boot/initramfs-6.18.7-ipfire.img Adding boot menu entry for UEFI Firmware Settings ... Root filesystem isn't btrfs, skipping... done ``` Afterwards, /boot has 26 Mb free as before the update. So, only the creation of that tmp file is having a problem (btw: wouldn’t it be possible to create that file on / and move it to /boot afterwards?). ```auto # df -h Filesystem Size Used Avail Use% Mounted on devtmpfs 890M 4.0K 890M 1% /dev tmpfs 919M 0 919M 0% /dev/shm tmpfs 919M 772K 918M 1% /run /dev/sda4 29G 2.7G 25G 10% / /dev/sda1 110M 76M 26M 75% /boot /dev/sda2 32M 278K 32M 1% /boot/efi /var/lock 8.0M 12K 8.0M 1% /var/lock none 919M 62M 858M 7% /var/log/rrd none 919M 300K 919M 1% /var/log/vnstat ``` ```auto # ll /boot total 67M -rw-r--r-- 1 root root 200K Feb 24 15:03 config-6.18.7-ipfire drwxr-xr-x 3 root root 16K Jan 1 1970 efi drwxr-xr-x 6 root root 4.0K May 6 16:29 grub -rw------- 1 root root 51M Mar 11 17:19 initramfs-6.18.7-ipfire.img drwx------ 2 root root 16K Dec 6 2021 lost+found -rw-r--r-- 1 root root 7.0M Feb 24 15:03 System.map-6.18.7-ipfire -rw-r--r-- 1 root root 8.9M Feb 24 15:03 vmlinuz-6.18.7-ipfire ``` The GUI shows “IPFire 2.29 (x86\_64) - Core-Update 201” and “An update requires a restart” which obviously I am hesitant to do =) What should I do? Reinstall fresh to have the installer create a bigger boot partition and restore the backup from before the update? ---
**Author:** ![dark0ipfire](https://community.ipfire.org/user_avatar/community.ipfire.org/dark0ipfire/32/16591_2.png) [@dark0ipfire](https://community.ipfire.org/u/dark0ipfire)\ **Post date:** [6 May 2026 15:20 UTC](https://community.ipfire.org/t/cu-201-no-space-left-on-device/15760/2 "2026-05-06T15:20:57Z")
Exactly the same happened just here, with an Oracle VirtualBox system: ![image](https://community.ipfire.org/uploads/default/original/2X/6/6f5d2faebaa6603a9e60db5574b364082bf86f5f.png) System reboot leads to a running core 201 with no more updates avail. ```auto [root@ipfire ~]# df -h Filesystem Size Used Avail Use% Mounted on devtmpfs 456M 4.0K 456M 1% /dev tmpfs 485M 0 485M 0% /dev/shm tmpfs 485M 452K 484M 1% /run /dev/sda4 7.4G 2.4G 4.6G 35% / /dev/sda1 110M 76M 26M 75% /boot /dev/sda2 32M 278K 32M 1% /boot/efi /var/lock 8.0M 12K 8.0M 1% /var/lock [root@ipfire ~]# ll /boot/ total 68556 -rw-r--r-- 1 root root 204588 Jan 29 22:38 config-6.18.7-ipfire drwxr-xr-x 3 root root 16384 Jan 1 1970 efi drwxr-xr-x 6 root root 4096 May 6 17:09 grub -rw------- 1 root root 53341640 Jan 30 23:59 initramfs-6.18.7-ipfire.img drwx------ 2 root root 16384 Jan 18 2022 lost+found -rw-r--r-- 1 root root 7261974 Jan 29 22:38 System.map-6.18.7-ipfire -rw-r--r-- 1 root root 9352192 Jan 29 22:38 vmlinuz-6.18.7-ipfire [root@ipfire ~]# ``` ---
**Author:** ![bbitsch](https://community.ipfire.org/user_avatar/community.ipfire.org/bbitsch/32/7420_2.png) [@bbitsch](https://community.ipfire.org/u/bbitsch)\ **Post date:** [6 May 2026 15:32 UTC](https://community.ipfire.org/t/cu-201-no-space-left-on-device/15760/3 "2026-05-06T15:32:51Z")
The date of the initramfs file is the date of CU200. In my system. ---
**Author:** ![bonnietwin](https://community.ipfire.org/user_avatar/community.ipfire.org/bonnietwin/32/12350_2.png) [@bonnietwin](https://community.ipfire.org/u/bonnietwin)\ **Post date:** [6 May 2026 15:43 UTC](https://community.ipfire.org/t/cu-201-no-space-left-on-device/15760/4 "2026-05-06T15:43:01Z")
> [@larsen](#): > > /boot has 26 Mb free as before the update. Your boot partition is 110MiB. The size for new installations was increased to 256MiB in 2022 with CU170. Then in 2023 with CU175 it was increased to 512MiB as that is the minimum required for an XFS filesystem. > [@larsen](#): > > What should I do? > Reinstall fresh to have the installer create a bigger boot partition and restore the backup from before the update? Yes my recommendation would be to do a fresh install and thereby ensure that you have a large enough boot partition not only for now but also for the future as the kernel size just keeps on increasing. ---
**Author:** ![bbitsch](https://community.ipfire.org/user_avatar/community.ipfire.org/bbitsch/32/7420_2.png) [@bbitsch](https://community.ipfire.org/u/bbitsch)\ **Post date:** [6 May 2026 15:54 UTC](https://community.ipfire.org/t/cu-201-no-space-left-on-device/15760/5 "2026-05-06T15:54:45Z")
Looking at the current state of dracut skript shows, that even with option --force initramfs isn’t just overwritten but the operation is create tmp file → cp to destination file. This means that the space for initramfs is needed twice. In CU200 this wasn’t the case. Therefore until now the process succeeded without problems. ---
**Author:** ![dark0ipfire](https://community.ipfire.org/user_avatar/community.ipfire.org/dark0ipfire/32/16591_2.png) [@dark0ipfire](https://community.ipfire.org/u/dark0ipfire)\ **Post date:** [7 May 2026 09:27 UTC](https://community.ipfire.org/t/cu-201-no-space-left-on-device/15760/6 "2026-05-07T09:27:02Z")
Indeed, the partition /boot in fresh installation looks much better: ```auto [root@ipfire ~]# df -h Filesystem Size Used Avail Use% Mounted on devtmpfs 445M 4.0K 445M 1% /dev tmpfs 485M 0 485M 0% /dev/shm tmpfs 485M 484K 484M 1% /run /dev/sda4 7.1G 2.1G 4.7G 31% / /dev/sda1 488M 98M 354M 22% /boot /dev/sda2 32M 294K 32M 1% /boot/efi /var/lock 8.0M 12K 8.0M 1% /var/lock [root@ipfire ~]# [root@ipfire ~]# ll /boot/ total 90688 -rw-r--r-- 1 root root 204588 Apr 21 15:04 config-6.18.7-ipfire drwxr-xr-x 3 root root 16384 Jan 1 1970 efi drwxr-xr-x 6 root root 4096 May 7 10:27 grub -rw------- 1 root root 76082445 Apr 21 15:06 initramfs-6.18.7-ipfire.img drwx------ 2 root root 16384 May 7 10:27 lost+found -rw-r--r-- 1 root root 7261974 Apr 21 15:04 System.map-6.18.7-ipfire -rw-r--r-- 1 root root 9274368 Apr 21 15:04 vmlinuz-6.18.7-ipfire ``` Maybe a general warning should be issued on systems with 110M /boot partition size to better do a fresh installation and no more updates. ---
**Author:** ![ramfast](https://community.ipfire.org/user_avatar/community.ipfire.org/ramfast/32/15583_2.png) [@ramfast](https://community.ipfire.org/u/ramfast)\ **Post date:** [9 May 2026 18:49 UTC](https://community.ipfire.org/t/cu-201-no-space-left-on-device/15760/7 "2026-05-09T18:49:57Z")
![IPFire_200](https://community.ipfire.org/uploads/default/original/2X/0/080cd52e1bce20da5cb3c3bb024ba6ed79479378.png) So according to your remark, I should stay with release 200 instead of migrating to 201 ? BR ---
**Author:** ![bonnietwin](https://community.ipfire.org/user_avatar/community.ipfire.org/bonnietwin/32/12350_2.png) [@bonnietwin](https://community.ipfire.org/u/bonnietwin)\ **Post date:** [11 May 2026 09:19 UTC](https://community.ipfire.org/t/cu-201-no-space-left-on-device/15760/8 "2026-05-11T09:19:36Z")
My recommendation would be to take a backup. Download it from the IPFire system. Do a fresh install from a CU201 iso and then do a restore from the backup. That way you will get a new boot partition that will be 512MiB and you will not run out of space with any updates. You can also create an ISO backup and buse that for the install and restore in one go. I have not tested that myself for several years. I always use normal install iso and a separate backup as I have processes on my IPFire system to automatically create backups on a weekly basis and then back them up to a central backup server using bacula. ---
**Author:** ![larsen](https://community.ipfire.org/user_avatar/community.ipfire.org/larsen/32/15419_2.png) [@larsen](https://community.ipfire.org/u/larsen)\ **Post date:** [11 May 2026 10:21 UTC](https://community.ipfire.org/t/cu-201-no-space-left-on-device/15760/9 "2026-05-11T10:21:24Z")
> [@bonnietwin](#): > > You can also create an ISO backup and buse that for the install and restore in one go. I have used this method when the /boot partition needed to be resized the first time some years ago. This went quite well, however, I needed to reinstall all addons manually, so make a list before you do this. There is a feature request that hasn’t been implemented, yet. > **[12588 – Backup: Rework and altering of functionalities and GUI for better...](https://bugzilla.ipfire.org/show_bug.cgi?id=12588)** ---
**Author:** ![ramfast](https://community.ipfire.org/user_avatar/community.ipfire.org/ramfast/32/15583_2.png) [@ramfast](https://community.ipfire.org/u/ramfast)\ **Post date:** [11 May 2026 11:06 UTC](https://community.ipfire.org/t/cu-201-no-space-left-on-device/15760/10 "2026-05-11T11:06:39Z")
> [@larsen](#): > > There is a feature request that hasn’t been implemented, yet. Hi, Yes I agree with you, should be very helpfull ---
**Author:** ![ramfast](https://community.ipfire.org/user_avatar/community.ipfire.org/ramfast/32/15583_2.png) [@ramfast](https://community.ipfire.org/u/ramfast)\ **Post date:** [15 May 2026 18:37 UTC](https://community.ipfire.org/t/cu-201-no-space-left-on-device/15760/11 "2026-05-15T18:37:24Z")
Thank’s Lars & Adolf Done today. I made a backup of IPF release 200 I have restored it. Hopefully I have made of list for the addons. The size of the boot partition was increased, so seems good for CU 201 In few days I will upgrade to CU 201 Thx ---
**Author:** ![dark0ipfire](https://community.ipfire.org/user_avatar/community.ipfire.org/dark0ipfire/32/16591_2.png) [@dark0ipfire](https://community.ipfire.org/u/dark0ipfire)\ **Post date:** [8 July 2026 20:40 UTC](https://community.ipfire.org/t/cu-201-no-space-left-on-device/15760/12 "2026-07-08T20:40:14Z")
I wonder why this issue shows only up in CU201 and not in CU202 and following ones. Has the dracut script changed back again? ---
**Author:** ![dark0ipfire](https://community.ipfire.org/user_avatar/community.ipfire.org/dark0ipfire/32/16591_2.png) [@dark0ipfire](https://community.ipfire.org/u/dark0ipfire)\ **Post date:** [9 July 2026 08:27 UTC](https://community.ipfire.org/t/cu-201-no-space-left-on-device/15760/13 "2026-07-09T08:27:54Z")
While testing CU203 I get these messages with a 110M sized /boot: ```auto dracut[I]: ***Creating image file '/boot/initramfs-6.18.32-ipfire.img.tmp'*** dracut[I]: ***Hardlinking files*** dracut[I]: ***Hardlinking files done*** cp: error writing '/boot/initramfs-6.18.32-ipfire.img.tmp': No space left on device dracut[F]: Creation of /boot/initramfs-6.18.32-ipfire.img.tmp failed Found bootloader device: /dev/sda Updating configuration... Installing GRUB on /dev/sda... ``` ---
**Author:** ![bonnietwin](https://community.ipfire.org/user_avatar/community.ipfire.org/bonnietwin/32/12350_2.png) [@bonnietwin](https://community.ipfire.org/u/bonnietwin)\ **Post date:** [9 July 2026 12:13 UTC](https://community.ipfire.org/t/cu-201-no-space-left-on-device/15760/14 "2026-07-09T12:13:54Z")
[https://community.ipfire.org/t/cu-201-no-space-left-on-device/15760/4](https://community.ipfire.org/t/cu-201-no-space-left-on-device/15760/4) ---
**Author:** ![odongarma](https://community.ipfire.org/user_avatar/community.ipfire.org/odongarma/32/9635_2.png) [@odongarma](https://community.ipfire.org/u/odongarma)\ **Post date:** [9 July 2026 12:32 UTC](https://community.ipfire.org/t/cu-201-no-space-left-on-device/15760/15 "2026-07-09T12:32:55Z")
I ran into the same problem, coming from an early Version with a very small boot partiton… First a full backup with clonezilla. Then with a gparted live USB Stick i resized the boot partiton to 1 GB works perfect and should be good enough for the future Greetz