Version-Release number of selected component: anaconda-18.19 Additional info: libreport version: 2.0.14 cmdline: /usr/bin/python /sbin/anaconda kernel: 3.6.1-1.fc18.x86_64 description: :The following was filed automatically by anaconda: :anaconda 18.19 exception report :Traceback (most recent call first): : File "/usr/lib64/python2.7/site-packages/pyanaconda/bootloader.py", line 1531, in install : raise BootLoaderError("bootloader install failed") : File "/usr/lib64/python2.7/site-packages/pyanaconda/bootloader.py", line 1542, in write : self.install() : File "/usr/lib64/python2.7/site-packages/pyanaconda/bootloader.py", line 2213, in writeBootLoader : storage.bootloader.write() : File "/usr/lib64/python2.7/site-packages/pyanaconda/install.py", line 128, in doInstall : writeBootLoader(storage, payload, instClass) : File "/usr/lib64/python2.7/threading.py", line 504, in run : self.__target(*self.__args, **self.__kwargs) : File "/usr/lib64/python2.7/site-packages/pyanaconda/threads.py", line 91, in run : threading.Thread.run(self, *args, **kwargs) :BootLoaderError: bootloader install failed
Created attachment 631515 [details] File: ifcfg.log
Created attachment 631516 [details] File: anaconda-tb
Created attachment 631517 [details] File: product
Created attachment 631518 [details] File: type
Created attachment 631519 [details] File: environ
Created attachment 631520 [details] File: storage.log
Created attachment 631521 [details] File: version
Created attachment 631522 [details] File: program.log
Created attachment 631523 [details] File: anaconda.log
Created attachment 631524 [details] File: syslog
Created attachment 631525 [details] File: hashmarkername
Created attachment 631526 [details] File: packaging.log
Created attachment 631527 [details] File: cmdline_file
Created attachment 631528 [details] File: release
15:11:47,731 ERR program: /usr/sbin/grub2-bios-setup: warning: this GPT partition label contains no BIOS Boot Partition; embedding won't be possible. 15:11:47,737 ERR program: /usr/sbin/grub2-bios-setup: warning: Embedding is not possible. GRUB can only be installed in this setup by using blocklists. However, blocklists are UNRELIABLE and their use is discouraged.. 15:11:47,738 ERR program: /usr/sbin/grub2-bios-setup: error: will not proceed with blocklists.
The reason for this might be the size of '/'. It was bigger than 2T. See #868899 for a way to reproduce (comment 2 point 3).
I wiped the partitions from a BIOS RAID1 array and started an i386 install using autopart and installing GNOME. I got this traceback when "installing bootloader." was on the installation progress screen Package: anaconda-18.19 Architecture: i686 OS Release: Fedora release 18-Beta-TC6
since started installing without swap nor a /boot, the installation obviously failed. Addtionally i managed to install with a / and a 'ghost /'. It is possible to 'ghost' a partition, which means that two mount points share a partition. (at least the for the UI they are two entries) Package: anaconda-18.19 OS Release: Fedora release 18-Beta-TC6
Thomas, please describe exactly how you hit this error. Tim, can you attach the anaconda-tb-* log? Reartes, please open new bugs for different issues.
> Reartes, please open new bugs for different issues. I had no choice, i used ABRT. (and i was unaware of this bug-report). As for the 'ghost' entries i will surely open another bug-report later.
I think I know what's going on here. We're allowing users to proceed with install even though there were errors when checking the storage configuration after leaving custom storage. I have a patch ready to test.
anaconda-18.28-1.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/FEDORA-2012-17823/anaconda-18.28-1.fc18
Package anaconda-18.28-1.fc18: * should fix your issue, * was pushed to the Fedora 18 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing anaconda-18.28-1.fc18' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-17823/anaconda-18.28-1.fc18 then log in and leave karma (feedback).
Installing the liveCD Package: anaconda-18.29-1.fc18.x86_64 OS Release: Fedora release 18
Looks like the .28 version didn't fix it, reopening.
Installing F18 beta from DVD on a system with with 3 drives, with this layout: /boot and swap on a 60GB SSD, / on a 305GB SATA disk, and /home on a 610GB SATA disk. It sat in the installing phase for 30+ minutes, then got this error. CPU is a 3 core AMD Phenom. Package: anaconda-18.29.2 OS Release: Fedora release 18-Beta
Please retest with smoke4 from here - https://dl.fedoraproject.org/pub/alt/qa/20121205_f18-smoke4/
I believe the bug happens due to my partition scheme. I just need to install a fresh F18 Beta to reproduce it. Package: anaconda-18.29.2 OS Release: Fedora release 18-Beta
I tried smoke4, but it didn't start X correctly. It starts the graphical interface but remains with the busy mouse pointer forever. I just tried smoke5, but after had selected the '/' (53GB), '/boot' (2GB) and swap (17GB) in the custom partitioning, it still complains about 'Error checking storage configuration' after had clicked at 'Finish Partitioning' button. Any ideas?
Ok, managed to install smoke5 on the same system and the grub is installed. However, in the next boot it shows: -----8<---- GRUB loading.. Welcome to GRUB! error: file '/grub2/i386-pc/normal.mod' not found. Entering rescue mode... grub rescue> _ -----8<---- the directory grub2/ has themes/ only and nothing else. So basically there is no more that backtrace, but it still doesn't succeed. Running: # grub2-install --target=i386-pc --recheck --debug /dev/sda puts all files there, but fails saying: warning: disk isn't LDM. warning: Embedding is not possible. GRUB can only be installed in this setup by using blocklists. However, blocklists are UNRELIABLE and their use is discouraged. Error: will not proceed with blocklists. The above restores the grub in MBR. But still fails due to the lack of grub.cfg. The following fixed it: # grub-mkconfig -o /boot/grub/grub.cfg Let me know if you need additional information.
Ok, I think the bug I am seeing now is actually this one: bz#831493 - Installing FC17 to system with Windows 7 with mirrored dynamic disks renders system unbootable. As the original backtrace doesn't show up with smoke5, I think we can close this one.
It happened at 'Installing bootloader' step. Package: anaconda-18.29.2-1.fc18.x86_64 OS Release: Fedora release 18
Thomas, can you re-test with smoke7?
anaconda does not allow to proceed with installation with root > 2T and no extra /boot now. Therefore I can not test this.
As a sidenote, the system on which I was doing the installation had an 250GB HDD on /dev/sdb, not > 2T.
Ozan, Can you give it a try with smoke8? The version you are using (from the Beta) is quite old. https://dl.fedoraproject.org/pub/alt/qa/20121218_f18-smoke8/
Normal Anaconda install, with a single file system, Traditional Partition (not LVM). Everything proceeds through software installation and post-installation procedures normally until Bootloader installation, then anaconda crashes. This is a somewhat unusual system with a large number of partitions. MS-DOS disk label, three primary partitions, one Extended partition, eleven Logical Partitions within the Extended. jw Package: anaconda-18.37.3-1.fc18.x86_64 OS Release: Fedora release 18
Regarding my system which contributed to this problem, I have just come across a potentially significant additional information. I have been working around this problem on one system ever since this report was filed. I recently found that although openSuSE 12.3 would install on the same system, it was not possible to boot Windows from that installation. On investigating I found that the grub2 config file was very confused about the partition type - it was trying to treat the Windows 7 partition as an LVM partition. When I manually edited the grub config file, and changed it to an msdos partition, the Windows boot succeeded. Based on this I suspect that anaconda might have been getting confused by an invalid or corrupt disk label or partition label, and this was causing it to crash. Although this is apparently a problem with this specific computer, or its disk drive, I still don't think this kind of problem should cause anaconda to crash... Thanks, jw
I'm going to close this one since it seems to be either fixed, or a different bug. If you see problems with f19 please open a new bug with logs.