From: Christian Wimmer <telefonchris@icloud.com>
To: Chris Murphy <lists@colorremedies.com>
Cc: Qu Wenruo <quwenruo.btrfs@gmx.com>, Qu WenRuo <wqu@suse.com>,
Anand Jain <anand.jain@oracle.com>,
"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: btrfs not booting any more
Date: Fri, 31 Jan 2020 13:35:47 -0300 [thread overview]
Message-ID: <783F3013-0759-46A1-BAB4-49BB22D913CF@icloud.com> (raw)
In-Reply-To: <CAJCQCtRyr17kdSdozU4_ZxJL_VdCWZe7DCCuUuz0cy2AiJs3=A@mail.gmail.com>
Hi guys,
I would need one more help from you before I can do that things by myself.
I have a different machine that runs windows and inside Vmware Fusion 15.
Inside runs as well Suse 15.1.
The linux operating system is on a 1TB virtual hard disk with following setup:
Disk /dev/sdb: 1000 GiB, 1073741824000 bytes, 2097152000 sectors
Disk model: VMware Virtual S
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 186C0CD6-F3B8-471C-B2AF-AE3D325EC215
Device Start End Sectors Size Type
/dev/sdb1 2048 18431 16384 8M BIOS boot
/dev/sdb2 18432 1920520191 1920501760 915.8G Linux filesystem
/dev/sdb3 2082992128 2097149951 14157824 6.8G Linux filesystem
The OS is on /dev/sdb2 but it does not boot any more (stays at grub_rescue).
What can I do now to repair it?
root@ubuntu:~# btrfs ins dump-tree -t root /dev/sdb2
btrfs-progs v5.2.1
parent transid verify failed on 72980660224 wanted 652165 found 652163
parent transid verify failed on 72980660224 wanted 652165 found 652163
Ignoring transid failure
leaf parent key incorrect 72980660224
Couldn't setup extent tree
parent transid verify failed on 72980660224 wanted 652165 found 652163
Ignoring transid failure
leaf parent key incorrect 72980660224
Couldn't setup device tree
ERROR: unable to open /dev/sdb2
root@ubuntu:~# btrfs ins dump-s /dev/sdb2
superblock: bytenr=65536, device=/dev/sdb2
---------------------------------------------------------
csum_type 0 (crc32c)
csum_size 4
csum 0xd35229e5 [match]
bytenr 65536
flags 0x1
( WRITTEN )
magic _BHRfS_M [match]
fsid affdbdfa-7b54-4888-b6e9-951da79540a3
metadata_uuid affdbdfa-7b54-4888-b6e9-951da79540a3
label
generation 652165
root 72978268160
sys_array_size 97
chunk_root_generation 649961
root_level 1
chunk_root 1265374330880
chunk_root_level 1
log_root 0
log_root_transid 0
log_root_level 0
total_bytes 983296901120
bytes_used 504341774336
sectorsize 4096
nodesize 16384
leafsize (deprecated) 16384
stripesize 4096
root_dir 6
num_devices 1
compat_flags 0x0
compat_ro_flags 0x0
incompat_flags 0x163
( MIXED_BACKREF |
DEFAULT_SUBVOL |
BIG_METADATA |
EXTENDED_IREF |
SKINNY_METADATA )
cache_generation 652165
uuid_tree_generation 557352
dev_item.uuid 8968cd08-0c45-4aff-ab64-65f979b21694
dev_item.fsid affdbdfa-7b54-4888-b6e9-951da79540a3 [match]
dev_item.type 0
dev_item.total_bytes 983296901120
dev_item.bytes_used 507877785600
dev_item.io_align 4096
dev_item.io_width 4096
dev_item.sector_size 4096
dev_item.devid 1
dev_item.dev_group 0
dev_item.seek_speed 0
dev_item.bandwidth 0
dev_item.generation 0
Where can I find default repair methods?
Thanks,
Chris
next prev parent reply other threads:[~2020-01-31 16:35 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-06 3:44 [PATCH] btrfs-progs: Skip device tree when we failed to read it Qu Wenruo
2019-12-06 6:12 ` Anand Jain
2019-12-06 15:50 ` Christian Wimmer
2019-12-06 16:34 ` Christian Wimmer
[not found] ` <762365A0-8BDF-454B-ABA9-AB2F0C958106@icloud.com>
2019-12-07 1:16 ` Qu WenRuo
2019-12-07 3:47 ` Christian Wimmer
2019-12-07 4:31 ` Qu Wenruo
2019-12-07 13:03 ` Christian Wimmer
2019-12-07 14:10 ` Qu Wenruo
2019-12-07 14:25 ` Christian Wimmer
2019-12-07 16:44 ` Christian Wimmer
2019-12-08 1:21 ` Qu WenRuo
2019-12-10 21:25 ` Christian Wimmer
2019-12-11 0:36 ` Qu Wenruo
2019-12-11 15:57 ` Christian Wimmer
[not found] ` <9FB359ED-EAD4-41DD-B846-1422F2DC4242@icloud.com>
2020-01-04 17:07 ` 12 TB btrfs file system on virtual machine broke again Christian Wimmer
2020-01-05 4:03 ` Chris Murphy
2020-01-05 13:40 ` Christian Wimmer
2020-01-05 14:07 ` Martin Raiber
2020-01-05 14:14 ` Christian Wimmer
2020-01-05 14:23 ` Christian Wimmer
2020-01-05 4:25 ` Qu Wenruo
2020-01-05 14:17 ` Christian Wimmer
2020-01-05 18:50 ` Chris Murphy
2020-01-05 19:18 ` Christian Wimmer
2020-01-05 19:36 ` Chris Murphy
2020-01-05 19:49 ` Christian Wimmer
2020-01-05 19:52 ` Christian Wimmer
2020-01-05 20:34 ` Chris Murphy
2020-01-05 20:36 ` Chris Murphy
[not found] ` <3F43DDB8-0372-4CDE-B143-D2727D3447BC@icloud.com>
2020-01-05 20:30 ` Chris Murphy
2020-01-05 20:36 ` Christian Wimmer
2020-01-05 21:13 ` Chris Murphy
2020-01-05 21:58 ` Christian Wimmer
2020-01-05 22:28 ` Chris Murphy
2020-01-06 1:31 ` Christian Wimmer
2020-01-06 1:33 ` Christian Wimmer
2020-01-11 17:04 ` 12 TB btrfs file system on virtual machine broke again (third time) Christian Wimmer
2020-01-11 17:23 ` Christian Wimmer
2020-01-11 19:46 ` Chris Murphy
2020-01-13 19:41 ` 12 TB btrfs file system on virtual machine broke again (fourth time) Christian Wimmer
2020-01-13 20:03 ` Chris Murphy
2020-01-31 16:35 ` Christian Wimmer [this message]
2020-05-08 12:20 ` btrfs reports bad key ordering after out of memory situation Christian Wimmer
2020-01-05 23:50 ` 12 TB btrfs file system on virtual machine broke again Qu Wenruo
2020-01-06 1:32 ` Christian Wimmer
2020-01-11 7:25 ` Andrei Borzenkov
2021-10-15 21:01 ` need help in a broken 2TB BTRFS partition Christian Wimmer
2021-10-16 10:08 ` Qu Wenruo
2021-10-16 17:29 ` Christian Wimmer
2021-10-16 22:55 ` Qu Wenruo
2021-10-16 17:35 ` Christian Wimmer
2021-10-16 23:27 ` Qu Wenruo
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=783F3013-0759-46A1-BAB4-49BB22D913CF@icloud.com \
--to=telefonchris@icloud.com \
--cc=anand.jain@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=lists@colorremedies.com \
--cc=quwenruo.btrfs@gmx.com \
--cc=wqu@suse.com \
/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.