Hello, One detail is missing, see below On Saturday, May 4, 2019 10:54:49 AM EDT Steve Grubb wrote: > On Saturday, May 4, 2019 10:29:18 AM EDT Tom Hughes wrote: > > > On 04/05/2019 15:24, Steve Grubb wrote: > > > > > I upgraded from a fully updated F29 to F30 today. Upon reboot I see > > > > > > grub> > > > > > > This seems like a pretty major bug in some component somewhere. I > > > don't > > > think this is a recoverable bug for most people, meaning they would > > > have > > > to reinstall and possibly lose everything. > > > > > > What component is at fault? I'd like to report this bug and have it > > > fixed > > > asap before other people experience a non-working system after > > > upgrade. > > > No idea how to recover the system at this point. It does have valuable > > > work related code and docs on it. > > > > > > https://fedoraproject.org/wiki/Common_F30_bugs#blscfg-fail > > > Thanks. It's nice that there is a writeup. But are non-technical people > expected to do this fix? (This is a rhetorical question to all of fedora- > devel.) Could dnf system-upgrade detect that it's running on a system that > will fail? Could it warn people beforehand or even apply the grub > upgrade first? > > I have to think the issue could be detected before upgrading. > > d=`mount | awk '$3 == "\/boot" { print $1 }' 2>/dev/null` > if [ "x$d" == "x" ] ; then > d=`mount | awk '$3 == "\/" { print $1 }' 2>/dev/null` > if [ "x$d" == "x" ] ; then > echo "Upgrading your grub2 install to a current version > cannot be done. You should not proceed with upgrading your system." > exit 1 > fi > grub2-install $s > if [ $? -ne 0 ] ; then > echo "grub2-install encountered an error. You should not > proceed with upgrading your system." > exit 1 > fi > fi > > ... > > Anyways...following the instruction on that page...when > configfile /grub2/grub.cfg.rpmsave > is run, it immediately shows me the menu and boot commences as it did. It > then says: "execute the grub2-install /dev/X command (where X is the boot > device, i.e sda) to update the GRUB core and the module" > > This is what happens: > > # mount | grep boot > /dev/sda1 on /boot type ext4 (rw,relatime,seclabel) > [root ~]# grub2-install /dev/sda1 > Installing for i386-pc platform. > grub2-install: warning: File system `ext2' doesn't support embedding. > grub2-install: 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.. > grub2-install: error: will not proceed with blocklists. > and rebooting the system now has: error: symbol 'grub_file_progress_hook' not found. Entering rescue mode... grub rescue> Which seems like a big step back from where I was. -Steve _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
