Ask Your Question
0

grub Error:File not found after botched fedup upgrade followed by "successful" fedora-upgrade

asked 2013-07-09 19:43:56 -0500

perl-de42 gravatar image

It was two steps backward one step forward; repeat..

Backstory

System started at Fedora 16 upgraded to 17 and 18. I ran:

fedup --network 19

Eventually was prompted to reboot. Reboot and the system just sat in the same place for hours. Reboot again and skipped the "upgrade" option at grub prompt and got back into 18. Googled around and learned of "fedora-upgrade" Ran that and let it replace all files of conflict (Backing up one that had a minor change where the PDF printer queue placed it's files) Rebooted. System acted like it was going to upgrade but then rebooted itself. Tried prior 3.9.6-200.fc18.i686 kernel installed with fedora 18 same result. Selected prior kernel to that (3.8.1-201.fc18.i686) and was able to boot with the fedora 18 kernel Googled some more, realized I could "edit" my grub temporarily at boot prompt. Removed items in 3.9 kernels related to "upgrade". Successfully booted latest kernel. Tried uninstalling and reinstalling the 3.9.9-301.fc19.i686 kernel. I still had "upgrade" issue. Googled more. Tried

grub-mkconfig -o /boot/grub2/grub.cfg

Rebooted This is where I started to get the errors

Current state:

Error:File not found
Error:File not found
Error:File not found

Which drops me into "grub" menu Which then also gives me Error:File not found But eventually boots. I also tried:

grub2-install /dev/sda6

But got an error: /usr/sbin/grub2-bios-setup: warning: File system 'ext2' dosen't support embedding. /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.. /usr/sbin/grub2-bios-setup: error: will not proceed with blocklists.

Just want a normal boot. Also would like to switch to a graphical boot (with image) if possible but currently don't know what I need to do.

Thanks

edit retag flag offensive close merge delete

Comments

What to do imply with "the system sat for a few hours"? Was the Fedora bubble still blinking to show that an upgrade was in progress? Also, if you read the docs, the grub command is grub2-install /dev/sda, not grub2-install /dev/sdaX.

You seem to have tinkered quite a bit. From your description, it seems like you aborted fedup mid way, then chose the yum upgrade method, and then manually added/removed kernel packages?

FranciscoD_ gravatar imageFranciscoD_ ( 2013-07-09 22:59:32 -0500 )edit
1

Ok, I have addressed the issue with grub2-install /dev/sda. However not before totally killing grub and having to download a new installer disk from fedora. And the machine I created the installer was not working well so the boot disk only got me to dracut. However, a few mount commands and chroot got me to the point where I could run that command.

perl-de42 gravatar imageperl-de42 ( 2013-07-11 12:15:48 -0500 )edit

The fedup install sat for at least 4 hours and the progress indicator had not moved at all. So no blinking was occuring. In hindsight, I probably should have rebooted and had grub not use the graphical boot so I could get some error message from the process.

perl-de42 gravatar imageperl-de42 ( 2013-07-11 12:24:26 -0500 )edit

I only removed the kernel package in a vain attempt to get Fedora to correct the grub issue.

perl-de42 gravatar imageperl-de42 ( 2013-07-11 12:27:46 -0500 )edit

Please let me know if there is anything I can find out now to identify the root cause of the upgrade failure.

perl-de42 gravatar imageperl-de42 ( 2013-07-11 12:40:56 -0500 )edit

1 Answer

Sort by ยป oldest newest most voted
0

answered 2013-07-11 20:37:52 -0500

FranciscoD_ gravatar image

Fixed with grub2-install /dev/sda

edit flag offensive delete link more

Question Tools

1 follower

Stats

Asked: 2013-07-09 19:43:56 -0500

Seen: 1,236 times

Last updated: Jul 11 '13