The following was filed automatically by anaconda: anaconda 11.5.0.47 exception report Traceback (most recent call first): File "/usr/lib/anaconda/iutil.py", line 111, in execWithRedirect raise RuntimeError, errstr File "/usr/lib/anaconda/packages.py", line 107, in turnOnFilesystems searchPath = 1) 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 1330, in nextClicked self.anaconda.dispatch.gotoNext() RuntimeError: Error running swapoff: Input/output error
Created attachment 342765 [details] Attached traceback automatically from anaconda.
You've got lots of the following errors in your traceback, which indicate this is a problem with your media or with the kernel driver. <6>sr 14:0:0:0: [sr0] Unhandled sense code <6>sr 14:0:0:0: [sr0] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE,SUGGEST_OK <6>sr 14:0:0:0: [sr0] Sense Key : Medium Error [current] <6>sr 14:0:0:0: [sr0] Add. Sense: L-EC uncorrectable error <3>end_request: I/O error, dev sr0, sector 8911912 <3>Buffer I/O error on device sr0, logical block 2227978 <3>Buffer I/O error on device sr0, logical block 2227979
Yeah, this looks like the same kernel driver problem for the Liteon 20A1H drive that has been an issue ever since F7. After F7 these drives stopped working properly. This bug needs routed to the kernel team and not just closed. BTW, I've since started plugging in a USB-DVD on the machines with these Liteon drives until the kernel driver gets fixed.
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
Created attachment 347507 [details] Attached traceback automatically from anaconda.
Created attachment 348097 [details] Attached traceback automatically from anaconda.
Created attachment 348842 [details] Attached traceback automatically from anaconda.
Created attachment 349209 [details] Attached traceback automatically from anaconda.
Created attachment 349224 [details] Attached traceback automatically from anaconda.
This this today with a rawhide install on kvm. After creating three partitions /dev/vda1 as /boot with ext3 /dev/vda2 as swap /dev/vda3 as / with ext4 but the error messages is not the same like in the the original report. It shows now: RuntimeError: Error running swapoff: No such file or directory -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
This message is a reminder that Fedora 11 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 11. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '11'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 11's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 11 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 11 changed to end-of-life (EOL) status on 2010-06-25. Fedora 11 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.