Bug 241088
| Summary: | Anaconda throws backtrace when installing on existing mdraid | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | David Nielsen <gnomeuser> | ||||
| Component: | anaconda | Assignee: | Anaconda Maintenance Team <anaconda-maint-list> | ||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Will Woods <wwoods> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | medium | ||||||
| Version: | rawhide | CC: | jarod | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | 11.2.0.65-1 | Doc Type: | Bug Fix | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2007-05-25 16:05:51 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: | |||||||
| Bug Depends On: | |||||||
| Bug Blocks: | 150226 | ||||||
| Attachments: |
|
||||||
|
Description
David Nielsen
2007-05-24 00:38:16 UTC
Created attachment 155310 [details]
anaconda dump
Okay, so.. you've got dmraid on.. sata_nv? Can you give us a bit more info about the RAID set up - number / type of disks, controller, etc? mdraid not dmraid Woods. it's an nforce3 SATA controller with dmraid capabilities turned off (since historically Linux has sucked on that, I plan to change it back for F8 to break it in interesting ways). 2 WDC WD4000YR-01P harddrives /boot on RAID1 /, /home and SWAP on LVM on top of a RAID0 ah, sorry.. it's late and I'm mixing up mdraid and dmraid again. according to pjones there was a bug in the mdraid metadata finding stuff that should be fixed in anaconda 11.2.0.64, so hopefully the next rawhide should be better. I managed to pull off an mdraid upgrade yesterday without a problem, whereas I couldn't a few days ago, so at least we're closer... We're trying to start the device md-1 which is weird. What's the output of mdadm -E for /dev/sda2, /dev/sdb1 and /dev/sdb2? Just set up a box with a pair of WD 120G ATA drives, 100M software raid1 /boot, the rest software raid0 with lvm atop it, featuring /, /home and swap. No more explodeyness, only oddity was grub needing to be reinstalled rather than upgrading the existing config for some reason. Works for me as of F7 RC2. |