All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wols Lists <antlists@youngman.org.uk>
To: Stefanie Leisestreichler
	<stefanie.leisestreichler@peter-speer.de>,
	linux-raid@vger.kernel.org
Subject: Re: RAID 1 | Test Booting from /dev/sdb
Date: Tue, 5 May 2020 09:51:12 +0100	[thread overview]
Message-ID: <5EB12900.3030505@youngman.org.uk> (raw)
In-Reply-To: <221092f3-5b8a-5d95-01d9-261e6449f747@peter-speer.de>

On 05/05/20 09:11, Stefanie Leisestreichler wrote:
> Hi.
> I want to test if grub is installed on both of the HDs which are part of
> my raid1 array. I wonder which would be the best solution to do so.
> 
> I think I will archive that when I shutdown the computer, make /dev/sda
> powerless and see if it is able to boot from /dev/sdb.
> 
> If it is not booting /dev/sdb will have no changes, I would shutdown,
> connect /dev/sda with power again, turn it on and do a "grub-install
> /dev/sdb". Depending on the state of the array (I guess it will need
> recovery) I would do a "mdadm /dev/md0 --add /dev/sdb1". After recovery
> I would try it again.
> 
> If it is booting from /dev/sdb this HD will have "more" data because of
> the one boot process than /dev/sda.

Why? If it boots to the grub menu, just hit an arrow key to stop the
timeout, and then hold the power button for 5 secs to shut it down again.

> I am not sure if it is a good idea
> to shutdown and just connect /dev/sda with power again, boot (assuming
> /dev/sda is the standard boot medium) because I do not know in which
> state the array will be. What to do in case I do not want to loose data
> from the last boot process with /dev/sdb?

Which would matter why? If you're worried about downloading mail etc,
just kill the network temporarily.

> Change boot medium to /dev/sdb
> and do a "mdadm /dev/md0 --add /dev/sda1" to get it recovered again
> without loosing the "added" data (i.e. in /var/log) from booting? Also
> device identifiers could change I guess. Even if I am fine with loosing
> the "added" data from booting with /dev/sdb, will - when booting again
> from /dev/sda - /dev/sda be the master in the array again?
> 
> It is not clear to me if I understood correctly in which case which
> array member will be the master which will be the base for recovery. Is
> it always the HD one booted from?
> 
The "master" if recovery is required will be the "older" one - in this
case sda because it was disconnected. HOWEVER. Just check whether you
have a bitmap or journal enabled. You can't have both at once, but the
result should be that sda rejoins the array cleanly, raid has a record
of which writes occurred while it was offline, and it will be updated.

> Could you please help me with that?
> 
> Thanks,
> Steffi

Cheers,
Wol

  parent reply	other threads:[~2020-05-05  8:51 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-05  8:11 RAID 1 | Test Booting from /dev/sdb Stefanie Leisestreichler
2020-05-05  8:39 ` Reindl Harald
2020-05-05  8:56   ` Stefanie Leisestreichler
2020-05-05  8:51 ` Wols Lists [this message]
2020-05-05  9:25   ` Stefanie Leisestreichler
2020-05-05  9:34     ` Wols Lists
2020-05-05  9:42       ` Stefanie Leisestreichler
2020-05-05  9:49         ` Reindl Harald

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=5EB12900.3030505@youngman.org.uk \
    --to=antlists@youngman.org.uk \
    --cc=linux-raid@vger.kernel.org \
    --cc=stefanie.leisestreichler@peter-speer.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.