Description of problem: installing F22 RC2 with network error occured during formating of /dev/sda5 Version-Release number of selected component: anaconda-22.20.13-1 The following was filed automatically by anaconda: anaconda 22.20.13-1 exception report Traceback (most recent call first): File "/usr/lib/python2.7/site-packages/blivet/formats/fs.py", line 656, in mount raise FSError("mount failed: %s" % rc) File "/usr/lib/python2.7/site-packages/blivet/formats/fs.py", line 893, in setup return self.mount(**kwargs) File "/usr/lib/python2.7/site-packages/blivet/osinstall.py", line 595, in mountFilesystems chroot=rootPath) File "/usr/lib/python2.7/site-packages/blivet/blivet.py", line 1407, in mountFilesystems readOnly=readOnly, skipRoot=skipRoot) File "/usr/lib/python2.7/site-packages/blivet/osinstall.py", line 1066, in turnOnFilesystems storage.mountFilesystems() File "/usr/lib64/python2.7/site-packages/pyanaconda/install.py", line 196, in doInstall turnOnFilesystems(storage, mountOnly=flags.flags.dirInstall, callbacks=callbacks_reg) File "/usr/lib64/python2.7/threading.py", line 766, in run self.__target(*self.__args, **self.__kwargs) File "/usr/lib64/python2.7/site-packages/pyanaconda/threads.py", line 244, in run threading.Thread.run(self, *args, **kwargs) FSError: mount failed: 32 Additional info: addons: com_redhat_kdump cmdline: /usr/bin/python2 /sbin/anaconda cmdline_file: BOOT_IMAGE=/images/pxeboot/vmlinuz inst.stage2=hd:LABEL=Fedora-22-x86_64 rd.live.check quiet dnf.rpm.log: May 21 15:03:50 INFO --- logging initialized --- executable: /sbin/anaconda hashmarkername: anaconda kernel: 4.0.2-300.fc22.x86_64 product: Fedora release: Cannot get release name. type: anaconda version: 22
Created attachment 1028182 [details] File: anaconda-tb
Created attachment 1028183 [details] File: anaconda.log
Created attachment 1028184 [details] File: dnf.log
Created attachment 1028185 [details] File: environ
Created attachment 1028186 [details] File: lsblk_output
Created attachment 1028187 [details] File: nmcli_dev_list
Created attachment 1028188 [details] File: os_info
Created attachment 1028189 [details] File: program.log
Created attachment 1028190 [details] File: storage.log
Created attachment 1028191 [details] File: syslog
Created attachment 1028192 [details] File: ifcfg.log
Created attachment 1028193 [details] File: packaging.log
Another user experienced a similar problem: F22 RC3 network install bug appeared during creation of EFI partition on /dev/sda5 (i use standard partitions, no lvm) addons: com_redhat_kdump cmdline: /usr/bin/python2 /sbin/anaconda cmdline_file: BOOT_IMAGE=/images/pxeboot/vmlinuz inst.stage2=hd:LABEL=Fedora-22-x86_64 rd.live.check quiet dnf.rpm.log: May 22 06:27:24 INFO --- logging initialized --- hashmarkername: anaconda kernel: 4.0.4-301.fc22.x86_64 package: anaconda-22.20.13-1 product: Fedora reason: FSError: mount failed: 32 release: Cannot get release name. version: 22
Another user experienced a similar problem: F22 RC3 Live Workstation install problem occured when formating the last partition /dev/sda6 (i do not use lvm, but standard partitions) i have the feeling that it occurs systematically when previous partitions have first to be deleted (installation on a disk with previous installation with all linux partitions were deleted) i have also 5 Windows partitions on the same disk cmdline: /usr/bin/python2 /sbin/anaconda --liveinst --method=livecd:///dev/mapper/live-base cmdline_file: BOOT_IMAGE=/isolinux/vmlinuz0 root=live:LABEL=Fedora-Live-WS-x86_64-22-3 ro rd.live.image quiet rhgb rd.live.check hashmarkername: anaconda kernel: 4.0.4-301.fc22.x86_64 other involved packages: python-libs-2.7.9-6.fc22.x86_64, python-blivet-1.0.9-1.fc22.noarch package: anaconda-core-22.20.13-1.fc22.x86_64 packaging.log: product: Fedora reason: FSError: mount failed: 32 release: Fedora release 22 (Twenty Two) version: 22
Another user experienced a similar problem: After setup partitions, it tries to install Fedora 22 on workstation. Then It prompts error message. It blocks installation. cmdline: /usr/bin/python2 /sbin/anaconda --liveinst --method=livecd:///dev/mapper/live-base cmdline_file: BOOT_IMAGE=vmlinuz0 initrd=initrd0.img root=live:CDLABEL=Fedora-Live-WS-x86_64-22-3 rootfstype=auto ro rd.live.image quiet rhgb rd.luks=0 rd.md=0 rd.dm=0 hashmarkername: anaconda kernel: 4.0.4-301.fc22.x86_64 other involved packages: python-libs-2.7.9-6.fc22.x86_64, python-blivet-1.0.9-1.fc22.noarch package: anaconda-core-22.20.13-1.fc22.x86_64 packaging.log: product: Fedora reason: FSError: mount failed: 32 release: Fedora release 22 (Twenty Two) version: 22
Another user experienced a similar problem: booted from USB chose to install to hard drive ( ATA CF Card ) dies about 30% into install - creating ext4 cmdline: /usr/bin/python2 /sbin/anaconda --liveinst --method=livecd:///dev/mapper/live-base cmdline_file: BOOT_IMAGE=vmlinuz0 initrd=initrd0.img root=live:CDLABEL=Fedora-Live-WS-i686-22-3 rootfstype=auto ro rd.live.image quiet rhgb rd.luks=0 rd.md=0 rd.dm=0 hashmarkername: anaconda kernel: 4.0.4-301.fc22.i686 other involved packages: python-libs-2.7.9-6.fc22.i686, python-blivet-1.0.9-1.fc22.noarch package: anaconda-core-22.20.13-1.fc22.i686 packaging.log: product: Fedora reason: FSError: mount failed: 32 release: Fedora release 22 (Twenty Two) version: 22
I have this issue. I can install fine on a kinston 32gb USB stick, but trying to install on a uDrive 512gb USB stick (yes - 512"GB") it crashed out at between 30%-40% into the installation.
I split the drive manually SDA1 - /boot - 2mb SDA2 - swap - 2mb SDA3 - /(root) - 50gb SDA4 - /home - remaining (about 450gb) It looks like it bombed out trying to format the root section. You'll have to look at my logs, I'm not an expert yet :) but that's where it seemed to crash every time - trying to format or install stuff to the root. I have tested the USB stick for error - looks fine. I have tried the same thing with another uDrive 512gb stick - same deal. Hope that helps. !
Hardware failure: 13:31:29,803 INFO kernel:[ 1709.123314] sd 0:0:0:0: [sda] tag#24 CDB: Write(10) 2a 00 30 58 00 40 00 05 c0 00 13:31:29,803 ERR kernel:[ 1709.123319] blk_update_request: I/O error, dev sda, sector 811073600 13:31:29,803 INFO kernel:[ 1709.123544] sd 0:0:0:0: [sda] tag#25 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE 13:31:29,803 INFO kernel:[ 1709.123550] sd 0:0:0:0: [sda] tag#25 Sense Key : Aborted Command [current] [descriptor] 13:31:29,803 INFO kernel:[ 1709.123553] sd 0:0:0:0: [sda] tag#25 Add. Sense: No additional sense information 13:31:29,803 INFO kernel:[ 1709.123556] sd 0:0:0:0: [sda] tag#25 CDB: Write(10) 2a 00 30 58 06 00 00 08 00 00 13:31:29,803 ERR kernel:[ 1709.123560] blk_update_request: I/O error, dev sda, sector 811075072 13:31:29,804 INFO kernel:[ 1709.123762] ata1: EH complete 13:31:29,804 NOTICE kernel:[ 1709.123785] XFS (dm-2): xfs_do_force_shutdown(0x1) called from line 1092 of file fs/xfs/xfs_buf.c. Return address = 0xffffffffa06c973c 13:31:29,804 ALERT kernel:[ 1709.123786] XFS (dm-2): I/O Error Detected. Shutting down filesystem 13:31:29,804 ALERT kernel:[ 1709.123787] XFS (dm-2): Please umount the filesystem and rectify the problem(s) 13:31:29,804 ALERT kernel:[ 1709.123789] XFS (dm-2): metadata I/O error: block 0x1a00040 ("xlog_bwrite") error 5 numblks 8200 13:31:29,804 WARNING kernel:[ 1709.123963] XFS (dm-2): failed to locate log tail 13:31:29,804 WARNING kernel:[ 1709.123964] XFS (dm-2): log mount/recovery failed: error -5 13:31:29,804 WARNING kernel:[ 1709.124001] XFS (dm-2): log mount failed