Description of problem: I don't remember what has happened exactly, i formated my drive with terminal and the fdisk command(had 2 OS - windows and linux), and after i folowed the steps for installing Fedora 20. i went out with my dog at 80% installed and when i came back it was with compleated installation and the bug window showed - something about lib/x64/python2.6(maybe different version and different path sequence). Hope this was helpfull . Regards Version-Release number of selected component: anaconda-20.25.15-1.fc20.x86_64 The following was filed automatically by anaconda: anaconda 20.25.15-1 exception report Traceback (most recent call first): File "/usr/lib64/python2.7/site-packages/pyanaconda/packaging/livepayload.py", line 96, in progress mnt_stat = os.statvfs(ROOT_PATH+mnt) File "/usr/lib64/python2.7/threading.py", line 764, in run self.__target(*self.__args, **self.__kwargs) File "/usr/lib64/python2.7/site-packages/pyanaconda/threads.py", line 192, in run threading.Thread.run(self, *args, **kwargs) OSError: [Errno 2] Няма такъв файл или директория: '/mnt/sysimage/boot' 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-Desktop-x86_64-20-1 rootfstype=auto ro rd.live.image quiet rhgb rd.luks=0 rd.md=0 rd.dm=0 BOOT_IMAGE=vmlinuz0 executable: /sbin/anaconda hashmarkername: anaconda kernel: 3.11.10-301.fc20.x86_64 other involved packages: python-libs-2.7.5-9.fc20.x86_64 product: Fedora release: Fedora release 20 (Heisenbug) type: anaconda version: 20
Created attachment 922995 [details] File: anaconda-tb
Created attachment 922996 [details] File: anaconda.log
Created attachment 922997 [details] File: environ
Created attachment 922998 [details] File: journalctl
Created attachment 922999 [details] File: lsblk_output
Created attachment 923000 [details] File: nmcli_dev_list
Created attachment 923001 [details] File: os_info
Created attachment 923002 [details] File: program.log
Created attachment 923003 [details] File: storage.log
Created attachment 923004 [details] File: ifcfg.log
Created attachment 923005 [details] File: packaging.log
Well, it looks like /mnt/sysimage/boot vanished about 65% into the installation. I can't see any way for that to happen without something in the live desktop environment messing with the mounts. Does this happen again if you retry it?
Will try and send you the result
It does not happend. Reggards