F21: BTRFS + LUKS won't boot on 3.19.x-x kernel

asked 2015-04-08 16:14:11 -0500

Jmlevick gravatar image

updated 2015-04-09 00:19:10 -0500

So I've been reading a little about BTRFS problems with 3.19 kernels here:


and I have a problem that I think may or may not be related:

The thing is, I can't boot my Fedora 21 x86_64 machine with 3.19.3-200 (BTRFS /) it doesn't even ask for the /home LUKS passphrase (/home is a ext4 partition). 3.17.x works fine... Performing a:

btrfs check --repair <partition>

while on initramfs (as recommended on the reddit thread) accomplishes nothing. Pressing "Esc" while booting to hide the plymouth loading screen and see "the log" returns a wierd red and purple mashup of letters:


When the system does boot with this kernel (at the 5th try or so), / filesystem is corrupt, returning cpio errors when unpacking RPM's and never installing them. Using older kernel results in being able to boot and install such packages with no problems, besides using the system normally.

What's happening here?

P.S. On the BTRFS wiki they recommend to apply btrfs-zero-log and on reddit some user mention btrfs scrub, but I'm on a SSD and I dunno how harmful those operations might be (repair itself seems harmful) so... ideas?

EDIT: Removing rhgb quiet from GRUB_CMDLINE_LINUX in /etc/default/grub and regenerating grub's configuration with:

grub2-mkconfig -o /boot/grub2/grub.cfg

"Solves" the issue by letting me hit escape at boot and enter the LUKS passphrase for /home... Then the system boots as normal and everything works as expected. placing again rhgb quiet and regenerating grub's conf leaves me with the same issue commented above. I do not have any propietary graphic drivers installed by the way.

EDIT 2: The system returned to an unbootable state just like that... The "solution"? regenerate grub's conf again (leaved rhgb quiet out of GRUB_CMDLINE_LINUX).

edit retag flag offensive close merge delete


johanh gravatar imagejohanh ( 2015-04-09 07:55:40 -0500 )edit

Fairly similar as I also have a UEFI machine but none of them have listed my workaround so I'm threating it as a different issue until I can confirm otherwise.... The thing is, my main problem is not being able to provide my LUKS password when the system misbehaves. I dunno if with non-encrypted home this would turn out differently.

Jmlevick gravatar imageJmlevick ( 2015-04-09 19:45:58 -0500 )edit