Kernel upgraded to 3.8.3 confused the bootloader [Solved]

Discussion in general that pertains to Sabayon Linux - Must Pertain to Sabayon Linux

Moderator: Moderators

Kernel upgraded to 3.8.3 confused the bootloader [Solved]

Postby msdobrescu » Fri Mar 29, 2013 22:49

Hello,

The issue described here hit me again.
Rigo updated the kernel from the weekly repo and at boot asks for the root ("could not find the root block device in .").
I have to give it /dev/sda3 again and again.
None of the things mentioned here works.
The kernel seems to be 3.8.3 branch 5, although several modules report 3.8.0 (nvidia and virtual box...)
Kernel switcher doesn't fix it either.
What happens?
How could it be fixed?
Last edited by msdobrescu on Wed Apr 17, 2013 19:08, edited 3 times in total.
msdobrescu
Technological Hen
 
Posts: 426
Joined: Sun Aug 21, 2011 8:48

Kernel mistakenly upgraded to 3.8.3 confused the bootloader

Postby msdobrescu » Sat Mar 30, 2013 8:07

I've switched on sabayonlinux.org repo, but no useful kernel found.
I would need to switch back to an earlier 3.8 version (it claims to be 3.8.3, I've had 3.8.2, if I remember well).
Would be useful to have all kernel versions deployed available to switch, not only the latest 3.8.x version, isn't it?
msdobrescu
Technological Hen
 
Posts: 426
Joined: Sun Aug 21, 2011 8:48

Re: Kernel mistakenly upgraded to 3.8.3 confused the bootloa

Postby msdobrescu » Sat Mar 30, 2013 9:44

Here is the kernel switching log:

Code: Select all
kernel-switcher switch linux-sabayon:3.8
>>  @@ Calculating dependencies...
>>  ## [R] [sabayonlinux.org] app-emulation/virtualbox-modules-4.2.8#3.8.0-sabayon|5   [4.2.8|5|3.8.0-sabayon]
>>  ## [R] [sabayonlinux.org] x11-drivers/nvidia-drivers-313.18#3.8.0-sabayon|4   [313.18|4|3.8.0-sabayon]
>>  ## [R] [sabayonlinux.org] sys-kernel/linux-sabayon-3.8.3|1   [3.8.3|1]
>>  @@ Packages needing to be installed/updated/downgraded: 3
>>  @@ Packages needing to be removed: 0
>>  @@ Download size: 0b
>>  @@ Freed disk space: 0.0b
>>  @@ You need at least: 106.7MB of free space
>>  ::: >>>  (1/1) 3 packages
>>    ## Package checksum matches: app-emulation:virtualbox-modules-4.2.8#3.8.0-sabayon~5.tbz2
>>    ## Package checksum matches: x11-drivers:nvidia-drivers-313.18#3.8.0-sabayon~4.tbz2
>>    ## Package checksum matches: sys-kernel:linux-sabayon-3.8.3~1.tbz2
>>  +++ >>>  (1/3) app-emulation/virtualbox-modules-4.2.8#3.8.0-sabayon
>>    ## Unpacking: app-emulation:virtualbox-modules-4.2.8#3.8.0-sabayon~5.tbz2
>>    ## Package phase: setup
>>    ## Package phase: preinstall
>>    ## Installing package: app-emulation/virtualbox-modules-4.2.8#3.8.0-sabayon
>>    ## [Kernel Modules for Virtualbox]
>>    ## Updating database: app-emulation/virtualbox-modules-4.2.8#3.8.0-sabayon
>>    ## Cleaning previously installed application data.
>>    ## Package phase: postremove
 * Removing app-emulation/virtualbox-modules-4.2.8 from moduledb.
>>    ## Package phase: postinstall
 * Updating module dependencies for 3.8.0-sabayon ...                                                                                                     [ ok ]
 * Adding module to moduledb.
 * Starting with the 3.x release new kernel modules were added,
 * be sure to load all the needed modules.
 *
 * Please add "vboxdrv", "vboxnetflt" and "vboxnetadp" to:
 * /etc/conf.d/modules
>>    ## Cleaning: app-emulation/virtualbox-modules-4.2.8#3.8.0-sabayon
>>  +++ >>>  (2/3) x11-drivers/nvidia-drivers-313.18#3.8.0-sabayon
>>    ## Unpacking: x11-drivers:nvidia-drivers-313.18#3.8.0-sabayon~4.tbz2
>>    ## Package phase: setup
>>    ## Package phase: preinstall
>>    ## Installing package: x11-drivers/nvidia-drivers-313.18#3.8.0-sabayon
>>    ## [NVIDIA GPUs kernel drivers]
>>    ## Updating database: x11-drivers/nvidia-drivers-313.18#3.8.0-sabayon
>>    ## Cleaning previously installed application data.
>>    ## Package phase: postremove
 * Removing x11-drivers/nvidia-drivers-313.18 from moduledb.
>>    ## Package phase: postinstall
 * Updating module dependencies for 3.8.0-sabayon ...                                                                                                     [ ok ]
 * Adding module to moduledb.

 * You must be in the video group to use the NVIDIA device
 * For more info, read the docs at
 * http://www.gentoo.org/doc/en/nvidia-guide.xml#doc_chap3_sect6
 *
 * This package installs a kernel module and X driver. Both must
 * match explicitly in their version. This means, if you restart
 * X, you must modprobe -r nvidia before starting it back up
 *
>>    ## Cleaning: x11-drivers/nvidia-drivers-313.18#3.8.0-sabayon
>>  +++ >>>  (3/3) sys-kernel/linux-sabayon-3.8.3
>>    ## Unpacking: sys-kernel:linux-sabayon-3.8.3~1.tbz2
>>    ## Package phase: setup
 * Preparing kernel and its modules
>>    ## Package phase: preinstall
 *
 * To avoid automounting and auto(un)installing with /boot,
 * just export the DONT_MOUNT_BOOT variable.
 *
 *
 * Assuming you do not have a separate /boot partition.
 *
>>    ## Installing package: sys-kernel/linux-sabayon-3.8.3
>>    ## [Official Sabayon Linux Standard kernel image]
>>    ## Updating database: sys-kernel/linux-sabayon-3.8.3
>>    ## Package phase: preremove
 *
 * To avoid automounting and auto(un)installing with /boot,
 * just export the DONT_MOUNT_BOOT variable.
 *
 *
 * Assuming you do not have a separate /boot partition.
 *
>>    ## Cleaning previously installed application data.
>>    ## Package phase: postremove
** Removing kernel '/boot/kernel-genkernel-x86_64-3.8.0-sabayon' and initramfs '/boot/initramfs-genkernel-x86_64-3.8.0-sabayon'
** Configuring GRUB bootloader. Removing the selected kernel ...
Generating grub.cfg ...
Found background: /boot/grub/default-splash.png
Found linux image: /boot/kernel-genkernel-x86_64-3.8.0-sabayon
Found initrd image: /boot/initramfs-genkernel-x86_64-3.8.0-sabayon
  No volume groups found
Found Windows 7 (loader) on /dev/sda1
done

 * You are currently booting with kernel:
 * kernel-genkernel-x86_64-3.8.0-sabayon
 *
 * Use 'eselect bzimage' in order to switch between the available ones

>>    ## Package phase: postinstall
 * Removing extents option for ext4 drives from /etc/fstab
 * Updating boot splash for /boot/initramfs-genkernel-x86_64-3.8.0-sabayon
** Adding kernel '/boot/kernel-genkernel-x86_64-3.8.0-sabayon' and initramfs '/boot/initramfs-genkernel-x86_64-3.8.0-sabayon'
** Configuring GRUB bootloader. Adding the new kernel ...
** Cannot find grub. Cannot properly configure kernel
Generating grub.cfg ...
Found background: /boot/grub/default-splash.png
Found linux image: /boot/kernel-genkernel-x86_64-3.8.0-sabayon
Found initrd image: /boot/initramfs-genkernel-x86_64-3.8.0-sabayon
  No volume groups found
Found Windows 7 (loader) on /dev/sda1
done

 * You are currently booting with kernel:
 * kernel-genkernel-x86_64-3.8.0-sabayon
 *
 * Use 'eselect bzimage' in order to switch between the available ones


 * If you are upgrading from a previous kernel, you may be interested
 * in the following document:
 *   - General upgrade guide: http://www.gentoo.org/doc/en/kernel-upgrade.xml

 * Updating module dependencies for 3.8.0-sabayon ...                                                                                                     [ ok ]
 * Please report kernel bugs at:
 * http://bugs.sabayon.org
 * The source code of this kernel is located at
 * =sys-kernel/sabayon-sources-3.8.3.
 * Sabayon Linux recommends that portage users install
 * sys-kernel/sabayon-sources-3.8.3 if you want
 * to build any packages that install kernel modules
 * (such as ati-drivers, nvidia-drivers, virtualbox, etc...).
>>    ## Cleaning: sys-kernel/linux-sabayon-3.8.3
>>  @@ Installation complete.
>>  @@ No configuration files to update.
Switching to nvidia OpenGL interface... done
>> sys-kernel/linux-sabayon-3.8.3 has been installed.
>> Attention: some external drivers cannot work across multiple kernels.
>> Please reboot your computer now !
msdobrescu
Technological Hen
 
Posts: 426
Joined: Sun Aug 21, 2011 8:48

Re: Kernel mistakenly upgraded to 3.8.3 confused the bootloa

Postby msdobrescu » Sat Mar 30, 2013 9:48

Could have the following error message the same source of the problem?

Cannot find grub. Cannot properly configure kernel

Code: Select all
>>    ## Package phase: postinstall
 * Removing extents option for ext4 drives from /etc/fstab
 * Updating boot splash for /boot/initramfs-genkernel-x86_64-3.8.0-sabayon
** Adding kernel '/boot/kernel-genkernel-x86_64-3.8.0-sabayon' and initramfs '/boot/initramfs-genkernel-x86_64-3.8.0-sabayon'
** Configuring GRUB bootloader. Adding the new kernel ...
** Cannot find grub. Cannot properly configure kernel
Generating grub.cfg ...
msdobrescu
Technological Hen
 
Posts: 426
Joined: Sun Aug 21, 2011 8:48

Re: Kernel mistakenly upgraded to 3.8.3 confused the bootloa

Postby linuxfluesterer » Sun Mar 31, 2013 10:27

It seems, only the last Kernel of a series (3.5, 3.6, 3.7, 3.8 ....) are offered (in Rigo).
But at http://www.kernel.org I saw, that Kernel 3.8.5 is already out (stable).
So, maybe there will be Kernel 3.8.4 offered in Rigo next week.
I'm waiting for it, because I still have some (little) problems with 3.8.3 now.

The only thing you may do instead is, that you can install Kernel 3.6 or Kernel 3.7 from Rigo (Linux Sabayon...).
After install an older one, you must start
Code: Select all
kernel-switcher
as root to select the one Kernel you want...
Anyway, when you install a new Kernel, the grub2-mkconfig command should be started.
If not, try to start manually as root:
Code: Select all
grub2-mkconfig -o /boot/grub/grub.cfg

Sorry, I don't have better news for you.

-Linuxfluesterer (I love KDE ...)
I really hope, that by the Brexit (poor Britain), TTIP will be finally prevented. But don't get tired to talk to your local politician to open eyes for danger to democracy because of TTIP
User avatar
linuxfluesterer
Old Dear Hen
 
Posts: 706
Joined: Thu Sep 20, 2012 19:47
Location: Germany

Re: Kernel mistakenly upgraded to 3.8.3 confused the bootloa

Postby msdobrescu » Sun Mar 31, 2013 10:57

I am pretty familiar with both, kernel-switcher and grub2-mkconfig, but they couldn't fix the issue.
It seems to be kernel related, from time to time.
What I can't do is getting the source of the problem.
At boot time, the log is rapidly flowing on the screen, but not saved anywhere, or I can't find it.
The cfg looks correct, so I think there is no grub issue.
Going back is not an option, as I've set everything to look in the new paths, i.e. /run/media/<user>/<disc label> since 3.8.
What else could I do?
msdobrescu
Technological Hen
 
Posts: 426
Joined: Sun Aug 21, 2011 8:48

Re: Kernel mistakenly upgraded to 3.8.3 confused the bootloa

Postby Stupot » Sun Mar 31, 2013 18:09

Are you dual booting with some other linux distro and perhaps using that distro's grub? Something has got to be different about your system since you've run into this issue twice and I haven't really seen any others running into this same issue.

If you can't do a
Code: Select all
kernel-switcher switch linux-sabayon:3.7
to get back to a bootable state, then the issue isn't with the way the 3.8 kernel is packed up, it's with how grub is working on your system.

Did you do an equo conf update after switching the kernel and perhaps overwrite some needed parameters?
Stupot
Sagely Hen
 
Posts: 1549
Joined: Wed Feb 14, 2007 3:44
Location: St. Louis, MO, USA

Re: Kernel mistakenly upgraded to 3.8.3 confused the bootloa

Postby msdobrescu » Sun Mar 31, 2013 18:18

I have no other linux installation, but it's a dual boot with Windows.
I could boot if I give the root as /dev/sda3 at boot time, when it requests it.
So it couldn't find it for a reason I don't know how to find.
I did equo conf update.
msdobrescu
Technological Hen
 
Posts: 426
Joined: Sun Aug 21, 2011 8:48

Re: Kernel mistakenly upgraded to 3.8.3 confused the bootloa

Postby Stupot » Sun Mar 31, 2013 21:56

I recall coming across an issue like this once upon a time when I had two separate HDDs.

For some reason, my motherboard would decide to change which HDD was sda and which was sdb, and doing so would have adverse effects on my grub.

Do you have a second harddrive installed? This may or may not be remotely related, just trying to get a feel for what's going on.

Grub should be attempting to use a UUID instead of /dev/sda# by default, which makes these issues more tricky to spot with a human eye.
Stupot
Sagely Hen
 
Posts: 1549
Joined: Wed Feb 14, 2007 3:44
Location: St. Louis, MO, USA

Re: Kernel mistakenly upgraded to 3.8.3 confused the bootloa

Postby msdobrescu » Mon Apr 01, 2013 6:33

Yes, I have many, but the root is the (hd0,msdos3) which corresponds to the /dev/sda3 I have to give to it when requested, if I understood the naming convention well.
msdobrescu
Technological Hen
 
Posts: 426
Joined: Sun Aug 21, 2011 8:48

Next

Return to Sabayon Linux General Discussion

Who is online

Users browsing this forum: No registered users and 1 guest