All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Murphy <lists@colorremedies.com>
To: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Cc: Glenn Trigg <ggtrigg@gmail.com>
Subject: Re: help request for an unmountable raid1 filesystem
Date: Thu, 28 Mar 2019 21:21:02 -0600	[thread overview]
Message-ID: <CAJCQCtQSv5t9UuGOLmBqxC66WoDzcR4gcQ8K_Yqs0-K_b8yxrg@mail.gmail.com> (raw)
In-Reply-To: <CAJCQCtQ3YFovgt4tFNQ+uLE81BiD0KFqPdvzE7Rxu+3wujWp2A@mail.gmail.com>

On Thu, Mar 28, 2019 at 8:27 PM Chris Murphy <lists@colorremedies.com> wrote:
>>So I suggest 5.0.4, or 4.19.32, or you can be brave and
> download this, image it to a USB stick (dd if=file of=/dev/ bs=1M
> oflag=direct) which of course will erase everything on the stick.
>
> https://kojipkgs.fedoraproject.org/compose/rawhide/Fedora-Rawhide-20190327.n.0/compose/Everything/x86_64/iso/Fedora-Everything-netinst-x86_64-Rawhide-20190327.n.0.iso
>
> That might have 5.1rc2 on it, or something in between rc1 and rc2.

Oh yeah, in case you go this route, at the bootloader menu, choose the
troubleshooting submenu and then choose to rescue a system. When you
get to the text installer there will be an option to get dropped to a
shell, at which point the installer quits. ~600MB


-- 
Chris Murphy

  reply	other threads:[~2019-03-29  3:21 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-09 21:35 help request for an unmountable raid1 filesystem Glenn Trigg
2019-03-23  0:45 ` Glenn Trigg
2019-03-29  0:53   ` Glenn Trigg
2019-03-29  2:27 ` Chris Murphy
2019-03-29  3:21   ` Chris Murphy [this message]
2019-03-30 23:43   ` Glenn Trigg
2019-03-31 21:34     ` Chris Murphy
2019-04-01  5:48       ` Glenn Trigg
2019-04-01 17:14         ` Chris Murphy
2019-04-05  5:51           ` Glenn Trigg
2019-04-05  6:44             ` Chris Murphy
2019-04-06  0:37               ` Glenn Trigg

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=CAJCQCtQSv5t9UuGOLmBqxC66WoDzcR4gcQ8K_Yqs0-K_b8yxrg@mail.gmail.com \
    --to=lists@colorremedies.com \
    --cc=ggtrigg@gmail.com \
    --cc=linux-btrfs@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 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.