From: Eric Levy <contact@ericlevy.name>
To: linux-btrfs@vger.kernel.org
Subject: RAID mount fails after upgrading to kernel 6.2.0
Date: Wed, 19 Jul 2023 21:13:59 -0400 [thread overview]
Message-ID: <B3M2YR.U71TM7CWM1P12@ericlevy.name> (raw)
I recently performed a routine update on a Linux Mint system, version
21.2 (Victoria). The update moved the kernel from 5.19.0 to 6.2.0. The
system includes a non-root mount that is Btrfs with RAID, which no
longer mounts. Error reporting is rather limited and opaque.
I am assuming the file system is healthy from the standpoint of the old
kernel, but I may need help understanding how to make it viable for the
new one.
Mounting from the command line prints the following:
mount: /mnt: wrong fs type, bad option, bad superblock on /dev/sdg,
missing codepage or helper program, or other error.
The following is extracted from the boot sequence recorded in the
kernel ring:
kernel: BTRFS error: device /dev/sdd belongs to fsid
c6f83d24-1ac3-4417-bdd9-6249c899604d, and the fs is already mounted
kernel: BTRFS error: device /dev/sdf belongs to fsid
c6f83d24-1ac3-4417-bdd9-6249c899604d, and the fs is already mounted
kernel: BTRFS info (device sde): using crc32c (crc32c-intel) checksum
algorithm
kernel: BTRFS info (device sde): turning on async discard
kernel: BTRFS info (device sde): disk space caching is enabled
kernel: BTRFS error (device sde): devid 7 uuid
2f62547b-067f-433c-bec1-b90e0c8cb75e is missing
kernel: BTRFS error (device sde): failed to read the system array: -2
kernel: BTRFS error (device sde): open_ctree failed
mount[969]: mount: /mnt: wrong fs type, bad option, bad superblock on
/dev/sde, missing codepage or helper program, or other error.
systemd[1]: mnt.mount: Mount process exited, code=exited, status=32/n/a
next reply other threads:[~2023-07-20 1:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-20 1:13 Eric Levy [this message]
2023-07-20 2:26 ` RAID mount fails after upgrading to kernel 6.2.0 Anand Jain
2023-07-20 2:50 ` Eric Levy
2023-07-20 5:48 ` Anand Jain
2023-07-20 20:10 ` Eric Levy
2023-07-21 4:49 ` Anand Jain
2023-07-21 5:31 ` Eric Levy
2023-07-22 10:59 ` Anand Jain
2023-07-21 8:02 ` Forza
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=B3M2YR.U71TM7CWM1P12@ericlevy.name \
--to=contact@ericlevy.name \
--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.