Bug 506807
| Summary: | Can't install Fedora 11 x86_64, in free space near 100GB non partitioned and win2008 server standard installed in the same machine | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | esdumbo2003 <esdumbo2003> | ||||||||
| Component: | anaconda | Assignee: | David Lehman <dlehman> | ||||||||
| Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||
| Severity: | medium | Docs Contact: | |||||||||
| Priority: | low | ||||||||||
| Version: | rawhide | CC: | areiner, guyloginin, ricardo.gladwell, rmaximo, vanmeeuwen+fedora | ||||||||
| Target Milestone: | --- | ||||||||||
| Target Release: | --- | ||||||||||
| Hardware: | x86_64 | ||||||||||
| OS: | Linux | ||||||||||
| Whiteboard: | anaconda_trace_hash:118554316a4d43d13a37b9ba94e1fc37e41a9b7b35bc1d706ad2db13fc9516a9 | ||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2009-08-14 17:37: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: | |||||||||||
| Attachments: |
|
||||||||||
Created attachment 348537 [details]
Attached traceback automatically from anaconda.
I tried to install before in graphic mode, now I tried in text mode. The problem is when anaconda try to create the partition in free space. The free space is near 100 GB. When I tried to create manual partition, the installer show the same error when save the parameters for first partition The machine is a Intel DG31PR with a Core2 Quad processor, and 500GB disk Note There isn't any problem to boot with live CD, but if I want to install from Live CD, happens the same problem Sorry, but English isn't my native language Comment on attachment 348537 [details]
Attached traceback automatically from anaconda.
I tried to install before in graphic mode, now I tried in text mode. The
problem is when anaconda try to create the partition in free space. The free
space is near 100 GB.
When I tried to create manual partition, the installer show the same error when
save the parameters for first partition
The machine is a Intel DG31PR with a Core2 Quad processor, and 500GB disk
Note
There isn't any problem to boot with live CD, but if I want to install from
Live CD, happens the same problem
Sorry, but English isn't my native language
Created attachment 348820 [details]
Attached traceback automatically from anaconda.
Comment on attachment 348820 [details]
Attached traceback automatically from anaconda.
The Fedora 10 installer experiences no difficulty with this arrangement (i.e. six-disk RAID 0 array with an ntfs Win XP Pro x64 partition, a Win 7 RC1 ntfs partition, and LVM for linux) -Very impressive. In addition, I do get a report about "sde" being not responsive during the text based Fedora 11 install portion of "Finding Devices | Finding Storage Devices".
To get past the Fedora 11 hang-up, a fresh Fedora 10 install was done -wiping out the existing linux installation. After that, the Fedora 11 install sort of works but errors out after installing packages and finalizing the installation. -I'll attempt that again to see if the bug report is different.
Off topic: The graphical install of F11 fails. With F10 it works without any problem on the same system with dual ATI 3870 PCIe graphics cards. Upon reboot of the F11 install, I am able to get into the new install but xorg is broken. Again, none of these problems occurred with F10.
Thank you.
For clarification, the RAID is BIOS RAID on a Gigabyte GA-MA780FXT-UD5P motherboard. Comment on attachment 348820 [details]
Attached traceback automatically from anaconda.
I had no such trouble with Fedora 10. This bug may be related to 506807 which I contributed to earlier today.
Thank you.
I just generated another bug report (i.e. 507255) which might be related to this one. The difference with the new bug is that it was generated After upgrading from F10 to F11 but before leaving the text-based installer. I got around bug 506807 by reinstalling F10 and immediately rebooting off of the F11 x86_64 DVD (i.e. without initializing / personalizing the F10 installation). Additional detail... The updated GRUB loader looks fine and appears to work fine but the F11 install will not boot to a GUI. Again, neither the LVM partition reuse nor the GUI issues occurred with Fedora 10. Thank you. *** Bug 507215 has been marked as a duplicate of this bug. *** I'm getting the same issue on my 32 bit 686 system, with RAID installed. Please see attached stack trace. Does anyone have a work around for this? Created attachment 350388 [details]
Anaconda stack trace log.
*** This bug has been marked as a duplicate of bug 495433 *** |
The following was filed automatically by anaconda: anaconda 11.5.0.59 exception report Traceback (most recent call first): File "/usr/lib64/python2.6/site-packages/parted/geometry.py", line 128, in intersect return Geometry(PedGeometry=self.__geometry.intersect(b.getPedGeometry())) File "/usr/lib/anaconda/storage/partitioning.py", line 501, in getBestFreeSpaceRegion free_geom = extended.geometry.intersect(_range) File "/usr/lib/anaconda/storage/partitioning.py", line 726, in allocatePartitions boot=_part.req_bootable) File "/usr/lib/anaconda/storage/partitioning.py", line 587, in doPartitioning allocatePartitions(disks, partitions) File "/usr/lib/anaconda/storage/partitioning.py", line 191, in doAutoPartition exclusiveDisks=anaconda.id.storage.clearPartDisks) File "/usr/lib/anaconda/dispatch.py", line 205, in moveStep rc = stepFunc(self.anaconda) File "/usr/lib/anaconda/dispatch.py", line 128, in gotoNext self.moveStep() File "/usr/lib/anaconda/text.py", line 712, in run anaconda.dispatch.gotoNext() File "/usr/bin/anaconda", line 965, in <module> anaconda.intf.run(anaconda) CreateException: Error al abrir /dev/sdb: No se ha encontrado el medio