LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Newbie (https://www.linuxquestions.org/questions/linux-newbie-8/)
-   -   GRUB 15 Error? (https://www.linuxquestions.org/questions/linux-newbie-8/grub-15-error-705769/)

your_shadow03 02-18-2009 09:43 PM

GRUB 15 Error?
 
I installed a new RHEL 4 AS Update 6 OS and this gave me the error:



Code:

Attempting Boot from Hard Drive (C:)
GRUB Loading stage1.5.

GRUB Loading,please wait
Error 15


billymayday 02-18-2009 10:05 PM

Error 15 is "file not found", so you most likely have a problem in your menu.lst/grub.conf

your_shadow03 02-18-2009 10:26 PM

How to solve the issue?
Will Rescue Disk Solve the issue?
Do I need to install OS from scratch?
Just for your info, I had configured RAID 0+1 from BIOS.
Installed LVM..So I guess the incorrect LVM Partitioning may be the culprit.

billymayday 02-18-2009 10:38 PM

You could start by posting menu.lst

your_shadow03 02-18-2009 11:16 PM

How can I reach to that file?
Do I need to boot through rescue disk?

billymayday 02-18-2009 11:22 PM

If you have one, that would work - then make sure you mount your boot partition.

your_shadow03 02-19-2009 02:58 AM

I went into rescue mode.
Mounted to chroot /mnt/sysconfig
Now I am in #ssh shell.
I checked with /boot/grub/grub.conf and found an entry saying:
#boot /dev/sda

Sorry I forgot to tell you something.. I had already 2 SAN Switch with name /dev/sda, /dev/sdb and /dev/sdc.I installed a new OS on /dev/ccissd0p0 local partition.
While Installation I choose /dev/ccissd0p0 partition and formatted it leaving the rest connected to MSA.

What I think is #boot /dev/sda may be clashing with /dev/sda of MSA?
Correct me if I am wrong

your_shadow03 02-19-2009 03:00 AM

I Tried booting through rescue disk :

#mv /dev/sda /dev/sda.old

Removed the hash in fron of #boot /dev/sda in /boot/grub/grub.conf file
And Then rebooted the system.
But No improvement/clue to what is going wrong.

Do I need to run #grub-install /dev/sda

your_shadow03 02-19-2009 03:45 AM

Billymayday,
I need your help and am sure you gonna help me in this regard.

I looked into another machine which is running without any issue and is also connected to MSA.
The Entry for running machine includes:

Code:

#boot=/dev/sda
default=1
timeout=5
#splashimage=(hd0,0)/boot/grub/splash.xpm.gz
hiddenmenu
title Red Hat Enterprise Linux AS (2.6.9-67.0.22.EL)
        root (hd0,0)
        kernel /boot/vmlinuz-2.6.9-67.0.22.EL ro root=LABEL=/ idle=poll
        initrd /boot/initrd-2.6.9-67.0.22.EL.img
title Red Hat Enterprise Linux AS (2.6.9-67.0.22.ELsmp)
        root (hd0,0)
        kernel /boot/vmlinuz-2.6.9-67.0.22.ELsmp ro root=LABEL=/ idle=poll
        initrd /boot/initrd-2.6.9-67.0.22.ELsmp.img
title Red Hat Enterprise Linux AS (2.6.9-67.ELsmp)
        root (hd0,0)
        kernel /boot/vmlinuz-2.6.9-67.ELsmp ro root=LABEL=/ idle=poll
        initrd /boot/initrd-2.6.9-67.ELsmp.img
title Red Hat Enterprise Linux AS-up (2.6.9-67.EL)
        root (hd0,0)
        kernel /boot/vmlinuz-2.6.9-67.EL ro root=LABEL=/ idle=poll
        initrd /boot/initrd-2.6.9-67.EL.img

My Machine Entry was also same except on my machine it says:
Code:

#splashimage=(hd4,0)/boot/grub/splash.xpm.gz
Why is # being put to machines connected to MSA?

billymayday 02-19-2009 03:42 PM

The # simply comments out the line, and the splashimage just puts a graphic behind the menu. Can't do a lot unless you can post the menu.lst from the version that doesn't work.

Can you also post "fdisk -l"


All times are GMT -5. The time now is 01:41 AM.