| 1 |
On 25/08/2014 12:17, Peter Humphrey wrote: |
| 2 |
|
| 3 |
<snip> |
| 4 |
|
| 5 |
> Well, it was simple. I just said "rc-update del mdraid boot" and all is now |
| 6 |
> well. I'd better revisit the docs to see if they still give the same advice. |
| 7 |
> |
| 8 |
> -- Regards Peter |
| 9 |
|
| 10 |
Very interesting indeed. I now wonder if this is a race condition |
| 11 |
between the init script running `mdadm -As` and the fact that the mdadm |
| 12 |
package installs udev rules that allow for automatic incremental |
| 13 |
assembly? Refer to /lib/udev/rules.d/64-md-raid.rules and you'll see |
| 14 |
that it calls `mdadm --incremental` for newly added devices. |
| 15 |
|
| 16 |
With that in mind, here's something else for you to try. Doing this will |
| 17 |
render these udev rules null and void: |
| 18 |
|
| 19 |
# touch /etc/udev/rules.d/64-md-raid.rules |
| 20 |
|
| 21 |
Thereafter, the mdraid script will be the only agent trying to assemble |
| 22 |
the 1.x metadata arrays so make sure that it is re-enabled. |
| 23 |
|
| 24 |
I'm not actually sure that there is any point in calling mdadm -As where |
| 25 |
the udev rules are present. I would expect it to be one approach or the |
| 26 |
other, but not both at the same time. |
| 27 |
|
| 28 |
Incidentally, the udev rules were a source of controversy in the |
| 29 |
following bug. Not everyone appreciates that they are installed by default. |
| 30 |
|
| 31 |
https://bugs.gentoo.org/show_bug.cgi?id=401707 |
| 32 |
|
| 33 |
--Kerin |
Archives