You are not logged in.
Hello
I'm trying to install Arch using dmraid, mostly following the Fake-RAID guide in the wiki. I'm using the 2008.04-RC iso. What I do different is that I make my own dmraid package with this patch, to support Raid10 on my Intel board. I personally don't think this is related to my problem, but you never know.
Anyways, the installation was going great, I just followed the guide. I rebooted, grub was loading fine, even my old Windows installation was happy. Linux, however, was less happy. It spews out tons of "attempt to access beyond end of device"'s, doesn't find the root partition, and throws me to a rescue prompt.
ramfs$ dmraid -ay
RAID set "isw_iifadcbec_Volume0-1" already active
RAID set "isw_iifadcbec_Volume0-0" already active
device-mapper: table: 254:2: mirror: unknown target type
device-mapper: ioctl: error adding target to table
ERROR: device-mapper target type "mirror" not in kernel
ramfs$ echo /dev/mapper/*
/dev/mapper/control
/dev/mapper/isw_iifadcbec_Volume0-0
/dev/mapper/isw_iifadcbec_Volume0-1
When booting from the install cd, /dev/mapper also contains
/dev/mapper/isw_iifadcbec_Volume01
/dev/mapper/isw_iifadcbec_Volume02
...
I suspect that this problem appears because the init image does not contain the module "dm-mirror". Does anyone know how to include this module, or perhaps I have a completely different problem?
Offline
I'll continue my monologue with my latest problems. I added a custom dm-mirror hook in mkinitcpio.conf to include the module, to my surprise it worked! Unfortunately, behind that door was another door, and I'm now completely clueless:
:: Running Hook [filesystems]
:: Loading root filesystem module...ext3
Waiting for devices to settle...done.
:: Initramfs Completed - control passing to kinit
IP-Config: no devices to configure
Waiting 0s before mounting root device...
kinit: Cannot open root device dm-7(254,7)
kinit: init not found!It appears that something can read from my raid volume, as an ext2 module is loaded if I tell the kernel that my boot partition is root. I've verified that there actually is a /sbin/init on the root partition. I've been running mkinitcpio more times than I can count, but the problem just won't go away... Is there anything else I can do?
Offline
I suggest that the dm-raid setup is removed by udev during the boot sequence causing the kinit bomb.
See on the net: How to boot from raid using dm-raid .....
Perhaps it will help.....
Prediction...This year will be a very odd year!
Hard work does not kill people but why risk it: Charlie Mccarthy
A man is not complete until he is married..then..he is finished.
When ALL is lost, what can be found? Even bytes get lonely for a little bit! X-ray confirms Iam spineless!
Offline
Uwolfer might be able to help since he fixed the hooks on the now in current dmraid package.
Offline
Thanks for your answers. I found the How to boot from raid using dmraid page. But, I don't have enough skills to incorporate his changes (or even see all his changes for the matter) into Arch and mkinitcpio in a way that will not break horribly every time I try to update. Plus it seems to just work without this for most people, I wonder why it doesn't work for me...
I'll try contacting Uwolfer.
Offline
I do not really have an idea..
What I have changed in /etc/mkinitcpio.conf:
MODULES="pata_jmicron ext3"
Here you probably need to add your "own" modules.
HOOKS="base udev sata dmraid usbinput keymap filesystems"
Offline
I'd go for a try with regular raid0 or raid1 just to check the original dmraid and see if the drivers work as they should. Then you'd at least know if the problem is patch-related.
Offline