1 |
On Thu, Mar 24, 2011 at 5:33 PM, Lindsay Haisley <fmouse-gentoo@×××.com> wrote: |
2 |
> Newer versions? Kernel 2.6.36 has a config option for RAID autodetect. |
3 |
> What are you referring to here, mdadm? |
4 |
|
5 |
Even the newest kernel supports autodetect, but autodetect only works |
6 |
with a specific kind of RAID superblock, I think version 0.90. |
7 |
Different versions of mdadm create arrays with different versions of |
8 |
superblock by default. Newer versions of superblocks cannot |
9 |
(presently) be autodetected by the kernel, so anyone using a newer |
10 |
type of superblock will have to do the "manual" config like this |
11 |
anyway. |
12 |
|
13 |
As for why it's not working in your case, I really don't know, but |
14 |
hopefully you can at least get it working /somehow/ so that you can |
15 |
use your system normally to get real work done, and can investigate |
16 |
why auto-detect doesn't work the way you'd like it to with less |
17 |
urgency. I've got an old Gentoo system that takes days to update, but |
18 |
if the system is usable during that time it's not really a big deal to |
19 |
me. It's the days-long updates when the system is in an unusable state |
20 |
that are a real nightmare. |
21 |
|
22 |
> @Paul, Ah, I see! |
23 |
> |
24 |
> The component drives in a RAID-1 array have the _same_ UUID, so I would |
25 |
> assume that a line in /etc/mdadm.conf such as: |
26 |
> |
27 |
> ARRAY /dev/md0 UUID=d3176595:06cb3677:46406ca7:d12d146f |
28 |
|
29 |
Right, exactly. Sorry I didn't make it clear before. |
30 |
|
31 |
I consider it somewhat of a miracle that I ever got any of it working |
32 |
on my computer in the first place, so I'm definitely speaking from an |
33 |
"as far as I know" point of view here. It's something I set up when |
34 |
building the computer and never had to think about it again. |