Re: [gentoo-user] Failure to start md at boot

[Peter Humphrey <peter@prh.myzen.co.uk>]

On Sunday 31 May 2015 16:34:19 Mick wrote:
> On Sunday 31 May 2015 16:09:22 Peter Humphrey wrote:
> > On Sunday 31 May 2015 15:18:19 Peter Humphrey wrote:
> > > On Sunday 31 May 2015 13:06:58 Mick wrote:
> > > > On Sunday 31 May 2015 10:01:43 Peter Humphrey wrote:
> > > > > On Friday 29 May 2015 01:10:52 I wrote:
> > > > > > OK, so this is what I have at present. I haven't booted with it
> > > > > > yet
> > > > > > to test it - I'll do that in the morning:
> > > > > > 
> > > > > > DEVICE /dev/sd[abcde][123456789]
> > > > > > ARRAY /dev/md1 UUID=ea156c7f:183ca28e:c44c77eb:7ee19756
> > > > > > ARRAY /dev/md5 UUID=e7640378:966a5b3a:c44c77eb:7ee19756
> > > > > > ARRAY /dev/md7 UUID=c2d056c4:9118021f:ad73c633:b38fa97c
> > > > > 
> > > > > Specifying the UUIDs hasn't helped. I still get failure to start
> > > > > /dev/md7
> > > > > during boot as often as not.
> > > > 
> > > > Did you try my suggestion to (also) specify the metadata type to see
> > > > if
> > > > it makes a difference?
> > > 
> > > Ah, no, I missed that. I'll try it and see how it goes.
> > 
> > It hasn't helped.
> > 
> > I think I know what the problem is: namely, that I haven't discovered how
> > to set up lvmetad. I get an error "lvmetad is running but disabled" but if
> > I enable it in /etc/lvm/lvm.conf I get a different error. What should I be
> > doing here? Google hasn't helped me.
> > 
> > In my own defence, I did mention this on Wednesday.
> 
> Sorry, but I don't really know much about LVM because I've never used it in
> anger.  I just (re)size my partitions as I need them to be.  However, I see
> this mentioned in the Wiki:
> 
> https://wiki.gentoo.org/wiki/Talk:LVM

Yes, I'd seen that, and several other sites that shed a little light.

One thing that does seem to have helped is that I've removed mdraid from the 
boot run level. Bug 521280 refers. It seems that mdraid must be in the boot 
run level during installation and the first few boots of the system, but should 
be removed again when the error "mdadm: No arrays found in config file or 
automatically" starts appearing at boot time.

-- 
Rgds
Peter