| 1 |
On Sat, 3 Apr 2010 16:07:06 -0700, Mark Knecht wrote: |
| 2 |
|
| 3 |
> The install is complete but it won't boot. grub finds the kernel |
| 4 |
> and starts booting but then I get the typical VFS file sync error as |
| 5 |
> the kernel starts looking for the install on /dev/md3. What I'm not |
| 6 |
> understanding is how does the boot process get the information |
| 7 |
> required to assemble the RAID device. By hand in the non-RAID install |
| 8 |
> I do this: |
| 9 |
> |
| 10 |
> keeper ~ # mdadm -A /dev/md3 /dev/sdb3 /dev/sdc3 |
| 11 |
> mdadm: /dev/md3 has been started with 2 drives. |
| 12 |
> keeper ~ # cat /proc/mdstat |
| 13 |
> Personalities : [raid1] |
| 14 |
> md3 : active raid1 sdb3[0] sdc3[1] |
| 15 |
> 52436092 blocks super 1.1 [2/2] [UU] |
| 16 |
> |
| 17 |
> unused devices: <none> |
| 18 |
> keeper ~ # |
| 19 |
> |
| 20 |
> but when I try to boot the RAID install it says it cannot find /dev/md3. |
| 21 |
|
| 22 |
You need to set the partition type for the RAIDed partitions to "Linux |
| 23 |
raid autodetect". You'll probably then find that the kernel sets the RAID |
| 24 |
as /dev/md0, not md3. |
| 25 |
|
| 26 |
|
| 27 |
-- |
| 28 |
Neil Bothwick |
| 29 |
|
| 30 |
"You want us to do WHAT?" - Ancient Chinese wall engineer. |
Archives