I have a Freedom Box Pioneer (hardware is an Olimex A20-OLinuXino-LIME2
unit with a Samsung 128 GB micro-SD card. The micro-SD is partitioned
into 2GB boot ext2 and the remainder as the root partition as BTRFS.
The thing has been crashing for months
and now it started giving GPG
signature errors when trying to run 'apt update'. I copied the entire micro-SD card to an image file with dd so I have a backup. Running
'btrfs check' resulted in a lot of errors so I ran the check and
directed the output to a file which is over 2MB in size! The following
is a small snippet of what it in the file:
Everything online hints that attempting repair is particularly
dangerous, but what else am I to do? At the moment the system is pretty
much useless.
I have a Freedom Box Pioneer (hardware is an Olimex A20-OLinuXino-LIME2
unit with a Samsung 128 GB micro-SD card. The micro-SD is partitioned
into 2GB boot ext2 and the remainder as the root partition as BTRFS.
The thing has been crashing for months and now it started giving GPG signature errors when trying to run 'apt update'. I copied the entire micro-SD card to an image file with dd so I have a backup. Running
'btrfs check' resulted in a lot of errors so I ran the check and
directed the output to a file which is over 2MB in size! The following
is a small snippet of what it in the file:
[1/7] checking root items
[2/7] checking extents (...)
Everything online hints that attempting repair is particularly
dangerous, but what else am I to do? At the moment the system is pretty
much useless.
I have a Freedom Box Pioneer (hardware is an Olimex A20-OLinuXino-LIME2
unit with a Samsung 128 GB micro-SD card. The micro-SD is partitioned
into 2GB boot ext2 and the remainder as the root partition as BTRFS.
The thing has been crashing for months and now it started giving GPG signature errors when trying to run 'apt update'. I copied the entire micro-SD card to an image file with dd so I have a backup. Running
'btrfs check' resulted in a lot of errors so I ran the check and
directed the output to a file which is over 2MB in size! The following
is a small snippet of what it in the file:
[1/7] checking root items
[2/7] checking extents
checksum verify failed on 2337062912 found 00000098 wanted 00000025
checksum verify failed on 2337062912 found 00000098 wanted 00000025
Csum didn't match
owner ref check failed [2337062912 16384]
ERROR: errors found in extent allocation tree or chunk allocation
[3/7] checking free space cache
[4/7] checking fs roots
checksum verify failed on 2337062912 found 00000098 wanted 00000025
checksum verify failed on 2337062912 found 00000098 wanted 00000025
Csum didn't match
root 11670 inode 1109704 errors 200, dir isize wrong
root 11670 inode 1109705 errors 2001, no inode item, link count wrong
unresolved ref dir 1109704 index 2 namelen 4 name json filetype 1 errors 4, no inode ref
root 11670 inode 1109706 errors 2001, no inode item, link count wrong
unresolved ref dir 1095383 index 2 namelen 11 name 20-json.ini filetype 7 errors 4, no inode ref
root 11670 inode 1109707 errors 2001, no inode item, link count wrong
unresolved ref dir 978863 index 4 namelen 7 name apache2 filetype
2 errors 4, no inode ref
root 11670 inode 1109710 errors 2001, no inode item, link count wrong
unresolved ref dir 1095409 index 2 namelen 11 name 20-json.ini filetype 7 errors 4, no inode ref
root 11670 inode 1109711 errors 2001, no inode item, link count wrong
unresolved ref dir 978863 index 5 namelen 3 name fpm filetype 2 errors 4, no inode ref
root 11670 inode 1109714 errors 2001, no inode item, link count wrong
unresolved ref dir 978864 index 30 namelen 4 name json filetype 1 errors 4, no inode ref
root 11670 inode 1109734 errors 2001, no inode item, link count wrong
unresolved ref dir 45938 index 176 namelen 17 name
gschemas.compiled filetype 1 errors 4, no inode ref
root 11670 inode 1109735 errors 2001, no inode item, link count wrong
unresolved ref dir 6679 index 36 namelen 15 name giomodule.cache filetype 1 errors 4, no inode ref
root 11670 inode 1109771 errors 2001, no inode item, link count wrong
unresolved ref dir 295871 index 242 namelen 24 name rsyslog.service.dsh-also filetype 1 errors 4, no inode ref
root 11670 inode 1109784 errors 2001, no inode item, link count wrong
unresolved ref dir 978742 index 31 namelen 12 name readline.ini filetype 1 errors 4, no inode ref
.
.
.
ERROR: errors found in fs roots
Opening filesystem to check...
Checking filesystem on /dev/mmcblk0p2
UUID: ea375ed2-d6e7-49d4-9b19-a624ba09b96c
The following tree block(s) is corrupted in tree 11670:
tree block bytenr: 6562955264, level: 1, node key: (1109704, 96, 3) found 19331854402 bytes used, error(s) found
total csum bytes: 14201108
total tree bytes: 1242775552
total fs tree bytes: 1160757248
total extent tree bytes: 61292544
btree space waste bytes: 327420862
file data blocks allocated: 182356692992
referenced 113920880640
Everything online hints that attempting repair is particularly
dangerous, but what else am I to do? At the moment the system is pretty
much useless.
All insights appreciated.
- Nate
--
"The optimist proclaims that we live in the best of all
possible worlds. The pessimist fears this is true."
Web: https://www.n0nb.us
Projects: https://github.com/N0NB
GPG fingerprint: 82D6 4F6B 0E67 CD41 F689 BBA6 FB2C 5130 D55A 8819
To satiate your curiosity, you can find out what files are corrupted, some
of the errors are giving filenames. If not, this is my saved command to obtain filename from inode numbers:
sudo btrfs inspect-internal inode-resolve 50845 /
And obtain filename from logical error:
sudo btrfs inspect-internal logical-resolve -v 540115857408 /
As far as I know, Btrfs may refuse to read file with wrong checksum, there may be another command to do that.
For the future: don't let things go this long. I know it's
tempting to say "maybe it won't happen again", but the second
time should be the last time before you take action.
2: Reinstall Debian on the new disk. Don't use btrfs on a
single-drive system; only use btrfs on a mirrored system. In most cases,
use ext4.
Everything online hints that attempting repair is particularly
dangerous, but what else am I to do?
Nate Bargmann wrote:
I have a Freedom Box Pioneer (hardware is an Olimex A20-OLinuXino-LIME2 unit with a Samsung 128 GB micro-SD card. The micro-SD is partitioned
into 2GB boot ext2 and the remainder as the root partition as BTRFS.
The thing has been crashing for months
For the future: don't let things go this long. I know it's
tempting to say "maybe it won't happen again", but the second
time should be the last time before you take action.
and now it started giving GPG
signature errors when trying to run 'apt update'. I copied the entire micro-SD card to an image file with dd so I have a backup. Running
'btrfs check' resulted in a lot of errors so I ran the check and
directed the output to a file which is over 2MB in size! The following
is a small snippet of what it in the file:
...
Everything online hints that attempting repair is particularly
dangerous, but what else am I to do? At the moment the system is pretty much useless.
1: get a new card, or, much better, replace with a SATA
SSD. (I see the Olimex has a SATA port. Use it!) Here's a https://www.newegg.com/adata-ultimate-su800-128gb/p/N82E16820215015?Item=9SIAJNUBMB4508
$29 128GB SSD from a reputable manufacturer.
2: Reinstall Debian on the new disk. Don't use btrfs on a
single-drive system; only use btrfs on a mirrored system. In most cases,
use ext4.
3: copy all the data you can from the image file.
Everything online hints that attempting repair is particularly
dangerous, but what else am I to do?
You sum up my experience with BTRFS. I too was "scared" off from it and reformatted my BTRFS partitions and went back to ext4 -- it's a known quantity fit for humans with tons of advice of how to handle problems/errors.
I have a Freedom Box Pioneer (hardware is an Olimex A20-OLinuXino-LIME2
unit with a Samsung 128 GB micro-SD card. The micro-SD is partitioned
into 2GB boot ext2 and the remainder as the root partition as BTRFS.
The thing has been crashing for months and now it started giving GPG signature errors when trying to run 'apt update'. I copied the entire micro-SD card to an image file with dd so I have a backup. Running
'btrfs check' resulted in a lot of errors so I ran the check and
directed the output to a file which is over 2MB in size! The following
is a small snippet of what it in the file:
Everything online hints that attempting repair is particularly
dangerous, but what else am I to do?
You sum up my experience with BTRFS. I too was "scared" off from it and reformatted my BTRFS partitions and went back to ext4 -- it's a known quantity fit for humans with tons of advice of how to handle problems/errors.
Hello,
On Thu, Jan 12, 2023 at 04:57:07PM -0600, Intense Red wrote:
Everything online hints that attempting repair is particularly
dangerous, but what else am I to do?
You sum up my experience with BTRFS. I too was "scared" off from it and reformatted my BTRFS partitions and went back to ext4 -- it's a known quantity fit for humans with tons of advice of how to handle problems/errors.
I too don't have a lot of love for btrfs, but I think it is a bit
unfair to criticise it in this scenario, which is a failing SD card
with no redundancy. If there'd been redundancy then btrfs should
have noticed the problems and got the data from the other
copy/copies, but here it had no opportunity to do so.
In the same situation, ext4 would have just carried on until it got read/write errors but this wouldn't have been any better. btrfs got
the same errors and reported more of its own that it noticed from
the incorrect checksums.
It sounds like the OP's use case didn't involve redundancy nor did
it involve any of the other btrfs features such as compression or
snapshots, so btrfs probably wasn't a good choice here. ext4 or XFS
may have been better here just because they are simpler. I can
understand not wanting to have a learning experience when it comes
to one's data.
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 297 |
Nodes: | 16 (0 / 16) |
Uptime: | 01:19:17 |
Calls: | 6,669 |
Calls today: | 1 |
Files: | 12,217 |
Messages: | 5,338,506 |