All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Murphy <lists@colorremedies.com>
To: Matt Zagrabelny <mzagrabe@d.umn.edu>
Cc: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: unable to mount disk?
Date: Tue, 28 Sep 2021 14:59:11 -0400	[thread overview]
Message-ID: <CAJCQCtT0CvQ1Rmwpq3_nu1+G5wVx7+5ivDxLMTRG+=Vk0Fh0-g@mail.gmail.com> (raw)
In-Reply-To: <CAOLfK3VL5P7uAPAqvaRHv5gcoT5hdVqkSR5Nz+hTcb=FRmj9ZQ@mail.gmail.com>

On Tue, Sep 28, 2021 at 2:53 PM Matt Zagrabelny <mzagrabe@d.umn.edu> wrote:
>
> Greetings btrfs folks,
>
> I am attempting to mount a filesystem on a (likely) failing disk:
>
> $ mount /var/local/media
> mount: /var/local/media: wrong fs type, bad option, bad superblock on
> /dev/sdb, missing codepage or helper program, or other error.
>
> excerpt from dmesg:
>
> [  352.642893] BTRFS info (device sdb): disk space caching is enabled
> [  352.642897] BTRFS info (device sdb): has skinny extents
> [  352.645562] BTRFS error (device sdb): devid 2 uuid
> bf09cc8f-44d6-412e-bc42-214ff122584a is missing
> [  352.645570] BTRFS error (device sdb): failed to read the system array: -2
> [  352.646770] BTRFS error (device sdb): open_ctree failed
>
> Is there anything I can do to attempt to recover this hardware issue?


This is a 2+ device Btrfs file system? And one of the devices, devid2,
is missing. So you need to figure out why. If the drive has in fact
failed, rather than just missing power/data connection, you can mount
degraded using the 'degraded' mount option. Just be advised that there
are potentially some consequences to operating under degraded mode,
depending on the specific configuration.

-- 
Chris Murphy

  reply	other threads:[~2021-09-28 18:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-28 18:44 unable to mount disk? Matt Zagrabelny
2021-09-28 18:59 ` Chris Murphy [this message]
2021-09-28 19:23   ` Matt Zagrabelny
2021-09-29  1:10     ` Chris Murphy

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='CAJCQCtT0CvQ1Rmwpq3_nu1+G5wVx7+5ivDxLMTRG+=Vk0Fh0-g@mail.gmail.com' \
    --to=lists@colorremedies.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=mzagrabe@d.umn.edu \
    /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.