1 |
Am 03.05.2014 14:17, schrieb Todd Goodman: |
2 |
> * Stefan G. Weichinger <lists@×××××.at> [140503 08:09]: |
3 |
>> Am 03.05.2014 13:39, schrieb Stefan G. Weichinger: |
4 |
>> |
5 |
>>> Booted with "rd.auto=1" and now I also get a funny start job |
6 |
>>> running/waiting for /dev/sda1 (/ on the SSD). |
7 |
>>> |
8 |
>>> Oh my! :-) |
9 |
>>> |
10 |
>>> pasta now. |
11 |
>> |
12 |
>> So, back from speed-lunch now ;-) |
13 |
>> |
14 |
>> While cooking the pasta I got a bit further: |
15 |
>> |
16 |
>> Box boots now with kernel 3.14.1 and with commented LVs in fstab. |
17 |
>> |
18 |
>> When I login and check there are no mdadm-raids assembled. |
19 |
>> |
20 |
>> When I "mdadm -A --scan" they get correctly assembled: |
21 |
>> |
22 |
>> |
23 |
>> # cat /proc/mdstat |
24 |
>> Personalities : [raid1] |
25 |
>> md4 : active raid1 sdb3[0] sdc6[2] |
26 |
>> 52395904 blocks super 1.2 [2/2] [UU] |
27 |
>> |
28 |
>> md1 : active raid1 sdb6[0] sdc3[1] |
29 |
>> 623963072 blocks [2/2] [UU] |
30 |
>> |
31 |
>> (Don't ask for the strange setup with sdb3/sdc6 and sdb6/sdc3, |
32 |
>> historically grown somehow ...) |
33 |
>> |
34 |
>> "vgchange -ay" then gets me all my LVs. Great so far. |
35 |
>> |
36 |
>> So the question is, what part of the whole setup should now assemble the |
37 |
>> arrays? |
38 |
>> |
39 |
>> I think, dracut, right? |
40 |
>> |
41 |
>> So I will now test booting with these funny "rd.auto" kernel line |
42 |
>> parameters ... |
43 |
>> |
44 |
>> Has mdadm.service to be enabled as well? Or is that redundant in a way? |
45 |
>> |
46 |
>> Stefan |
47 |
> |
48 |
> FWIW, I have a similar problem with mdadm and dracut and do something |
49 |
> similarly to what's described in: |
50 |
> |
51 |
> http://rich0gentoo.wordpress.com/2012/01/21/a-quick-dracut-module/ |
52 |
|
53 |
Thanks for the link .... I will keep it in mind ... for now I try to |
54 |
stay as close to the stuff in portage as possible (and it worked until |
55 |
yesterday ;-) ). |
56 |
|
57 |
S |