LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (http://www.linuxquestions.org/questions/slackware-14/)
-   -   GRUB Error 15: Dual Boot Slack and OpenIndiana (http://www.linuxquestions.org/questions/slackware-14/grub-error-15-dual-boot-slack-and-openindiana-888614/)

x360539 06-27-2011 02:15 PM

GRUB Error 15: Dual Boot Slack and OpenIndiana
 
Hi all,

I have a dual-boot system with OpenIndiana and Slackware.

Slackware is installed on /dev/sda1
OpenIndiana is installed on /dev/sda2

OpenIndiana was installed after Slackware and installed GRUB (the legacy version). Of course, OpenIndiana didn't register Slack in the GRUB menu. (It doesn't seem to want to play nice with other systems.)

So, before editing the GRUB menu in OI, I've been experimenting at the GRUB command line, trying to get Slack to boot.

When I enter:

Code:

grub> root (hd0,0)
I get:

Code:

Filesystem type is ext2fs, partition type 0x83
Which tells me I'm targeting the correct partition.

But when I enter:

Code:

grub> kernel /boot/vmlinuz root=/dev/sda1 ro
I get:

Code:

Error 15: File not found
I'm not sure what I'm missing. I've also tried entering the entire name of the kernel, but I get the same error.

Is it because OI installed GRUB is some odd location? Would that make a difference?

Thanks.

T3RM1NVT0R 06-27-2011 03:30 PM

@ Reply
 
Hi there,

Try this:

Make a copy of grub.conf

1. Type root (As you did)
2. Instead of typing grub> kernel /boot/vmlinuz root=/dev/sda1 ro type setup (hd0) instead
3. cat grub.conf file and see if you have got boot partitions pointing to correct location. Else paste the output here so that we guys can have a look at it.

x360539 06-27-2011 11:21 PM

Thanks so much for the reply!

After I did:

Code:

root (hd0,0)
I entered:

Code:

setup (hd0)
which produced:

Code:

Checking if "/boot/grub/stage1" exists...no
Checking if "/grub/stage1" exists...no

Which is odd because "/boot/grub/stage1" does exist on OI.

I couldn't find grub.conf, but the "menu.lst" file from "/rpool/boot/grub/menu.lst" appears below. Slack is the first "unknown" partition:

Code:

splashimage /boot/grub/splash.xpm.gz
foreground 343434
background F7FbFF
default 0
timeout 30
#---------- ADDED BY BOOTADM - DO NOT EDIT ----------
title OpenIndiana Development oi_148 X86
findroot (pool_rpool,1,a)
bootfs rpool/ROOT/openindiana
splashimage /boot/solaris.xpm
foreground FF0000
background A8A8A8
kernel$ /platform/i86pc/kernel/$ISADIR/unix -B $ZFS-BOOTFS,console=graphics
module$ /platform/i86pc/$ISADIR/boot_archive
#---------------------END BOOTADM--------------------

# Unknown partition of type 131 found on /dev/rdsk/c2t0d0p0 partition: 1
# It maps to the GRUB device: (hd0,0) .

# Unknown partition of type 0 found on /dev/rdsk/c2t0d0p0 partition: 3
# It maps to the GRUB device: (hd0,2) .

# Unknown partition of type 0 found on /dev/rdsk/c2t0d0p0 partition: 4
# It maps to the GRUB device: (hd0,3) .

# Unknown partition of type 0 found on /dev/rdsk/c2t3d0p0 partition: 2
# It maps to the GRUB device: (hd0,1) .

The "menu.list" file located in the traditional location "/boot/grub/menu.lst" has a note in it:

Code:

# With zfs root the active menu.lst file is /<pool>/boot/grub/menu.lst
# This reference copy of the file is not used.

I don't know if this moving of the GRUB files around due to ZFS has something to do with the problem.

Thanks!

Woodsman 06-28-2011 02:18 PM

Quote:

But when I enter:

grub> kernel /boot/vmlinuz root=/dev/sda1 ro

I get:

Error 15: File not found
GRUB needs a device location. Try something this:

grub> kernel (hd0,0)/boot/vmlinuz root=/dev/sda1 ro

You likely do not have a common /boot partition. Therefore /boot is unique to each operating system.

For Slackware:

(hd0,0)/boot/vmlinuz root=/dev/sda1 ro

For OpenIndiana:

(hd0,1)/boot/vmlinuz root=/dev/sda2 ro

GRUB starts counting with zero. Therefore the Slackware partition, /dev/sda1, is located on device zero and partition zero (hd0,0). The OpenIndiana partition, /dev/sda2, is located on device zero and partition one (hd0,1).

T3RM1NVT0R 06-28-2011 03:13 PM

@ Reply
 
Hi x360539,

You could give a try to steps mentioned by Woodsman.

It appears to me that OpenIndiana replaced the boot loader which Slack has configured before or it might be possible that it has installed its own bootloader and not added any entry for slack.

I am assuming that as of now you are able to boot in OpenIndiana but not in slack (I might be wrong, just a guess I am making)

Perhaps you could have a look at the following link which describes how you can edit menu.lst file to get desired OS listed in: http://boff.wordpress.com/2007/01/17...rub-boot-menu/

I hope this helps.


All times are GMT -5. The time now is 10:07 AM.