+ Thomas -Balu- Walter <tw@itreff.de> [18.06.02 11:25]:
[root=/dev/md1 not working]
Update - I am getting closer :)
One reason why it did not work here was that I had to create
the initrd in chroot (the mounted md-devices the original system got
copied to), this was it got /dev/md*, raidmodules and
other things needed to get raid running into the initrd.
I did not even have to change the partition type to autodetect, since
raidstart and such are available and get started in the created initrd.
(master = first ide controller, secondary = second IDE controller, no
master/slave hdd)
But now I am stuck and booting while simulating a broken secondary IDE
controller.
If I take off the master cable (powered off of course) I can boot into
the raid - and get the following messages:
md: could not lock [dev 03:03] sero-size? Marking faulty
md: could not import [dev 03:03], trying to mount raid nevertheless
md: autorun
...
former device [dev 03:03] is unavailable, removing from array
...
So it just ignores hda and boots into the remaining mirrored hdc.
But after rebuilding the raidset and removing the cable to the secondary
controller i get:
ide0 on 0x1f0-0x1f7, 0x 3f6 on IRQ14
md: could not lock [dev 16:03] sero-size? Marking faulty
md: could not import [dev 16:03]
md: autostart [dev 16:03] failed
/dev/md1: invalid argument
...
Kernel panic, because of missing root.
To fix I've tried to make the partitions raid-autodetect, created a new
initrd (because the old one still had "failed-disk" in it) and finally
added "
disk=/dev/hda
bios=0x80
disk=/dev/hdc
bios=0x80
" to lilo.conf.
with no luck - Why does it not "try to mount raid nevertheless" this
way?
Balu
-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
