| View previous topic :: View next topic |
| Author |
Message |
sglorz
n00b
Joined: 09 Jun 2011
Posts: 13
|
 Posted: Wed Jul 20, 2011 2:42 pm Post subject: |
 |
|
| Yes it helps! Thanks! |
|
| Back to top |
|
 |
wildbug
n00b
Joined: 07 Oct 2007
Posts: 73
|
| Posted: Thu Jul 21, 2011 6:46 pm Post subject: |
|
|
| NeddySeagoon wrote: | The kernel will only auto assemble raid sets with raid superblock version 0.90. The default now is version 1.2
If your /boot is raided, is must be raid1 with superblock version 0.90 or grub will not start. |
I don't think this is true. I know I've read that, too (/usr/src/linux/Documentation/md.txt, IIRC), but I have 0.90, 1.1, and 1.2 arrays on my system, including unpartitioned volumes (i.e., /dev/sdk, not /dev/sdk1, so no 0xFD), and all are auto-assembled. |
|
| Back to top |
|
|
wildbug
n00b
Joined: 07 Oct 2007
Posts: 73
|
| Posted: Thu Jul 21, 2011 7:05 pm Post subject: |
|
|
Hmm, I might be wrong about my previous post. md reports that it's looking for 0.90 superblocks when it assembles my root device; the other devices aren't assembled until about 11 seconds later (dmesg). Is OpenRC responsible for that? I'm not using /etc/init.d/mdadm.
Anyway...
There's another way to start md devices at boot other than by autodetection. You can supply the md= kernel parameter. I.e.,
| Code: | | kernel /linux-2.6.39 root=/dev/md127 md=127,/dev/sda,/dev/sdb,/dev/sdc raid=noautodetect |
I think this works with all superblock versions. See http://www.kernel.org/doc/Documentation/md.txt |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Kernel & Hardware
