FC7 grub suddenly stops booting Solaris Express CE
Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
FC7 grub suddenly stops booting Solaris Express CE
I have installed 3 OSs on my laptop (Win2003, FC7, Solaris Express CE),I used to use Linux grub to boot 3 OS without any problem. Recently I have upgraded my FC7 by using Ymux
Suddenly while I was trying to boot Solaris Express CE , it can not boot it!!!!! I can see the menu list for grub, and when I choose Solaris to be booted, all I see is below :
Solaris Express CE
rootnoverify (hd0,2)
chainloader +1
How can I fix this issue ?
Output for the FC7's grub menu.lst file is :
# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this file
# NOTICE: You have a /boot partition. This means that
# all kernel and initrd paths are relative to /boot/, eg.
# root (hd0,4)
# kernel /vmlinuz-version ro root=/dev/sda7
# initrd /initrd-version.img
#boot=/dev/sda
default=2
timeout=15
splashimage =(hd0,4)/grub/splash.xpm.gz
#hiddenmenu
# I say that /boot partion is on sda5, and / is on pratition sda7
title Fedora 7 (2.6.23.1-21.fc7)
root (hd0,4)
kernel /vmlinuz-2.6.23.1-21.fc7 ro root=LABEL=/ rhgb quiet
initrd /initrd-2.6.23.1-21.fc7.img
#I commented these below lines, because I used "Yumex" to update my system on 17-11-07
#title Fedora Core 7(2.6.21-1.3194.fc7)
# root (hd0,4)
# kernel /vmlinuz-2.6.21-1.3194.fc7 ro root=LABEL=/ rhgb quiet
# initrd /initrd-2.6.21-1.3194.fc7.img
# I say that windows partion is on sda1
title W2K3 Server
rootnoverify (hd0,0)
chainloader +1
makeactive
#I say that solaris partion is on sda3
title Solaris Express CE
rootnoverify (hd0,2)
chainloader +1
2) now if that does not work....I need you, if you are still happy to try me, to be very explicit and tell me the results of the troubleshooter when at grub at mbr after you press c for commands and then type root (hd0,.....and press the tab key....I want you to report what grub reports about your structure....because altho I appreciate you claim solaris is on sda3 = hd0,2 in grub speak.....maybe our assumptions are wrong.
leaping ahead....if you see hd0,4 for example is reporting a non-linux non-fat non-ntfs structure then that is your solaris and you change the grub menu to reflect the new numbers ok?
3) the other thing with the link....is grub is chainloading to the solaris bootloader and maybe there is an issue with solaris bootloader....which is beyond my skill level....but if that is the case you can post to a solaris forum.....its a case of elimination.
when at grub at mbr after you press c for commands and
From within Linux (not through booting and press e ) I opened the terminal and type in : " grub " then I did :
Code:
[root@localhost ~]# grub
grub> root (hd0, PRESS TAB
Possible partitions are:
Partition num: 0, Filesystem type unknown, partition type 0x7
Partition num: 1, Filesystem type is fat, partition type 0xc
Partition num: 2, Filesystem type unknown, partition type 0xbf
Partition num: 4, Filesystem type is ext2fs, partition type 0x83
Partition num: 5, Filesystem type is ext2fs, partition type 0x83
Partition num: 6, Filesystem type is ext2fs, partition type 0x83
Partition num: 7, Filesystem type unknown, partition type 0x82
nice try but within linux you are using a device map file which can stuff me up.
Please please reboot and press C at the grub menu screen. if its exactly same then we can move forward.
edit culled
2) let us know if at any time you have used another bootloader after grub was fedora installed into mbr....or you used a partition tool especially partition magic types
while you are there though, lets do some stuff manually
mbr...press C for commands
enter root (hd0,......and press tab key.......
if and only if 2 shows up as a 0xbf then its the solaris so complete the command to get to a non solaris
eg call it root (hd0,0)....who cares it reports ntfs (7)
Now issue a new command set, grub forgets your old root command
rootnoverify (hd0,2) (and press enter)....if it returns 0xbf then type
chainloader +1 (and press enter) ....if no error
makeactive (and press enter) if no error
boot (and press enter)....if sol boots you have an error in your menu so copy and paste.....but you do not need the extra command boot.
Please please reboot and press C at the grub menu screen. if its exactly same then we can move forward.
Yes, it is exactly same.
Now my turn to ask
why is the swap partition (sda8) of type : "unknown " under grub command from from within Linux and from the c command ? while the same partition (sda8) of type : swap (known) under /etc/fstab ???
2) let us know if at any time you have used another bootloader after grub was fedora installed into mbr....or you used a partition tool especially partition magic types
I used Acronis to partition the hard disk and , then I installed Linux and then I installed solaris, I used solaris DVD to format the place (its partition) where it is residing now. i hope I answer what you was looking to know
well thanks for showing me your fstab and sorry I have a more important thing to say its
/dev/sda3 swap swap defaults 0 0
LABEL=SWAP-sda8 swap swap defaults 0 0
2) WT? your fstab is claiming you have 2 swaps....sda3 and sda8 thats wrong for a start.
I do not have a problem that you used partition tools but sometimes they muck up the mbr part table.
3) lets go back a step.....
my post 11 bottom section was a series of grub commands to chainload into solaris....did you try it...can you write down and report all errors you see please
4) your /var/log/syslog and messages should have an entry for an error for trying to mount a swap that is not a swap format......unless something has happened and now your old solaris is now truly a linux swap....well linux swap is the same as a solaris swap but still not a solaris bootable system
5) we may be getting somewhere....run a live cd....run qtparted or gparted or fdisk or cfdisk or sfdisk and see what each partition is.
if sda3 is now a swap you have to re-install solaris and change your fstab for linux.
while you are there though, lets do some stuff manually
You meant while I am at grub shell,,,,didn't you ?
Quote:
mbr...press C for commands
I did not get how to do this , could please explain ? what I did was at ( grub> )shell I typed in : MBR,,,,then press c,,,but it gave me error message,,,,,then I tried to press Enter,,,,but it gave me error message as well.
What I did is: at a grub shell I did like this :
Code:
grub>root,,,,,,press Enter
(hd0,2): Filesystem type is ext2fs, partition type oxbf
Are you happy with the result of : ext2fs vs 0xbf!!!!
Quote:
my post 11 bottom section was a series of grub commands to chainload into solaris....did you try it...can you write down and report all errors you see please
I will try this after we fixed the issue for MBR above.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.