Version-Release number of selected component: anaconda-core-22.20.13-1.fc22.x86_64 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/disklabel.py", line 271, in commit raise DiskLabelCommitError(msg) File "/usr/lib/python2.7/site-packages/blivet/devices/partition.py", line 562, in _create self.disk.format.commit() File "/usr/lib/python2.7/site-packages/blivet/devices/partition.py", line 591, in create self._create() File "/usr/lib/python2.7/site-packages/blivet/deviceaction.py", line 303, in execute self.device.create() File "/usr/lib/python2.7/site-packages/blivet/devicetree.py", line 372, in processActions action.execute(callbacks) File "/usr/lib/python2.7/site-packages/blivet/blivet.py", line 162, in doIt self.devicetree.processActions(callbacks) File "/usr/lib/python2.7/site-packages/blivet/osinstall.py", line 1057, in turnOnFilesystems storage.doIt(callbacks) 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) DiskLabelCommitError: Could not commit to disk /dev/sda, (py_ped_disk_commit) Additional info: 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 ide_core.trim=0 executable: /sbin/anaconda 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 product: Fedora release: Fedora release 22 (Twenty Two) type: anaconda version: 22
Created attachment 1059361 [details] File: anaconda-tb
Created attachment 1059362 [details] File: anaconda.log
Created attachment 1059363 [details] File: environ
Created attachment 1059364 [details] File: journalctl
Created attachment 1059365 [details] File: lsblk_output
Created attachment 1059366 [details] File: nmcli_dev_list
Created attachment 1059367 [details] File: os_info
Created attachment 1059368 [details] File: program.log
Created attachment 1059369 [details] File: storage.log
Created attachment 1059370 [details] File: ifcfg.log
This is either a hardware problem or a kernel bug. From the logs at the time it attempted to write the sda partition tables: Aug 05 04:00:28 localhost kernel: sda: sda1 sda2 Aug 05 04:00:58 localhost kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen Aug 05 04:00:58 localhost kernel: ata4.00: failed command: DATA SET MANAGEMENT Aug 05 04:00:58 localhost kernel: ata4.00: cmd 06/01:01:00:00:00/00:00:00:00:00/a0 tag 11 dma 512 out res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Aug 05 04:00:58 localhost kernel: ata4.00: status: { DRDY } Aug 05 04:00:58 localhost kernel: ata4: hard resetting link Aug 05 04:00:58 localhost kernel: ata4: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Aug 05 04:00:58 localhost kernel: ata4.00: configured for UDMA/133 Aug 05 04:00:58 localhost kernel: ata4.00: device reported invalid CHS sector 0 Aug 05 04:00:58 localhost kernel: ata4: EH complete Aug 05 04:01:29 localhost kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen Aug 05 04:01:29 localhost kernel: ata4.00: failed command: DATA SET MANAGEMENT Aug 05 04:01:29 localhost kernel: ata4.00: cmd 06/01:01:00:00:00/00:00:00:00:00/a0 tag 13 dma 512 out res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Aug 05 04:01:29 localhost kernel: ata4.00: status: { DRDY } Aug 05 04:01:29 localhost kernel: ata4: hard resetting link Aug 05 04:01:29 localhost kernel: ata4: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Aug 05 04:01:29 localhost kernel: ata4.00: configured for UDMA/133 Aug 05 04:01:29 localhost kernel: ata4.00: device reported invalid CHS sector 0 Aug 05 04:01:29 localhost kernel: ata4: EH complete Aug 05 04:02:00 localhost kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen Aug 05 04:02:00 localhost kernel: ata4.00: failed command: DATA SET MANAGEMENT Aug 05 04:02:00 localhost kernel: ata4.00: cmd 06/01:01:00:00:00/00:00:00:00:00/a0 tag 26 dma 512 out res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Aug 05 04:02:00 localhost kernel: ata4.00: status: { DRDY } Aug 05 04:02:00 localhost kernel: ata4: hard resetting link Aug 05 04:02:00 localhost kernel: ata4: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Aug 05 04:02:00 localhost kernel: ata4.00: configured for UDMA/133 Aug 05 04:02:00 localhost kernel: ata4.00: device reported invalid CHS sector 0 Aug 05 04:02:00 localhost kernel: ata4: EH complete