The following was filed automatically by anaconda: anaconda 11.5.0.38 exception report Traceback (most recent call first): File "/usr/lib/python2.6/site-packages/parted/disk.py", line 154, in commit return self.__disk.commit() File "/usr/lib/anaconda/storage/devices.py", line 789, in commit self.partedDisk.commit() File "/usr/lib/anaconda/storage/devices.py", line 1130, in create self.disk.commit() File "/usr/lib/anaconda/storage/deviceaction.py", line 206, 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 210, in doIt self.devicetree.processActions() File "/usr/lib/anaconda/packages.py", line 115, in turnOnFilesystems anaconda.id.storage.doIt() 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/gui.py", line 1317, in nextClicked self.anaconda.dispatch.gotoNext() IOException: Input/output error during write on /dev/sda
Created attachment 337975 [details] Attached traceback automatically from anaconda.
The following errors from your exception indicate this is not a problem with anaconda. You are having problems with your hardware, like a drive is getting ready to fail, or there's something wrong with the kernel driver. I'm reassigning to kernel for now and they can make the determination if it's hardware or not. <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
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 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
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.