Bug 172532
| Summary: | installer crashes on kickstart install | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Russell Coker <rcoker> | ||||
| Component: | anaconda | Assignee: | Anaconda Maintenance Team <anaconda-maint-list> | ||||
| Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | |||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | medium | ||||||
| Version: | rawhide | CC: | agk, dwysocha, mbroz | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | i386 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2008-03-14 23:41:24 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
Russell Coker
2005-11-06 12:26:33 UTC
Created attachment 120769 [details]
Anaconda dump log
The lvm tools don't seem to like their own metadata Incorrect metadata area header checksum Can't remove logical volume "test" under snapshot I think that one might have been from the "create snap-shot on root LV and dead-lock your machine" problem. In any case, I specified in the kickstart config file that I wanted the entire partition table wiped. Why couldn't it just wipe it without examining it? Not sure if this is still an issue, but anaconda in this case (kickstart with option to wipe everything) should remove all possible metadata on discs, not only partition table. Metadata can be broken on disk and lvm will of course fail then - this is not lvm2 bug. requested by Jams Antill Is this still happening under rawhide? The information we've requested above is required in order to review this problem report further and diagnose/fix the issue if it is still present. Since there have not been any updates to the report since thirty (30) days or more since we requested additional information, we're assuming the problem is either no longer present in the current Fedora release, or that there is no longer any interest in tracking the problem. Setting status to "INSUFFICIENT_DATA". If you still experience this problem after updating to our latest Fedora release and can provide the information previously requested, please feel free to reopen the bug report. Thank you in advance. |