public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
Search results ordered by [date|relevance]  view[summary|nested|Atom feed]
thread overview below | download: 
* Re: [gentoo-user] General weirdness - a tale of woe.
  @ 2015-05-27 13:21 99% ` Rich Freeman
  0 siblings, 0 replies; 1+ results
From: Rich Freeman @ 2015-05-27 13:21 UTC (permalink / raw
  To: gentoo-user

On Wed, May 27, 2015 at 7:59 AM, Peter Humphrey <peter@prh.myzen.co.uk> wrote:
> This is a KDE amd64 system with /usr under / and no initrd.

Just to clarify, is /usr on a separate filesystem, or the same as /?
I don't think that is your problem in any case, but it might be
relevant.

> ... bunch of KDE stuff

I've had the odd KDE issue along the way, like having extra panels
spawning off-screen with notifications showing up in wierd places as a
result.  That doesn't sound like your specific problem, but assuming a
KDE expert doesn't chime in here you might consider pursuing those
questions in a KDE forum/list, or maybe even in the Gentoo forums
where there is a section for desktop environments.  Again, assuming
somebody doesn't recognize your problem here.

> The last thing is that at reboot the RAID-1 volume manager often fails to
> start. It says afterwards that it's running, but all the /dev/vg7/* are absent
> (that's where the logical volumes live). The file system root lives on /dev/md5
> with metadata < 1.0, while /dev/vg7 has metadata >1.0. The fact that it
> happens often but not always suggests a timing problem to me.

I've sometimes seen this sort of thing with kernel raid autodetection,
especially with metadata <1.  I suspect that an initramfs might help
you out, assuming the filesystems on that RAID are useful in early
boot.  However, openrc and the raid init scripts should do a good job
of configuring your raid if your mdadm.conf and such is correct, so if
you don't need those filesystems until late in boot I don't think an
initramfs will make much of a difference, since it would likely use
the exact same userspace tools as openrc already does.  Make sure your
mdadm.conf is set up to search all devices that could contain RAID
(drive device names can get re-ordered), and it doesn't hurt to put
ARRAY lines in mdadm.conf to give it hints.

I do recommend just using an initramfs if you're using RAID for
early-boot filesystems.  While it is an extra step I find it is much
more robust than kernel autodetection (and if something goes wrong you
usually get an emergency shell where you can just manually get the
RAID up and type exit and watch the system boot).  It also lets you
use metadata >1 and I find that to be a lot more robust in general.
With an initramfs you can basically boot anything you can mount from a
booted system, but without one your options are more limited.

-- 
Rich


^ permalink raw reply	[relevance 99%]

Results 1-1 of 1 | reverse | options above
-- pct% links below jump to the message on this page, permalinks otherwise --
2015-05-27 11:59     [gentoo-user] General weirdness - a tale of woe Peter Humphrey
2015-05-27 13:21 99% ` Rich Freeman

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox