LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (https://www.linuxquestions.org/questions/slackware-14/)
-   -   Unable to boot Slackware off SUSE GrUB (https://www.linuxquestions.org/questions/slackware-14/unable-to-boot-slackware-off-suse-grub-841705/)

grumpy.biatch 11-01-2010 10:29 AM

Unable to boot Slackware off SUSE GrUB
 
Hi,

I've a multiboot machine and I recently installed Slackware64-13.1 on sda33. I added menu entry in SUSE boot loader and configured menu list as per http://www.linuxquestions.org/questi...oblems-244455/, it returns GrUB error 15.

Here is my menu list entry for Slackware -
Code:


###Don't change this comment - YaST2 identifier: Original name: other###
title Slackware64-13.1
    root (hd0,32)
    kernel /boot/vmlinuz root=/dev/sda33 ro hdd=scsi
    savedefault
    boot

Here is lilo configuration file -

During Lilo install on sda33 it returned error saying unable to install Lilo on sda33, please configure it manually. I mounted the partition and found lilo.conf in '/'.

Secondly, I will like to label Slackware '/' & '/home', can I use gparted and label them or I need to make further configurations, have not seen any label on '/etc/fstab' or '/etc/lilo.conf'

Best,

David

udaman 11-01-2010 10:37 AM

I boot my Slackware from my Suse Grub. I installed LILO on the Salckware boot partition, and chainload it from the Grub bootloader. Here's the call in /boot/grub/menu.lst

Code:

###  manually added
title Slackware 13.1
    root (hd2,0)
    chainloader (hd2,0)+1

That calls LILO, and LILO boot Slackware.

grumpy.biatch 11-01-2010 10:47 AM

Quote:

Originally Posted by udaman (Post 4145873)
I boot my Slackware from my Suse Grub. I installed LILO on the Salckware boot partition, and chainload it from the Grub bootloader. Here's the call in /boot/grub/menu.lst

Code:

###  manually added
title Slackware 13.1
    root (hd2,0)
    chainloader (hd2,0)+1

That calls LILO, and LILO boot Slackware.

Thanks mate, will try that now.

grumpy.biatch 11-01-2010 10:51 AM

Doesnt boot, GrUB error 13.

udaman 11-01-2010 10:57 AM

Paste your menu.lst here, just the part that calls Slackware. Are you using the drive and partition that LILO is on? It looks like it isn't even seeing the LILO boot partition. In Legacy Grub 0.97, (hd0) is the first drive sda, and (hd0,0) is the first partition, sda1. So you would need for sda33, (hd0,34).

grumpy.biatch 11-01-2010 11:00 AM

Quote:

Originally Posted by udaman (Post 4145892)
Paste your menu.lst here, just the part that calls Slackware. Are you using the drive and partition that LILO is on? It looks like it isn't even seeing the LILO boot partition. In Legacy Grub 0.97, (hd0) is the first drive sda, and (hd0,0) is the first partition, sda1. So you would need for sda33, (hd0,34).

Here is Slack section -

Quote:

###Don't change this comment - YaST2 identifier: Original name: other###
title Slackware64-13.1
root (hd0,32)
chainloader (hd0,32)+1

udaman 11-01-2010 11:08 AM

oops, my mistake. (hd0,32) is correct.

Here's my /etc/lilo.conf section:

Code:

# Linux root partition section
image = /boot/vmlinuz-huge-2.6.33.4
 initrd=/boot/initrd-huge-2.6.33.4.gz
 root = /dev/sdc1
 label = Linux
 read-only
# End root Linux partition section


My root = /dev/sdc1 corresponds to (hd2,0)

Check that you have it right in your lilo.conf. And check that you're using grub 0.97 and not grub 1.98

grumpy.biatch 11-01-2010 11:10 AM

Quote:

Originally Posted by udaman (Post 4145908)
oops, my mistake. (hd0,32) is correct.

Here's my /etc/lilo.conf section:

Code:

# Linux root partition section
image = /boot/vmlinuz-huge-2.6.33.4
 initrd=/boot/initrd-huge-2.6.33.4.gz
 root = /dev/sdc1
 label = Linux
 read-only
# End root Linux partition section


My root = /dev/sdc1 corresponds to (hd2,0)

Check that you have it right in your lilo.conf. And check that you're using grub 0.97 and not grub 1.98

i guess i should try rootnoverify. Even if Lilo is failed this should boot slack, it works with bsd & solaris kernel.

i dont see any of those entries in my lilo.conf, check this http://pastebin.com/zD4YsgMj

that doesnt work either. guess i need to reinstall lilo. is there any restriction like >sdx16 or something.

udaman 11-01-2010 12:17 PM

Quote:

Originally Posted by grumpy.biatch (Post 4145910)
is there any restriction like >sdx16 or something.


It doesn't appear that there a restriction in your particular case. Check this post.
http://www.linuxquestions.org/linux/...ading_in_Linux

And this post as a tutorial:

http://www.justlinux.com/forum/showthread.php?t=144294

grumpy.biatch 11-01-2010 10:25 PM

Quote:

Originally Posted by udaman (Post 4145969)
It doesn't appear that there a restriction in your particular case. Check this post.
http://www.linuxquestions.org/linux/...ading_in_Linux

And this post as a tutorial:

http://www.justlinux.com/forum/showthread.php?t=144294

Please correct me if I am wrong -

1. Boot Slackware DVD
2. mount /dev/sda33 /mnt
3. liloconfig
4. put lilo on '/' @ /dev/sda33

How do i change the disk labels or they are irrelevant during boot.

JZL240I-U 11-02-2010 02:09 AM

You can change them e.g. with fdisk but they are irrelevant for boot. Even if your /etc/fstab uses /dev/disk/by-id/..... labels, these are different from the names one can stick on ones partitions.

grumpy.biatch 11-02-2010 05:06 AM

Quote:

Originally Posted by JZL240I-U (Post 4146542)
You can change them e.g. with fdisk but they are irrelevant for boot. Even if your /etc/fstab uses /dev/disk/by-id/..... labels, these are different from the names one can stick on ones partitions.

Thanks.

grumpy.biatch 11-02-2010 05:10 AM

[solved]
 
i reinstalled Slackware without Lilo and added it to menu.lst in SUSE -

Code:


Title Slackware64-13.1
root (hd0,32)
kernel /boot/vmlinuz root=/dev/sda33 ro
boot

This logs me in console, I guess I will need to change the runlevel. How do I do that in Slack.

Best,

David

JZL240I-U 11-02-2010 05:12 AM

That is determined in /etc/inittab. Just have a look, it is pretty obvious (I can't post an example, I'm sitting in front of a windows box).

grumpy.biatch 11-02-2010 05:28 AM

Quote:

Originally Posted by JZL240I-U (Post 4146664)
That is determined in /etc/inittab. Just have a look, it is pretty obvious (I can't post an example, I'm sitting in front of a windows box).

I guess I need to set that to '4'

Is that right?


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