apologize in advance.Iaveoogledntilyrainurtsndaveot
found my problem.Iaveheckedutheiloocs,heEADME.raid1ile,
the linux+root+boot+raid howto, etc.A lot of the RAID1 stuff has been beat
to death, but I can't quite find my exact problem.
I'mairlyuch00bn the RAID department and this is a long post, so
please be patient.
I am using mdadm, running kernel 2.6.5 on Debian 3.0 stable (woody), on a
I have two EIDE drives (WD800JB, 80GB) of identical size and partitioned
were set to the Linux and Linux Swap partition types appropriately via
I had done the 'missing disk' installation procedure, installing Debian
on /dev/hda, mirroring the /dev/hdaN partitions to their /dev/hdcN
counterparts via tar (with the exception of swap), then used mdadm to
create 8 RAID-1 arrays with the /dev/hdaN partitions as missing and using
the appropriate /dev/hdcN partitions.Soaroood.Theystems
running with 6 out of the 8 RAID arrays synced.
The problem I am having is getting the boot and root partitions working.
I will show my DESIRED configuration, then explain the problem further.
/dev/hd[ac]10 = /dev/md6 = /
/dev/hd[ac]11 = /dev/md7 = /storage
All arrays except /dev/md0 (boot) and /dev/md6 (root) are synced.Allf
the arrays exist, but the boot partition is only running with /dev/hdc1 and
the root partition is only running with /dev/hdc10.
For starters, knowing that the array handling /boot might be tricky, I left
the boot partition of /dev/hda1 in /etc/lilo.conf and figured I would deal
with the /boot array later.
When I was providing mdadm with the names of the missing partitions in order
for it to start syncing, I used basically the same command, obviously
changing the RAID device and disk partition for each command.Whename
up to the root partition, I used:
It returned the following error message:
Checking dmesg, I see:
I thought that since maybe the system was actually booting off /dev/hda1
that it was somehow locking the disk, so 'md' couldn't lock it in order to
add it to the array.Wouldhiseorrectssumption?
To test, I started trying to get the boot RAID going.I'msingilo
22.2-3, but have also temporarily tried compiling 22.5.9 to no avail.My
intention was to use lilo to write boot info to /dev/md0, which only
consists of /dev/hdc1 for now, boot the system, then sync it by
adding /dev/hda1 to the array.Heresy?etc/lilo.conf:
I had unmounted /dev/hda1 from /boot, mounted /dev/md0 to /boot, and tried:
Now I am stuck.Theatalessageshro