Bug 587813
Summary: | anaconda crashes when creating md RAID with uninitialized drive on F13 beta | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Chris Snook <chris.snook> |
Component: | anaconda | Assignee: | Anaconda Maintenance Team <anaconda-maint-list> |
Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | high | Docs Contact: | |
Priority: | low | ||
Version: | 13 | CC: | anaconda-maint-list, bcl, hdegoede, jonathan, vanmeeuwen+fedora |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2010-05-04 13:12:04 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: |
Description
Chris Snook
2010-04-30 23:02:33 UTC
To clarify the storage config, that's a 1 GB RAID 1 /boot, a 2x750 GB RAID 1 root VG, and an additional 2x200 GB RAID 0 VG for swap and mountpoints that don't actually get used during the install. I doubt the precise filesystem layout is critical to reproducing the bug, but unfortunately I had to get the system in question up and running and no longer have the ability to reproduce the problem myself. It may be possible to reproduce in a virtual machine. If it is possible, please add the /tmp/*log files to this bug Chris, As Brian already indicated, please reproduce this, and then when anaconda crashes collect all files under /tmp ending with log and also the file with tb in its name. You can use for example scp to copy these files out of the installer environment. Without these log files there is very little we can do to fix this bug. Regards, Hans Sadly, I've been unable to reproduce the bug, and the other user appears to have been hitting something else. (In reply to comment #4) > Sadly, I've been unable to reproduce the bug, and the other user appears to > have been hitting something else. Ok, closing this as insufficient info then. If you ever hit an anaconda problem in the future, collect the logs immediately when you hit the problem. Thanks for reporting! |