Arch Linux

dotnetfireball

Member

Registered: 2005-11-07

Posts: 6

RAID Installation

Hi , i am trying to install archlinux using the latest Alpha ISO 0.8 i have read this http://wiki.archlinux.org/index.php/Ins … AID_or_LVM ,i have partitioned my two HD but it show only 1 md device "/dev/md0" how i wrong?

sorry for my english.

dotnetfireball

Member

Registered: 2005-11-07

Posts: 6

Re: RAID Installation

I have solved with mknod , but now when i try to boot the system i receive the error
kinit: cannot open root device md0(9,0)
kinit: init not found!

docloy

Member

Registered: 2006-12-12

Posts: 8

Re: RAID Installation

I have the same problem here. I have set up three arrays

/dev/md0 (/dev/sda3 & /dev/sdb3)    /
/dev/md1 (/dev/sda2 & /dev/sdb2)    /boot
/dev/md2 (/dev/sda4 & /dev/sdb4)   /home

md1 and md2 work fine but I can't boot from md0. The only possibility is that I boot from /dev/sda3 or sdb3. So how can I fix this?

Some informations:
$ df -h
Dateisystem          Größe Benut  Verf Ben% Eingehängt auf
/dev/md0               28G  3,2G   23G  13% /
none                  506M     0  506M   0% /dev/shm
/dev/md1              132M  7,5M  118M   6% /boot
/dev/md2              265G   64G  188G  26% /home

$ cat /proc/mdstat
Personalities : [raid1] [raid6] [raid5] [raid4] [linear] [multipath] [raid0] [raid10]
md2 : active raid1 sda4[0] sdb4[1]
      282141440 blocks [2/2] [UU]

md1 : active raid1 sda1[0] sdb1[1]
      136448 blocks [2/2] [UU]

md0 : active raid1 sdb3[1]
      29302464 blocks [2/1] [_U]

unused devices: <none>

WiLLiE

Member

From: Sweden

Registered: 2005-02-27

Posts: 135

Re: RAID Installation

For starters, add sda3 to your md0 raid.
Have you added the root=/dev/md0 and md=0,/dev/blabla to grub?

docloy

Member

Registered: 2006-12-12

Posts: 8

Re: RAID Installation

Thank you Willie. I've forgotten to post it. I had add the sda3 to md0 and also to grub. But then I got the same message then dotnetfireball:

kinit: cannot open root device md0(9,0)
kinit: init not found!

So I had to change in grub to /dev/sda3 to have be able to boot the system. I also used the Howto http://wiki.archlinux.org/index.php/Ins … AID_or_LVM

I read in this forum I should add to modules in mkinitcpio raid1 and raid456.
So I don't really know why it is not working. I installed it three times and I used arch linux current 0.7.2, arch linux current .0.7.2 19th Nov. 06 and also arch linux base 19th Nov 06

I hope you guys can figure it out because I don't have any other ideas and also haven't found any solutions. (sorry for my english - i hope you can get everything)

WiLLiE

Member

From: Sweden

Registered: 2005-02-27

Posts: 135

Re: RAID Installation

Strange. I followed the same guide, and for me it worked the first time. (although the guide is missing the create node part, which I had to look up myself, and the raid1 & raid456 modules.)
Perhaps re-read the guide again to make sure you haven't missed anything?

Oh and btw, I already had arch installed, so I just copied (cp -a) / and /home to my server, made the raid's, and copied them back.
Worked right away.

Post your mkinitcpio.conf, menu.lst and the output of sudo fdisk -l

docloy

Member

Registered: 2006-12-12

Posts: 8

Re: RAID Installation

Okay so here it is...

mkinitcpio.conf:

# vim:set ft=sh
# MODULES
# The following modules are loaded before any boot hooks are
# run.  Advanced users may wish to specify all system modules
# in this array.  For instance:
#     MODULES="piix ide_disk reiserfs"
MODULES="raid1 raid456"

# BINARIES
# This setting includes, into the CPIO image, and additional
# binaries a given user may wish.  This is run first, so may
# be used to override the actual binaries used in a given hook.
# (Existing files are NOT overwritten is already added)
# BINARIES are dependancy parsed, so you may safely ignore libraries
BINARIES=""

# FILES
# This setting is similar to BINARIES above, however, files are added
# as-is and are not parsed in anyway.  This is useful for config files.
# Some users may wish to include modprobe.conf for custom module options,
# like so:
#    FILES="/etc/modprobe.conf"
FILES=""

# HOOKS
# This is the most important setting in this file.  The HOOKS control the
# modules and scripts added to the image, and what happens at boot time.
# Order is important, and it is recommended that you do not change the
# order in which HOOKS are added.  Run 'mkinitcpio -H <hook>' for
# help on a given hook.
# 'base' is _required_ unless you know precisely what you are doing.
# 'udev' is _required_ in order to automatically load modules
# 'modload' may be used in place of 'udev', but is not recommended
# 'filesystems' is _required_ unless you specify your fs modules in MODULES
# Examples:
#    This setup specifies all modules in the MODULES setting above.
#    No raid, lvm, or encrypted root is needed.
#    HOOKS="base"
#
#    This setup will autodetect all modules for your system and should
#    work as a sane default
#    HOOKS="base udev autodetect ide scsi sata filesystems"
#
#    This setup will generate a 'full' image which supports most systems.
#    No autodetection is done.
#    HOOKS="base udev ide scsi sata usb filesystems"
#
#    This setup assembles an ide raid array with an encrypted root FS.
#    Note: See 'mkinitcpio -H raid' for more information on raid devices.
#    HOOKS="base udev ide filesystems raid encrypt"
#
#    This setup loads an LVM volume group on a usb device.
#    HOOKS="base udev usb filesystems lvm"
HOOKS="base raid udev autodetect ide scsi sata filesystems"
md=0,/dev/sda3,/dev/sdb3, md=1,/dev/sda1,/dev/sdb1 md=2,/dev/sda4,/dev/sdb4

------------------------------------------------------------------------------------
I also tried what happens if I change the position of raid in HOOKS.

So next - menu.lst:

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

# DEVICE NAME CONVERSIONS
#
#  Linux           Grub
# -------------------------
#  /dev/fd0        (fd0)
#  /dev/hda        (hd0)
#  /dev/hdb2       (hd1,1)
#  /dev/hda3       (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
#     +-------------------------------------------------+

# 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/vmlinuz]
root   (hd0,0)
kernel /vmlinuz26 root=/dev/sda3 ro
initrd /kernel26.img

# (1) Arch Linux (RAID1)
title  Arch Linux raid1 [/boot/vmlinuz]
root   (hd0,0)
kernel /vmlinuz26 root=/dev/md0 ro md=0,/dev/sda3,/dev/sdb3
initrd /kernel26.img

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

and fdisk -l

# fdisk -l

Platte /dev/md0: 30.0 GByte, 30005723136 Byte
2 Köpfe, 4 Sektoren/Spuren, 7325616 Zylinder
Einheiten = Zylinder von 8 × 512 = 4096 Bytes

Festplatte /dev/md0 enthält keine gültige Partitionstabelle

Platte /dev/sda: 320.0 GByte, 320072933376 Byte
255 Köpfe, 63 Sektoren/Spuren, 38913 Zylinder
Einheiten = Zylinder von 16065 × 512 = 8225280 Bytes

   Gerät  boot.     Anfang        Ende     Blöcke   Id  System
/dev/sda1   *           1          17      136521   fd  Linux raid autodetect
/dev/sda2              18         140      987997+  82  Linux Swap / Solaris
/dev/sda3             141        3788    29302560   fd  Linux raid autodetect
/dev/sda4            3789       38913   282141562+  fd  Linux raid autodetect

Platte /dev/sdb: 320.0 GByte, 320072933376 Byte
255 Köpfe, 63 Sektoren/Spuren, 38913 Zylinder
Einheiten = Zylinder von 16065 × 512 = 8225280 Bytes

   Gerät  boot.     Anfang        Ende     Blöcke   Id  System
/dev/sdb1   *           1          17      136521   fd  Linux raid autodetect
/dev/sdb2              18         140      987997+  82  Linux Swap / Solaris
/dev/sdb3             141        3788    29302560   fd  Linux raid autodetect
/dev/sdb4            3789       38913   282141562+  fd  Linux raid autodetect

Platte /dev/md1: 139 MByte, 139722752 Byte
2 Köpfe, 4 Sektoren/Spuren, 34112 Zylinder
Einheiten = Zylinder von 8 × 512 = 4096 Bytes

Festplatte /dev/md1 enthält keine gültige Partitionstabelle

Platte /dev/md2: 288.9 GByte, 288912834560 Byte
2 Köpfe, 4 Sektoren/Spuren, 70535360 Zylinder
Einheiten = Zylinder von 8 × 512 = 4096 Bytes

Festplatte /dev/md2 enthält keine gültige Partitionstabelle

------------------------------------------------------------------------------------

If there is anything in German which I should translate in English just ask me and I try to. And thank you for your help - I hope we can fix it!

WiLLiE

Member

From: Sweden

Registered: 2005-02-27

Posts: 135

Re: RAID Installation

Ok, I will take a closer look when I get home from work tomorrow.

You say you can't boot from /dev/md0, but yet your df -h says your /dev/md0 is mounted at / ?

And the md=x line in mkinitcpio.conf, I just think the guide was unclear and it should'nt be there. I didn't put it there, and it works anyway.

Oh, and you executed:
mkinitcpio -g /boot/kernel26.img
and not:
mkinitcpio -g /boot/kernel26beyond.img
?

And check your last lines in /etc/mdadm.conf. (especially md0)
Perhaps you forgot to update md0? (check the output of
mdadm -D --scan)

docloy

Member

Registered: 2006-12-12

Posts: 8

Re: RAID Installation

Yes I executed mkinitcpio -g /boot/kernel26.img

These are the last lines from /etc/mdadm.conf

ARRAY /dev/md0 level=raid1 num-devices=2 UUID=51611a07:46c1407b:6c861d0c:975344$
ARRAY /dev/md1 level=raid1 num-devices=2 UUID=5a76afd7:b5cfb8ec:5f5da1c0:395ce5$
ARRAY /dev/md2 level=raid1 num-devices=2 UUID=afc52df8:4764e094:8ec2bb73:d2e308$

And that's the output from mdadm -D --scan

# mdadm -D --scan
ARRAY /dev/md0 level=raid1 num-devices=2 UUID=51611a07:46c1407b:6c861d0c:97534421
ARRAY /dev/md1 level=raid1 num-devices=2 UUID=5a76afd7:b5cfb8ec:5f5da1c0:395ce5fb
ARRAY /dev/md2 level=raid1 num-devices=2 UUID=afc52df8:4764e094:8ec2bb73:d2e308c2

I don't know how to discribe it, but it seems like the system isn't able to build the array when I start it. So i can't boot from md0. But while it is booting from sda3 it builds/manages the arrays. I don't know.

WiLLiE

Member

From: Sweden

Registered: 2005-02-27

Posts: 135

Re: RAID Installation

What filesystem did you put on /dev/md0? etx3? reiserfs?

docloy

Member

Registered: 2006-12-12

Posts: 8

Re: RAID Installation

I used for all partitions ext3.

WiLLiE

Member

From: Sweden

Registered: 2005-02-27

Posts: 135

Re: RAID Installation

Sorry, much work lately. What's the status?

docloy

Member

Registered: 2006-12-12

Posts: 8

Re: RAID Installation

No problem, but the status is still the same. I have no ideas why it doesn't work. And I can't understand why md1 and md2 work fine but I can't boot from md0. Maybe you have an other idea?

perg

Member

Registered: 2007-01-22

Posts: 3

Re: RAID Installation

Hi, I have the same problem, with the same error message. I can also boot from sda3 or sdb3, and md0 will be mounted to /. And as with docloy, the md0 array has then lost one disk. I'm using reiserfs.
The strange thing is that the boot from md0 works approximately one out of 5 times.

2eleven

Member

Registered: 2007-01-23

Posts: 6

Re: RAID Installation

I am having the exact same issue after upgrading from 0.7.1 to current and following the steps in the raid doc referenced above for mkinitcpio and grub. My system boots successfully about every 5th try. All other times it panics with:

:: Initramfs Completed - control passing to kinit
IP-Config: no devices to configure
md: Will configure md1 (super-block) from /dev/sda2,/dev/sdb2,/dev/sdc2,/dev/sdd
2, below.
kinit: Unable to mount root fs on device md1(9,1)
kinit: init not found!
Kernel panic - not syncing: Attempted to kill init!

My / filesystem is /dev/md1, /boot is /dev/md0.

Hope someone can figure this out. I'm about to wipe my hard drive and reinstall 0.7.1 (or maybe I just need to back out mkinitcpio and return to using mkinitrd?).

Thanks,

John

2eleven

Member

Registered: 2007-01-23

Posts: 6

Re: RAID Installation

OK - I think I've solved my problem (at least I've rebooted about 10 times with no problems). Out of desperation, I just started experimenting with mkinitcpio.conf and I added ext3 to the MODULES list. I'm not sure why it works, but it seems to do the trick.

Hopefully this will be helpful to some of the other people here experiencing similar problems.

John

perg

Member

Registered: 2007-01-22

Posts: 3

Re: RAID Installation

Putting reiserfs in the MODULES list didn't help, but rootfstype=reiserfs did it for me.
Thanks

STiAT

Member

From: Vienna, Austria

Registered: 2004-12-23

Posts: 606

Re: RAID Installation

hmh, a raid setup util would be nice... even when it's just a guided install and archers have to do some settings on their own...

Not even ubuntu features RAID (in my case 0) installation by default... i also have enough problems getting my (once again) newly bought system up right now, my first touch with stripe (hardware) raid..

Already 4 arch machines then ... i'm getting raided by arch

Last edited by STiAT (2007-04-03 22:59:12)

---

Ability is nothing without opportunity.