Bug 118531 - Changing default boot OS in 10.0 RC1 destroy 9.2 boot-up
Summary: Changing default boot OS in 10.0 RC1 destroy 9.2 boot-up
Status: RESOLVED DUPLICATE of bug 104048
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: YaST2 (show other bugs)
Version: RC 1
Hardware: x86-64 SUSE Other
: P5 - None : Major
Target Milestone: ---
Assignee: E-mail List
QA Contact: Klaus Kämpf
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-09-23 05:27 UTC by Jan Petersen
Modified: 2005-09-26 09:36 UTC (History)
0 users

See Also:
Found By: Beta-Customer
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments
Tar archive with crash file documentation (590.00 KB, application/x-tar)
2005-09-24 01:15 UTC, Jan Petersen
Details
fstab file to support bug schenario #2 (402 bytes, text/plain)
2005-09-24 01:28 UTC, Jan Petersen
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Jan Petersen 2005-09-23 05:27:16 UTC
After having bworked with OpenSuse 10.0 RC1 for a few days, I wanted to set the
default boot-up OS back to 9.2 on my dual-boot system.
I had been booting up in both 9.2 and 10.0 until tonight with no problem.
SuSE 9.2 is installed on hda3 and 10.0 RC1 on hda4.

Booting up in 10.0 I started YaST, open the boot control pane, selected SuSE 9.2
in the list and click "Set as Default", Saved and rebooted.
Now 9.2 boot-up displays:

md: Autodetedting RAID arrays
md: autorun ...
md: ... autorun DONE.
Kernel Panic - not syncing: VFS: Unable to mount root fs on unknown-block(3,3)

Debug info:
linux:/home/jpeterse # fdisk -l

Disk /dev/hda: 60.0 GB, 60011642880 bytes
255 heads, 63 sectors/track, 7296 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/hda1   *           1        1275    10241406    7  HPFS/NTFS
/dev/hda2            1276        1401     1012095   82  Linux swap / Solaris
/dev/hda3            1402        5841    35656268   83  Linux
/dev/hda4            5841        7296    11695319+  83  Linux

menu.lst:
# Modified by YaST2. Last modification on Thu Sep 22 20:36:33 CDT 2005

color white/blue black/light-gray
default 1
timeout 8
gfxmenu (hd0,3)/boot/message

###Don't change this comment - YaST2 identifier: Original name: linux###
title SUSE LINUX 10.0
    root (hd0,3)
    kernel /boot/vmlinuz root=/dev/hda4 vga=0x317 selinux=0    resume=/dev/hda2
 splash=silent showopts
    initrd /boot/initrd

###Don't change this comment - YaST2 identifier: Original name: SUSE LINUX 9.2
simple-mouse (/dev/hda3)###

title SUSE LINUX 9.2 (/dev/hda3)
    kernel (hd0,2)/boot/vmlinuz root=/dev/hda3 vga=0x317 selinux=0 splash=silent
console=tty0 resume=/dev/hda2 desktop elevator=as showopts

I also found that having the hda3 mounted from within OpenSuSE 10.0 as /data1
will change the menu.lst file to reference /data1/boot/vmlinuz as boot path,
when you update default boot OS configuration in YaST.

Now if only I knew how to get my 9.2 to boot up again ...
Comment 1 Michael Gross 2005-09-23 08:49:29 UTC
Could you provide the y2logs, please?
Maby read: http://www.opensuse.org/Bug_Reporting_FAQ#YaST
Comment 2 Martin Lasarsch 2005-09-23 09:20:07 UTC
is this the whole menu.lst? ... there is no initrd in the 9.2 section 
Comment 3 Jan Petersen 2005-09-24 01:15:10 UTC
Created attachment 50779 [details]
Tar archive with crash file documentation

Sorry it took a bit to get back to you. Yes, the problem is that the initrd
section is missing.

I restored the system so that booting was working for both 10.0 and 9.2.
Here is the exact steps I took to:

1. Open YaST and non-root
2. Select the Boot Loader Module
3. Authenticate as root
4. Select "SuSE 9.2" in the list
5. Click "Set as Default"
6. Click "Finish" and exist YaST.
7. Reboot system to 9.2
8. Kernel Panic.

Attached is menu.lst before YaST update and after YaST update and the y2log
file.

I found 2 additional problems. Take a look at the attached screenshot. Note
that the path to the 9.2. partition includes the directory mapping from the
fstab file "/data1". Should you click "edit" to edit the boot option, the path
entere into the menu.lst file will include the reference to the local
directory.

At the same screenshot, I rescalled the window. Notice that the "Abort" and
"Finish" buttons are now outside the visible area of the form, and there are no
scrollbars.
Comment 4 Jan Petersen 2005-09-24 01:28:53 UTC
Created attachment 50780 [details]
fstab file to support bug schenario #2

Figured you might need the fstab file as well to review the path mapping issue.
Note that the /dev/hda3 was not mounted at the time YaST was run, and the
screenshot was taken.
Comment 5 Martin Lasarsch 2005-09-26 09:36:12 UTC

*** This bug has been marked as a duplicate of 104048 ***