From: Tobias Geerinckx-Rice via Bug reports for GNU Guix <bug-guix@gnu.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Vagrant Cascadian <vagrant@debian.org>, 38086@debbugs.gnu.org
Subject: bug#38086: RAID installation script with ‘mdadm’ no longer works
Date: Sat, 18 Jan 2020 23:03:13 +0100 [thread overview]
Message-ID: <87h80sbexq.fsf@nckx> (raw)
In-Reply-To: <87lfq4v3nb.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1045 bytes --]
Ludovic Courtès 写道:
> As you can see, it’s attempting to make a RAID1 device out of
> two
> partitions (not two disks), which makes no sense in the real
> world, but
> is easier to handle here. So I wonder if this is what’s causing
> it to
> hang…
It's just waiting for input:
$ # dd & losetup magic, where loop0 is 20% larger than loop1
$ sudo mdadm --create /dev/md0 --verbose --level=mirror
--raid-devices=2 /dev/loop{0,1}
mdadm: Note: this array has metadata at the start and
may not be suitable as a boot device. If you plan to
store '/boot' on this device please ensure that
your boot-loader understands md/v1.x metadata, or use
--metadata=0.90
mdadm: size set to 101376K
mdadm: largest drive (/dev/loop1) exceeds size (101376K) by more
than 1%
Continue creating array?
Adding --force does not avoid this.
I recommend tweaking the partition table to make both members
equal, but a ‘yes|’ also works if you're in a hurry ;-)
Kind regards,
T G-R
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2020-01-18 22:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-06 10:13 bug#38086: RAID installation script with ‘mdadm’ no longer works Ludovic Courtès
2019-11-06 11:07 ` Gábor Boskovits
2019-11-11 23:28 ` Ludovic Courtès
2019-11-22 18:30 ` Ludovic Courtès
2020-01-17 22:42 ` Vagrant Cascadian
2020-01-18 13:29 ` Gábor Boskovits
2020-01-18 21:46 ` Ludovic Courtès
2020-01-18 22:03 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix [this message]
2020-01-19 22:13 ` Ludovic Courtès
2020-01-19 22:31 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87h80sbexq.fsf@nckx \
--to=bug-guix@gnu.org \
--cc=38086@debbugs.gnu.org \
--cc=ludo@gnu.org \
--cc=me@tobias.gr \
--cc=vagrant@debian.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).