From: <tyomix@tuta.io>
To: Linux Btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: Can't mount or recover! Help! ERROR: cannot read chunk root ERROR: cannot open file system
Date: Sat, 22 Jun 2019 01:00:16 +0200 (CEST) [thread overview]
Message-ID: <LhwGCp6--3-1@tuta.io> (raw)
In-Reply-To: <LhwD3kS--3-1@tuta.io>
[root@TYOMIX tyomix]# btrfs restore -D /dev/sda3 /dev/null
checksum verify failed on 1048576 found E4E3BDB6 wanted 00000000
checksum verify failed on 1048576 found E4E3BDB6 wanted 00000000
bad tree block 1048576, bytenr mismatch, want=1048576, have=0
ERROR: cannot read chunk root
Could not open root, trying backup super
checksum verify failed on 1048576 found E4E3BDB6 wanted 00000000
checksum verify failed on 1048576 found E4E3BDB6 wanted 00000000
bad tree block 1048576, bytenr mismatch, want=1048576, have=0
ERROR: cannot read chunk root
Could not open root, trying backup super
ERROR: superblock bytenr 274877906944 is larger than device size 243400704000
Could not open root, trying backup super
[root@TYOMIX tyomix]#
Jun 22, 2019, 1:46 AM by tyomix@tuta.io:
> [root@TYOMIX tyomix]# mount -t btrfs -o ro,recovery /dev/sda3 /mnt
> mount: /mnt: wrong fs type, bad option, bad superblock on /dev/sda3, missing codepage or helper program, or other error.
> [root@TYOMIX tyomix]# mount -t btrfs -o ro,usebackuproot /dev/sda3 /mnt
> mount: /mnt: wrong fs type, bad option, bad superblock on /dev/sda3, missing codepage or helper program, or other error.
> [root@TYOMIX tyomix]# btrfs check /dev/sda3
> Opening filesystem to check...
> checksum verify failed on 1048576 found E4E3BDB6 wanted 00000000
> checksum verify failed on 1048576 found E4E3BDB6 wanted 00000000
> bad tree block 1048576, bytenr mismatch, want=1048576, have=0
> ERROR: cannot read chunk root
> ERROR: cannot open file system
> [root@TYOMIX tyomix]# uname -a
> Linux TYOMIX 5.1.9-arch1-1-ARCH #1 SMP PREEMPT Tue Jun 11 16:18:09 UTC 2019 x86_64 GNU/Linux
> [root@TYOMIX tyomix]# btrfs --version
> btrfs-progs v5.1
> [root@TYOMIX tyomix]# btrfs fi show
> Label: 'Extra' uuid: 23a08cb0-5289-407f-a1c3-192709bb9476
> Total devices 1 FS bytes used 96.19GiB
> devid 1 size 107.42GiB used 99.02GiB path /dev/sdc1
>
> Label: 'Data' uuid: 2bff7854-bbe0-4368-bf46-8f191805d9ca
> Total devices 1 FS bytes used 171.19GiB
> devid 1 size 226.68GiB used 223.01GiB path /dev/sda3
>
>
>
parent reply other threads:[~2019-06-21 23:00 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <LhwD3kS--3-1@tuta.io>]
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=LhwGCp6--3-1@tuta.io \
--to=tyomix@tuta.io \
--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 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 NNTP newsgroup(s).