mdadm running on hosts without raid devices

[Jeff Waugh]

the mdadm init script could check to see if there are any devices before running
mdadm. is this a good idea? what will we need to check in /proc/mdstat?

 * > 2 lines long?

 * length of first line ("Personalities : [raid1]")

 * existence of md* lines?

[Matt Zimmerman (mdz)]

We can either do that, or chicken out and use the existing START_DAEMON
configuration parameter to disable it by default.

It doesn't really cause any harm to run all the time, but it would be nice if it
were smarter

[Stan Pinte (stanpinte)]

(In reply to comment #0)
> the mdadm init script could check to see if there are any devices before running
> mdadm. is this a good idea? what will we need to check in /proc/mdstat?
>
> * > 2 lines long?
>
> * length of first line ("Personalities : [raid1]")
>
> * existence of md* lines?

My installation is freezing at mdadm configuration...

(ps | grep mdadm says two root processes "invoke-rc.d mdadm-raid start")

I have two master hard drives...(one is 80 gig, and the other 10 gig).

I will try again with the second HD disabled.

I would suggest to disable mdadm by default...

Stan.

[Matt Zimmerman (mdz)]

(In reply to comment #2)
> My installation is freezing at mdadm configuration...
>
> (ps | grep mdadm says two root processes "invoke-rc.d mdadm-raid start")

If so, this is an entirely separate bug which should be reported. I've never
seen this happen, and have received no other reports of such behaviour, so
include as much information as possible to try to help us reproduce the problem.

[Jeff Waugh (jdub)]

Fixed in 1.8.1-1ubuntu2.

[Matt Zimmerman (mdz)]

*** Bug 13570 has been marked as a duplicate of this bug. ***

[Mikkel Kamstrup Erlandsen (kamstrup)]

Upon boot I get and error message like: "adm: No arrays found in config file". I
have no raid or anything fancy, I don't get why I have to get an error message
then :)

This is on Hoary updated this morning.

[Matt Zimmerman (mdz)]

This bug was fixed some time ago.

There was recently a similar bug, where the installer created
/etc/mdadm/mdadm.conf on systems without RAID, causing the message described in
comment #6. That bug was fixed in base-installer 1.15ubuntu5, released Monday,
March 7th.

The workaround to suppress the message is: sudo rm -f /etc/madm/mdadm.conf

[Colin Watson (cjwatson)]

(In reply to comment #7)
> There was recently a similar bug, where the installer created
> /etc/mdadm/mdadm.conf on systems without RAID, causing the message described in
> comment #6. That bug was fixed in base-installer 1.15ubuntu5, released Monday,
> March 7th.

Minor correction: that's mdcfg 1.09ubuntu3, not base-installer.

[Trouilliez vincent (vincent-trouilliez-modulonet)]

(In reply to comment #7)
> This bug was fixed some time ago.
>
> There was recently a similar bug, where the installer created
> /etc/mdadm/mdadm.conf on systems without RAID, causing the message described in
> comment #6. That bug was fixed in base-installer 1.15ubuntu5, released Monday,
> March 7th.
>
> The workaround to suppress the message is: sudo rm -f /etc/madm/mdadm.conf

Thanks, worked like a charm :-)

--
Vince