From: Arno Wagner <arno@wagner.name>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] Correct rebuild process for hardware RAID 6 array with LUKS data ?
Date: Wed, 17 Jan 2018 17:40:20 +0100 [thread overview]
Message-ID: <20180117164020.GA16943@tansi.org> (raw)
In-Reply-To: <1516004542.5a5c64becf99f@mail.inbox.lv>
You are confusing layers here.
Just rebuild your hardware RAID as you would with unencrypted data.
It does not care whether the _data_ on the combined RAID device
is encrypted or not.
From your list, that would be steps 1., 4. and 5. The rest
has no place in this. Incidentally, the RAID controller
never sees the data decrypted.
That is also why you do not find this question or an answer:
It is simply not relevant to cryptsetup/LUKS.
Regards,
Arno
On Mon, Jan 15, 2018 at 09:22:22 CET, nouser wrote:
> I haven't seen this question answered before and it's not easy to
> search the list archives.
> I'm not aware of an IRC channel to ask such a simple question.
> What is the correct process to initiate a hardware RAID rebuild to
> ensure the reconstructed disk writes encrypted data?
> Steps performed: may be incorrect
> 1. activate degraded array (vendor tool)
> 2. cryptsetup luksOpen /dev/sdX sdX
> 3. mount /dev/mapper/sdX /mnt/tmp
> 4. insert new hard drive
> 5. rebuild begins
> My confusion is as follows.
> LUKS data is encrypted at rest.
> Once a LUKS container is unlocked and mounted that data is clear and
> visible to the operating system and RAID controller. A hardware RAID
> controller should not be aware of LUKS or encrypted data.
> During the RAID rebuild I was monitoring CPU usage.
> There were no CPU spikes typical with writing encrypted data.
> I'm wondering if the RAID controller is writing unencrypted data from
> the unlocked LUKS container.
> Which leads to my original question.
> 1. What is the correct process to rebuild a hardware RAID array with
> encrypted LUKS data?
> 2. Should the LUKS container be unlocked and filesystem mounted before
> inserting a new hard drive to initiate a rebuild? Does it make a
> difference either way? Will a bad method destroy or corrupt data?
> 3. What is the best method to verify the rebuilt disk was written with
> encrypted data?
> Thank you for your time and I apologize.
> I couldn't find a clear answer.
> Thank you,
> Wrangl3r
> _______________________________________________
> dm-crypt mailing list
> dm-crypt@saout.de
> http://www.saout.de/mailman/listinfo/dm-crypt
--
Arno Wagner, Dr. sc. techn., Dipl. Inform., Email: arno@wagner.name
GnuPG: ID: CB5D9718 FP: 12D6 C03B 1B30 33BB 13CF B774 E35C 5FA1 CB5D 9718
----
A good decision is based on knowledge and not on numbers. -- Plato
If it's in the news, don't worry about it. The very definition of
"news" is "something that hardly ever happens." -- Bruce Schneier
prev parent reply other threads:[~2018-01-17 16:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-15 8:22 [dm-crypt] Correct rebuild process for hardware RAID 6 array with LUKS data ? nouser
2018-01-17 11:35 ` Hannes Erven
2018-01-17 16:40 ` Arno Wagner [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=20180117164020.GA16943@tansi.org \
--to=arno@wagner.name \
--cc=dm-crypt@saout.de \
/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 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.