#4930 BFO: booting Fedora 22 and 23 beta fails at dracut-initqueue with "no space left on device" error
Closed: Fixed None Opened 8 years ago by rathann.

= bug description =
I run the following commands from BFO FAQ:
wget -O/boot/bfo.lkrn http://dl.fedoraproject.org/pub/alt/bfo/bfo.lkrn
grubby --add-kernel=/boot/bfo.lkrn --title="Boot BFO"
reboot
on an F22 VM.
After rebooting from bfo.lkrn, I selected "Install currently supported Fedora releases" -> Fedora-22-x86_64.
Kernel and initrd get loaded and executed, but after reaching target basic system, boot fails with:
dracut-initqueue[554]: cp: error writing '/updated/...various files': No space left on device
dracut-initqueue[554]: cp: failed to extend '/updated/...various files': No space left on device
[...]
dracut-initqueue[554]: cp: cannot copy directory, '.', onto itself, '/updates/.'
dracut-initqueue[554]: mount: wrong fs type, bad option, bad superblock on /dev/loop0,
[...]
dracut-initqueue[554]: umount: /run/initramfs/squashfs: not mounted
dracut-initqueue[554]: /sbin/dmsquash-live-root: line 271: printf: write error: No space left on device
dracut-initqueue[554]: Warning: could not boot.
dracut-initqueue[554]: Warning: /dev/root does not exist
Starting Dracut Emergency Shell...

Unfortunately, I'm not able to get the initial error - console buffer doesn't let me scroll back that far and journalctl begins with one of the "error writing..." messages already.


Sorry about the typos (I had to re-type what I see on a VNC console) and messed-up formatting.

How much memory does your vm have?

If you give it more does it start working?

It has 512MB and I cannot give it any more (paid hosting). I kind of figured it might be the issue. Is it possible to activate swap on existing device upon boot?

Not that I can see off hand. ;(

I looked at dracut and anaconda boot options and didn't see anything, but perhaps I missed it.

Yes after setting ram to >1GB has fixed the issue thank you.

Login to comment on this ticket.

Metadata