Grub Loading stage2 “(hd0,0)/message” has the wrong format press a key to continue

Hello,

I just upgraded one of my SLES Servers from 9 to 10.4.  The server that was upgraded was one of our Dev instances of Oracle (on a physical box).

There were a couple of errors that were encountered but they were all able to be fixed except one.  

The error is:

Grub Loading stage2 “(hd0,0)/message” has the wrong format press a key to continue.

After a key is pressed the server would and continues to boot correctly.  

I have tried everything possible that I know of to take care of the error.  I have not been able to get it to go past that error.  

Here is the first part of my menu.1st

default 0
timeout 8
gfxmenu (hd0,0)/message

###Don't change this comment - YaST2 identifier: Original name: linux###
title SUSE Linux Enterprise Server 10 SP4

I have verified that my message file is in the location listed above.  I have changed that to /boot/message and nothing changed.

I verified that the message file was the right type.  cpio
Even copied a working one from another server with the same version of SLES

I verified that they drive is correctly identified in yast, /etc/fstab and grub.conf

Anyone have any ideas?

Additional note:
I went into the menu.1st and #'d out the line that referred to the message file.  Rebooted the server and it booted up just fine.  Weird.  Any way to stop this from happening on my production Oracle servers?
toddlarsonAsked:
Who is Participating?
 
Kerem ERSOYPresidentCommented:
Hi,

The old default for ATA drives were /dev/hdax and now for all drives it is /dev/sdax. I guess your default drive has changed but your config is still the same.. just edit your /boot/grub/device.map

and make sure the contents is:
(hd0) /dev/sda

Open in new window


The drive name should be in accordance with your

chkdisk -l 

Open in new window


output...

Cheers,
K.
0
 
toddlarsonAuthor Commented:
chkdsk is not a valid program on my SLES box.  I did do some other troubleshooting after thinking about the problem for a couple of days.  The error was only occuring because the GUI screen would not load.  Since it is a server that no one has any need to see the pretty bootup screen, I just remmed out the line and the server boots up fine.  

Thanks for your help
0
 
Kerem ERSOYPresidentCommented:
Sorry I meant
fdisk -l

Open in new window


What was I thinking :))
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.