From: Ricardo Wurmus <rekado@elephly.net>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: guix-devel <guix-devel@gnu.org>,
Mathieu Othacehe <othacehe@gnu.org>,
guix-sysadmin@gnu.org
Subject: Re: Dropping gzip-compressed substitutes
Date: Mon, 21 Feb 2022 12:26:26 +0100 [thread overview]
Message-ID: <87ilt8cv58.fsf@elephly.net> (raw)
In-Reply-To: <878ru4pzsr.fsf@gmail.com>
Maxim Cournoyer <maxim.cournoyer@gmail.com> writes:
> This week, I'd like to try the following to see if we could get past
> this:
>
> 1. Do the experiment again, now a 'rootdelay=20' kernel parameter was
> added to Berlin's config. This may well be enough.
>
> 2. In case mounting the RAID 10 Btrfs root partition still fails with
> missing drive errors, try the following workaround suggested in the
> #btrfs channel, which forces a 'btrfs device scan' on each device of the
> array, with the following mount option:
>
> "device=/dev/sda3,/dev/sdb3,/dev/sdc3,/dev/sdd3,/dev/sde3,/dev/sdf3"
>
> To make it more convenient to experiment with different values for the
> rootdelay or add the device option above, I'm planning to 'guix system init'
> with the following patch applied: https://issues.guix.gnu.org/40998,
> which allows providing 'rootflags' directly from the kernel command line
> (thus by editing the GRUB config at boot).
Good work, Maxim! Your persistence is admirable.
> I'll try to synchronize with Ricardo in the channel and hope they
> weren't too frightened by our last experiment to not shy away from
> trying again :-).
We can make another attempt this week. Do we need to sync anything
before trying again? Also: would be nice if we could do “guix system
init” without copying everything again and again whenever we try again…
My toddler has been pretty sick for the past couple of days, and I
haven’t slept enough to be using my brain without hand-holding :) I’ll
try to be around long enough in the eaerly evenings to see to it that
the server reboots fine, but if things go awfully sideways I just cannot
commit to riding the bike to the data centre. Let’s hope it will just
work fine with your changes to the initrd.
See you later on IRC — I gotta have a nap :)
--
Ricardo
next prev parent reply other threads:[~2022-02-21 11:34 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-07 18:44 Dropping gzip-compressed substitutes Maxim Cournoyer
2022-02-07 20:02 ` Ricardo Wurmus
2022-02-08 13:34 ` Mathieu Othacehe
2022-02-08 14:13 ` Maxim Cournoyer
2022-02-08 16:53 ` Ricardo Wurmus
2022-02-09 2:35 ` Maxim Cournoyer
2022-02-09 5:06 ` Maxim Cournoyer
2022-02-09 10:29 ` Efraim Flashner
2022-02-14 17:50 ` Ludovic Courtès
2022-02-14 20:04 ` Attila Lendvai
2022-02-15 12:20 ` Mathieu Othacehe
2022-02-15 18:29 ` Christopher Baines
2022-02-21 5:13 ` Maxim Cournoyer
2022-02-21 11:26 ` Ricardo Wurmus [this message]
2022-02-21 20:04 ` Gábor Boskovits
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=87ilt8cv58.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=guix-devel@gnu.org \
--cc=guix-sysadmin@gnu.org \
--cc=maxim.cournoyer@gmail.com \
--cc=othacehe@gnu.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).