Bug 950206

Summary: cannot rescue btrfs system
Product: [Fedora] Fedora Reporter: Jeff Bastian <jbastian>
Component: python-blivetAssignee: Vratislav Podzimek <vpodzime>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: medium    
Version: 19CC: anaconda-maint-list, bcl, bugzilla, dlehman, g.kaviyarasu, jonathan, mkolman, sbueno, vanmeeuwen+fedora
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: python-blivet-0.20-1 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-02-18 11:11:00 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
anaconda.log from rescue boot
none
program.log from rescue boot
none
storage.log from rescue boot
none
syslog from rescue boot none

Description Jeff Bastian 2013-04-09 20:36:10 UTC 
Description of problem:
I installed Fedora 19 Alpha RC1 with btrfs (due to bug 950145) but ran into a problem with grub2 (see bug 817187), so I booted into Rescue mode from the installation DVD.  The Rescue told me:
  You don't have any Linux partitions.  Press return to get a shell.
  The system will reboot automatically when you exist from the shell.

What?  I just installed it a few minutes ago!  How can I not have any Linux partitions?

I fired up a shell and tried it manually:
  mount -t btrfs -o subvol=root /dev/sda4 /mnt/sysimage
  mount -t btrfs -o subvol=home /dev/sda4 /mnt/sysimage/home
  mount -t ext4                 /dev/sda2 /mnt/sysimage/boot
  mount -t vfat                 /dev/sda1 /mnt/sysimage/boot/efi
  mount --bind /dev /mnt/sysimage/dev
  mount --bind /sys /mnt/sysimage/sys
  mount --bind /proc /mnt/sysimage/proc
  chroot /mnt/sysimage

And now I can rescue my system.

Why couldn't anaconda do that?

Version-Release number of selected component (if applicable):
anaconda 19.16-1

How reproducible:
unsure

Steps to Reproduce:
1. install F19 Alpha RC1 with btrfs filesystem
2. try a rescue boot
  
Actual results:
rescue says no Linux partitions found

Expected results:
rescue finds OS and mounts it at /mnt/sysimage

Additional info:
Comment 1 Jeff Bastian 2013-04-09 20:40:59 UTC 
Created attachment 733353 [details]
anaconda.log from rescue boot
Comment 2 Jeff Bastian 2013-04-09 20:41:22 UTC 
Created attachment 733354 [details]
program.log from rescue boot
Comment 3 Jeff Bastian 2013-04-09 20:41:57 UTC 
Created attachment 733355 [details]
storage.log from rescue boot
Comment 4 Jeff Bastian 2013-04-09 20:42:27 UTC 
Created attachment 733356 [details]
syslog from rescue boot
Comment 5 Jeff Bastian 2013-04-11 21:23:02 UTC 
This is most likely related to bug 950145 and bug 951244 which are also due to the corrupt backup GPT label and so Anaconda ignores any existing partitions on the disk.
Comment 6 Chris Murphy 2013-06-24 05:40:37 UTC 
Mostly works with anaconda-19.30.9-1 however it fails to locate and mount a btrfs /boot subvolume without notification. /boot is simply empty.
Comment 7 Vratislav Podzimek 2013-07-30 12:00:13 UTC 
I've just tested that the BTRFS-based system is found and mounted, but there are some problems with subvolumes causing usually the /boot not to be mounted. Reassigning to blivet as the problem lies in there.
Comment 8 David Lehman 2013-07-30 14:55:17 UTC 
FSSet._parseOneLine just needs to pass the options to devicetree.resolveDevice as a keyword arg since that's the only place to find the subvol, whether by name or id.
Comment 9 Vratislav Podzimek 2013-08-01 11:19:14 UTC 
(In reply to David Lehman from comment #8)
> FSSet._parseOneLine just needs to pass the options to
> devicetree.resolveDevice as a keyword arg since that's the only place to
> find the subvol, whether by name or id.
That works, thanks! Patch sent to anaconda-patches.
Comment 10 Fedora End Of Life 2015-01-09 22:33:16 UTC 
This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 19 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.
Comment 11 Fedora End Of Life 2015-02-18 11:11:00 UTC 
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.