Mdthbs

My parents are Afghan

Using mean length and mean weight to calculate mean BMI?

Opposite party turned away from voting when ballot is all opposing party

Creating Stored Procedure in local db that references tables in linked server

Expl3 and recent xparse on overleaf: No expl3 loader detected

logo selection for poster presentation

When an electron around an atom drops to a lower state, is 100% of the energy converted to a photon?

Is it a good idea to copy a trader when investing?

Steganography in Latex

How to start your Starctaft II games vs AI immediatly?

Capturing the entire webpage with WebExecute's CaptureImage

What dice to use in a game that revolves around triangles?

How to avoid making self and former employee look bad when reporting on fixing former employee's work?

Program for finding longest run of zeros from a list of 100 random integers which are either 0 or 1

Is it possible to do moon sighting in advance for 5 years with 100% accuracy?

Trying to understand a summation

How do I give a darkroom course without negatives from the attendees?

Identity of a supposed anonymous referee revealed through "Description" of the report

What are these pads?

Linear Independence for Vectors of Cosine Values

99 coins into the sacks

Can I bring back Planetary Romance as a genre?

Does this website provide consistent translation into Wookiee?

What's an appropriate age to involve kids in life changing decisions?

btrfs “bad tree block” prevents mount and repair

How to repair a BTRFS block?BTRFS RAID6 array is broken, how do I fix it?Filesystem is reporting a write error on a specific sector even after the partition is moved furtherbtrfs error unknown - root fs will not mountBtrfs forced readonly/corrupted after conversion from ext4Why do I get an immediate error on balance startBtrfs errors on boot, can't boot my Fedora LinuxHow to recover a btrfs filesystem with two identical devicesFind all blocks on device not used by the filesystemBtrfs How do I replace a failing/failed hard drive on a RAID1 setup with no available SATA ports

.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}

0

I have a 120 GB Samsung SSD which I setup as a LUKS volume with btrfs in Xubuntu 18.04 which has been running fine until I tried booting this afternoon and discovered lines like this in dmesg when it attempts to mount (after the LUKS passphrase has been accepted):

[ 8023.426359] BTRFS info (device dm-0): disk space caching is enabled

[ 8023.426361] BTRFS info (device dm-0): has skinny extents

[ 8023.427820] BTRFS error (device dm-0): bad tree block start, want 120516247552 have 17642829462275766793

[ 8023.427828] BTRFS warning (device dm-0): failed to read tree root

[ 8023.459232] BTRFS error (device dm-0): open_ctree failed

If that "want" value is supposed to be a byte offset it seems way beyond any sane amount. I booted to an Ubuntu 19.04 flash drive and tried doing a rescue chunk-recover which reported 111 recoverable chunks and "Chunk tree recovered successfully", but it didn't have any impact on the problem. I ran the chunk-recover process again and it produced output identical to the first run so it seems to not be doing anything.

I tried doing a rescue super-recover just to see what happened and it reported 2 superblocks which were already in good condition and it didn't take any action.

At this point I backed up the disk with dd to a file on some working storage. I know my data (or at least some of it) is still there, since I can see the contents of plain text files if I page through an xxd dump of the image.

I tried doing check --repair which I understand is a last resort, but that didn't get off the ground either, with an error similar to the mount failure in dmesg:

enabling repair mode

Opening filesystem to check...

checksum verify failed on 120516247552 found 4D050B32 wanted 0EB4D74B

checksum verify failed on 120516247552 found 4D050B32 wanted 0EB4D74B

bad tree block 120516247552, bytenr mismatch, want=120516247552, have=17642829462275766793

Couldn't read tree root

ERROR: cannot open file system

Any guidance is appreciated. Also I'm pretty sure this isn't a duplicate of BTRFS bad tree block start

btrfs

share|improve this question

asked 1 hour ago

some_stackersome_stacker

1

New contributor

some_stacker is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

add a comment | 

0

I have a 120 GB Samsung SSD which I setup as a LUKS volume with btrfs in Xubuntu 18.04 which has been running fine until I tried booting this afternoon and discovered lines like this in dmesg when it attempts to mount (after the LUKS passphrase has been accepted):

[ 8023.426359] BTRFS info (device dm-0): disk space caching is enabled

[ 8023.426361] BTRFS info (device dm-0): has skinny extents

[ 8023.427820] BTRFS error (device dm-0): bad tree block start, want 120516247552 have 17642829462275766793

[ 8023.427828] BTRFS warning (device dm-0): failed to read tree root

[ 8023.459232] BTRFS error (device dm-0): open_ctree failed

If that "want" value is supposed to be a byte offset it seems way beyond any sane amount. I booted to an Ubuntu 19.04 flash drive and tried doing a rescue chunk-recover which reported 111 recoverable chunks and "Chunk tree recovered successfully", but it didn't have any impact on the problem. I ran the chunk-recover process again and it produced output identical to the first run so it seems to not be doing anything.

I tried doing a rescue super-recover just to see what happened and it reported 2 superblocks which were already in good condition and it didn't take any action.

At this point I backed up the disk with dd to a file on some working storage. I know my data (or at least some of it) is still there, since I can see the contents of plain text files if I page through an xxd dump of the image.

I tried doing check --repair which I understand is a last resort, but that didn't get off the ground either, with an error similar to the mount failure in dmesg:

enabling repair mode

Opening filesystem to check...

checksum verify failed on 120516247552 found 4D050B32 wanted 0EB4D74B

checksum verify failed on 120516247552 found 4D050B32 wanted 0EB4D74B

bad tree block 120516247552, bytenr mismatch, want=120516247552, have=17642829462275766793

Couldn't read tree root

ERROR: cannot open file system

Any guidance is appreciated. Also I'm pretty sure this isn't a duplicate of BTRFS bad tree block start

btrfs

share|improve this question

asked 1 hour ago

some_stackersome_stacker

1

New contributor

some_stacker is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

add a comment | 

I have a 120 GB Samsung SSD which I setup as a LUKS volume with btrfs in Xubuntu 18.04 which has been running fine until I tried booting this afternoon and discovered lines like this in dmesg when it attempts to mount (after the LUKS passphrase has been accepted):

[ 8023.426359] BTRFS info (device dm-0): disk space caching is enabled

[ 8023.426361] BTRFS info (device dm-0): has skinny extents

[ 8023.427820] BTRFS error (device dm-0): bad tree block start, want 120516247552 have 17642829462275766793

[ 8023.427828] BTRFS warning (device dm-0): failed to read tree root

[ 8023.459232] BTRFS error (device dm-0): open_ctree failed

If that "want" value is supposed to be a byte offset it seems way beyond any sane amount. I booted to an Ubuntu 19.04 flash drive and tried doing a rescue chunk-recover which reported 111 recoverable chunks and "Chunk tree recovered successfully", but it didn't have any impact on the problem. I ran the chunk-recover process again and it produced output identical to the first run so it seems to not be doing anything.

I tried doing a rescue super-recover just to see what happened and it reported 2 superblocks which were already in good condition and it didn't take any action.

At this point I backed up the disk with dd to a file on some working storage. I know my data (or at least some of it) is still there, since I can see the contents of plain text files if I page through an xxd dump of the image.

I tried doing check --repair which I understand is a last resort, but that didn't get off the ground either, with an error similar to the mount failure in dmesg:

enabling repair mode

Opening filesystem to check...

checksum verify failed on 120516247552 found 4D050B32 wanted 0EB4D74B

checksum verify failed on 120516247552 found 4D050B32 wanted 0EB4D74B

bad tree block 120516247552, bytenr mismatch, want=120516247552, have=17642829462275766793

Couldn't read tree root

ERROR: cannot open file system

Any guidance is appreciated. Also I'm pretty sure this isn't a duplicate of BTRFS bad tree block start

btrfs

share|improve this question

asked 1 hour ago

some_stackersome_stacker

1

New contributor

some_stacker is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

[ 8023.426359] BTRFS info (device dm-0): disk space caching is enabled

[ 8023.426361] BTRFS info (device dm-0): has skinny extents

[ 8023.427820] BTRFS error (device dm-0): bad tree block start, want 120516247552 have 17642829462275766793

[ 8023.427828] BTRFS warning (device dm-0): failed to read tree root

[ 8023.459232] BTRFS error (device dm-0): open_ctree failed

enabling repair mode

Opening filesystem to check...

checksum verify failed on 120516247552 found 4D050B32 wanted 0EB4D74B

checksum verify failed on 120516247552 found 4D050B32 wanted 0EB4D74B

bad tree block 120516247552, bytenr mismatch, want=120516247552, have=17642829462275766793

Couldn't read tree root

ERROR: cannot open file system

share|improve this question

asked 1 hour ago

some_stackersome_stacker

1

New contributor

some_stacker is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

share|improve this question

asked 1 hour ago

some_stackersome_stacker

1

New contributor

some_stacker is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

asked 1 hour ago

some_stackersome_stacker

1

New contributor

some_stacker is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

asked 1 hour ago

some_stackersome_stacker

1