Failes to boot up after upgrade

Dear all,
unti last night I was using opensuse 12.1 .

at grub I receive the following messages (as system is down and could not copy paste please find screnhots)before booting halts.
ImageShack® - Online Photo and Video Hosting

Other files needed for troubleshooting are given below


# Modified by YaST2. Last modification on Mon Jan 14 17:49:18 CET 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 2
timeout 8
##YaST - generic_mbr
gfxmenu (hd0,1)/message

##YaST - activate
###Don't change this comment - YaST2 identifier: Original name: linux###
title openSUSE 12.1 - 3.4.11-2.16 (default)
    root (hd0,1)
    kernel /vmlinuz-3.4.11-2.16-default root=/dev/sda3 splash=0
resume=/dev/sda6 splash=silent quiet showopts vga=0x31a
    initrd /initrd-3.4.11-2.16-default

###Don't change this comment - YaST2 identifier: Original name: failsafe###
title Failsafe -- openSUSE 12.1 - 3.4.11-2.16 (default)
    root (hd0,1)
    kernel /vmlinuz-3.4.11-2.16-default root=/dev/sda3 showopts apm=off
noresume edd=off powersaved=off nohz=off highres=off
processor.max_cstate=1 nomodeset  x11failsafe vga=0x31a
    initrd /initrd-3.4.11-2.16-default

###Don't change this comment - YaST2 identifier: Original name: linux###
title Desktop -- openSUSE 12.1 - 3.4.11-2.16
    root (hd0,1)
    kernel /vmlinuz-3.4.11-2.16-desktop root=/dev/sda3 splash=0
resume=/dev/sda6 splash=silent quiet showopts vga=0x31a
    initrd /initrd-3.4.11-2.16-desktop

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

###Don't change this comment - YaST2 identifier: Original name: floppy###
title Diskette
    rootnoverify (fd0)
    chainloader +1

###Don't change this comment - YaST2 identifier: Original name: other###
title Windows 7
    map (hd0) (hd0)
    map (hd0) (hd0)
    rootnoverify (hd0,0)
    makeactive
    chainloader +1



device.map
(fd0)   /dev/fd0
(hd0)   /dev/disk/by-id/ata-WDC_WD20EVDS-63T3B0_WD-WCAVY6660374
~

linux:/home/linux # fdisk -l

Disk /dev/sda: 2000.4 GB, 2000398934016 bytes
255 heads, 63 sectors/track, 243201 cylinders, total 3907029168 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 identifier: 0x0000a718

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *          63   524297339   262148638+   7  HPFS/NTFS/exFAT
/dev/sda2       524297340   526353659     1028160   83  Linux
/dev/sda3       526353660   780309179   126977760   83  Linux
/dev/sda4       780309180  3907024064  1563357442+   f  W95 Ext'd (LBA)
/dev/sda5       780309243  3894156062  1556923410   83  Linux
/dev/sda6      3894157312  3907022847     6432768   82  Linux swap / Solaris

Disk /dev/sdb: 32.0 GB, 32015122432 bytes
21 heads, 21 sectors/track, 141790 cylinders, total 62529536 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 identifier: 0xc3072e18

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1   *        8064    62529535    31260736    c  W95 FAT32 (LBA)


contents of boot partitions

and the contents of boot directory

-rw------- 1 root root      512 Nov  3 10:22 backup_mbr
lrwxrwxrwx 1 root root        1 Aug 29 05:38 boot -> .
-rw-r--r-- 1 root root     1236 Oct 25  2011 boot.readme
-rw-r--r-- 1 root root   131150 Oct  4 20:56 config-3.4.11-2.16-default
-rw-r--r-- 1 root root   131351 Oct  4 20:56 config-3.4.11-2.16-desktop
drwxr-xr-x 2 root root     4096 Jan 15 07:31 grub
lrwxrwxrwx 1 root root       26 Jan 14 16:49 initrd ->
initrd-3.4.11-2.16-default
-rw-r--r-- 1 root root 13668583 Jan 14 16:50 initrd-3.4.11-2.16-default
-rw-r--r-- 1 root root 13314471 Jan 14 16:51 initrd-3.4.11-2.16-desktop
drwx------ 2 root root    16384 Aug 28 12:19 lost+found
-rw-r--r-- 1 root root   582656 Jan 14 16:44 message
-rw-r--r-- 1 root root   634719 Oct  4 22:08 symtypes-3.4.11-2.16-default.gz
-rw-r--r-- 1 root root   635604 Oct  4 23:02 symtypes-3.4.11-2.16-desktop.gz
-rw-r--r-- 1 root root   222417 Oct  4 22:04 symvers-3.4.11-2.16-default.gz
-rw-r--r-- 1 root root   222379 Oct  4 22:51 symvers-3.4.11-2.16-desktop.gz
-rw-r--r-- 1 root root      409 Oct  4 22:04 sysctl.conf-3.4.11-2.16-default
-rw-r--r-- 1 root root      520 Oct  4 22:51 sysctl.conf-3.4.11-2.16-desktop
-rw-r--r-- 1 root root  2405545 Oct  4 21:52 System.map-3.4.11-2.16-default
-rw-r--r-- 1 root root  2487319 Oct  4 22:30 System.map-3.4.11-2.16-desktop
-rw-r--r-- 1 root root  5467969 Oct  4 22:04 vmlinux-3.4.11-2.16-default.gz
-rw-r--r-- 1 root root  5719500 Oct  4 22:50 vmlinux-3.4.11-2.16-desktop.gz
lrwxrwxrwx 1 root root       27 Jan 14 16:49 vmlinuz ->
vmlinuz-3.4.11-2.16-default
-rw-r--r-- 1 root root  4694960 Oct  4 21:52 vmlinuz-3.4.11-2.16-default
-rw-r--r-- 1 root root  4919280 Oct  4 22:30 vmlinuz-3.4.11-2.16-desktop
 

What else do you think might be needed to fix that ?

Regards
Alex

Well I also tried to update it through live dvd. To make it clear I did not proceed on that .

Surpisingly even though I did the system upgrade as was described on internet the live dvd procedure finds 1674 packages to update.

I also got that message during the process.

ImageShack® - Online Photo and Video Hosting

Now I have aborted that procedure too waiting for feedback

Regards
Alex

On 2013-01-15 09:36, alaios wrote:
>
> Well I also tried to update it through live dvd. To make it clear I did
> not proceed on that .
>
> Surpisingly even though I did the system upgrade as was described on
> internet the live dvd procedure finds 1674 packages to update.

Where exactly on internet?


Cheers/Saludos
Carlos E. R. (12.1 test at Minas-Anor)

Here:
https://en.opensuse.org/SDB:System_upgrade
I followed the zypper commands at the bottom

My bad. I found the mistake

2. Add update-repository.zypper addrepo --check --refresh --name ‘openSUSE-12.1-Update’ http://download.opensuse.org/update/12.1/ repo-update
Replace 12.1 above with your current openSUSE version**edit] 3. Update system to the latest packages.**

zypper refresh
zypper update

I have mistyped step 2 and instead of 12.1 I wrote 12.2 , so I left the system with one repository so I only did the upgrade half way.

Will it help now through the rescue system of live cd to chroot to the roor partition and run the following?

Disable all existing repositories that pre-date openSUSE 12.2,zypper modifyrepo --all --disable
*

    • Add the new openSUSE 12.2 repositories,*

zypper addrepo --name “openSUSE-12.2-OSS” http://download.opensuse.org/distribution/12.2/repo/oss/ repo-12.2-oss
zypper addrepo --name “openSUSE-12.2-Non-Oss” http://download.opensuse.org/distribution/12.2/repo/non-oss/ repo-12.2-non-oss
zypper addrepo --refresh --name “openSUSE-12.2 Update-Oss” http://download.opensuse.org/update/12.2/ repo-12.2-update
zypper addrepo --refresh --name “openSUSE-12.2-Update-Non-Oss” http://download.opensuse.org/update/12.2-non-oss/ repo-12.2-non-oss-update
The last argument sets an alias (a shorthand), you can also choose another alias for the new repositories in the above command.

    • Search for updated openSUSE 12.2 compatible third-party repositories that you used before and add them.*
  • Warning: Use with caution. Using third-party repositories could increase the chances that the upgrade will not complete correctly.zypper addrepo --name <name> <url> <alias>
    Or, if you have URL of a .repo file:
    zypper ar <url.repo>
    • Now execute the full distribution upgrade. It is strongly recommended that you run this inside GNU screen or tmux to protect the upgrade process in case anything should go wrong with the X session during the upgrade. Packages for both screen and tmux are available in the main openSUSE repositories.*

zypper ref
zypper dup
With the above command zypper will download the required packages when it installs them. To download all packages in advance, use: zypper dup --download "in-advance
"

On 2013-01-15 11:46, alaios wrote:
>
> Here:
> https://en.opensuse.org/SDB:System_upgrade
> I followed the zypper commands at the bottom

Ok. In that case, when you attempt later a DVD upgrade it will downgrade
some (many) packages, because it does not have access to the updates in
the update repo. That’s why it says that it is going to upgrade so many
packages.


https://en.opensuse.org/SDB:Offline_upgrade


Cheers/Saludos
Carlos E. R. (12.1 test at Minas-Anor)

I am doing first a backup of my Documents partition. I also saved /etc/fstab as I think it might be changed through the update.
How severe is this warning during the update procedure?

ImageShack® - Online Photo and Video Hosting

On 2013-01-15 12:26, alaios wrote:

>
> I am doing first a backup of my Documents partition. I also saved
> /etc/fstab as I think it might be changed through the update.

I don’t think so.

However, I recomend a full backup previous to a system upgrade.

> How severe is this warning during the update procedure?
>
> ‘ImageShack® - Online Photo and Video Hosting’
> (http://imageshack.us/photo/my-images/29/photo0181k.jpg/)

I answered that on another thread. Very serious.


Cheers/Saludos
Carlos E. R. (12.1 test at Minas-Anor)

Hi,
I am back to normal life. Update fixed the problems ! Great work. System is back and running

I wonder though how I can check if there are minor problems residing that might cause nightmares in the future.

These are the checks I have done, so far (please recommend more of those)

  1. Konsole-> About-> Kde version printed there is 4.8.4 Release 2
cat /etc/issue
Welcome to openSUSE 12.2 "Mantis" - Kernel \r (\l).


uname -r
3.4.6-2.10-desktop
  1. fstab entries:
/dev/sda3 /                    ext4       acl,user_xattr        1 1
/dev/sda2 /boot                ext4       acl,user_xattr        1 1
/dev/sda5 /home                ext4       acl,user_xattr        1 1
/dev/sda6 swap                 swap       defaults              0 0
#sshfs#hide@hide:/home/hide        /home/hide        fuse comment=sshfs,exec,uid=1000,allow_other,reconnect,transform_symlinks,BatchMode=yes,nonempty,noauto 0 0


#sshfs#hide@hide:/storage/        /home/hide        fuse comment=sshfs,noexec,ro,allow_other,reconnect,transform_symlinks,BatchMode=yes,nonempty,noauto 0 0



proc                 /proc                proc       defaults              0 0
sysfs                /sys                 sysfs      noauto                0 0
debugfs              /sys/kernel/debug    debugfs    noauto                0 0
usbfs                /proc/bus/usb        usbfs      noauto                0 0
devpts               /dev/pts             devpts     mode=0620,gid=5       0 0
~                                                                                                                                                                                                                                                                              
~                                                                                                        

I guess that the 4 has to be fixed and the mount to contain uuid instead of kernel device name. I think I can do that through Yast

  1. Current repositories
zypper lr
# | Alias                     | Name                               | Enabled | Refresh
--+---------------------------+------------------------------------+---------+--------
1 | openSUSE-12.2-1.6         | openSUSE-12.2-1.6                  | Yes     | No     
2 | repo-debug                | openSUSE-12.2-Debug                | No      | Yes    
3 | repo-debug-update         | openSUSE-12.2-Update-Debug         | No      | Yes    
4 | repo-debug-update-non-oss | openSUSE-12.2-Update-Debug-Non-Oss | No      | Yes    
5 | repo-non-oss              | openSUSE-12.2-Non-Oss              | Yes     | Yes    
6 | repo-oss                  | openSUSE-12.2-Oss                  | Yes     | Yes    
7 | repo-source               | openSUSE-12.2-Source               | No      | Yes    
8 | repo-update               | openSUSE-12.2-Update               | Yes     | Yes    
9 | repo-update-non-oss       | openSUSE-12.2-Update-Non-Oss       | Yes     | Yes    


What to change in the provided repositories? Anything to remove/add?

  1. More things to check ?

Regards
Alex

Hi,
I am sorry that this not very polite but I am not using the repaired system before I get some answers for the 1-6. Mostly I am afraid that I should not do more harm in the future.

Regards
Alex

On 2013-01-15 15:26, alaios wrote:
> Hi,
> I am back to normal life. Update fixed the problems ! Great work.
> System is back and running
>
> I wonder though how I can check if there are minor problems residing
> that might cause nightmares in the future.

Well, all the recommendations for after an upgrade I can think of were
written here:

Offline upgrade
method

so I’m not going to write them again :slight_smile:


Cheers / Saludos,

Carlos E. R.
(from 11.4, with Evergreen, x86_64 “Celadon” (Minas Tirith))

Thanks for that. I went through that page. What about my points 4-6?

I think that would be all.
alex

On 2013-01-17 09:36, alaios wrote:

> Thanks for that. I went through that page. What about my points 4-6?

Point 4 I already explained in detail on another post, another thread
where you also participate (Re: Grub problem after upgrade to OpenSuSE
12.2).

#5. Repos are alright as far as I can see.

#6 AFAICS no.


Cheers / Saludos,

Carlos E. R.
(from 11.4, with Evergreen, x86_64 “Celadon” (Minas Tirith))

Usually I have only done fresh install of OpenSuse. This time I wanted to perform an upgrade to save time and hassle. I was about to run “zypper dup” when I read this thread and got a little scared/spooked,

Should I use zypper dup, or go for the zypper update?

I have followed the Opensuse SDB:System ypgrade steps.

  1. Disabled all the opensuse 12.1 repos
  2. Added the new opensuse 12.2 repos
  3. Updated my 3rd party repos to 12.2 (KDE, Packman, VLC, Wine, NVidia)
  4. Have run zypper ref.
  5. Ready to upgrade, but should I exit KDE and run the upgrade from console instead? The SDB:Upgrade recommends Screen or tmux.

On 2013-02-01 21:56, DJViking wrote:
>
> Usually I have only done fresh install of OpenSuse. This time I wanted
> to perform an upgrade to save time and hassle. I was about to run
> “zypper dup” when I read this thread and got a little scared/spooked,
>
> Should I use zypper dup, or go for the zypper update?

dup, of course. dup is short for distribution upgrade.

> I have followed the Opensuse SDB:System ypgrade steps.
> 1) Disabled all the opensuse 12.1 repos
> 2) Added the new opensuse 12.2 repos
> 3) Updated my 3rd party repos to 12.2 (KDE, Packman, VLC, Wine, NVidia)
> 4) Have run zypper ref.
> 5) Ready to upgrade, but should I exit KDE and run the upgrade from
> console
instead? The SDB:Upgrade recommends Screen or tmux.

Yes, absolutely. Run it from text mode.


Cheers / Saludos,

Carlos E. R.
(from 12.1 x86_64 “Asparagus” at Telcontar)