All of lore.kernel.org
 help / color / mirror / Atom feed
* Reasons why mdmon is not starting?
@ 2011-12-09 20:05 Joachim Achtzehnter
  0 siblings, 0 replies; only message in thread
From: Joachim Achtzehnter @ 2011-12-09 20:05 UTC (permalink / raw)
  To: linux-raid

Hi,

When trying to understand why an existing Intel RAID1 volume always ends 
up in read-only state during a Debian installation attempt I saw from 
various posts on mailing lists that this is likely because mdmon isn't 
running. What possible reasons cause mdmon to exit?

I've tried several installation images and some have old versions of 
mdadm, which explains the problem for those cases, but I've also tried a 
recent live CD with the latest version (3.2.2), and I've tried starting 
the array manually, also with the latest version of mdadm/mdmon 
installed in /sbin. Somehow, mdmon either doesn't get started by mdadm 
or it exits prematurely without any indication of reasons in syslog.

When I try to start mdmon in a console it immediately exits without any 
message. What might be causing this? Any suggestions what to try?

Thanks,

Joachim


-- 
work:	joachima@netacquire.com		http://www.netacquire.com
home:	joachim@kraut.ca		http://www.kraut.ca

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2011-12-09 20:05 UTC | newest]

Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2011-12-09 20:05 Reasons why mdmon is not starting? Joachim Achtzehnter

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.