LinuxQuestions.org
Visit the LQ Articles and Editorials section
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices

Reply
 
Search this Thread
Old 10-21-2012, 09:59 PM   #1
damgar
Senior Member
 
Registered: Sep 2009
Location: dallas, tx
Distribution: Slackware - current multilib/gsb Arch
Posts: 1,949
Blog Entries: 8

Rep: Reputation: 201Reputation: 201Reputation: 201
Booting RAID0 with LILO


I have been up against this all day. As much "because it's there" as any real use, I have installed Slackware-current as of yesterday to an mdadm RAID0 setup. I have (on a seperate disk altogether) created a /boot partition during installation and everything is there.

I have found plenty of tutorials for this, mostly older (Slack 12.x) that give the same answer.. Use a seperate /boot, add append = "root=/dev/md0" to lilo.conf and away you go. This might work, but LILO will not let me do it. When I run LILO it tells me that only RAID1 is allowed and refuses to install. I'm assuming something has changed, but I'm not sure what it is.
 
Old 10-21-2012, 10:21 PM   #2
TobiSGD
Moderator
 
Registered: Dec 2009
Location: Hanover, Germany
Distribution: Gentoo
Posts: 15,364
Blog Entries: 2

Rep: Reputation: 3981Reputation: 3981Reputation: 3981Reputation: 3981Reputation: 3981Reputation: 3981Reputation: 3981Reputation: 3981Reputation: 3981Reputation: 3981Reputation: 3981
Please post your /etc/lilo.conf and the output of
Code:
parted -l
run as root.
Please use code-tags for this.
 
Old 10-21-2012, 10:42 PM   #3
Richard Cranium
Senior Member
 
Registered: Apr 2009
Location: Carrollton, Texas
Distribution: Slackware64 14.1
Posts: 1,414

Rep: Reputation: 398Reputation: 398Reputation: 398Reputation: 398
Any reason why you don't want to use an initrd?
 
Old 10-21-2012, 10:56 PM   #4
wildwizard
Member
 
Registered: Apr 2009
Location: Oz
Distribution: slackware64-14.0
Posts: 755

Rep: Reputation: 226Reputation: 226Reputation: 226
I've been testing things out to work out the right way to do this and I have the following notes so far :-


Quote:
* notes
use partition type da
if /boot is raid use metadata 0.9 and raid 1 only
swap is not detected on partitioned raid (installer bug only)


* create parititions and arrays
mdadm --create /dev/md/root
result /dev/md/root is symlink to /dev/md127
installer will only see /dev/md127 not /dev/md/root

* install ....
- lilo simple

* goto new system
chroot /mnt

* setup lilo to boot raid
mkinitrd -r /dev/md*** -f ext4 -R -m ext4
change kernel symlinks to point to generic kernel
configure lilo
- add compact
- add lba32
- add initrd = /boot/initrd.gz
- check root =
reinstall lilo

* if fixing system from install cd after the fact
assemble arrays manually
mount filesystems in order under /mnt
chroot /mnt
/dev will not be populated properly
- mount /proc
- get minor/major number from /proc/partitions for md***
- mknod /dev/md*** b major minor
 
Old 10-21-2012, 10:58 PM   #5
damgar
Senior Member
 
Registered: Sep 2009
Location: dallas, tx
Distribution: Slackware - current multilib/gsb Arch
Posts: 1,949
Blog Entries: 8

Original Poster
Rep: Reputation: 201Reputation: 201Reputation: 201
lilo.conf
Code:
# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
lba32 # Allow booting past 1024th cylinder with a recent BIOS
boot = /dev/sdb
compact # faster, but won't work on all systems.
# Boot BMP Image.
# Bitmap in BMP format: 640x480x8
bitmap = /boot/slack.bmp
# Menu colors (foreground, background, shadow, highlighted
# foreground, highlighted background, highlighted shadow):
bmp-colors = 255,0,255,0,255,0
# Location of the option table: location x, location y, number of
# columns, lines per column (max 15), "spill" (this is how many
# entries must be in the first column before the next begins to
# be used. We don't specify it here, as there's just one column.
bmp-table = 60,6,1,16
# Timer location x, timer location y, foreground color,
# background color, shadow color.
bmp-timer = 65,27,0,255
# Standard menu.
# Or, you can comment out the bitmap menu above and
# use a boot message with the standard menu:
#message = /boot/boot_message.txt
# Append any additional kernel parameters:
#append="root=/dev/md0,vt.default_utf8=1"
prompt
timeout = 300
# Normal VGA console
vga = normal
# Ask for video mode at boot (time out to normal in 30s)
#vga = ask
# VESA framebuffer console @ 1024x768x64k
# vga=791
# VESA framebuffer console @ 1024x768x32k
# vga=790
# VESA framebuffer console @ 1024x768x256
# vga=773
# VESA framebuffer console @ 800x600x64k
# vga=788
# VESA framebuffer console @ 800x600x32k
# vga=787
# VESA framebuffer console @ 800x600x256
# vga=771
# VESA framebuffer console @ 640x480x64k
# vga=785
# VESA framebuffer console @ 640x480x32k
# vga=784
# VESA framebuffer console @ 640x480x256
# vga=769
# ramdisk = 0 # paranoia setting
# End LILO global section
# Linux bootable partition config begins
image = /boot/vmlinuz
root = /dev/md0
label = Linux
read-only # Partitions should be mounted read-only for checking
# Linux bootable partition config ends
parted -l
Code:
Model: ATA WDC WD10EARX-00N (scsi)
Disk /dev/sda: 1000GB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt

Number  Start   End    Size   File system  Name        Flags
 1      1049kB  537GB  537GB               Linux RAID  raid


Model: ATA WDC WD3200AAKX-0 (scsi)
Disk /dev/sdb: 320GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt

Number  Start   End     Size    File system  Name              Flags
 1      1049kB  21.5GB  21.5GB  ext4         Linux filesystem


Model: ATA WDC WD10EARX-00N (scsi)
Disk /dev/sdc: 1000GB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt

Number  Start   End    Size   File system  Name        Flags
 1      1049kB  537GB  537GB               Linux RAID  raid


Model:  Patriot Memory (scsi)
Disk /dev/sdd: 31.6GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt

Number  Start   End     Size    File system  Name              Flags
 1      1049kB  53.5MB  52.4MB  fat16        EFI System        boot
 2      53.5MB  21.5GB  21.5GB  ext2         Linux filesystem


Model: HP v100w (scsi)
Disk /dev/sde: 4041MB
Sector size (logical/physical): 512B/512B
Partition Table: msdos

Number  Start   End     Size    Type     File system  Flags
 1      1049kB  4041MB  4040MB  primary  fat32


Model: Linux Software RAID Array (md)
Disk /dev/md0: 1074GB
Sector size (logical/physical): 512B/4096B
Partition Table: loop

Number  Start  End     Size    File system  Flags
 1      0.00B  1074GB  1074GB  ext4
I should note that I've tried several ways to get the root=/dev/md0 in there. Both with just the append and no root= and vice versa.

Last edited by damgar; 10-21-2012 at 10:59 PM.
 
Old 10-21-2012, 11:07 PM   #6
damgar
Senior Member
 
Registered: Sep 2009
Location: dallas, tx
Distribution: Slackware - current multilib/gsb Arch
Posts: 1,949
Blog Entries: 8

Original Poster
Rep: Reputation: 201Reputation: 201Reputation: 201
Quote:
Originally Posted by Richard Cranium View Post
Any reason why you don't want to use an initrd?
I'm totally fine with an initrd. I don't know what modules it would need to load. I've run the generator script. At one point I was able to boot and fail as though an initrd would save the day, but at this point I can't even get lilo to run. I'm not sure exactly what is going on here other than I've tried so many things it's all running together!
 
Old 10-21-2012, 11:08 PM   #7
wildwizard
Member
 
Registered: Apr 2009
Location: Oz
Distribution: slackware64-14.0
Posts: 755

Rep: Reputation: 226Reputation: 226Reputation: 226
1. You must use an initrd generated with -R
2. Your lilo.conf is installing to sdb (is that right, normally you go onto sda)
3. No need for that append root=rubbish just make sure the appropriate linux section has the right root=
4. Is your separate /boot actually mounted while your doing this? (As this is probably where lilo is crapping out)
 
Old 10-21-2012, 11:09 PM   #8
damgar
Senior Member
 
Registered: Sep 2009
Location: dallas, tx
Distribution: Slackware - current multilib/gsb Arch
Posts: 1,949
Blog Entries: 8

Original Poster
Rep: Reputation: 201Reputation: 201Reputation: 201
Quote:
Originally Posted by wildwizard View Post
I've been testing things out to work out the right way to do this and I have the following notes so far :-
What is with partition type da instead of fd?
 
Old 10-21-2012, 11:23 PM   #9
damgar
Senior Member
 
Registered: Sep 2009
Location: dallas, tx
Distribution: Slackware - current multilib/gsb Arch
Posts: 1,949
Blog Entries: 8

Original Poster
Rep: Reputation: 201Reputation: 201Reputation: 201
Quote:
Originally Posted by wildwizard View Post
1. You must use an initrd generated with -R
2. Your lilo.conf is installing to sdb (is that right, normally you go onto sda)
3. No need for that append root=rubbish just make sure the appropriate linux section has the right root=
4. Is your separate /boot actually mounted while your doing this? (As this is probably where lilo is crapping out)
Lost the append, mounted /boot, created the initrd, ran lilo. It works! Thank you!
 
Old 11-03-2012, 08:19 PM   #10
damgar
Senior Member
 
Registered: Sep 2009
Location: dallas, tx
Distribution: Slackware - current multilib/gsb Arch
Posts: 1,949
Blog Entries: 8

Original Poster
Rep: Reputation: 201Reputation: 201Reputation: 201
I decided to play with Gentoo. Gentoo is on one contiguous partition. I edited lilo.conf to add the pertinent info for Gentoo, didn't edit anything that had been working, and now I'm back to getting the RAID1 warning?
 
Old 11-03-2012, 09:42 PM   #11
wildwizard
Member
 
Registered: Apr 2009
Location: Oz
Distribution: slackware64-14.0
Posts: 755

Rep: Reputation: 226Reputation: 226Reputation: 226
Are you running lilo from a RAID0 partition still or are you running it from the new Gentoo install?
 
Old 11-04-2012, 08:36 AM   #12
damgar
Senior Member
 
Registered: Sep 2009
Location: dallas, tx
Distribution: Slackware - current multilib/gsb Arch
Posts: 1,949
Blog Entries: 8

Original Poster
Rep: Reputation: 201Reputation: 201Reputation: 201
I was running it from within Slackware. I saved room on the non RAID disk that houses /boot. I got it working eventually. I installed gentoo by chroot from my installed Slackware on the RAID0. I had screwed up and copied over an initrd that I created under the raided Slack to the gentoo partition on accident. Something in that seems to have caused lilo to not like the gentoo install. It was strange because running lilo would add the raided slackware and then balk at the non raided gentoo complaining about raid. I got it straightened out when I decided I'm no guru and just copied over a .config for one of Pat's huge kernels and went from there.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Booting to RAID0 OpenCircuit Slackware 5 12-08-2005 11:54 PM
lilo and windows on Hardware RAID0 (3ware) ganja_guru Linux - Hardware 2 08-23-2005 01:42 PM
Trouble booting a new RAID0 machine with Debian sarge miggins Linux - Hardware 1 12-01-2004 12:27 AM
lilo problem with sata (sil3112) raid0 slackman Slackware - Installation 5 09-28-2004 04:34 PM
mandrake 9.1 - LILO - windows on a raid0 array desteffy Linux - Hardware 1 07-08-2003 12:04 AM


All times are GMT -5. The time now is 07:33 PM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration