| 1 |
Am 03.05.2014 13:39, schrieb Stefan G. Weichinger: |
| 2 |
|
| 3 |
> Booted with "rd.auto=1" and now I also get a funny start job |
| 4 |
> running/waiting for /dev/sda1 (/ on the SSD). |
| 5 |
> |
| 6 |
> Oh my! :-) |
| 7 |
> |
| 8 |
> pasta now. |
| 9 |
|
| 10 |
So, back from speed-lunch now ;-) |
| 11 |
|
| 12 |
While cooking the pasta I got a bit further: |
| 13 |
|
| 14 |
Box boots now with kernel 3.14.1 and with commented LVs in fstab. |
| 15 |
|
| 16 |
When I login and check there are no mdadm-raids assembled. |
| 17 |
|
| 18 |
When I "mdadm -A --scan" they get correctly assembled: |
| 19 |
|
| 20 |
|
| 21 |
# cat /proc/mdstat |
| 22 |
Personalities : [raid1] |
| 23 |
md4 : active raid1 sdb3[0] sdc6[2] |
| 24 |
52395904 blocks super 1.2 [2/2] [UU] |
| 25 |
|
| 26 |
md1 : active raid1 sdb6[0] sdc3[1] |
| 27 |
623963072 blocks [2/2] [UU] |
| 28 |
|
| 29 |
(Don't ask for the strange setup with sdb3/sdc6 and sdb6/sdc3, |
| 30 |
historically grown somehow ...) |
| 31 |
|
| 32 |
"vgchange -ay" then gets me all my LVs. Great so far. |
| 33 |
|
| 34 |
So the question is, what part of the whole setup should now assemble the |
| 35 |
arrays? |
| 36 |
|
| 37 |
I think, dracut, right? |
| 38 |
|
| 39 |
So I will now test booting with these funny "rd.auto" kernel line |
| 40 |
parameters ... |
| 41 |
|
| 42 |
Has mdadm.service to be enabled as well? Or is that redundant in a way? |
| 43 |
|
| 44 |
Stefan |
Archives