Bug 505744
| Summary: | Anaconda Fails to Create Partitions, Destroys GRUB | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Daniel Qarras <dqarras> |
| Component: | anaconda | Assignee: | Anaconda Maintenance Team <anaconda-maint-list> |
| Status: | CLOSED RAWHIDE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | high | Docs Contact: | |
| Priority: | low | ||
| Version: | 11 | CC: | anaconda-maint-list, bjorn, jgranado, rmaximo, vanmeeuwen+fedora |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2009-11-16 14:27:18 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
Daniel Qarras
2009-06-13 11:28:36 UTC
I had the same problem with a single disk and a much simpler partition layout. I requested a 400 MB boot partition with ext3, a 20 GB root partition with ext4, no swap partition, and to leave the rest of the disk unused. (I poked around a bit before that and changed my mind when Anaconda told me that /boot couldn't be on ext4.) I got the same error as Daniel, that mounting the first partition as /boot failed. I took the disk out and connected it to another computer, where fdisk reports the following: Disk /dev/sdc: 80.0 GB, 80026361856 bytes 255 heads, 63 sectors/track, 9729 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0x13c9f7c0 Device Boot Start End Blocks Id System /dev/sdc1 * 1 51 409600 83 Linux Partition 1 does not end on cylinder boundary. /dev/sdc2 51 2601 20480000 83 Linux /dev/sdc3 2601 2601 1024 83 Linux I don't remember requesting that third partition. The version of Anaconda is the one in Fedora-11-i386-DVD.iso. So, any news on this? Destroying GRUB is very bad, hopefully this is fixed soon? (In reply to comment #0) > Description of problem: > A system with Windows XP / Fedora 10 dual-boot using GRUB on /dev/sda with two .... > When trying again, same problem occurs. Manually checking partitioning with > fdisk one sees that /dev/sdb1 does not end on cylinder boundary but otherwise Not ending on a cylinder boundry is no longer an issue. This is just fdisk being legacy. The new LBA approach to address storage blocks is much better. Additionaly, fdisk give a warning not an error. In this case this warning can be ignored. > partitioning seems to be ok. Since anaconda fails to create file systems every > time, one needs to manually wipe out /dev/sdb1 and /dev/sdb3, recreate them > (causing /dev/sdb1 to end on cylinder boundary) and then restart the > installation, then anaconda finally succeeds creating the file systems. > > I now have F11 installed so unfortunately I cannot retest this or provide logs > but I thought this is worth reporting since destroying GRUB can be devastating > for most users. This is indeed something that needs to be addressed. With that said, can you test with rawhide? For f11 we cannot do much of anything. But we are moving forward with f12 installer. This issue is probably already fixed. I failed to mention that withoug the log files (/tmp/*log* at installation time) we can't debug this accurately. I just finished installing F12 RC4 on the original system and all went well this time. I think it should be safe to close this report but I'll leave the final decision to you. Thanks. Great, thanks for retesting. |