The following was filed automatically by anaconda: anaconda 14.17.4 exception report Traceback (most recent call first): File "/usr/lib/python2.7/site-packages/pyanaconda/storage/formats/fs.py", line 372, in doFormat raise FormatCreateError("format failed: %s" % ret.rc, self.device) File "/usr/lib/python2.7/site-packages/pyanaconda/storage/formats/fs.py", line 937, in doFormat FS.doFormat(self, *args, **kwargs) File "/usr/lib/python2.7/site-packages/pyanaconda/storage/formats/fs.py", line 851, in create return self.doFormat(*args, **kwargs) File "/usr/lib/python2.7/site-packages/pyanaconda/storage/deviceaction.py", line 290, in execute options=self.device.formatArgs) File "/usr/lib/python2.7/site-packages/pyanaconda/storage/devicetree.py", line 700, in processActions action.execute(intf=self.intf) File "/usr/lib/python2.7/site-packages/pyanaconda/storage/__init__.py", line 313, in doIt self.devicetree.processActions() File "/usr/lib/python2.7/site-packages/pyanaconda/packages.py", line 110, in turnOnFilesystems anaconda.storage.doIt() File "/usr/lib/python2.7/site-packages/pyanaconda/dispatch.py", line 212, in moveStep rc = stepFunc(self.anaconda) File "/usr/lib/python2.7/site-packages/pyanaconda/dispatch.py", line 131, in gotoNext self.moveStep() File "/usr/lib/python2.7/site-packages/pyanaconda/gui.py", line 1174, in nextClicked self.anaconda.dispatch.gotoNext() FormatCreateError: ('format failed: 1', '/dev/sda3')
Created attachment 450717 [details] Attached traceback automatically from anaconda.
Are you mounting filesystems on the shell on tty2? If so, please don't do that. Apparently the filesystems on /dev/sda3 and /dev/sda4 are already mounted at /mnt/m3 and /mnt/m4, respectively. You must not have any devices mounted or otherwise active if you expect anaconda to operate on them in any way.
You are right, although I now not remember exactly how things were, mountpoints /mnt/mNUMBER are my stuff, they aren't from anaconda. And likely there was some filesystem mounted (maybe some flash disk, I use it eg for "gdisk" utility, as it isn't on Fedora i386 boot disk. Or there could be more HDDs and I mounted some for other reason, I now not remember). Thus, sorry for noise with this event.
Created attachment 456674 [details] Attached traceback automatically from anaconda.
Created attachment 457355 [details] Attached traceback automatically from anaconda.
Comment on attachment 457355 [details] Attached traceback automatically from anaconda. - fault generated when attempting to install FC14 from DVD to iscsi on iomega ix4-200d
Created attachment 472894 [details] Attached traceback automatically from anaconda.
Created attachment 472903 [details] F14 x64 error I am not sure that this is the correct bug report, but anaconda reported to it automatically... Some more information from my side: I am trying to install F14 DVD and I get this error when trying to create the partitions. The hard drives are new, and I formatted them under windows in order to check for bad sectors - none found. The partition configuration is following: /dev/sdb1 - ext4 mounted to "/boot", size 500MB /dev/sdb2 - RAID partition, size 933869 /dev/sdc1 - RAID partition, size 933869 /dev/md0 - RAID device (LVM Group), size 1867712MB /dev/mapper/vg_i5-lv_root - Logical volume, ext4 mounted to "/", size 1707712MB /dev/mapper/vg_i5-lv_swap - Logical volume, swap, size 160000MB Regarding the physical machine: The motherboard is Asus P7P55D-E LX and the two WG 1TB HDD are attached to the SATA-3 (6Gb) interface. Another Seagate 500GB is attached to normal SATA-2. Please tell me If you need more information The previous attachment is from F14 i686, this one is F14 x64
This is the error from the command attempting to create the filesystem: 22:55:40,422 INFO program: Running... mke2fs -t ext4 /dev/mapper/vg_i5-lv_root <snip> 22:58:54,391 ERR program: mke2fs 1.41.12 (17-May-2010) 22:58:54,392 ERR program: ext2fs_mkdir: Attempt to read block from filesystem resulted in short read while creating root dir This is a small sample of the errors found throughout the system log: 20:58:44,728 INFO kernel:[ 1763.595440] sd 7:0:0:0: [sdc] Unhandled error code 20:58:44,728 INFO kernel:[ 1763.595442] sd 7:0:0:0: [sdc] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK 20:58:44,728 INFO kernel:[ 1763.595445] sd 7:0:0:0: [sdc] CDB: Write(10): 2a 00 31 20 18 00 00 00 08 00 20:58:44,728 ERR kernel:[ 1763.595457] end_request: I/O error, dev sdc, sector 824186880 20:58:44,729 INFO kernel:[ 1763.596174] sd 6:0:0:0: [sdb] Unhandled error code 20:58:44,729 INFO kernel:[ 1763.596176] sd 6:0:0:0: [sdb] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK 20:58:44,729 INFO kernel:[ 1763.596178] sd 6:0:0:0: [sdb] CDB: Write(10): 2a 00 31 2f b5 08 00 04 00 00 20:58:44,729 ERR kernel:[ 1763.596183] end_request: I/O error, dev sdb, sector 825210120 This all indicates there is a problem with your disks.
Thank you Dave. I tried several things and still think it is a bug. 1. I installed Windows and successfully formatted the hard drives. 2. I used Ubuntu Live CD and created RAID partition and formatted it with mkfs.ext4 -c /dev/md0 It didn't find any bad sectors. 3. I started the Fedora installer again and tried to install F14 in the partitions that I created with Ubuntu Desktop CD. Unfortunatelly I /boot must cannot be on RAID0 device, so I changed /dev/md0 to be RAID1. It forces the installer to reformat /dev/md0 (however I didn't touch the physical partitions created with Ubuntu). Again I get the same error. See the attached log 'F14 x64 error 2'. Maybe it is a mke2fs bug? I manged to workaround the installer by creating all required partition with Ubuntu Desktop CD, so the installer allow me to perform install without formating any of the partitions.
Created attachment 473667 [details] Error when recreating and formatting /dev/md0 as RAID0 (which was previously RAID1)
Same basic failure. The mkfs is failing to create the filesystem: 18:43:17,703 INFO program: Running... mke2fs -t ext4 /dev/md0 <snip> 18:45:54,459 ERR program: mke2fs 1.41.12 (17-May-2010) 18:45:54,459 ERR program: ext2fs_mkdir: Attempt to read block from filesystem resulted in short read while creating root dir Corresponding errors in syslog: 16:45:56,552 ERR kernel:[ 332.544241] end_request: I/O error, dev sdc, sector 1953521640 16:45:56,552 ERR kernel:[ 332.544245] end_request: I/O error, dev sdc, sector 1953521640 16:45:56,552 WARNING kernel:[ 332.544248] md: super_written gets error=-5, uptodate=0 16:45:56,552 INFO kernel:[ 332.544310] sd 7:0:0:0: [sdc] Unhandled error code 16:45:56,552 INFO kernel:[ 332.544312] sd 7:0:0:0: [sdc] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK 16:45:56,552 INFO kernel:[ 332.544315] sd 7:0:0:0: [sdc] CDB: Write(10): 2a 00 74 70 5f f0 00 00 02 00 16:45:56,552 ERR kernel:[ 332.544321] end_request: I/O error, dev sdc, sector 1953521648 16:45:56,552 ERR kernel:[ 332.544326] end_request: I/O error, dev sdc, sector 1953521648 16:45:56,552 WARNING kernel:[ 332.544329] md: super_written gets error=-5, uptodate=0 16:45:56,556 ERR kernel:[ 332.547399] end_request: I/O error, dev sdc, sector 0
Created attachment 474738 [details] Attached traceback automatically from anaconda.
Created attachment 474773 [details] Attached traceback automatically from anaconda.
Created attachment 474774 [details] Attached traceback automatically from anaconda.
Maybe it's a problem with mkfs? [root@2aul00132 ~]# mkfs.ext4 /dev/sda3 mke2fs 1.41.14 (22-Dec-2010) /dev/sda3 is mounted; will not make a filesystem here! [root@2aul00132 ~]# mkfs.ext4 /dev/sda3 mke2fs 1.41.14 (22-Dec-2010) /dev/sda3 is mounted; will not make a filesystem here!
That's normal with mkfs. You cannot create a filesystem on mounted partitions. You have to unmount them first.
Created attachment 476102 [details] Attached traceback automatically from anaconda.
Created attachment 480206 [details] Attached traceback automatically from anaconda.
Created attachment 481069 [details] Attached traceback automatically from anaconda.
Created attachment 493725 [details] Attached traceback automatically from anaconda.
Created attachment 499061 [details] Attached traceback automatically from anaconda.
Created attachment 505695 [details] Attached traceback automatically from anaconda.
Created attachment 524814 [details] Attached traceback automatically from anaconda.
In case this helps the developer or anyone else, the workaround to this, when trying to install on a new SSD, was to format the drive with ext4 and then the restart the Fedora install process. As a worst-case scenario fix, the dialog box could suggest the above to the user. In terms of a comment: The severity of this bug is far too low, this bug would be a showstopper to most linux newbies and doesn't inspire confidence.
are any of the reporters still having issues with F17?
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle. Changing version to '19'. (As we did not run this process for some time, it could affect also pre-Fedora 19 development cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.) More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19