LinuxQuestions.org
Welcome to the most active Linux Forum on the web.
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > SUSE / openSUSE
User Name
Password
SUSE / openSUSE This Forum is for the discussion of Suse Linux.

Notices


Reply
  Search this Thread
Old 01-16-2021, 02:28 PM   #16
cmt29
LQ Newbie
 
Registered: Dec 2020
Posts: 8

Original Poster
Rep: Reputation: Disabled

Thanks for further replies. I have given up trying to reinstall the bootloader, and having backed up my /home partition, I did a full reinstall.

But it's a shame I never really learned what happened or how to fix it.



Quote:
Originally Posted by mrmazda View Post
The correct filename is /boot/grub2/grub.cfg.
Yes, I had tried this earlier. But it hadn't worked. Clearly I was desperately trying anything to get it working!

Quote:
Originally Posted by mrmazda View Post
My question is what via ordinary updates caused the failing result observed. I'm not aware of anything special about a preempt kernel that could foul the boot process. It seems to me more likely the grub.cfg regeneration process during updates was corrupted or aborted.
Quote:
Originally Posted by colorpurple21859
What is this patch you are referring to, details please.
In answer to both of these, I'm probably using the word 'patch' incorrectly. It seems that a packaging error resulted in virtualbox requiring the kernel preempt (see https://bugzilla.opensuse.org/show_bug.cgi?id=1180625). It seems to have caused various hardware issues for some (see, e.g. https://forums.opensuse.org/showthre...ith-Virtualbox)

Following the update, my Grub menu was fine. It was during boot up that an error occured. I've not yet trawled through the logs to see what it was yet. Following that failed boot, it was then that I was landed at the Grub prompt. And from there all attempts at rescue failed.

Quote:
Originally Posted by mrmazda View Post
In attempting rescue, not executing mount -a after executing chroot /mnt, resulted in /dev/sdb1 not being mounted within the chroot environment.
Sorry if my reporting of my actions is inaccurate, but I certainly did mount -a every time after the chroot. But the error seemed to be more about not finding the vg, even though it was mounted.

Quote:
Originally Posted by mrmazda View Post
A clue to learning what went wrong might be possible by searching through /var/log/pbl*.
I looked back at that log. Here is the before/after section:
Code:
>>>>>>>>>>>>>>>>
2020-12-17 09:11:39 <1> update-bootloader-7148 new.126: update-bootloader-7148 = /sbin/update-bootloader, version = 0.931, root = /dev/dm-0
2020-12-17 09:11:39 <1> update-bootloader-7148 main.269: /sbin/update-bootloader --refresh
2020-12-17 09:11:39 <1> update-bootloader-7148 main.271: bootloader = grub2-efi
2020-12-17 09:11:39 <1> update-bootloader-7148 main.277: locale = 
2020-12-17 09:11:44 <1> update-bootloader-7148 run_command.294: '/usr/lib/bootloader/grub2-efi/config' = 0, output:
<<<<<<<<<<<<<<<<
+ /usr/sbin/grub2-mkconfig -o /boot/grub2/grub.cfg
Generating grub configuration file ...
Found theme: /boot/grub2/themes/openSUSE/theme.txt
Found linux image: /boot/vmlinuz-5.3.18-lp152.57-preempt
Found initrd image: /boot/initrd-5.3.18-lp152.57-preempt
Found linux image: /boot/vmlinuz-5.3.18-lp152.57-default
Found initrd image: /boot/initrd-5.3.18-lp152.57-default
Found linux image: /boot/vmlinuz-5.3.18-lp152.54-default
Found initrd image: /boot/initrd-5.3.18-lp152.54-default
Found linux image: /boot/vmlinuz-5.3.18-lp152.50-default
Found initrd image: /boot/initrd-5.3.18-lp152.50-default
done
>>>>>>>>>>>>>>>>
2020-12-17 10:14:20 <1> update-bootloader-9787 new.126: update-bootloader-9787 = /sbin/update-bootloader, version = 0.931, root = /dev/dm-0 (chroot)
2020-12-17 10:14:20 <1> update-bootloader-9787 main.269: /sbin/update-bootloader --refresh
2020-12-17 10:14:20 <1> update-bootloader-9787 main.271: bootloader = grub2-efi
2020-12-17 10:14:20 <1> update-bootloader-9787 main.277: locale = 
2020-12-17 10:14:25 <1> update-bootloader-9787 run_command.294: '/usr/lib/bootloader/grub2-efi/config' = 0, output:
<<<<<<<<<<<<<<<<
+ /usr/sbin/grub2-mkconfig -o /boot/grub2/grub.cfg
/usr/bin/grub2-editenv: error: unknown filesystem.
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-5.3.18-lp152.57-preempt
Found initrd image: /boot/initrd-5.3.18-lp152.57-preempt
/usr/sbin/grub2-probe: error: unknown filesystem.
Found linux image: /boot/vmlinuz-5.3.18-lp152.57-default
Found initrd image: /boot/initrd-5.3.18-lp152.57-default
Found linux image: /boot/vmlinuz-5.3.18-lp152.54-default
Found initrd image: /boot/initrd-5.3.18-lp152.54-default
Found linux image: /boot/vmlinuz-5.3.18-lp152.50-default
Found initrd image: /boot/initrd-5.3.18-lp152.50-default
/usr/bin/grub2-editenv: error: unknown filesystem.
done
>>>>>>>>>>>>>>>>
So, as I described above, the preempt kernel was installed fine in Grub, and it booted through the Grub menu. It was later on in the boot that it failed. The only things I can think of are, 1. I've toggled secure boot on and off a few times in the past. And 2. I had a custom v4l2loopback module that has to be manually built every time the kernel updates. But quite why that led to problems with my grub installation, I have no idea.

As I said above, I'm back up and running now, but can't really mark this thread as "solved". Perhaps I should mark it "closed"?
 
  


Reply



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
LXer: openSUSE Leap 15.0 Reached End of Life, Upgrade to openSUSE Leap 15.1 Now LXer Syndicated Linux News 0 12-01-2019 09:21 AM
LXer: openSUSE Leap 42.3 Linux OS Reached End of Life, Upgrade to openSUSE Leap 15.1 LXer Syndicated Linux News 0 06-30-2019 01:54 AM
LXer: openSUSE Leap 42.2 is out, how to upgrade safely from openSUSE Leap 42.1 LXer Syndicated Linux News 0 11-17-2016 07:18 AM
grub2 can't see my win 7 partition and yast2 bootloader can't reinstall grub2 jjrojaspy SUSE / openSUSE 5 07-07-2013 10:38 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > SUSE / openSUSE

All times are GMT -5. The time now is 04:36 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration