Why does the GRUB multi-Start Menu fail?

Source: Internet
Author: User
Why does the GRUB multi-Start Menu fail? -- Linux general technology-Linux technology and application information. For details, refer to the following section. Hard Disk installation:
Primary partition XP (sda1)
Logical partition:
FAT32 (sda5)
NTFS (sda6)
Ext3 (sda7)
Swap (sda8)
Ext3 (sda9)
Ext3 (sda10)
The installation is as follows:
Install the Red Flag 6.0 grub. conf file on sda7 as follows:
# 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, 6)
# Kernel/boot/vmlinuz-version ro root =/dev/sda7
# Initrd/boot/initrd-version.img
# Boot =/dev/sda
Default = 0
Timeout = 5
Gfxmenu (hd0, 6)/boot/message
Title RedFlag (2.6.22.6-1)
Root (hd0, 6)
Kernel/boot/vmlinuz-2.6.22.6-1 ro root = LABEL =/vga = 788 splash = silent resume =/dev/sda8
Initrd/boot/initrd-2.6.22.6-1.img
Title Other
Rootnoverify (hd0, 0)
Chainloader + 1

After fc8 is installed on sda9, FC is left in the Startup menu, and then the startup Item of the red flag is added to grub of fc8. The Startup menu is normal. Grub. conf is as follows:
# 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, 8)
# Kernel/boot/vmlinuz-version ro root =/dev/sda9
# Initrd/boot/initrd-version.img
# Boot =/dev/sda
Default = 0
Timeout = 5
Splashimage = (hd0, 8)/boot/grub/splash.xpm.gz
Hiddenmenu
Title RedFlag (2.6.22.6-1)
Root (hd0, 6)
Kernel/boot/vmlinuz-2.6.22.6-1 ro root = LABEL =/vga = 788 splash = silent resume =/dev/sda8
Initrd/boot/initrd-2.6.22.6-1.img
Title Fedora (2.6.23.1-42. fc8)
Root (hd0, 8)
Kernel/boot/vmlinuz-2.6.23.1-42.fc8 ro root = LABEL =/1 rhgb quiet
Initrd/boot/initrd-2.6.23.1-42.fc8.img
Title Other
Rootnoverify (hd0, 0)
Chainloader + 1

After opensuse10.3 was installed on sda10, it was found that suse automatically recognized other systems. Why does SUSE change the FC8 Startup menu to a red flag, now there are two red flags in the Start Menu. After two red flags are entered, they are both red flags, and none of them are FC8. Why? How can I retrieve the FC8 menu?
No grub. conf in/boot/grub in SUSE only menu. lst
The SUSE menu. lst file is as follows:
# Modified by YaST2. Last modification on Juan? 3 ?? 19 15:07:27 UTC 2008
Default 0
Timeout 8
Gfxmenu (hd0, 9)/boot/message

### Don't change this comment-YaST2 identifier: Original name: linux ###
Title openSUSE 10.3
Root (hd0, 9)
Kernel/boot/vmlinuz-2.6.22.5-31-default root =/dev/disk/by-id/scsi-SATA_ST3160811AS_6PT4JL2X-part10 vga = 0x317 devfs = mount, dall resume =/dev/sda8 splash = silent showopts
Initrd/boot/initrd-2.6.22.5-31-default

### Don't change this comment-YaST2 identifier: Original name: RedFlag (2.6.22.6-1) (/dev/sda7 )###
Title RedFlag (2.6.22.6-1) (/dev/sda7)
Root (hd0, 6)
Configfile/boot/grub/menu. lst

### Don't change this comment-YaST2 identifier: Original name: RedFlag (2.6.22.6-1) (/dev/sda9 )###
Title RedFlag (2.6.22.6-1) (/dev/sda9)
Root (hd0, 8)
Configfile/boot/grub/menu. lst

### Don't change this comment-YaST2 identifier: Original name: windows ###
Title Windows
Rootnoverify (hd0, 9)
Chainloader (hd0, 0) + 1

### Don't change this comment-YaST2 identifier: Original name: failsafe ###
Title Failsafe -- openSUSE 10.3
Root (hd0, 9)
Kernel/boot/vmlinuz-2.6.22.5-31-default root =/dev/disk/by-id/scsi-SATA_ST3160811AS_6PT4JL2X-part10 vga = normal showopts ide = nodma apm = off acpi = off noresume nosmp noapic maxcpus = 0 edd = off 3
Initrd/boot/initrd-2.6.22.5-31-default

Thank you!

[ This post was last edited by ghostbod]
Related Article

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.