Bug 574811

Summary:

Failure to install on Intel Matrix RAID box when raid level 1 is active

Product:

[Fedora] Fedora

Reporter:

Doug Ledford <dledford>

Component:

anaconda

Assignee:

Hans de Goede <hdegoede>

Status:

CLOSED NOTABUG

QA Contact:

Fedora Extras Quality Assurance <extras-qa>

Severity:

high

Docs Contact:

Priority:

high

Version:

CC:

dlehman, hdegoede, jonathan, vanmeeuwen+fedora

Target Milestone:

---

Target Release:

---

Hardware:

All

OS:

Linux

Whiteboard:

Fixed In Version:

Doc Type:

Bug Fix

Doc Text:

Story Points:

---

Clone Of:

574587

Environment:

Last Closed:

2010-03-22 23:03:57 UTC

Type:

---

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
dmesg output from raid1 attempt	none
contents of /proc/mdstat at time sda and sdb were declared not part of a raid set	none
program.log from raid1 attempt	none
storage.log from raid1 attempt	none
syslog from raid1 attempt	none

Description Doug Ledford 2010-03-18 15:31:00 UTC

+++ This bug was initially created as a clone of Bug #574587 +++


Update: trying this with a raid1 array already created by the BIOS avoided the traceback (at least initially, I made it traceback later).  However, it told me that disks sda and sdb had BIOS raid data, but are not part of any recognized BIOS raid sets.  Ignoring disks sda, sdb.

I'm attaching more support files from this boot with the machine in raid1 mode.


--- Additional comment from hdegoede on 2010-03-18 04:17:54 EDT ---

Hi Doug,

Thanks for the bug report, and thanks for testing!  Please file a separate bug for the RAID 1 issue.

------------------------------------------------------------------------------

New bug for raid1 issue.

Comment 1 Doug Ledford 2010-03-18 15:31:51 UTC

Created attachment 401048 [details]
dmesg output from raid1 attempt

Comment 2 Doug Ledford 2010-03-18 15:32:18 UTC

Created attachment 401049 [details]
contents of /proc/mdstat at time sda and sdb were declared not part of a raid set

Comment 3 Doug Ledford 2010-03-18 15:32:41 UTC

Created attachment 401050 [details]
program.log from raid1 attempt

Comment 4 Doug Ledford 2010-03-18 15:33:06 UTC

Created attachment 401051 [details]
storage.log from raid1 attempt

Comment 5 Doug Ledford 2010-03-18 15:33:37 UTC

Created attachment 401052 [details]
syslog from raid1 attempt

Comment 6 Hans de Goede 2010-03-19 10:43:07 UTC

Hi,

I cannot reproduce this, there is one known bug when a false positive of
this warning gets shown. When using ISW RAID and *not* selecting the
raidset in the advanced storage disk selection screen (you can find the set
under the Firmware RAID tab).

Is that what you are seeing? IOW are you not selecting the set as part of
the drives to have available during the installation ?

Regards,

Hans


p.s.

If you look in the dmesg and syslog log files, you will see a lockdep warning there related to mdraid this appears to be very real my ISW raid5 test install hung halfway, with stuck process messages for the kflush threads.

Comment 7 Doug Ledford 2010-03-19 14:46:49 UTC

No, on my box I am never presented with the option to select the two raid1 disks as install targets.  The two raid1 disks are sda and sdb, and when I select simple disk setup, it eventually shows me sdc and sdd, and I select those and then next and that's when it tells me that sda and sdb are part of a BIOS raid set but don't have raid info and therefore can't be used.

Comment 8 Hans de Goede 2010-03-19 14:55:27 UTC

(In reply to comment #7)
> No, on my box I am never presented with the option to select the two raid1
> disks as install targets.  The two raid1 disks are sda and sdb, and when I
> select simple disk setup, it eventually shows me sdc and sdd, and I select
> those and then next and that's when it tells me that sda and sdb are part of a
> BIOS raid set but don't have raid info and therefore can't be used.    

Ah,

So you are in effect indeed not selecting the RAID set, and thus hitting the false positive warning bug as I described.

For BIOS RAID you need to select advanced storage, not simple. Then on the advanced storage screen switch the Firmware RAID tab, select your set and everything should work from there on.

Regards,

Hans

Comment 9 Hans de Goede 2010-03-22 10:39:26 UTC

Doug,

Are you still seeing this when following the instructions from comment 9 ?

Thanks,

Hans

Comment 10 Doug Ledford 2010-03-22 23:03:57 UTC

OK, selecting advanced did the trick.  So, no, I don't still see this.