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