From: NeilBrown <neilb@suse.com>
To: Gareth Evans <donotspam@fastmail.fm>
Cc: linux-raid@vger.kernel.org
Subject: Re: mdadm/Software RAID problems
Date: Thu, 25 Jun 2015 09:21:32 +1000 [thread overview]
Message-ID: <20150625092132.5791ab5f@noble> (raw)
In-Reply-To: <1434739736.4161728.300185905.45F829A7@webmail.messagingengine.com>
On Fri, 19 Jun 2015 19:48:56 +0100 Gareth Evans <donotspam@fastmail.fm>
wrote:
> Having failed in my first attempt at setting up encrypted software RAID on Ubuntu 14.04.2, I discovered there seem to be many and various problems with software RAID on Ubuntu and Debian at least.
>
> For example, I have found via testing on KVM and VirtualBox (with and on Ubuntu 14.04.2 and with Debian 8.1) that:
>
> 1. Encrypted RAID doesn't boot after installation (no volume groups found, with unencrypted raided /boot)
> 2. Degraded unencrypted RAID doesn't boot (loops on "Intermittently starting RAID arrays..." with a few lines of related output)
> 3. /etc/initramfs-tools/conf.d/mdadm doesn't seem to exist as the Ubuntu Server Guide suggests it should
> 4. adding bootdegraded=true to grub options at boot seems to have no effect.
>
> The second point above seems particularly concerning because it would seem (unencrypted) software RAID (which works well enough while it's working) fails precisely when it is needed, which rather defeats the point.
>
> I have found lots of bug reports, some still "new" and of "undecided" importance after several years, for various problems, but not many solutions.
>
> I'm not sure if the issues lie with upstream or distro-related mdadm or other packages, or perhaps kernel issues?
Most of the issues you identify lie on the overlap between mdadm and
the boot loader - mkinitramfs or dracut or whatever.
It is distro problem to make these work together. As upstream md and
mdadm maintainer I'm happy to work with distro maintainer to resolve
issues. I can tell you how I think it should work and discuss how it
can work, but I am not in a position to diagnose exactly what is
happening and figure out what to fix.
You really need to follow this up with Debian, though unfortunately I
think the current Debian mdadm maintainer is not able to put in as much
time as he would like.
NeilBrown
>
> Just FYI, I did consider FreeBSD as an alternative which implements ZFS-on-Root disk pools and GELI encryption. After limited testing this seems to work (even with only one disk if you just want to use it for encryption) but I understand ZFS can be corrupted by hardware problems (eg. faulty RAM), and FreeBSD doesn't seem to want to open LUKS containers on-the-fly, such as an encrypted external HD.
>
> I would prefer a Linux solution - any explanations, solutions, tips or advice re linux software RAID would be gratefully received.
>
> With kind regards
> Gareth
> --
> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
prev parent reply other threads:[~2015-06-24 23:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-19 18:48 mdadm/Software RAID problems Gareth Evans
2015-06-20 5:56 ` mdadm/Software RAID problems - update Gareth Evans
2015-06-21 14:21 ` mdadm/Software RAID problems - another update Gareth Evans
2015-06-24 23:26 ` NeilBrown
2015-06-24 23:21 ` NeilBrown [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150625092132.5791ab5f@noble \
--to=neilb@suse.com \
--cc=donotspam@fastmail.fm \
--cc=linux-raid@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).