After upgrade from 12.3 to 13.1, cannot boot new kernel

English Install/Boot/Login
#1

Greetings,

his is another upgrade failure. I’ve read thru this forum and found a few similar posts, but haven’t found what I consider a match.

After upgrading from 12.3 to 13.1, my system just hangs in the splash screen when I try to boot the new kernel, openSUSE - 3.11.6-4. The old “openSUSE 12.3” kernel boots ok, and it looks mostly like my 12.3 system does, though of course this is actually 13.1 with the 12.3 kernel:
->cat /etc/os-release


NAME=openSUSE
VERSION="13.1 (Bottle)"
VERSION_ID="13.1"
PRETTY_NAME="openSUSE 13.1 (Bottle) (x86_64)"
ID=opensuse
ANSI_COLOR="0;32"
CPE_NAME="cpe:/o:opensuse:opensuse:13.1"
BUG_REPORT_URL="https://bugs.opensuse.org"
HOME_URL="https://opensuse.org/"
ID_LIKE="suse"

I did the upgrade by following the instructions in SDB:System upgrade (I updated the repos and ran “zypper dup” and “zypper ref” commands), and there were no errors in the upgrade
/var/log/zypper.log:

2013-12-15 22:04:44 <1> vicksburg.site(4554) [zypp] TargetImpl.cc(commit):1370 TargetImpl::commit(<pool>, CommitPolicy( DownloadInHeaps )) returns: CommitResult  (total 5523, done 5523, error 0, skipped 0, updateMessages 1)

I must be not be using grub2, because the grub-menu I see is in /boot/grub/menu.lst -
→ sudo cat /boot/grub/menu.lst

# Modified by YaST2. Last modification on Sun Dec 15 21:09:44 MST 2013
# THIS FILE WILL BE PARTIALLY OVERWRITTEN by perl-Bootloader
# For the new kernel it try to figure out old parameters. In case we are not able to recognize it (e.g. change of flavor or strange install order ) it it use as fallback installation parameters from /etc/sysconfig/bootloader

default 0
timeout 8
gfxmenu (hd0,0)/message
##YaST - activate

###Don't change this comment - YaST2 identifier: Original name: linux###
title Desktop -- openSUSE - 3.11.6-4
    root (hd0,0)
    kernel /vmlinuz-3.11.6-4-desktop root=/dev/vg1/rootlv resume=/dev/disk/by-id/ata-ST31000528AS_5VP0MEAM-part2 splash=silent quiet showopts vga=0x375
    initrd /initrd-3.11.6-4-desktop

###Don't change this comment - YaST2 identifier: Original name: failsafe###
title Failsafe -- openSUSE - 3.11.6-4
    root (hd0,0)
    kernel /vmlinuz-3.11.6-4-desktop root=/dev/vg1/rootlv showopts apm=off noresume edd=off powersaved=off nohz=off highres=off processor.max_cstate=1 x11failsafe vga=0x375
    initrd /initrd-3.11.6-4-desktop


###Don't change this comment - YaST2 identifier: Original name: xen###
title Xen -- openSUSE - 3.11.6-4
    root (hd0,0)
    kernel /xen.gz vgamode=0x375
    module /vmlinuz-3.11.6-4-xen root=/dev/vg1/rootlv
    module /initrd-3.11.6-4-xen


###Don't change this comment - YaST2 identifier: Original name: linux###
title Desktop -- openSUSE 12.3 - 3.7.10-1.16
    root (hd0,0)
    kernel /vmlinuz-3.7.10-1.16-desktop root=/dev/vg1/rootlv resume=/dev/disk/by-id/ata-ST31000528AS_5VP0MEAM-part2 splash=silent quiet showopts vga=0x375
    initrd /initrd-3.7.10-1.16-desktop


###Don't change this comment - YaST2 identifier: Original name: failsafe###
title Failsafe -- openSUSE 12.3 - 3.7.10-1.16
    root (hd0,0)
    kernel /vmlinuz-3.7.10-1.16-desktop root=/dev/vg1/rootlv showopts apm=off noresume edd=off powersaved=off nohz=off highres=off processor.max_cstate=1 x11failsafe vga=0x375
    initrd /initrd-3.7.10-1.16-desktop


###Don't change this comment - YaST2 identifier: Original name: xen###
title Xen -- openSUSE 12.3 - 3.7.10-1.16
    root (hd0,0)
    kernel /xen.gz vgamode=0x375
    module /vmlinuz-3.7.10-1.16-xen root=/dev/vg1/rootlv
    module /initrd-3.7.10-1.16-xen


###Don't change this comment - YaST2 identifier: Original name: linux###
title GNU GRUB 2 -- openSUSE 12.2 - GNU GRUB 2
    kernel (hd0,0)/grub2/core.img root=/dev/vg1/rootlv resume=/dev/disk/by-id/ata-ST31000528AS_5VP0MEAM-part2 splash=silent quiet showopts vga=0x375

So I tried booting into the new kernel in SAFE mode, and what I get is these messages scrolling by repeatedly in a console:

PARTIAL MODE. Incomplete logical volumes will be processed.
Volume group “vg1” not found
No volume groups found

When they finally stopped, the console says:

Could not find /dev/vg1/rootlv.
Want me to fall back to /dev/vg1/rootlv? (Y/n)

I typed the Y key, but it was ignored, and the system seems dead.

So obviously the kernel is not able to read my LVM disk. Is this related to the LVM issue that I saw referenced? I’m not using raid, but I do have LVM. I also don’t think disk utilization is an issue. I have a 500MB /boot partition (sda1), swap (sda2), an unused ext3(sda3), and LVM on the rest (sda4ext, sda5) of my 1000GB drive. I mount / (root), /home, and /mydata on separate logical volumes:

sudo /usr/sbin/fdisk -l

Disk /dev/sda: 1000.2 GB, 1000204886016 bytes, 1953525168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk label type: dos
Disk identifier: 0xc0000000

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *          63     1028159      514048+  83  Linux
/dev/sda2         1028160    13607054     6289447+  82  Linux swap / Solaris
/dev/sda3        13608960   432211967   209301504   83  Linux
/dev/sda4       432212761  1953520064   760653652    f  W95 Ext'd (LBA)
/dev/sda5       432212823  1953520064   760653621   8e  Linux LVM

Disk /dev/mapper/vg1-datalv: 268.4 GB, 268435456000 bytes, 524288000 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/mapper/vg1-homelv: 107.4 GB, 107374182400 bytes, 209715200 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/mapper/vg1-rootlv: 53.7 GB, 53687091200 bytes, 104857600 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

df:

Filesystem             1K-blocks      Used Available Use% Mounted on
/dev/mapper/vg1-rootlv  51606140  18834588  30150112  39% /
devtmpfs                 4079164        16   4079148   1% /dev
tmpfs                    4092592         4   4092588   1% /dev/shm
tmpfs                    4092592      2360   4090232   1% /run
tmpfs                    4092592         0   4092592   0% /sys/fs/cgroup
tmpfs                    4092592      2360   4090232   1% /var/lock
tmpfs                    4092592      2360   4090232   1% /var/run
/dev/mapper/vg1-datalv 258030980 205313724  39611976  84% /mydata
/dev/mapper/vg1-homelv 103212320  57741712  40227728  59% /home
/dev/sda1                 498018    278262    194054  59% /boot

What do I do now?

It might help to know that I’ve only upgraded, not installed, since about 11.4 timeframe- thru all 12.x versions. That’s probably why I’m still in grub “one”.

#2

You really should not have the old kernel. I’m guessing you missed changing one or more repos to the new repos so you have a mixed install

let’s look at zypper lr as a starting place

#3

I agree and was surprised to see the old menu.lst entries, but I recall seeing a thread in this forum that grub keeps the last kernel… At any rate I’m glad it did or I’d have a completely borked system.

Here’s my zypper lr, and I see that I do have a duplicate entry (14 and 17) but otherwise is correct. Can I remove it and recover from it?
Most of the other entries (other than suse 12.3) have been disabled for quite a while, i only keep them there for reference. I try to keep my system stock openSuse, and am not running any packman or reddwarf packages at this time.

#  | Alias                      | Name                               | Enabled | Refresh | URI                                                                        
---+----------------------------+------------------------------------+---------+---------+----------------------------------------------------------------------------
 1 | Mozilla_for_OpenSUSE       | Mozilla for OpenSUSE               | No      | No      | http://download.opensuse.org/repositories/mozilla/openSUSE_12.3/           
 2 | Videolan                   | Videolan (only used for libdvdcss) | No      | No      | http://download.videolan.org/pub/vlc/SuSE/12.3/                            
 3 | X11-Xorg                   | X11-Xorg                           | No      | No      | http://download.opensuse.org/repositories/X11:/XOrg/openSUSE_12.1/         
 4 | google-earth               | google-earth                       | No      | No      | http://dl.google.com/linux/earth/rpm/stable/x86_64                         
 5 | my_IBM-related_downloads   | my IBM-related downloads           | No      | No      | dir:///home/rcbell/downloads/IBMstuff                                      
 6 | my_downloads               | my downloads                       | No      | No      | dir:///home/rcbell/downloads                                               
 7 | packman                    | packman openSUSE-12.3              | No      | No      | http://packman.jacobs-university.de/suse/12.3/                             
 8 | reddwarf                   | Red Dwarf                          | No      | No      | http://download.opensuse.org/repositories/home:/RedDwarf/openSUSE_11.3/    
 9 | repo-12.3-non-oss          | openSUSE-12.3-Non-Oss              | No      | No      | http://download.opensuse.org/distribution/12.3/repo/non-oss/               
10 | repo-12.3-non-oss-update   | openSUSE-12.3-Update-Non-Oss       | No      | No      | http://download.opensuse.org/update/12.3-non-oss/                          
11 | repo-12.3-oss              | openSUSE-12.3-OSS                  | No      | No      | http://download.opensuse.org/distribution/12.3/repo/oss/                   
12 | repo-12.3-update           | openSUSE-12.3 Update-Oss           | No      | No      | http://download.opensuse.org/update/12.3/                                  
13 | repo-13.1-non-oss          | openSUSE-13.1-Non-Oss              | Yes     | Yes     | http://download.opensuse.org/distribution/13.1/repo/non-oss/               
14 | repo-13.1-non-oss-update   | openSUSE-13.1-Update-Non-Oss       | Yes     | Yes     | http://download.opensuse.org/update/13.1-non-oss/                          
15 | repo-13.1-oss              | openSUSE-13.1-Oss                  | Yes     | Yes     | http://download.opensuse.org/distribution/13.1/repo/oss/                   
16 | repo-13.1-oss-update       | openSUSE-13.1-Update-Oss           | Yes     | Yes     | http://download.opensuse.org/update/13.1/                                  
17 | repo-update-non-oss        | openSUSE-13.1-Update-Non-Oss       | Yes     | Yes     | http://download.opensuse.org/update/13.1-non-oss/                          
18 | sametime-connect_oc-respin | sametime-connect oc-respin         | No      | No      | http://pokgsa.ibm.com/projects/o/openclient/lotus/sametime/oc-respin/8.5.2/
#4

I found the post about grub keeping multiple kernels, here

wolfi323 says,

Then the kernel. Since a while now, multiversion is enabled by default for kernel packages. It is configured to keep at least 2 kernels. Since you upgraded from 12.3 and there’s only 1 kernel yet for 13.1 (there has been no kernel update yet), and the latest 12.3 kernel is still installed therefore.
You should have an entry with kernel 3.11.6 as well in the menu, just boot that. (maybe have a look in “Advanced Options”)
If you want to, you can of course uninstall the old kernel in YaST->Software Management f.e. Just select the kernel package and click on “Versions” in the bottom-right area to uninstall just the old version.

but am I misunderstanding this?

#5

gogalthorp wrote:

>
> You really should not have the old kernel. I’m guessing you missed
> changing one or more repos to the new repos so you have a mixed install
>
> let’s look at zypper lr as a starting place
>

To add a point to consider: on one update 12.3 -> 13.1 I had the 12.3 kernel
still hanging around causing several problems, mainly with bootup and boot
loader changes/re-install. This was on a UEFI disk and the cure was to
finally boot to a command prompt and use YAST to remove the old kernel.
I’ve only run into this on one installation but it IS a possible outcome.

–
Will Honea

#6

Okay, but I don’t think that having the old kernel in /boot is the problem, though. I think they are tolerated being there. I’ve have an old 2.6 kernel hanging around. Also, this is not a UEFI system.
Here is the contents of /boot:

drwx------  2 root root    12288 Nov 29  2009 lost+found
-rw-------  1 root root      512 Nov 29  2009 backup_mbr
-rw-r--r--  1 root root  4552032 Feb 19  2011 vmlinuz-2.6.37-20-desktop
-rw-r--r--  1 root root  5290399 Feb 19  2011 vmlinux-2.6.37-20-desktop.gz
-rw-r--r--  1 root root  2244915 Feb 19  2011 System.map-2.6.37-20-desktop
-rw-r--r--  1 root root   196405 Feb 19  2011 symvers-2.6.37-20-desktop.gz
-rw-r--r--  1 root root 11704648 Feb 19  2011 initrd-2.6.37-20-desktop
-rw-r--r--  1 root root   120310 Feb 19  2011 config-2.6.37-20-desktop
-rw-r--r--  1 root root 11980780 Feb 20  2011 xen-syms-dbg-4.0.2_01-2.1
-rw-r--r--  1 root root 12996274 Feb 20  2011 xen-syms-4.0.2_01-2.1
-rw-r--r--  1 root root   692183 Feb 20  2011 xen-dbg-4.0.2_01-2.1.gz
-rw-r--r--  1 root root   692734 Feb 20  2011 xen-4.0.2_01-2.1.gz
-rw-r--r--  1 root root  3930689 Feb 20  2011 vmlinuz-2.6.37-20-xen
-rw-r--r--  1 root root  4617844 Feb 20  2011 vmlinux-2.6.37-20-xen.gz
-rw-r--r--  1 root root  1998616 Feb 20  2011 System.map-2.6.37-20-xen
-rw-r--r--  1 root root   193334 Feb 20  2011 symvers-2.6.37-20-xen.gz
-rw-r--r--  1 root root 12390635 Feb 20  2011 initrd-2.6.37-20-xen
-rw-r--r--  1 root root   117036 Feb 20  2011 config-2.6.37-20-xen
-rw-r--r--  1 root root     2475 Feb 13  2013 _MY_PARTITION_TABLE
-rw-r--r--  1 root root   136018 Jun  7  2013 config-3.7.10-1.16-desktop
-rw-r--r--  1 root root   131621 Jun  7  2013 config-3.7.10-1.16-xen
-rw-r--r--  1 root root  2257332 Jun  7  2013 System.map-3.7.10-1.16-xen
-rw-r--r--  1 root root  5119414 Jun  7  2013 vmlinux-3.7.10-1.16-xen.gz
-rw-r--r--  1 root root      409 Jun  7  2013 sysctl.conf-3.7.10-1.16-xen
-rw-r--r--  1 root root   236382 Jun  7  2013 symvers-3.7.10-1.16-xen.gz
-rw-r--r--  1 root root   690766 Jun  7  2013 symtypes-3.7.10-1.16-default.gz
-rw-r--r--  1 root root   670794 Jun  7  2013 symtypes-3.7.10-1.16-xen.gz
-rw-r--r--  1 root root  2531845 Jun  7  2013 System.map-3.7.10-1.16-desktop
-rw-r--r--  1 root root  5813683 Jun  7  2013 vmlinux-3.7.10-1.16-desktop.gz
-rw-r--r--  1 root root      516 Jun  7  2013 sysctl.conf-3.7.10-1.16-desktop
-rw-r--r--  1 root root   241451 Jun  7  2013 symvers-3.7.10-1.16-desktop.gz
-rw-r--r--  1 root root   691699 Jun  7  2013 symtypes-3.7.10-1.16-desktop.gz
-rw-r--r--  1 root root  4351464 Jun  7  2013 vmlinuz-3.7.10-1.16-xen
-rw-r--r--  1 root root  4998200 Jun  7  2013 vmlinuz-3.7.10-1.16-desktop
-rw-r--r--  1 root root   691535 Jun  7  2013 symtypes-3.7.10-1.16-debug.gz
lrwxrwxrwx  1 root root        5 Jul  4 16:04 grub2-efi.rpmsave -> grub2
-rw-r--r--  1 root root     1484 Oct 17 23:48 boot.readme
-rw-r--r--  1 root root   135010 Nov  1 04:14 config-3.11.6-4-xen
-rw-r--r--  1 root root   140360 Nov  1 04:17 config-3.11.6-4-desktop
-rw-r--r--  1 root root  2403700 Nov  1 04:53 System.map-3.11.6-4-xen
-rw-r--r--  1 root root  5361171 Nov  1 05:02 vmlinux-3.11.6-4-xen.gz
-rw-r--r--  1 root root      409 Nov  1 05:02 sysctl.conf-3.11.6-4-xen
-rw-r--r--  1 root root   253952 Nov  1 05:02 symvers-3.11.6-4-xen.gz
-rw-r--r--  1 root root   721880 Nov  1 05:08 symtypes-3.11.6-4-xen.gz
-rw-r--r--  1 root root   745233 Nov  1 05:26 symtypes-3.11.6-4-default.gz
-rw-r--r--  1 root root  2697475 Nov  1 05:58 System.map-3.11.6-4-desktop
-rw-r--r--  1 root root   746083 Nov  1 06:01 symtypes-3.11.6-4-debug.gz
-rw-r--r--  1 root root  6075542 Nov  1 06:22 vmlinux-3.11.6-4-desktop.gz
-rw-r--r--  1 root root      516 Nov  1 06:23 sysctl.conf-3.11.6-4-desktop
-rw-r--r--  1 root root   261933 Nov  1 06:23 symvers-3.11.6-4-desktop.gz
-rw-r--r--  1 root root  4546072 Nov  1 06:27 vmlinuz-3.11.6-4-xen
-rw-r--r--  1 root root   746472 Nov  1 06:34 symtypes-3.11.6-4-desktop.gz
-rw-r--r--  1 root root  5210216 Nov  1 11:33 vmlinuz-3.11.6-4-desktop
-rw-r--r--  1 root root 14685732 Dec  4 08:16 xen-syms-dbg-4.3.1_02-4.4
-rw-r--r--  1 root root   838107 Dec  4 08:16 xen-dbg-4.3.1_02-4.4.gz
-rw-r--r--  1 root root 15087684 Dec  4 08:19 xen-syms-4.3.1_02-4.4
-rw-r--r--  1 root root   830807 Dec  4 08:19 xen-4.3.1_02-4.4.gz
lrwxrwxrwx  1 root root       20 Dec 15 21:09 vmlinuz-xen -> vmlinuz-3.11.6-4-xen
lrwxrwxrwx  1 root root       19 Dec 15 21:09 initrd-xen -> initrd-3.11.6-4-xen
lrwxrwxrwx  1 root root       24 Dec 15 21:09 vmlinuz -> vmlinuz-3.11.6-4-desktop
drwxr-xr-x  2 root root     1024 Dec 15 21:18 grub
lrwxrwxrwx  1 root root        1 Dec 15 21:18 boot -> .
-rw-r--r--  1 root root   620544 Dec 15 21:31 message
drwxr-xr-x  7 root root     1024 Dec 15 21:48 grub2
drwxr-xr-x 27 root root     4096 Dec 16 06:34 ..
lrwxrwxrwx  1 root root       21 Dec 16 13:06 xen-syms -> xen-syms-4.3.1_02-4.4
lrwxrwxrwx  1 root root       23 Dec 16 13:06 xen-dbg.gz -> xen-dbg-4.3.1_02-4.4.gz
lrwxrwxrwx  1 root root       23 Dec 16 13:06 xen-dbg-4.gz -> xen-dbg-4.3.1_02-4.4.gz
lrwxrwxrwx  1 root root       23 Dec 16 13:06 xen-dbg-4.3.gz -> xen-dbg-4.3.1_02-4.4.gz
lrwxrwxrwx  1 root root       19 Dec 16 13:06 xen-4.gz -> xen-4.3.1_02-4.4.gz
lrwxrwxrwx  1 root root       19 Dec 16 13:06 xen-4.3.gz -> xen-4.3.1_02-4.4.gz
lrwxrwxrwx  1 root root       25 Dec 16 13:07 xen-syms-dbg -> xen-syms-dbg-4.3.1_02-4.4
lrwxrwxrwx  1 root root       19 Dec 16 13:07 xen.gz -> xen-4.3.1_02-4.4.gz
-rw-------  1 root root 27262696 Dec 16 13:08 initrd-3.11.6-4-desktop
lrwxrwxrwx  1 root root       23 Dec 16 13:08 initrd -> initrd-3.11.6-4-desktop
drwxr-xr-x  5 root root     5120 Dec 16 13:08 .
-rw-------  1 root root 27588282 Dec 16 13:08 initrd-3.11.6-4-xen
-rw-------  1 root root 25999976 Dec 16 13:08 initrd-3.7.10-1.16-desktop
-rw-------  1 root root 26379838 Dec 16 13:08 initrd-3.7.10-1.16-xen
#7

rcbell wrote:

> Okay, but I don’t think that having the old kernel in /boot is the
> problem, though.

Agreed. After thinking about it, ISTR that the busted installation actually
was the result of the grub install step after the update. That left some
entries refering to the 3.7.10 (12.3) kernel when the 3.11.xxx entries were
not written to the active grub2 menu. 13.1 has been a challenge from the
git-go here - I need to keep a written log for this one!

–
Will Honea

#8

I just booted the 13.1 KDE Live, and I was able to mount all of the LVM logical volumes on my hard drive from Dolphin- they each appear in “places”, and clicking on them brings up the files without a problem. Does that provide any hints that this is or could not be an LVM problem? Is anyone interested in debugging this?

If not, what should I do next? Does the install DVD have some kind of “repair install” that I could try?

And if not that, what about doing a new install into my root logical volume- since my home LV and data LV are separate, would a new install leave those two LVs alone?

Thanks,
Craig