The following was filed automatically by anaconda: anaconda 13.35 exception report Traceback (most recent call first): File "/usr/lib/anaconda/storage/formats/disklabel.py", line 244, in commit raise DiskLabelCommitError(msg) File "/usr/lib/anaconda/storage/devices.py", line 1267, in create self.disk.format.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 677, in processActions action.execute(intf=self.intf) File "/usr/lib/anaconda/storage/__init__.py", line 290, in doIt self.devicetree.processActions() File "/usr/lib/anaconda/packages.py", line 109, in turnOnFilesystems anaconda.storage.doIt() File "/usr/lib/anaconda/dispatch.py", line 205, in moveStep rc = stepFunc(self.anaconda) File "/usr/lib/anaconda/dispatch.py", line 126, in gotoNext self.moveStep() File "/usr/lib/anaconda/gui.py", line 1313, in nextClicked self.anaconda.dispatch.gotoNext() DiskLabelCommitError: Could not commit to disk /dev/sda
Created attachment 401205 [details] Attached traceback automatically from anaconda.
Initial config: IT8212 raid ide controller (non raid mode) /dev/sda - 200Gb Seagate /dev/sdb - 200Gb Seagate /dev/sda1 - 100Mb, Primary, NTFS (Win7 System reserved) /dev/sda2 - 29899Mb, Primary, NTFS (Win7 System) free 160782Mb 0. Enter the partitioning menu (Basic Storage Devices, select first hdd). 1. Select custom layout 2. Create standart partition (/boot,ext4,500mb, force primary). Ok, /dev/sda3 created. 3. Create LVM physical volume(69500Mb fixed size). Ok, /dev/sda4 (160282Mb extended) created, /dev/sda5 (69500Mb physical volume(LVM)) created. 4. Select /dev/sda5 and press "create". 5. Change Volume Group Name to SysVolGroup and add five logical volumes (mount point, fs, logical volume name, size) (,swap,VolSwap,4096Mb) (/tmp,ext4,VolTmp,10016Mb) (/home,ext4,VolHome,20000Mb) (/var,ext4,VolVar,10016Mb) (/,ext4,VolRoot,25344Mb) 6. Press "Ok" (to return to partitioning menu) no problem so far 7. Press "Next" and select "Write changes to disk" 8. exception!
You have tons of kernel error messages in your syslog indicating problems reading or writing to your hardware. anaconda is unable to handle this situation, nor should it really be expected to given the nature of the failure. Reassigning. 09:43:07,086 DEBUG kernel:it821x: can't process command 0xE7 09:43:07,086 ERR kernel:ata11.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 09:43:07,086 ERR kernel:ata11.00: failed command: FLUSH CACHE 09:43:07,086 ERR kernel:ata11.00: cmd e7/00:00:00:00:00/00:00:00:00:00/a0 tag 0 09:43:07,086 ERR kernel: res 50/00:01:01:00:00/00:00:00:00:00/00 Emask 0x1 (device error) 09:43:07,086 ERR kernel:ata11.00: status: { DRDY } 09:43:07,105 INFO kernel:ata11.00: configured for DMA 09:43:07,105 ERR kernel:end_request: I/O error, dev sda, sector 0 09:43:07,105 INFO kernel:ata11: EH complete
Hmm, I just check by test program HDD and IDE-cable on different type controller (JB36x) and did not find any problems (no bad blocks and good s.m.a.r.t.). Win7 is work without problems from the same HDD and controller (it8212). Imho driver of it821x is source of errors. P.S.Very similar problem I found on http://ubuntuforums.org/showthread.php?p=8414906
This bug appears to have been reported against 'rawhide' during the Fedora 14 development cycle. Changing version to '14'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Created an attachment (id=440593) Attached traceback automatically from anaconda.
My computer is/has been working fine with both Windows XP and Fedora, successively upgraded up to Fedora 11, with no changes to the disk partitioning, and suddenly while upgrading to Fedora 13, it crashes. Now I am left without Linux as I can't install it at all. It's a pity.
I got this message on the ISO i downloaded today, so I used an ISO i downloaded on December 16, 2010. The installation from the older ISO worked correctly.
*** Bug 696714 has been marked as a duplicate of this bug. ***