# Revision history [back]

### Kernel 3.11 & BTRFS: system doesn't boot

Today I ran a regular "sudo yum -y update" and Fedora just "blew up in my face" with the following screen after a reboot:

if I issue the "journalctl" command I can see a BTRFS error:

(My system's root partition is in BTRFS).

And as far as I've googled no one had this issue before and to be honest, I don't know how to solve it...

The "sosreport.txt" file just doesn't copy anywhere, I plug a USB in and then run:

cp /run/initramfs/sosreport.txt /dev/sdc1


and the command apparently runs successfully but when I check the USB it is empty, same if I save it to "/var" "/var/log" or "/usr", the file just doesn't appear anywhere. I ran "cat" on such file and it is enormous to photograph it, but I took another pic that might be helpful:

It's worth to mention that I don't have any propietary drivers running on this system and if I boot with the last kernel before the update (which is 3.10.11-200.fc19.x86_64) everything works normally. The problematic kernel version is the 3.11.1-200.fc19.x86_64 one.

Here you have my partition table:

And my lspci output is here: https://gist.github.com/Jmlevick/843bbe330d0e758415ab

Does anyone know how to solve this?

Thanks.

P.S. With kernel 3.12.0-0.rc1.git3.1.fc21.x86_64 (a debug kernel from rawhide) the problem is not present.

### Kernel 3.11 & BTRFS: system doesn't boot

Today I ran a regular "sudo yum -y update" and Fedora just "blew up in my face" with the following screen after a reboot:

if I issue the "journalctl" command I can see a BTRFS error:

(My system's root partition is in BTRFS).

And as far as I've googled no one had this issue before and to be honest, I don't know how to solve it...

The "sosreport.txt" file just doesn't copy anywhere, I plug a USB in and then run:

cp /run/initramfs/sosreport.txt /dev/sdc1


and the command apparently runs successfully but when I check the USB it is empty, same if I save it to "/var" "/var/log" or "/usr", the file just doesn't appear anywhere. I ran "cat" on such file and it is enormous to photograph it, but I took another pic that might be helpful:

It's worth to mention that I don't have any propietary drivers running on this system and if I boot with the last kernel before the update (which is 3.10.11-200.fc19.x86_64) everything works normally. The problematic kernel version is the 3.11.1-200.fc19.x86_64 one.

Here you have my partition table:

And my lspci output is here: https://gist.github.com/Jmlevick/843bbe330d0e758415ab

Does anyone know how to solve this?

Thanks.

P.S. With kernel 3.12.0-0.rc1.git3.1.fc21.x86_64 (a debug kernel from rawhide) the problem is not present.

### Kernel 3.11 & BTRFS: system doesn't boot

Today I ran a regular "sudo yum -y update" and Fedora just "blew up in my face" with the following screen after a reboot:

if I issue the "journalctl" command I can see a BTRFS error:

(My system's root partition is in BTRFS).

And as far as I've googled no one had this issue before and to be honest, I don't know how to solve it...

The "sosreport.txt" file just doesn't copy anywhere, I plug a USB in and then run:

cp /run/initramfs/sosreport.txt /dev/sdc1


and the command apparently runs successfully but when I check the USB it is empty, same if I save it to "/var" "/var/log" or "/usr", the file just doesn't appear anywhere. I ran "cat" on such file and it is enormous to photograph it, but I took another pic that might be helpful:

It's worth to mention that I don't have any propietary drivers running on this system and if I boot with the last kernel before the update (which is 3.10.11-200.fc19.x86_64) everything works normally. The problematic kernel version is the 3.11.1-200.fc19.x86_64 one.

Here you have my partition table:

And my lspci output is here: https://gist.github.com/Jmlevick/843bbe330d0e758415ab

Does anyone know how to solve this?

Thanks.

P.S. With kernel 3.12.0-0.rc1.git3.1.fc21.x86_64 (a debug kernel from rawhide) the problem is not present.

### Kernel 3.11 & BTRFS: system doesn't boot

Today I ran a regular "sudo yum -y update" and Fedora just "blew up in my face" with the following screen after a reboot:

if I issue the "journalctl" command I can see a BTRFS error:

(My system's root partition is in BTRFS).

And as far as I've googled no one had this issue before and to be honest, I don't know how to solve it...

The "sosreport.txt" file just doesn't copy anywhere, I plug a USB in and then run:

cp /run/initramfs/sosreport.txt /dev/sdc1


and the command apparently runs successfully but when I check the USB it is empty, same if I save it to "/var" "/var/log" or "/usr", the file just doesn't appear anywhere. I ran "cat" on such file and it is enormous to photograph it, but I took another pic that might be helpful:

It's worth to mention that I don't have any propietary drivers running on this system and if I boot with the last kernel before the update (which is 3.10.11-200.fc19.x86_64) everything works normally. The problematic kernel version is the 3.11.1-200.fc19.x86_64 one.

Here you have my partition table:

And my lspci output is here: https://gist.github.com/Jmlevick/843bbe330d0e758415ab

Does anyone know how to solve this?

Thanks.

P.S. With kernel 3.12.0-0.rc1.git3.1.fc21.x86_64 (a debug kernel from rawhide) the problem is not present.

 5 retagged mether 7061 ●43 ●67 ●111 https://fedoraproject....

### Kernel 3.11 & BTRFS: system doesn't boot

Today I ran a regular "sudo yum -y update" and Fedora just "blew up in my face" with the following screen after a reboot:

if I issue the "journalctl" command I can see a BTRFS error:

(My system's root partition is in BTRFS).

And as far as I've googled no one had this issue before and to be honest, I don't know how to solve it...

The "sosreport.txt" file just doesn't copy anywhere, I plug a USB in and then run:

cp /run/initramfs/sosreport.txt /dev/sdc1


and the command apparently runs successfully but when I check the USB it is empty, same if I save it to "/var" "/var/log" or "/usr", the file just doesn't appear anywhere. I ran "cat" on such file and it is enormous to photograph it, but I took another pic that might be helpful:

It's worth to mention that I don't have any propietary drivers running on this system and if I boot with the last kernel before the update (which is 3.10.11-200.fc19.x86_64) everything works normally. The problematic kernel version is the 3.11.1-200.fc19.x86_64 one.

Here you have my partition table:

And my lspci output is here: https://gist.github.com/Jmlevick/843bbe330d0e758415ab

Does anyone know how to solve this?

Thanks.

P.S. With kernel 3.12.0-0.rc1.git3.1.fc21.x86_64 (a debug kernel from rawhide) the problem is not present.

 6 retagged mether 7061 ●43 ●67 ●111 https://fedoraproject....

### Kernel 3.11 & BTRFS: system doesn't boot

Today I ran a regular "sudo yum -y update" and Fedora just "blew up in my face" with the following screen after a reboot:

if I issue the "journalctl" command I can see a BTRFS error:

(My system's root partition is in BTRFS).

And as far as I've googled no one had this issue before and to be honest, I don't know how to solve it...

The "sosreport.txt" file just doesn't copy anywhere, I plug a USB in and then run:

cp /run/initramfs/sosreport.txt /dev/sdc1


and the command apparently runs successfully but when I check the USB it is empty, same if I save it to "/var" "/var/log" or "/usr", the file just doesn't appear anywhere. I ran "cat" on such file and it is enormous to photograph it, but I took another pic that might be helpful:

It's worth to mention that I don't have any propietary drivers running on this system and if I boot with the last kernel before the update (which is 3.10.11-200.fc19.x86_64) everything works normally. The problematic kernel version is the 3.11.1-200.fc19.x86_64 one.

Here you have my partition table: