Description of problem: install in a custom partition of old Fedora install, anaconda stopped at 100% but crashed / not finished Version-Release number of selected component: anaconda-20.25.15-1.fc20.i686 The following was filed automatically by anaconda: anaconda 20.25.15-1 exception report Traceback (most recent call first): File "/usr/lib/python2.7/site-packages/pyanaconda/bootloader.py", line 1426, in write_device_map dev_map = open(map_path, "w") File "/usr/lib/python2.7/site-packages/pyanaconda/bootloader.py", line 1554, in write self.write_device_map() File "/usr/lib/python2.7/site-packages/pyanaconda/bootloader.py", line 2328, in writeBootLoader storage.bootloader.write() File "/usr/lib/python2.7/site-packages/pyanaconda/install.py", line 173, in doInstall writeBootLoader(storage, payload, instClass, ksdata) File "/usr/lib/python2.7/threading.py", line 764, in run self.__target(*self.__args, **self.__kwargs) File "/usr/lib/python2.7/site-packages/pyanaconda/threads.py", line 192, in run threading.Thread.run(self, *args, **kwargs) IOError: [Errno 2] No such file or directory: '/mnt/sysimage/boot/grub2/device.map' Additional info: cmdline: /usr/bin/python /sbin/anaconda --liveinst --method=livecd:///dev/mapper/live-base cmdline_file: initrd=initrd0.img root=live:CDLABEL=Fedora-Live-LXDE-i686-20-1 rootfstype=auto ro rd.live.image rhgb rd.luks=0 rd.md=0 rd.dm=0 BOOT_IMAGE=vmlinuz0 executable: /sbin/anaconda hashmarkername: anaconda kernel: 3.11.10-301.fc20.i686 other involved packages: python-libs-2.7.5-9.fc20.i686 product: Fedora release: Fedora release 20 (Heisenbug) type: anaconda version: 20
Created attachment 901418 [details] File: anaconda-tb
Created attachment 901419 [details] File: anaconda.log
Created attachment 901420 [details] File: environ
Created attachment 901421 [details] File: journalctl
Created attachment 901422 [details] File: lsblk_output
Created attachment 901423 [details] File: nmcli_dev_list
Created attachment 901424 [details] File: os_info
Created attachment 901425 [details] File: program.log
Created attachment 901426 [details] File: storage.log
Created attachment 901427 [details] File: ifcfg.log
Created attachment 901428 [details] File: packaging.log
i searched related bugs and found an old issue here: https://bugzilla.redhat.com/show_bug.cgi?id=735730, 735785, 798483, IOError: [Errno 2] No such file or directory: '/mnt/sysimage/boot/grub2/device.map' : upgrade with 'install new bootloader configuration' fails IOError: No such file or directory: '/mnt/sysimage/boot/grub2/device.map' not sure how to resolve, iM on a multiboot setup, so i wanted to reuse an old partition i used for an old Fedora 15 install, previously upgraded from version 11 and 12, then 14 :D
Created attachment 922049 [details] logs I am having the same problem on a specific machine. I can reproduce the bug. Sometimes I get different errors, like errno 30, as I already reported in https://bugzilla.redhat.com/show_bug.cgi?id=1123174#c12
My problem was originated by an incompatibility between computer's SATA controller and the SSD drive, so please ignore my comments and logs.
11:54:36,084 INFO program: rsync: recv_generator: mkdir "/mnt/sysimage/boot/efi/EFI/fedora" failed: No space left on device (28) 11:54:36,086 INFO program: *** Skipping any contents from this failed directory *** 11:54:36,087 INFO program: rsync: recv_generator: mkdir "/mnt/sysimage/boot/grub2" failed: No space left on device (28) 11:54:36,088 INFO program: *** Skipping any contents from this failed directory *** 11:54:36,088 INFO program: rsync: mkstemp "/mnt/sysimage/boot/.vmlinuz-3.11.10-301.fc20.i686.hmac.APu8p1" failed: No space left on device (28) 11:54:36,089 INFO program: rsync: mkstemp "/mnt/sysimage/boot/.System.map-3.11.10-301.fc20.i686.zCv3hL" failed: No space left on device (28) 11:54:36,089 INFO program: rsync: mkstemp "/mnt/sysimage/boot/.config-3.11.10-301.fc20.i686.yUpKCv" failed: No space left on device (28) etc, is the problem. So there's not enough free space on /boot, and anaconda didn't check for that.
*** Bug 1194958 has been marked as a duplicate of this bug. ***
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. 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 EOL if it remains open with a Fedora 'version' of '20'. 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. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 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, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. 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.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.