Dotaz: GRUB - chybejici polozky v menu

[jurasek]

Dobry den  Mam instalovany CentOS release 5.4 (Final). Serverova deska S3420GP s fake-raidem. V tom RAIDu na desce je udelany mirror. Pri instalaci to instalator nasel a pouzil jako /dev/sda. Divne je, ze v /dev/mapper je jenom soubor control

[root@mail dev]# ls -l /dev/mapper/
celkem 0
crw------- 1 root root 10, 63 bře 10 14:55 control

Vse se zdalo byt krasne a ciste dokud jsem neinstaloval updaty jadra /vse probehlo OK/ a jadra se zdaji byt nainstalovane

[root@mail dev]# ls -l /boot
celkem 23628
-rw-r--r-- 1 root root   65937 zář  3  2009 config-2.6.18-164.el5
-rw-r--r-- 1 root root   65972 led 20 13:57 config-2.6.18-164.11.1.el5
-rw-r--r-- 1 root root   65971 lis  3 22:38 config-2.6.18-164.6.1.el5
-rw-r--r-- 1 root root   65971 pro 16 03:22 config-2.6.18-164.9.1.el5
drwxr-xr-x 2 root root    4096 úno 26 11:43 extlinux
drwxr-xr-x 2 root root    4096 bře 10 16:28 grub
-rw------- 1 root root 2662271 lis 27 21:21 initrd-2.6.18-164.el5.img
-rw------- 1 root root 2639899 led 27 10:00 initrd-2.6.18-164.11.1.el5.img
-rw------- 1 root root 2640108 lis 27 21:32 initrd-2.6.18-164.6.1.el5.img
-rw------- 1 root root 2640489 pro 18 10:42 initrd-2.6.18-164.9.1.el5.img
-rw-r--r-- 1 root root   80032 bře 16  2009 message
-rw-r--r-- 1 root root  108707 zář  3  2009 symvers-2.6.18-164.el5.gz
-rw-r--r-- 1 root root  108759 led 20 13:57 symvers-2.6.18-164.11.1.el5.gz
-rw-r--r-- 1 root root  108758 lis  3 22:39 symvers-2.6.18-164.6.1.el5.gz
-rw-r--r-- 1 root root  108759 pro 16 03:23 symvers-2.6.18-164.9.1.el5.gz
-rw-r--r-- 1 root root 1225101 zář  3  2009 System.map-2.6.18-164.el5
-rw-r--r-- 1 root root 1227215 led 20 13:57 System.map-2.6.18-164.11.1.el5
-rw-r--r-- 1 root root 1226663 lis  3 22:38 System.map-2.6.18-164.6.1.el5
-rw-r--r-- 1 root root 1227070 pro 16 03:22 System.map-2.6.18-164.9.1.el5
-rw-r--r-- 1 root root 1932284 zář  3  2009 vmlinuz-2.6.18-164.el5
-rw-r--r-- 1 root root 1936156 led 20 13:57 vmlinuz-2.6.18-164.11.1.el5
-rw-r--r-- 1 root root 1933820 lis  3 22:38 vmlinuz-2.6.18-164.6.1.el5
-rw-r--r-- 1 root root 1935068 pro 16 03:22 vmlinuz-2.6.18-164.9.1.el5

pak jsem rebootoval.

Bootuje stale jadro ktere se nainstalovalo pri instalaci systemu (2.6.18-164.el5)

[root@mail dev]# uname -a
Linux mail.blabla.cz 2.6.18-164.el5 #1 SMP Thu Sep 3 03:28:30 EDT 2009 x86_64 x86_64 x86_64 GNU/Linux

 

Takze jsem mrknul na bootmenu /boot/grub/menu.lst

[root@mail dev]# cat /boot/grub/menu.lst
# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this file
# NOTICE:  You do not have a /boot partition.  This means that
#          all kernel and initrd paths are relative to /, eg.
#          root (hd0,0)
#          kernel /boot/vmlinuz-version ro root=/dev/mapper/ddf1_4c53492020202020808629250000000038418a1600001450p1
#          initrd /boot/initrd-version.img
#boot=/dev/mapper/ddf1_4c53492020202020808629250000000038418a1600001450
default=0
timeout=5
splashimage=(hd0,0)/boot/grub/splash.xpm.gz
hiddenmenu
title CentOS (2.6.18-164.11.1.el5)
root (hd0,0)
kernel /boot/vmlinuz-2.6.18-164.11.1.el5 ro root=LABEL=/
initrd /boot/initrd-2.6.18-164.11.1.el5.img
title CentOS (2.6.18-164.9.1.el5)
root (hd0,0)
kernel /boot/vmlinuz-2.6.18-164.9.1.el5 ro root=LABEL=/
initrd /boot/initrd-2.6.18-164.9.1.el5.img
title CentOS (2.6.18-164.6.1.el5)
root (hd0,0)
kernel /boot/vmlinuz-2.6.18-164.6.1.el5 ro root=LABEL=/
initrd /boot/initrd-2.6.18-164.6.1.el5.img
title CentOS (2.6.18-164.el5)
root (hd0,0)
kernel /boot/vmlinuz-2.6.18-164.el5 ro root=LABEL=/
initrd /boot/initrd-2.6.18-164.el5.img

vse vypadalo OK.

 

Proved jsem reboot a chtel vybrat jadro rucne v bootmenu GRUBu. Problem je ale v tom, ze v menu je pouze a jenom jadro CentOS (2.6.18-164.el5) .

Takze to je cely muj pribeh. Pokud mate nekdo nejaky napad, sem s nim.

Predem dik

jura

Odpovědi

[NN]

To je divny, mas tam 3 polozky a bootuje to tu treti a default je 0. Jses si jisty pokud tam mas raid, ze bootojes ze stejneho disku, ze ktereho vypisujes ten grub ?

NN

[jurasek]

Jo, zkusil jsem primontovat obe zarizeni zarazene v raidu samostatne a /boot/grub/menu.lst je identicke na obou discich. To me napadlo jako prvni.

[jurasek]

Je to divny v dmesg vidim toto:

 

device-mapper: multipath: version 1.0.5 loaded                                                                               
EXT3 FS on sdb1, internal journal                                                                                            
kjournald starting.  Commit interval 5 seconds                                                                               
EXT3 FS on sda9, internal journal                                                                                            
EXT3-fs: mounted filesystem with ordered data mode.                                                                          
kjournald starting.  Commit interval 5 seconds                                                                               
EXT3 FS on sda8, internal journal                                                                                            
EXT3-fs: mounted filesystem with ordered data mode.                                                                          
kjournald starting.  Commit interval 5 seconds                                                                               
EXT3 FS on sda7, internal journal                                                                                            
EXT3-fs: mounted filesystem with ordered data mode.                                                                          
kjournald starting.  Commit interval 5 seconds                                                                               
EXT3 FS on sda6, internal journal                                                                                            
EXT3-fs: mounted filesystem with ordered data mode.                                                                          
kjournald starting.  Commit interval 5 seconds                                                                               
EXT3 FS on sda5, internal journal                                                                                            
EXT3-fs: mounted filesystem with ordered data mode.                                                                          
kjournald starting.  Commit interval 5 seconds                                                                               
EXT3 FS on sda3, internal journal                                                                                            
EXT3-fs: mounted filesystem with ordered data mode.

 

ale v systemu:

[root@mail log]# mount
/dev/sda1 on / type ext3 (rw)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
devpts on /dev/pts type devpts (rw,gid=5,mode=620)
/dev/sda9 on /home type ext3 (rw)
/dev/sda8 on /tmp type ext3 (rw)
/dev/sda7 on /opt type ext3 (rw)
/dev/sda6 on /usr type ext3 (rw)
/dev/sda5 on /zal type ext3 (rw)
/dev/sda3 on /var type ext3 (rw)
tmpfs on /dev/shm type tmpfs (rw)
none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw)

takze ted nevim z ceho je namontovany / - korenovy FS.

[jurasek]

Takze to vypada ze je namontovany /dev/sdb1 ale hlasi to /dev/sda1 co s tim ?

 

[root@mail /]# dumpe2fs -h /dev/sda1
dumpe2fs 1.39 (29-May-2006)
Filesystem volume name:   /
Last mounted on:          <not available>
Filesystem UUID:          551977e5-abe2-4fcb-8093-d939a762d734
Filesystem magic number:  0xEF53
Filesystem revision #:    1 (dynamic)
Filesystem features:      has_journal ext_attr resize_inode dir_index filetype sparse_super large_file
Default mount options:    user_xattr acl
Filesystem state:         clean
Errors behavior:          Continue
Filesystem OS type:       Linux
Inode count:              255232
Block count:              255024
Reserved block count:     12751
Free blocks:              183043
Free inodes:              250377
First block:              0
Block size:               4096
Fragment size:            4096
Reserved GDT blocks:      62
Blocks per group:         32768
Fragments per group:      32768
Inodes per group:         31904
Inode blocks per group:   997
Filesystem created:       Fri Nov 27 21:12:04 2009
Last mount time:          Fri Nov 27 21:15:52 2009
Last write time:          Fri Nov 27 21:22:03 2009
Mount count:              1
Maximum mount count:      -1
Last checked:             Fri Nov 27 21:12:04 2009
Check interval:           0 (<none>)
Reserved blocks uid:      0 (user root)
Reserved blocks gid:      0 (group root)
First inode:              11
Inode size:          128
Journal inode:            8
Default directory hash:   tea
Directory Hash Seed:      511cc3c9-d3ac-4052-9176-842bdfcd71b3
Journal backup:           inode blocks
Journal size:             16M

[root@mail /]# dumpe2fs -h /dev/sdb1
dumpe2fs 1.39 (29-May-2006)
Filesystem volume name:   /
Last mounted on:          <not available>
Filesystem UUID:          551977e5-abe2-4fcb-8093-d939a762d734
Filesystem magic number:  0xEF53
Filesystem revision #:    1 (dynamic)
Filesystem features:      has_journal ext_attr resize_inode dir_index filetype needs_recovery sparse_super large_file
Default mount options:    user_xattr acl
Filesystem state:         clean
Errors behavior:          Continue
Filesystem OS type:       Linux
Inode count:              255232
Block count:              255024
Reserved block count:     12751
Free blocks:              55847
Free inodes:              243335
First block:              0
Block size:               4096
Fragment size:            4096
Reserved GDT blocks:      62
Blocks per group:         32768
Fragments per group:      32768
Inodes per group:         31904
Inode blocks per group:   997
Filesystem created:       Fri Nov 27 21:12:04 2009
Last mount time:          Wed Mar 10 14:55:45 2010
Last write time:          Wed Mar 10 14:55:45 2010
Mount count:              25
Maximum mount count:      -1
Last checked:             Fri Nov 27 21:12:04 2009
Check interval:           0 (<none>)
Reserved blocks uid:      0 (user root)
Reserved blocks gid:      0 (group root)
First inode:              11
Inode size:          128
Journal inode:            8
Default directory hash:   tea
Directory Hash Seed:      511cc3c9-d3ac-4052-9176-842bdfcd71b3
Journal backup:           inode blocks
Journal size:             16M