1 |
Try appending md=3,/dev/sdb3,/dev/sdc3 to the kernel command line |
2 |
parameters. |
3 |
|
4 |
On 04/04/2010 01:45 AM, Albert Hopkins wrote: |
5 |
> On Sat, 2010-04-03 at 16:07 -0700, Mark Knecht wrote: |
6 |
>> The install is complete but it won't boot. grub finds the kernel |
7 |
>> and starts booting but then I get the typical VFS file sync error as |
8 |
>> the kernel starts looking for the install on /dev/md3. What I'm not |
9 |
>> understanding is how does the boot process get the information |
10 |
>> required to assemble the RAID device. |
11 |
> |
12 |
> GRUB does not assemble raid. That's why it only works with RAID1. |
13 |
> |
14 |
> By your own account, GRUB has succeeded, therefore GRUB is not the |
15 |
> problem. |
16 |
> |
17 |
> The problem is the kernel |
18 |
> |
19 |
> The kernel assembles RAID by looking for partitions of with the Linux |
20 |
> RAID partition type, finding out what kind of RAID they are, and |
21 |
> assembling them (according to their RAID volume UUID). |
22 |
> |
23 |
> You apparently only have one RAID volume. It's probably being assigned |
24 |
> to /dev/md0, yet you are passing root=/dev/md3.. not sure why you are |
25 |
> doing that. |
26 |
|
27 |
-- |
28 |
Xavier Parizet |
29 |
YaGB : http://gentooist.com |
30 |
GPG : C7DC B10E FC21 63BE |
31 |
B453 D239 F6E6 DF65 1569 91BF |