LinuxQuestions.org
Welcome to the most active Linux Forum on the web.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Software > Linux - Kernel
User Name
Password
Linux - Kernel This forum is for all discussion relating to the Linux kernel.

Notices


Reply
  Search this Thread
Old 05-10-2010, 03:33 AM   #1
JZL240I-U
Senior Member
 
Registered: Apr 2003
Location: Germany
Distribution: openSuSE Tumbleweed-KDE, Mint 18.3+19.0, MX-18
Posts: 4,251

Rep: Reputation: Disabled
Kernel updating: where go the files, how is GRUB informed?


This is my setup:

sda1: /boot of SuSE 11.0 with sda7: / and sda8: /home
sda2: openSolaris
sda3: FreeBSD 8.0
...
sda10: /boot of SuSE 11.2 with sda11: / and sda12: /home

Now, sda1 boots them all, effectively sda10 will be ignored. I want to migrate to SuSE 11.2 but I can't really do that, since any updating of its kernel results in an error. Now you know why I ask:
  • where is the kernel, i.e. the physcal data file of vmlinux of an installation kept?
  • there are a /lib/modules/<kernel-version> directories for different versions and kernel types, all empty but the newest one. Why? How can I keep the old modules for a roll back?
  • How does GRUB know what kernel to load?
  • How is GRUB taking care of two (more) distributions with differing kernel versions?
In other words I'm suspecting that my setup invalidates GRUB's loading scheme insofar as the "old" GRUB doesn't feel responsible for the updated "new" SuSE but I can't really redress a situation which I simply do not understand. Any hints, explanations or links for reading up on it are very much appreciated.
 
Old 05-10-2010, 04:29 AM   #2
deadeyes
Member
 
Registered: Aug 2006
Posts: 609

Rep: Reputation: 79
1. the vmlinuz file is saved in /boot. Do note that in many distributions there is a symlink from vmlinuz (or what have you) to the actual vmlinuz-<versionnumber>
2. That seems strange... I would think it removes those empty directories as well. What are you doing then? DO you install your new kernel package? Or do you update it?
Updating will probably uninstall the current version and install the new one while installing will just install the new version.
Make sure you have the same /boot mounted on both Suse installs and make sure they don't override each other.
3. This is pretty basic linux knowledge: /boot/grub/menu.lst
In this file you will find the stanzas for each entry you get when booting your system.
The "kernel" line says what vmlinuz files should be loaded.
4. GRUB just reads the /boot/grub/menu.lst
If you have multiple distributions you can add a new stanza and change the kernel line, the root and probably the initram line.
 
Old 05-10-2010, 04:55 AM   #3
JZL240I-U
Senior Member
 
Registered: Apr 2003
Location: Germany
Distribution: openSuSE Tumbleweed-KDE, Mint 18.3+19.0, MX-18
Posts: 4,251

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by deadeyes View Post
1. the vmlinuz file is saved in /boot. ...
Right here my problems in understanding begin. I have two /boot partitions (sda1 and sda10). Booting commences from sda1 but only sda10 is mounted from /etc/fstab. When I call YAST or zypper to update my kernel how can I make sure that the correct /boot is updated?

Quote:
Originally Posted by deadeyes View Post
2. That seems strange... I would think it removes those empty directories as well. What are you doing then? DO you install your new kernel package? Or do you update it?...
Usually the system the still boots but with loads of errors. I then proceed to /lib/modules and there I create a symbolic link with the version name of the old kernel to the new one as target. After that the errors during boot are gone, but I don't even truly know what kernel I am running as "uname -r" gives the old name while the above mentioned links point to the new modules...

Quote:
Originally Posted by deadeyes View Post
Updating will probably uninstall the current version and install the new one while installing will just install the new version.
Ahh, now here is a thought. I'll try it with zypper, I don't know how to control YAST sufficiently.

Quote:
Originally Posted by deadeyes View Post
Make sure you have the same /boot mounted on both Suse installs and make sure they don't override each other.
That is currently not clear. When I installed 11.2 it wanted to overwrite my menu.lst so I gave it its own /boot (sda10) which I later disabled for booting but which gets still mounted as /boot in 11.2. Saturday I tried to install the 11.2 GRUB on sda1 to straighten this out but I created disaster (GRUB error 18, six hours of repair, gfx/message still gone...). I suspect the problems stem from here...

Quote:
Originally Posted by deadeyes View Post
3. ... The "kernel" line says what vmlinuz files should be loaded.
Right. So I'm afraid the "new" /boot on sda10 got the updates. Still where are those bloody kernel files? Or are they in fact physically in /boot?

<edit> I'll prodeed like this: I'll change /etc/fstab to use sda1 as /boot and "hide" sda10. That should do the trick. I'll report later, I won't be able to work on that machine for a few days. Thanks for your input</edit>

Last edited by JZL240I-U; 05-10-2010 at 08:15 AM.
 
Old 05-10-2010, 05:48 AM   #4
syg00
LQ Veteran
 
Registered: Aug 2003
Location: Australia
Distribution: Lots ...
Posts: 17,918

Rep: Reputation: 2852Reputation: 2852Reputation: 2852Reputation: 2852Reputation: 2852Reputation: 2852Reputation: 2852Reputation: 2852Reputation: 2852Reputation: 2852Reputation: 2852
Don't change anything - that will only make diagnosis harder. I'm surprised you can get that lot (especially OpenSolaris) booted at all. Go to sf.net and get the bootinfoscript - run it (from Linux) and post the RESULTS.txt it generates.
 
Old 05-11-2010, 06:04 AM   #5
deadeyes
Member
 
Registered: Aug 2006
Posts: 609

Rep: Reputation: 79
Quote:
Originally Posted by JZL240I-U View Post
Right here my problems in understanding begin. I have two /boot partitions (sda1 and sda10). Booting commences from sda1 but only sda10 is mounted from /etc/fstab. When I call YAST or zypper to update my kernel how can I make sure that the correct /boot is updated?
The kernel will be installed to your currently mounted /boot.
You can just go into the grub line and use the tab key for completion. It would be easy to see what /boot is used.
Be careful with changing what /boot should be used (grub-install) as this can make your system unbootable.
In the end you should have all kernels on one /boot and use that one.

Quote:
Usually the system the still boots but with loads of errors. I then proceed to /lib/modules and there I create a symbolic link with the version name of the old kernel to the new one as target. After that the errors during boot are gone, but I don't even truly know what kernel I am running as "uname -r" gives the old name while the above mentioned links point to the new modules...
No need to create the symlink.
Check that the root filesystem is correctly configured (this is not the same as the "root (hd0,4)" directive). There should be a directory /lib/modules/`uname-r` or something.

Quote:
That is currently not clear. When I installed 11.2 it wanted to overwrite my menu.lst so I gave it its own /boot (sda10) which I later disabled for booting but which gets still mounted as /boot in 11.2. Saturday I tried to install the 11.2 GRUB on sda1 to straighten this out but I created disaster (GRUB error 18, six hours of repair, gfx/message still gone...). I suspect the problems stem from here...
You could mount both boot partitions and merge the files.

Quote:
Right. So I'm afraid the "new" /boot on sda10 got the updates. Still where are those bloody kernel files? Or are they in fact physically in /boot?

<edit> I'll prodeed like this: I'll change /etc/fstab to use sda1 as /boot and "hide" sda10. That should do the trick. I'll report later, I won't be able to work on that machine for a few days. Thanks for your input</edit>
Those vmlinuz kernel files are in /boot. HOwever the modules are on your root partition for that OS.

So in the end it would be possible to mount the /dev/sda1 (if that is the one used) and install the kernel (make sure it does not override your existing kernels.).
Do I understand correct if you have now 2 times 11.2?
 
Old 05-11-2010, 06:41 AM   #6
JZL240I-U
Senior Member
 
Registered: Apr 2003
Location: Germany
Distribution: openSuSE Tumbleweed-KDE, Mint 18.3+19.0, MX-18
Posts: 4,251

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by deadeyes View Post
The kernel will be installed to your currently mounted /boot.
That's what I surmised above.

Quote:
Originally Posted by deadeyes View Post
In the end you should have all kernels on one /boot and use that one.
Ideed. That's why and how I created all this hassle.


Quote:
Originally Posted by deadeyes View Post
No need to create the symlink. Check that the root filesystem is correctly configured (this is not the same as the "root (hd0,4)" directive). There should be a directory /lib/modules/`uname-r` or something.
It's exectly here "/lib/modules/`uname-r`" where I create that link which is absolutely necessary since the kernel otherwise can't load the kernel shared objects, so e.g. the firewall or the USB-services won't start. But it is a crutch, no doubt.

Quote:
Originally Posted by deadeyes View Post
You could mount both boot partitions and merge the files.
Yeah, well, to be on the secure side, I will follow the advice of syg00, then change /boot and do a system update. That should take care of all necessities.

Quote:
Originally Posted by deadeyes View Post
Those vmlinuz kernel files are in /boot. HOwever the modules are on your root partition for that OS.
Well I think(!) /boot on /dev/sda1 is only 50 MB so that might be a problem for further updates, I'll have to look.

Quote:
Originally Posted by deadeyes View Post
So in the end it would be possible to mount the /dev/sda1 (if that is the one used) and install the kernel (make sure it does not override your existing kernels.).
That's exactly how I plan it, now that I better understand what I inadvertently set up.

Quote:
Originally Posted by deadeyes View Post
Do I understand correct if you have now 2 times 11.2?
No, it is one 11.0 and one 11.2, the latter one got the modules in the new /lib modules/<uname -r>, the former one the kernel in the old /boot -- or so I think. I'll report as soon as I find out.

Last edited by JZL240I-U; 05-12-2010 at 02:29 AM.
 
Old 05-12-2010, 02:26 AM   #7
JZL240I-U
Senior Member
 
Registered: Apr 2003
Location: Germany
Distribution: openSuSE Tumbleweed-KDE, Mint 18.3+19.0, MX-18
Posts: 4,251

Original Poster
Rep: Reputation: Disabled
Hi syg00

This is the RESULTS.txt
Code:
                Boot Info Script 0.55    dated February 15th, 2010                    

============================= Boot Info Summary: ==============================

 => Grub 0.96 is installed in the MBR of /dev/sda and looks on the same drive 
    in partition #1 for /boot/grub/stage2 and /boot/grub/menu.lst.
 => No boot loader is installed in the MBR of /dev/sdb
 => No boot loader? is installed in the MBR of /dev/sdc

sda1: _________________________________________________________________________

    File system:       ext3
    Boot sector type:  Grub
    Boot sector info:  Grub 0.96 is installed in the boot sector of sda1 and 
                       looks at sector 859201 of the same hard drive for the 
                       stage2 file. A stage2 file is at this location on 
                       /dev/sda. Stage2 looks on partition #1 for 
                       /boot/grub/menu.lst.
    Operating System:  
    Boot files/dirs:   /boot/grub/menu.lst /grub/menu.lst

sda2: _________________________________________________________________________

    File system:       
    Boot sector type:  Grub
    Boot sector info:  Grub 0.95 is installed in the boot sector of sda2 and 
                       looks at sector 996080 of the same hard drive for the 
                       stage2 file. A stage2 file is at this location on 
                       /dev/sda. Stage2 looks on partition #2 for 
                       /boot/grub/menu.lst.
    Mounting failed:
mount: unknown filesystem type ''

sda3: _________________________________________________________________________

    File system:       ufs
    Boot sector type:  Unknown
    Boot sector info:      Mounting failed:
mount: unknown filesystem type ''
mount: wrong fs type, bad option, bad superblock on /dev/sda3,
       missing codepage or helper program, or other error
       In some cases useful info is found in syslog - try
       dmesg | tail  or so


sda4: _________________________________________________________________________

    File system:       Extended Partition
    Boot sector type:  -
    Boot sector info:  
sda5: _________________________________________________________________________

    File system:       ext3
    Boot sector type:  -
    Boot sector info:      Operating System:  
    Boot files/dirs:   
sda6: _________________________________________________________________________

    File system:       ext3
    Boot sector type:  -
    Boot sector info:      Operating System:  
    Boot files/dirs:   
sda7: _________________________________________________________________________

    File system:       ext3
    Boot sector type:  -
    Boot sector info:      Operating System:   Welcome to openSUSE 11.0 
                       (i586) - Kernel ().
    Boot files/dirs:   /etc/fstab

sda8: _________________________________________________________________________

    File system:       ext3
    Boot sector type:  -
    Boot sector info:      Operating System:  
    Boot files/dirs:   
sda9: _________________________________________________________________________

    File system:       swap
    Boot sector type:  -
    Boot sector info:  
sda10: _________________________________________________________________________

    File system:       ext4
    Boot sector type:  Grub
    Boot sector info:  Grub 0.97 is installed in the boot sector of sda10 and 
                       looks at sector 325370892 of the same hard drive for 
                       the stage2 file. A stage2 file is at this location on 
                       /dev/sda. Stage2 looks on partition #10 for 
                       /boot/grub/menu.lst.
    Operating System:  
    Boot files/dirs:   /boot/grub/menu.lst /grub/menu.lst

sda11: _________________________________________________________________________

    File system:       ext4
    Boot sector type:  -
    Boot sector info:      Operating System:  Welcome to openSUSE 11.2 
                       "Emerald" - Kernel ().
    Boot files/dirs:   /etc/fstab

sda12: _________________________________________________________________________

    File system:       ext4
    Boot sector type:  -
    Boot sector info:      Operating System:  
    Boot files/dirs:   
sdb1: _________________________________________________________________________

    File system:       vfat
    Boot sector type:  MSDOS5.0: Fat 16
    Boot sector info:  No errors found in the Boot Parameter Block.
    Operating System:  MS-DOS 6.22
    Boot files/dirs:   /boot.ini /ntldr /NTDETECT.COM /IO.SYS /MSDOS.SYS 
                       /COMMAND.COM

sdb2: _________________________________________________________________________

    File system:       swap
    Boot sector type:  -
    Boot sector info:  
sdb4: _________________________________________________________________________

    File system:       ext3
    Boot sector type:  -
    Boot sector info:      Operating System:  
    Boot files/dirs:   
sdc1: _________________________________________________________________________

    File system:       vfat
    Boot sector type:  Fat16
    Boot sector info:  According to the info in the boot sector, sdc1 has 
                       2015200 sectors.. But according to the info from the 
                       partition table , it has 2016735 sectors.
    Operating System:  
    Boot files/dirs:   
=========================== Drive/Partition Info: =============================

Drive: sda ___________________ _____________________________________________________

Disk /dev/sda: 251.0 GB, 251000193024 bytes
255 heads, 63 sectors/track, 30515 cylinders, total 490234752 sectors
Units = sectors of 1 * 512 = 512 bytes
Disk identifier: 0x00041d0d

Partition  Boot         Start           End          Size  Id System

/dev/sda1    *             63       996,029       995,967  83 Linux
/dev/sda2             996,030    21,013,019    20,016,990  bf Solaris
/dev/sda3          21,013,020    52,484,354    31,471,335  a5 FreeBSD
/dev/sda4          52,484,355   490,223,474   437,739,120   f W95 Ext d (LBA)
/dev/sda5         198,097,578   219,078,404    20,980,827  83 Linux
/dev/sda6         219,078,468   258,164,549    39,086,082  83 Linux
/dev/sda7         258,164,613   289,635,884    31,471,272  83 Linux
/dev/sda8         289,635,948   321,107,219    31,471,272  83 Linux
/dev/sda9         321,107,283   325,107,404     4,000,122  82 Linux swap / Solaris
/dev/sda10        325,107,468   329,300,369     4,192,902  83 Linux
/dev/sda11        329,300,433   402,701,354    73,400,922  83 Linux
/dev/sda12         52,484,481   198,097,514   145,613,034  83 Linux


Drive: sdb ___________________ _____________________________________________________

Disk /dev/sdb: 10.2 GB, 10245537792 bytes
255 heads, 63 sectors/track, 1245 cylinders, total 20010816 sectors
Units = sectors of 1 * 512 = 512 bytes
Disk identifier: 0x00000000

Partition  Boot         Start           End          Size  Id System

/dev/sdb1    *             63     4,192,964     4,192,902   6 FAT16
/dev/sdb2           4,192,965    11,197,304     7,004,340  82 Linux swap / Solaris
/dev/sdb4          11,197,305    20,000,924     8,803,620  83 Linux


Drive: sdc ___________________ _____________________________________________________

Disk /dev/sdc: 1031 MB, 1031798784 bytes
16 heads, 32 sectors/track, 3936 cylinders, total 2015232 sectors
Units = sectors of 1 * 512 = 512 bytes
Disk identifier: 0xee35fa74

Partition  Boot         Start           End          Size  Id System

/dev/sdc1                  32     2,016,767     2,016,736   e W95 FAT16 (LBA)

/dev/sdc1 ends after the last sector of /dev/sdc

blkid -c /dev/null: ____________________________________________________________

Device           UUID                                   TYPE       LABEL                         

/dev/sda1        2914c084-eca7-4c47-8d3f-c84ffb5b1ef1   ext3       11.0/boot                     
/dev/sda10       7415dbf5-d5d8-4fa2-b5a3-850c3eb456bd   ext4                                     
/dev/sda11       9b4f7589-3975-400b-b0e9-897603be9b10   ext4                                     
/dev/sda12       ba4720c3-910c-49a5-9547-f64ddef533c3   ext4                                     
/dev/sda13                                              zfs                                      
/dev/sda17                                              ufs                                      
/dev/sda18                                              ufs                                      
/dev/sda19                                              ufs                                      
/dev/sda20                                              ufs                                      
/dev/sda21                                              ufs                                      
/dev/sda22                                              ufs                                      
/dev/sda3                                               ufs                                      
/dev/sda5        1c7a72bf-7910-4a35-bc7a-954a760ec09b   ext3                                     
/dev/sda6        f3997f99-2499-4bbe-af79-91f89268534e   ext3       11.0/                         
/dev/sda7        b72f96e0-d36a-4fee-87c9-f327fdc4947e   ext3                                     
/dev/sda8        e53de2c5-991d-4624-9165-9c21be1fac99   ext3                                     
/dev/sda9        0b376c46-a76c-44cc-b37e-7aca71e75e8c   swap       swap                          
/dev/sdb1        3365-7709                              vfat       MS-DOS_6                      
/dev/sdb2        633530b3-2288-4342-9782-8181b888901c   swap       SWAP                          
/dev/sdb4        b7270ce9-2e8f-47ac-9699-52731f429415   ext3                                     
/dev/sdc1        B58E-12C6                              vfat       MRXCoolDriv                   

============================ "mount | grep ^/dev  output: ===========================

Device           Mount_Point              Type       Options

/dev/sda11       /                        ext4       (rw,acl,user_xattr)
/dev/sda10       /boot                    ext4       (rw,acl,user_xattr)
/dev/sda12       /home                    ext4       (rw,acl,user_xattr)
/dev/sda1        /11.0-boot               ext3       (rw,noexec,nosuid,nodev)
/dev/sdc1        /media/MRXCoolDriv       vfat       (rw,nosuid,nodev,uid=0,utf8,shortname=mixed,flush)


=========================== sda1/boot/grub/menu.lst: ===========================

# Modified by YaST2. Last modification on Fr Okt  3 17:08:08 UTC 2008
default 0
timeout 8
# gfxmenu (hd0,0)/message
##YaST - activate

###Don't change this comment - YaST2 identifier: Original name: linux###
title openSUSE 11.2 - 2.6.31.5-0.1-default
    root (hd0,0)
    kernel /vmlinuz-2.6.31.5-0.1-default root=/dev/disk/by-id/scsi-SATA_Maxtor_6L250R0_L607SAMG-part11 lang=de resume=/dev/sdb2 splash=verbose showopts vga=0x314 CPUFREQ=no acpi=force
    initrd /initrd-2.6.31.5-0.1-default

###Don't change this comment - YaST2 identifier: Original name: linux###
title openSUSE 11.0 - 2.6.25.5-1.1-pae
    root (hd0,0)
    kernel /vmlinuz-2.6.25.5-1.1-pae root=/dev/disk/by-id/scsi-SATA_Maxtor_6L250R0_L607SAMG-part7 lang=de resume=/dev/sdb2 splash=verbose showopts vga=0x314 CPUFREQ=no acpi=force
    initrd /initrd-2.6.25.5-1.1-pae

###Don't change this comment - YaST2 identifier: Original name: failsafe###
title Failsafe -- openSUSE 11.0 - 2.6.25.5-1.1
    root (hd0,0)
    kernel /vmlinuz-2.6.25.5-1.1-pae root=/dev/disk/by-id/scsi-SATA_Maxtor_6L250R0_L607SAMG-part7 showopts ide=nodma apm=off acpi=off noresume nosmp noapic maxcpus=0 edd=off x11failsafe vga=0x314
    initrd /initrd-2.6.25.5-1.1-pae

###Don't change this comment - YaST2 identifier: Original name: FreeBSD###
title FreeBSD 8.0 RELEASE 11-2009
    rootnoverify (hd0,2)
    makeactive
    chainloader (hd0,2)+1

###Don't change this comment - YaST2 identifier: Original name: FreeBSD###
title FreeBSD 8.0 mit GRUB direkt
    rootnoverify (hd0,2)
    makeactive
    root (hd0,2,a)
    kernel /boot/loader

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

###Don't change this comment - YaST2 identifier: Original name: DOS###
#title openSolaris 05/08
#    root (hd0,1,a)
#    kernel /platform/i86pc/multiboot -B console=ttya
#    module /platform/i86pc/boot_archive

###Don't change this comment - YaST2 identifier: Original name: DOS###
title openSolaris 05/08 ... JustLinux
    hide (hd0,0)
    hide (hd0,1)
    hide (hd0,2)
    hide (hd0,3)
    root (hd0,1)
    chainloader (hd0,1)+1

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

============================= sda1/grub/menu.lst: =============================

# Modified by YaST2. Last modification on Fr Okt  3 17:08:08 UTC 2008
default 0
timeout 8
# gfxmenu (hd0,0)/message
##YaST - activate

###Don't change this comment - YaST2 identifier: Original name: linux###
title openSUSE 11.2 - 2.6.31.5-0.1-default
    root (hd0,0)
    kernel /vmlinuz-2.6.31.5-0.1-default root=/dev/disk/by-id/scsi-SATA_Maxtor_6L250R0_L607SAMG-part11 lang=de resume=/dev/sdb2 splash=verbose showopts vga=0x314 CPUFREQ=no acpi=force
    initrd /initrd-2.6.31.5-0.1-default

###Don't change this comment - YaST2 identifier: Original name: linux###
title openSUSE 11.0 - 2.6.25.5-1.1-pae
    root (hd0,0)
    kernel /vmlinuz-2.6.25.5-1.1-pae root=/dev/disk/by-id/scsi-SATA_Maxtor_6L250R0_L607SAMG-part7 lang=de resume=/dev/sdb2 splash=verbose showopts vga=0x314 CPUFREQ=no acpi=force
    initrd /initrd-2.6.25.5-1.1-pae

###Don't change this comment - YaST2 identifier: Original name: failsafe###
title Failsafe -- openSUSE 11.0 - 2.6.25.5-1.1
    root (hd0,0)
    kernel /vmlinuz-2.6.25.5-1.1-pae root=/dev/disk/by-id/scsi-SATA_Maxtor_6L250R0_L607SAMG-part7 showopts ide=nodma apm=off acpi=off noresume nosmp noapic maxcpus=0 edd=off x11failsafe vga=0x314
    initrd /initrd-2.6.25.5-1.1-pae

###Don't change this comment - YaST2 identifier: Original name: FreeBSD###
title FreeBSD 8.0 RELEASE 11-2009
    rootnoverify (hd0,2)
    makeactive
    chainloader (hd0,2)+1

###Don't change this comment - YaST2 identifier: Original name: FreeBSD###
title FreeBSD 8.0 mit GRUB direkt
    rootnoverify (hd0,2)
    makeactive
    root (hd0,2,a)
    kernel /boot/loader

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

###Don't change this comment - YaST2 identifier: Original name: DOS###
#title openSolaris 05/08
#    root (hd0,1,a)
#    kernel /platform/i86pc/multiboot -B console=ttya
#    module /platform/i86pc/boot_archive

###Don't change this comment - YaST2 identifier: Original name: DOS###
title openSolaris 05/08 ... JustLinux
    hide (hd0,0)
    hide (hd0,1)
    hide (hd0,2)
    hide (hd0,3)
    root (hd0,1)
    chainloader (hd0,1)+1

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

=================== sda1: Location of files loaded by Grub: ===================


    .4GB: boot/grub/menu.lst
    .4GB: boot/grub/stage2
    .0GB: boot/initrd
    .0GB: boot/initrd-2.6.25.5-1.1-pae
    .0GB: boot/initrd-2.6.31.5-0.1-default
    .0GB: boot/vmlinuz
    .0GB: boot/vmlinuz-2.6.25.5-1.1-pae
    .0GB: boot/vmlinuz-2.6.31.5-0.1-default
    .4GB: grub/menu.lst
    .4GB: grub/stage2
    .0GB: initrd
    .0GB: initrd-2.6.25.5-1.1-pae
    .0GB: initrd-2.6.31.5-0.1-default
    .0GB: vmlinuz
    .0GB: vmlinuz-2.6.25.5-1.1-pae
    .0GB: vmlinuz-2.6.31.5-0.1-default

=============================== sda7/etc/fstab: ===============================

/dev/disk/by-id/scsi-SATA_Maxtor_6L250R0_L607SAMG-part1 /boot                ext3       acl,user_xattr        1 2
#/dev/disk/by-id/scsi-SATA_Maxtor_91021U2_G23BBE7C-part2 swap                 swap       defaults              0 0
/dev/disk/by-id/scsi-SATA_Maxtor_6L250R0_L607SAMG-part9 swap                 swap       defaults              0 0
/dev/disk/by-id/scsi-SATA_Maxtor_6L250R0_L607SAMG-part7 /                    ext3       acl,user_xattr        1 1
/dev/disk/by-id/scsi-SATA_Maxtor_91021U2_G23BBE7C-part1 /DOS                 vfat       users,gid=users,umask=0002,utf8=true 0 0
/dev/disk/by-id/scsi-SATA_Maxtor_91021U2_G23BBE7C-part4 /backup              ext3       defaults              1 2
/dev/disk/by-id/scsi-SATA_Maxtor_6L250R0_L607SAMG-part8 /home                ext3       acl,user_xattr        1 2
/dev/disk/by-id/scsi-SATA_Maxtor_6L250R0_L607SAMG-part5 /11.0	             ext3       defaults              1 2
/dev/disk/by-id/scsi-SATA_Maxtor_6L250R0_L607SAMG-part6 /Bilder              ext3       defaults              1 2
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

/dev/fd0             /media/floppy        auto       noauto,user,async     0 0
#/dev/hdd             /media/dvdram        subfs      noauto,fs=cdfss,rw,procuid,nosuid,nodev,exec,iocharset=utf8 0 0

========================== sda10/boot/grub/menu.lst: ==========================

# Modified by YaST2. Last modification on Sat May  8 18:07:35 CEST 2010
# THIS FILE WILL BE PARTIALLY OVERWRITTEN by perl-Bootloader
# Configure custom boot parameters for updated kernels in /etc/sysconfig/bootloader

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

###Don't change this comment - YaST2 identifier: Original name: linux###
title SUSE LINUX 
    root (hd0,9)
    kernel /vmlinuz root=/dev/disk/by-id/ata-Maxtor_6L250R0_L607SAMG-part11 resume=/dev/disk/by-id/ata-Maxtor_91021U2_G23BBE7C-part2 splash=silent quiet showopts
    initrd /initrd

###Don't change this comment - YaST2 identifier: Original name: failsafe###
title Failsafe -- SUSE LINUX 
    root (hd0,9)
    kernel /vmlinuz root=/dev/disk/by-id/ata-Maxtor_6L250R0_L607SAMG-part11 showopts apm=off noresume nosmp maxcpus=0 edd=off powersaved=off nohz=off highres=off processor.max_cstate=1 x11failsafe
    initrd /initrd

============================= sda10/grub/menu.lst: =============================

# Modified by YaST2. Last modification on Sat May  8 18:07:35 CEST 2010
# THIS FILE WILL BE PARTIALLY OVERWRITTEN by perl-Bootloader
# Configure custom boot parameters for updated kernels in /etc/sysconfig/bootloader

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

###Don't change this comment - YaST2 identifier: Original name: linux###
title SUSE LINUX 
    root (hd0,9)
    kernel /vmlinuz root=/dev/disk/by-id/ata-Maxtor_6L250R0_L607SAMG-part11 resume=/dev/disk/by-id/ata-Maxtor_91021U2_G23BBE7C-part2 splash=silent quiet showopts
    initrd /initrd

###Don't change this comment - YaST2 identifier: Original name: failsafe###
title Failsafe -- SUSE LINUX 
    root (hd0,9)
    kernel /vmlinuz root=/dev/disk/by-id/ata-Maxtor_6L250R0_L607SAMG-part11 showopts apm=off noresume nosmp maxcpus=0 edd=off powersaved=off nohz=off highres=off processor.max_cstate=1 x11failsafe
    initrd /initrd

=================== sda10: Location of files loaded by Grub: ===================


 166.5GB: boot/grub/menu.lst
 166.5GB: boot/grub/stage2
 166.6GB: boot/initrd
 166.6GB: boot/initrd-2.6.31.12-0.2-default
 166.6GB: boot/vmlinuz
 166.6GB: boot/vmlinuz-2.6.31.12-0.2-default
 166.5GB: grub/menu.lst
 166.5GB: grub/stage2
 166.6GB: initrd
 166.6GB: initrd-2.6.31.12-0.2-default
 166.6GB: vmlinuz
 166.6GB: vmlinuz-2.6.31.12-0.2-default

=============================== sda11/etc/fstab: ===============================

/dev/disk/by-id/ata-Maxtor_6L250R0_L607SAMG-part10 /boot                ext4       acl,user_xattr        1 2
/dev/disk/by-id/ata-Maxtor_6L250R0_L607SAMG-part9 swap                 swap       defaults              0 0
#/dev/disk/by-id/ata-Maxtor_91021U2_G23BBE7C-part2 swap                 swap       defaults              0 0
/dev/disk/by-id/ata-Maxtor_6L250R0_L607SAMG-part11 /                    ext4       acl,user_xattr        1 1
#/dev/disk/by-id/ata-Maxtor_91021U2_G23BBE7C-part1 /DOS                 vfat       users,gid=users,umask=0002,utf8=true 0 0
/dev/disk/by-id/ata-Maxtor_6L250R0_L607SAMG-part12 /home                ext4       acl,user_xattr        1 2
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
/dev/disk/by-id/ata-Maxtor_6L250R0_L607SAMG-part1 /11.0-boot      auto       noauto,user           0 0
/dev/disk/by-id/ata-Maxtor_6L250R0_L607SAMG-part5 /11.0-backup        auto       noauto,user           0 0
/dev/disk/by-id/ata-Maxtor_6L250R0_L607SAMG-part6 /bilder               auto       noauto,user           0 0
/dev/disk/by-id/ata-Maxtor_6L250R0_L607SAMG-part7 /11.0-system              auto       noauto,user           0 0
/dev/disk/by-id/ata-Maxtor_6L250R0_L607SAMG-part8 /11.0-home      auto       noauto,user           0 0
#/dev/disk/by-id/ata-Maxtor_91021U2_G23BBE7C-part4 /sdb4           auto       noauto,user           0 0

================================ sdb1/boot.ini: ================================

[boot loader]
timeout=5
default=multi(0)disk(0)rdisk(0)partition(2)\WINNT
[operating systems]
multi(0)disk(0)rdisk(0)partition(2)\WINNT="Windows NT Workstation, Version 4.0" 
multi(0)disk(0)rdisk(0)partition(2)\WINNT="Windows NT Workstation, Version 4.0 [VGA-Modus]" /basevideo /sos 
C:\boothda.lin="SuSE Linux 9.0pro" 
C:\="MS-DOS" 
=========================== Unknown MBRs/Boot Sectors/etc =======================

Unknown BootLoader  on sda3

00000000  eb 3c 00 00 00 00 00 00  00 00 00 00 02 00 00 00  |.<..............|
00000010  00 00 00 00 00 00 00 00  12 00 02 00 00 00 00 00  |................|
00000020  00 00 00 00 00 16 1f 66  6a 00 51 50 06 53 31 c0  |.......fj.QP.S1.|
00000030  88 f0 50 6a 10 89 e5 e8  c0 00 8d 66 10 cb fc 31  |..Pj.......f...1|
00000040  c9 8e c1 8e d9 8e d1 bc  00 7c 89 e6 bf 00 07 fe  |.........|......|
00000050  c5 f3 a5 be ee 7d 80 fa  80 72 2c b6 01 e8 60 00  |.....}...r,...`.|
00000060  b9 01 00 be be 8d b6 01  80 7c 04 a5 75 07 e3 19  |.........|..u...|
00000070  f6 04 80 75 14 83 c6 10  fe c6 80 fe 05 72 e9 49  |...u.........r.I|
00000080  e3 e1 be a2 7d eb 4b 31  d2 89 16 00 09 b6 10 e8  |....}.K1........|
00000090  2e 00 bb 00 90 8b 77 0a  01 de bf 00 c0 b9 00 ae  |......w.........|
000000a0  29 f1 f3 a4 fa 49 74 14  e4 64 a8 02 75 f7 b0 d1  |)....It..d..u...|
000000b0  e6 64 e4 64 a8 02 75 fa  b0 df e6 60 fb e9 50 13  |.d.d..u....`..P.|
000000c0  bb 00 8c 8b 44 08 8b 4c  0a 0e e8 5a ff 73 2a be  |....D..L...Z.s*.|
000000d0  9d 7d e8 1c 00 be a7 7d  e8 16 00 30 e4 cd 16 c7  |.}.....}...0....|
000000e0  06 72 04 34 12 ea 00 00  ff ff bb 07 00 b4 0e cd  |.r.4............|
000000f0  10 ac 84 c0 75 f4 b4 01  f9 c3 2e f6 06 b0 08 80  |....u...........|
00000100  74 22 80 fa 80 72 1d bb  aa 55 52 b4 41 cd 13 5a  |t"...r...UR.A..Z|
00000110  72 12 81 fb 55 aa 75 0c  f6 c1 01 74 07 89 ee b4  |r...U.u....t....|
00000120  42 cd 13 c3 52 b4 08 cd  13 88 f5 5a 72 cb 80 e1  |B...R......Zr...|
00000130  3f 74 c3 fa 66 8b 46 08  52 66 0f b6 d9 66 31 d2  |?t..f.F.Rf...f1.|
00000140  66 f7 f3 88 eb 88 d5 43  30 d2 66 f7 f3 88 d7 5a  |f......C0.f....Z|
00000150  66 3d ff 03 00 00 fb 77  9d 86 c4 c0 c8 02 08 e8  |f=.....w........|
00000160  40 91 88 fe 28 e0 8a 66  02 38 e0 72 02 b0 01 bf  |@...(..f.8.r....|
00000170  05 00 c4 5e 04 50 b4 02  cd 13 5b 73 0a 4f 74 1c  |...^.P....[s.Ot.|
00000180  30 e4 cd 13 93 eb eb 0f  b6 c3 01 46 08 73 03 ff  |0..........F.s..|
00000190  46 0a d0 e3 00 5e 05 28  46 02 77 88 c3 52 65 61  |F....^.(F.w..Rea|
000001a0  64 00 42 6f 6f 74 00 20  65 72 72 6f 72 0d 0a 00  |d.Boot. error...|
000001b0  80 90 90 90 90 90 90 90  90 90 90 90 90 90 00 00  |................|
000001c0  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
*
000001e0  00 00 00 00 00 00 00 00  00 00 00 00 00 00 80 00  |................|
000001f0  01 00 a5 fe ff ff 00 00  00 00 50 c3 00 00 55 aa  |..........P...U.|
00000200


=============================== StdErr Messages: ===============================

mdadm: No arrays found in config file or automatically
Thanks for mentioning bootscriptinfo, I didn't know about it. After running bootscriptinfo I changed /etc/fstab in all installations to mount /dev/sda1 in /boot. No problems arose. I haven't updated the kernel yet, 11.2 believes it is up to date (which it is not) due to my earlier attempts to update. I'll see if I can force it somehow (alternatively a new patch-level will be in the repositories). I'll report back then.

Thanks for all the help syg00 and deadeyes .

P.S.: Oh, btw. /boot (/dev/sda1)is 500 MB no problems there.

Last edited by JZL240I-U; 05-12-2010 at 02:30 AM.
 
Old 05-12-2010, 12:11 PM   #8
deadeyes
Member
 
Registered: Aug 2006
Posts: 609

Rep: Reputation: 79
Code:
###Don't change this comment - YaST2 identifier: Original name: linux###
title openSUSE 11.2 - 2.6.31.5-0.1-default
    root (hd0,0)
    kernel /vmlinuz-2.6.31.5-0.1-default root=/dev/disk/by-id/scsi-SATA_Maxtor_6L250R0_L607SAMG-part11 lang=de resume=/dev/sdb2 splash=verbose showopts vga=0x314 CPUFREQ=no acpi=force
    initrd /initrd-2.6.31.5-0.1-default
So this is your new install, right?

You can do the following:
Mount /dev/sda10 on another mountpoint then /boot (as /boot should be your sda1), for example /mnt/secondboot.
Now copy the files mentioned above (cp /mnt/secondboot/initrd-2.6.31.5-0.1-default /boot, cp /mnt/secondboot/vmlinuz-2.6.31.5-0.1-default /boot)
These files should not interfere here as it does not yet exist.
That should be it.
However I am not sure what SuSe edits in the file so maybe it gets overwritten again after installing a new kernel or something.
I also wonder if the resume device will work as it should if you share it between 2 systems.

IMPORTANT: make absolutely sure you have a backup(the /boot partition is small so that shouldn't be any problem).
In that case the menu.lst, kernel and initrd images can be restored fast and easy.(just copy the whole tree)

Quote:
I'm surprised you can get that lot (especially OpenSolaris) booted at all.
Solaris for x86 also uses grub. So this is not really surprising to me
BTW: that script is good to know... good to troubleshoot!
 
Old 05-19-2010, 06:17 AM   #9
JZL240I-U
Senior Member
 
Registered: Apr 2003
Location: Germany
Distribution: openSuSE Tumbleweed-KDE, Mint 18.3+19.0, MX-18
Posts: 4,251

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by deadeyes View Post
Code:
...
title openSUSE 11.2 - 2.6.31.5-0.1-default
    root (hd0,0)
    kernel /vmlinuz-2.6.31.5-0.1-default root=/dev/disk/by-id/scsi-SATA_Maxtor_6L250R0_L607SAMG-part11 lang=de resume=/dev/sdb2 splash=verbose showopts vga=0x314 CPUFREQ=no acpi=force
    initrd /initrd-2.6.31.5-0.1-default
So this is your new install, right?
Right, that's it.

Quote:
Originally Posted by deadeyes View Post
...Now copy the files mentioned above (cp /mnt/secondboot/initrd-2.6.31.5-0.1-default /boot, cp /mnt/secondboot/vmlinuz-2.6.31.5-0.1-default /boot)
This is unnecessary. Look at the GRUB-stanza,in particular "root=/dev/disk/by-id/scsi-SATA_Maxtor_6L250R0_L607SAMG-part11" <- this is the new kernel (as confirmed by "uname -r" when it is started).

Quote:
Originally Posted by deadeyes View Post
...I also wonder if the resume device will work as it should if you share it between 2 systems.
No problem as it is /swap (for both SuSEs and additionally for openSolaris).

But you gave me an idea: I'll see whether I find the new kernel and initrd and create a new GRUB stanza by hand Well, well, well...

On second thought, I remember the initrd but the kernel is missing. But I can find that on the Novell site I'd guess. I'll report back, when I know more.
 
Old 06-02-2010, 11:50 AM   #10
JZL240I-U
Senior Member
 
Registered: Apr 2003
Location: Germany
Distribution: openSuSE Tumbleweed-KDE, Mint 18.3+19.0, MX-18
Posts: 4,251

Original Poster
Rep: Reputation: Disabled
In the end I didn't do it by hand. Firstly, the kernel is missing and usually comes in a one-click-installation on the Novell site, and then the next patch level had come out ... so I updated it via YAST after having straightened out the mess with the two /boot partitions.

Thanks again for all the help syg00 and deadeyes. You helped me to better understand the boot process and about the kernel whereabouts, not to mention to get to know the bootinfoscript . See you hereabouts .

P.S.: Oh yes, GRUB's menu.lst really does get updated automatically by YAST, so that part of my original question is answered too.

Last edited by JZL240I-U; 06-02-2010 at 11:52 AM.
 
Old 06-23-2010, 12:53 AM   #11
rogerjeny
LQ Newbie
 
Registered: Jun 2010
Posts: 3

Rep: Reputation: 0
These all information is really nice to click the installation to the novel site it can be updated automatically . It is really appreciate that Os can boot the system .
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

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
Grub not updating kernel version MyHeartPumpsFreon Linux - Software 4 12-04-2007 11:11 PM
updating kernel image with GRUB loader rich442 MEPIS 3 04-06-2007 04:29 PM
Updating Grub after kernel Compile beepee Linux - Software 3 11-15-2006 01:05 PM
Grub 0.97 issues on slackware - grub-install is very slow, & updating menu.lst fails dieyouspammer Linux - Software 1 02-27-2006 01:06 PM
Updating Grub.conf With New Kernel hanserr Linux - Newbie 3 02-27-2004 05:01 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Software > Linux - Kernel

All times are GMT -5. The time now is 05:45 AM.

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
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration