On a 64bit BIOS system I get "Cannot find a boot loader installed" messages since grub2-2.02-0.git10270.6.mga6 .... that doesn't make sense, because that version only cleaned the spec file..... or can grub2-2.02-0.git10270.5.mga6 have caused this? I did no kernel update between grub2-*.5.mga6 and grub2-*.6.mga6 I'll check a 32bit system later.
cannot reproduce on 32bit
Hardware: All => x86_64
CC: (none) => doktor5000
(In reply to Marja van Waes from comment #1) > cannot reproduce on 32bit But, after installing grub2 from updates_testing, I had immediately run "update-grub2" and "grub2-install", so I may well have seen this then, but only once if "grub2-install" fixed it. On the 64bit system that still has the issue, I had only run "update-grub2". Btw, Barry had seen the same error on 32bit, when testing a fix for the excess Fedora patches. Rindolf saw it on 64bit. I've now run grub2-install on the 64bit system where I kept getting those messages when installing new kernels. Waiting for next new kernel, now :-)
(In reply to Marja van Waes from comment #2) > > I've now run grub2-install on the 64bit system where I kept getting those > messages when installing new kernels. Waiting for next new kernel, now :-) Just installed kernel-desktop-4.6.0-0.rc7.2.mga6 There was indeed no more error about not found boot loader installed, and /boot/grub2/grub.cfg was updated. :-)
@ Barry Maybe this affects more cauldron users than I thought. Maybe grub2 doesn't run grub2-install when it's updated, if it thinks the package was installed without being used before, which it seems to think since the "all fedora patches" version we had?
Assignee: bugsquad => zen25000
seems to think, unless "grub2-install /dev/sda" was manually run
Yes there was something odd happened with the Fedora patches scenario, as I mentioned to you on IRC IIRC. When boot had failed due to that grub2 issue, the next grub2 update caused drakboot to issue the 'no bootloader found' message and grub2-install was not run and I had to manually run it. After that all was well until I tested another broken grub2 version and the same happened again. (This was on an old pIII i586 alongside Win98 and XP) I did this many times and it was quite reproducible. It was as though the grub2 modules were inaccessible or maybe core.img was corrupted. I was not too concerned about that - more about fixing the main issue. So since this only affects Cauldron it's quite correct to recommend running grub2-install with appropriate arguments (when needed) followed by update-grub2 as a workaround.
Can this be closed now?
(In reply to Barry Jackson from comment #7) > Can this be closed now? Yes, new pre-6sta1 QA isos ware released three days ago, with a better grub2 on them, so I doubt anyone will still get bitten by this issue
Status: NEW => RESOLVEDResolution: (none) => FIXED