-
Notifications
You must be signed in to change notification settings - Fork 245
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Assertion start >= found_start && end <= found_end
failed
#852
Comments
I ran it on an unreliable microSD after dumping it. Low-level reads are always successful on this kind of cards (ddrescue needed just one pass with no errors), but data turn out to be borked sometimes. btrfs driver is picky about that and yields input/output errors. I have a similar card of the kind formatted to FAT32 and inserted into a phone, and have downloaded an anime season with CRC32 checksums in names there. There are playback errors sometimes with those video files, and when I dumped them via adbfs, I noticed that checksums of some files don't match, but match on other reads or when the card gets colder. So if I didn't know checksums, I could not know if the files are corrupted in the first place. Pretty like at good ol' diskette times with no low-level checksums, eh? |
Oh, and worth noting that on third such a card, I set up a redundant RAID array, and it works like a charm. I still hope I can do something like that for the card with Btrfs from OP (I use it to run Arch Linux Arm on a Chromebook, so it's under high load). |
Next run:
|
|
The text was updated successfully, but these errors were encountered: