Bug 1039283 - Rescue mode is unable to detect system on degraded RAID
Summary: Rescue mode is unable to detect system on degraded RAID
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 20
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-07 15:42 UTC by Alexey Torkhov
Modified: 2015-01-16 22:23 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-01-16 22:21:02 UTC
Type: Bug


Attachments (Terms of Use)

Description Alexey Torkhov 2013-12-07 15:42:23 UTC
Description of problem:
Rescue mode of install DVD does not recognize system that is on degraded RAID.

I was trying following layout:
vda1 /boot RAID1 (degraded)
vda2 / RAID1 (degraded)
vda3 swap RAID0 (incomplete/broken)

The system was bootable (just enters in emergency mode when booting because swap is missing)

Version-Release number of selected component (if applicable):
anaconda-20.25.14-1.fc20.x86_64

Steps to Reproduce:
1. Install using software RAID
2. Boot into rescue CD and try to mount existing system

Actual results:
Can not find existing system

Expected results:
Rescue mounts system

Comment 1 Fedora Blocker Bugs Application 2013-12-07 16:11:05 UTC
Proposed as a Blocker for 20-final by Fedora user atorkhov using the blocker tracking app because:

 The rescue mode of the installer must be able to detect and mount any installation performed according to the applicable criteria, and provide a shell with access to utilities capable of performing typical recovery operations.

Comment 2 Alexey Torkhov 2013-12-07 20:52:56 UTC
This probably feature probably is not designed and not simple to implement, so removing blocker proposition.

Comment 3 David Shea 2015-01-16 22:21:02 UTC
I just tried a rescue mode boot with a degraded RAID1 and it was mounted at /mnt/sysimage, so I guess this got fixed at some point. Feel free to reopen the bug if there's still issues.

Comment 4 David Shea 2015-01-16 22:23:28 UTC
Also, if there is still an issue, please attach the log files from /tmp from the point where you get to a rescue shell.


Note You need to log in before you can comment on or make changes to this bug.