Bug 506654
Summary: | Disk partitioning utility fails to detect disks correctly. | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Nils Hammar <u60149431> | ||||||
Component: | anaconda | Assignee: | Anaconda Maintenance Team <anaconda-maint-list> | ||||||
Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
Severity: | medium | Docs Contact: | |||||||
Priority: | low | ||||||||
Version: | 11 | CC: | anaconda-maint-list, rmaximo, vanmeeuwen+fedora | ||||||
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: | 2009-06-19 09:22:41 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
Nils Hammar
2009-06-18 07:29:05 UTC
Created attachment 348529 [details]
Error message from anaconda.
This is the error message that anaconda provided when it failed to write the configuration to disk.
Created attachment 348530 [details]
Picture of device names provided by OS.
The device names provided seems to be unusable later on.
The motherboard is an ASUS P4P800-E Deluxe. Previously it did have BIOS 1004, but there is no change after an upgrade to BIOS 1009. This seems to be similar to bug 496339; https://bugzilla.redhat.com/show_bug.cgi?id=496339 After a lot of pain it seems like the only way to make things work during the installation is to accept the default partitioning and never enter the customization screen. I can't say that I like that at all - especially since I want a non-default partitioning. :( I finally found the real culprit in all this, and a workaround in bug 499733. *** This bug has been marked as a duplicate of bug 499733 *** |