raid installation

delacruz · 2009-06-12 05:39:27

I have been trying for some time to install archlinux using raid. I have failed. I get this screen once it "boots".

here is my setup

Hardrive One = sda
Hardrive Two = sdb

md1 /boot
md2 swap
md3 /
md4 /home

fstab

# 
# /etc/fstab: static file system information
#
# <file system>        <dir>         <type>    <options>          <dump> <pass>
none                   /dev/pts      devpts    defaults            0      0
none                   /dev/shm      tmpfs     defaults            0      0

/dev/md3             /   auto  defaults   0      1
/dev/md2               swap swap defaults   0      0
/dev/md1               /boot auto defaults            0      0
/dev/md4               /home auto defaults         0        0

mdadm

# mdadm configuration file
#
# mdadm will function properly without the use of a configuration file,
# but this file is useful for keeping track of arrays and member disks.
# In general, a mdadm.conf file is created, and updated, after arrays
# are created. This is the opposite behavior of /etc/raidtab which is
# created prior to array construction.
#
#
# the config file takes two types of lines:
#
#    DEVICE lines specify a list of devices of where to look for
#      potential member disks
#
#    ARRAY lines specify information about how to identify arrays so
#      so that they can be activated
#


# You can have more than one device line and use wild cards. The first 
# example includes SCSI the first partition of SCSI disks /dev/sdb,
# /dev/sdc, /dev/sdd, /dev/sdj, /dev/sdk, and /dev/sdl. The second 
# line looks for array slices on IDE disks.
#
#DEVICE /dev/sd[bcdjkl]1
#DEVICE /dev/hda1 /dev/hdb1
#
# The designation "partitions" will scan all partitions found in
# /proc/partitions
DEVICE partitions


# ARRAY lines specify an array to assemble and a method of identification.
# Arrays can currently be identified by using a UUID, superblock minor number,
# or a listing of devices.
#
#    super-minor is usually the minor number of the metadevice
#    UUID is the Universally Unique Identifier for the array
# Each can be obtained using
#
#     mdadm -D <md>
#
# To capture the UUIDs for all your RAID arrays to this file, run these:
#    to get a list of running arrays:
#    # mdadm -D --scan >>/etc/mdadm.conf
#    to get a list from superblocks:
#    # mdadm -E --scan >>/etc/mdadm.conf
#
#ARRAY /dev/md0 UUID=3aaa0122:29827cfa:5331ad66:ca767371
#ARRAY /dev/md1 super-minor=1
#ARRAY /dev/md2 devices=/dev/hda1,/dev/hdb1
#
# ARRAY lines can also specify a "spare-group" for each array.  mdadm --monitor
# will then move a spare between arrays in a spare-group if one array has a
# failed drive but no spare
#ARRAY /dev/md4 uuid=b23f3c6d:aec43a9f:fd65db85:369432df spare-group=group1
#ARRAY /dev/md5 uuid=19464854:03f71b1b:e0df2edd:246cc977 spare-group=group1
#


# When used in --follow (aka --monitor) mode, mdadm needs a
# mail address and/or a program.  To start mdadm's monitor mode, add
# "mdadm" to your DAEMONS array in /etc/rc.conf
#
# If the lines are not found, mdadm will exit quietly
#MAILADDR root@mydomain.tld
#PROGRAM /usr/sbin/handle-mdadm-events
ARRAY /dev/md1 level=raid1 num-devices=2 metadata=0.90 UUID=d921b73d:19b91554:99a4f6e0:b2f0f45c
ARRAY /dev/md2 level=raid1 num-devices=2 metadata=0.90 UUID=2f1d1eb5:bcd22224:d16efa7d:897f4cac
ARRAY /dev/md3 level=raid0 num-devices=2 metadata=0.90 UUID=7a809522:8143b514:a88c7b4c:1a038dfd
ARRAY /dev/md4 level=raid0 num-devices=2 metadata=0.90 UUID=c19859ce:d29dcb55:8a97e6a4:892b0fc7

menu.lst

# Config file for GRUB - The GNU GRand Unified Bootloader
# /boot/grub/menu.lst

# DEVICE NAME CONVERSIONS 
#
#  Linux           Grub
# -------------------------
#  /dev/fd0        (fd0)
#  /dev/sda        (hd0)
#  /dev/sdb2       (hd1,1)
#  /dev/sda3       (hd0,2)
#

#  FRAMEBUFFER RESOLUTION SETTINGS
#     +-------------------------------------------------+
#          | 640x480    800x600    1024x768   1280x1024
#      ----+--------------------------------------------
#      256 | 0x301=769  0x303=771  0x305=773   0x307=775
#      32K | 0x310=784  0x313=787  0x316=790   0x319=793
#      64K | 0x311=785  0x314=788  0x317=791   0x31A=794
#      16M | 0x312=786  0x315=789  0x318=792   0x31B=795
#     +-------------------------------------------------+
#  for more details and different resolutions see
#  http://wiki.archlinux.org/index.php/GRUB#Framebuffer_Resolution 

# general configuration:
timeout   5
default   0
color light-blue/black light-cyan/blue

# boot sections follow
# each is implicitly numbered from 0 in the order of appearance below
#
# TIP: If you want a 1024x768 framebuffer, add "vga=773" to your kernel line.
#
#-*

# (0) Arch Linux
title  Arch Linux  [/boot/vmlinuz26]
root   (hd0,0)
kernel /vmlinuz26 root=/dev/md3 ro md=1,/dev/hda1,/dev/hdb1 md=0,/dev/hda3,/dev/hdb3
initrd /kernel26.img

# (1) Windows
#title Windows
#rootnoverify (hd0,0)
#makeactive
#chainloader +1

I really think my menu.lst is not correct. Can someone please help me correct it and any other mistakes/problems that one sees.

- thanks

EDIT: please move to installation section, my apologizes.

Last edited by delacruz (2009-06-12 05:41:46)

Uruz2012 · 2009-06-12 06:34:41

I think you need to change md3 to hd0?

I'm not 100% on that but afaik grub doesn't recognize anythin but the hd0,0 or a uuid to point to a drive.

edit: Here's a copy of the same part of my menu.lst

# (0) Arch Linux
title Arch Linux
root (hd0,2)
kernel /boot/vmlinuz26 resume=/dev/disk/by-uuid/fc932866-6334-40f9-a495-548aeea4fed8 root=/dev/disk/by-uuid/550b6cbe-5ed5-4dc5-b8db-66ed8d498d6a ro
initrd /boot/kernel26.img

My grub is installed to the same partition as Arch so I didn't need to fiddle around with it that much.

Last edited by Uruz2012 (2009-06-12 06:40:26)

delacruz · 2009-06-12 06:54:36

hd0 did not work

and what is resume?

fukawi2 · 2009-06-12 10:07:43

What is your mkinitcpio.conf?

Remove the 'raid' hook and add the 'mdadm' hook like this:

HOOKS="base udev autodetect pata scsi sata mdadm filesystems"

Remember that order is important!

Arch Linux

#1 2009-06-12 05:39:27

raid installation

#2 2009-06-12 06:34:41

Re: raid installation

#3 2009-06-12 06:54:36

Re: raid installation

#4 2009-06-12 10:07:43

Re: raid installation

Board footer