Bug 498144
| Summary: | anaconda F11 issue | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Parag Nemade <pnemade> | ||||||
| Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> | ||||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
| Severity: | medium | Docs Contact: | |||||||
| Priority: | medium | ||||||||
| Version: | 11 | CC: | christophvanderreijden, itamar, kernel-maint, lsatenstein, pjones, rmaximo, vanmeeuwen+fedora, zeus | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | i386 | ||||||||
| OS: | Linux | ||||||||
| Whiteboard: | anaconda_trace_hash:ced9659aa97e8a4db66c81e839dba14c78ccea1da32f8f30f554ee27a2f2ddb0 | ||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2009-07-29 08:56:57 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 341701 [details]
Attached traceback automatically from anaconda.
I am doing this on F10 with kvm kernel-2.6.27.19-170.2.35.fc10.i686 virt-manager-0.6.0-5.fc10.i386 This is not a bug with anaconda. You have a ton of error messages like the following in your exception report:
<3>ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
<3>ata1.00: cmd ca/00:01:00:00:00/00:00:00:00:00/e0 tag 0 dma 512 out
<3> res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
<3>ata1.00: status: { DRDY }
<4>ata1: link is slow to respond, please be patient (ready=0)
<4>ata1: device not ready (errno=-16), forcing hardreset
<6>ata1: soft resetting link
<6>ata1.00: configured for MWDMA2
<6>ata1: EH complete
This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle. Changing version to '11'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping Fedora 11 beta and Fedora 11 release. Anaconda crashes solidly, not allowing a trace back. Cannot do an installation. On this system, Fedora10 anaconda works fine, as does installation of Ubuntu and XP. Fedora11 beta and Fedora11 release crashes on this system and does not allow saving the traceback, or copying the traceback to a file. The mother board is an asus P5Q, System Memory 4 gigs, sata device 250gigs, intel e7300 dual core cpu. Repeat, all previous versions of Fedora install fine on this system. That includes IDE and Sata. Further comments. Tried the 386-F11 version after the x64-f11 version failed to load. All dvds tested clean. There is a real problem for me. I cannot install F11 on this system. I tried with vesa driver and all variations. Graphics card is a ATI hd3450, but that should not make a difference. The F11 Beta version (dated day of beta release), on this system crashes and locks up too. Leslie PS. I have a second system (different motherboard (intel d95gnt -video integrated, 4 gigs, 300g hard disk), and the F11 beta is just fine. So, is it something with the bios, or annaconda. (If it was the bios, why would the other systems boot, as well as live cds. I can confirm I cant install F11 via preupgrade on my laptop with ATI X200 onboard gfx.. anaconda doesnt start just freezed.. Here is what I noted for my two problems. a) Gparted had been used to create a /boot (1g ext3), a swap (8gig) and a / (ext4 for 80gigs). I managed, when anaconda locked up, to query the virtual terminal, and I was able to determine that anaconda was looking for the lvm implementation. So... I deleted /boot, /swap and / and then from within anaconda, (which now did not crash), I reallocated /boot, /swap and /. I did not bother to make a separate /home. Anaconda has problems with the presence of pre-allocated directories when there is no lvm F11 is up and running on the p5q system. Is this being addressed for Fedora 12? Assuming kernel-maintainers are very busy (as no comment received on this bug from them) and I am now running successfully F-11 final release, I would like to close this bug. Created attachment 356689 [details]
Attached traceback automatically from anaconda.
Installation of Fedora11 from DVD i386 failed. Failure occurred during the installation while writing storage configuration to disk. A window "Storage Activation Falied" holds the message: An error was encountered while activating your storage configuration. Details: Input/output error during write on /dev/sda. The created attachement (id=356689) to this comment was filed automatically and sent to this (498144) bug report. What would you suggest me to proceed to install Fedora11 successfully? |
The following was filed automatically by anaconda: anaconda 11.5.0.47 exception report Traceback (most recent call first): File "/usr/lib/python2.6/site-packages/parted/disk.py", line 162, in commitToDevice return self.__disk.commit_to_dev() File "/usr/lib/python2.6/site-packages/parted/disk.py", line 152, in commit if not self.commitToDevice(): File "/usr/lib/anaconda/storage/devices.py", line 808, in commit self.partedDisk.commit() File "/usr/lib/anaconda/storage/devices.py", line 1157, in create self.disk.commit() File "/usr/lib/anaconda/storage/deviceaction.py", line 203, in execute self.device.create(intf=intf) File "/usr/lib/anaconda/storage/devicetree.py", line 659, in processActions action.execute(intf=self.intf) File "/usr/lib/anaconda/storage/__init__.py", line 234, in doIt self.devicetree.processActions() File "/usr/lib/anaconda/packages.py", line 117, in turnOnFilesystems anaconda.id.storage.doIt() IOException: Input/output error during write on /dev/sda