Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1223760 - System installed on firmware-RAID is unbootable (no grub is provided)
Summary: System installed on firmware-RAID is unbootable (no grub is provided)
Keywords:
Status: CLOSED DUPLICATE of bug 1223332
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 22
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: F22FinalBlocker
TreeView+ depends on / blocked
 
Reported: 2015-05-21 12:15 UTC by Petr Schindler
Modified: 2015-05-21 15:18 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-05-21 15:18:01 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)
anaconda's program.log after the installation (894.54 KB, text/plain)
2015-05-21 12:16 UTC, Petr Schindler 		no flags Details
View All

Description Petr Schindler 2015-05-21 12:15:18 UTC 
Description of problem:
I set up RAID0 with 1 ssd disk and 2 normal disks and I tried it with 2 normal disks in RAID0. Then I run installation from F22 Live-Workstation RC2. Everything worked fine. But after reboot there is no bootable system. Even when I try UEFI entry Fedora it doesn't boot. From disk it doesn't boot to grub.

When I look into anaconda's program.log there is output from new-kernel-pkgs which isn't there normally. Part of it:

3:45:42,105 INFO program: Running... new-kernel-pkg --mkinitrd --dracut --depmod --update 4.0.2-300.fc22.x86_64
13:46:03,104 INFO program: depmod: ERROR: /boot/System.map-4.0.2-300.fc22.x86_64:2414: invalid line: ffffffffatch
13:46:03,104 INFO program: 
13:46:03,104 INFO program: depmod: ERROR: /boot/System.map-4.0.2-300.fc22.x86_64:4992: invalid line: ffffffff810firq
13:46:03,104 INFO program: 
13:46:03,105 INFO program: depmod: ERROR: /boot/System.map-4.0.2-300.fc22.x86_64:5832: invalid line: ffffffff811m_stop
13:46:03,105 INFO program: 
13:46:03,105 INFO program: depmod: ERROR: /boot/System.map-4.0.2-300.fc22.x86_64:5913: invalid line: ffffm_stop
13:46:03,105 INFO program: 
13:46:03,105 INFO program: depmod: ERROR: /boot/System.map-4.0.2-300.fc22.x86_64:6702: invalid line: fffffffstroy_buf
...
...
...

Version-Release number of selected component (if applicable):
4.0.2-300.fc22.x86_64
F22 RC2


Additional info:
I propose this as blocker. It violates beta criterion: "The installer must be able to detect and install to hardware or firmware RAID storage devices."
Comment 1 Petr Schindler 2015-05-21 12:16:06 UTC 
Created attachment 1028115 [details]
anaconda's program.log after the installation
Comment 2 Stephen Gallagher 2015-05-21 15:07:34 UTC 
This may be hardware-dependent. I just installed successfully on a four-disk RAID0 array provided by LSI hardware on a Dell PowerEdge T620. I installed on EFI.

I experienced no errors like those Petr saw above and it booted just fine.

I'm -1 to blocking on this.
Comment 3 Josh Boyer 2015-05-21 15:18:01 UTC 
Petr tested with 4.0.4-301 which has the fix from bug 1223332 on the same machine.  He said that worked fine, so I'm going to mark this as a duplicate.

*** This bug has been marked as a duplicate of bug 1223332 ***
Note You need to log in before you can comment on or make changes to this bug.