Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#23868 - [mdadm] error on startup scanning arrays for errors
Attached to Project:
Arch Linux
Opened by Jonathan Liu (net147) - Thursday, 21 April 2011, 10:51 GMT
Last edited by Tobias Powalowski (tpowa) - Saturday, 23 April 2011, 19:32 GMT
Opened by Jonathan Liu (net147) - Thursday, 21 April 2011, 10:51 GMT
Last edited by Tobias Powalowski (tpowa) - Saturday, 23 April 2011, 19:32 GMT
|
DetailsDescription:
An error message is shown on mdadm startup: "mdadm: Only one autorebuild process allowed in scan mode, aborting". The daemon loads successfully but the command "mdadm --monitor --oneshot --scan" fails with the aforementioned error message. I think "mdadm --monitor --oneshot --scan" should be removed as it doesn't seem to be needed anymore anyway (see https://bugs.archlinux.org/task/23691#comment74954). Additional info: * mdadm 3.2.1-2 Steps to reproduce: * /etc/rc.d/mdadm stop * /etc/rc.d/mdadm start |
This task depends upon
Closed by Tobias Powalowski (tpowa)
Saturday, 23 April 2011, 19:32 GMT
Reason for closing: Fixed
Additional comments about closing: 3.2.1-3
Saturday, 23 April 2011, 19:32 GMT
Reason for closing: Fixed
Additional comments about closing: 3.2.1-3