8000 [error] Crashed: This is not a valid block. · Issue #470 · cryfs/cryfs · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

[error] Crashed: This is not a valid block. #470

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.

Sign up for GitHub

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

Jump to bottom
Open
GongHeng2017 opened this issue Feb 20, 2024 · 6 comments
Open

[error] Crashed: This is not a valid block. #470

GongHeng2017 opened this issue Feb 20, 2024 · 6 comments

Comments

@GongHeng2017
Copy link
GongHeng2017 commented Feb 20, 2024 •
edited
Loading

Expected Behavior

Successfully mount

Actual Behavior

1A84Zr98NbuaSYudOE55KY
Failed mount.
Note: The script content is to execute the cryfs mount command:
cryfs base/ mount/

Steps to Reproduce the Problem

  1. I was successfully mounted last time, and the current mounting failed.

Specifications

  • CryFS Version: 0.9.10
  • Operating System (incl. Version): debian 10

There are more than 6g files in it, can I find it back?
@GongHeng2017
Copy link
Author

@smessmer

@GongHeng2017
Copy link
Author

When debugging the Cryfs source code, it is found that the content in the first data block is empty.

@GongHeng2017
Copy link
Author

image
image
image
As shown in the figure above, the size of other data blocks is normal, but the content of the first block is empty.

@GongHeng2017
Copy link
Author

Excuse me, is there any way to restore data in this situation?
Even if some data is restored.

@GongHeng2017
Copy link
Author

@smessmer Can you answer me？ I will thanks you very much。

@smessmer
Copy link
Member
smessmer commented Oct 2, 2024

This sounds like your file system got corrupted. Sorry to hear this happened to you. 0.9 is a pretty old version. Depending on what kind of block it is, you might be able to still access the rest of the filesystem. If it is a directory block, then that directory and subdirectories will be inaccessible.

I'm working on a tool to recover at least some of the data from corrupted file systems, but it isn't ready yet. It is written in Rust and will likely be released with the 2.x Rust rewrite of CryFS.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@smessmer @GongHeng2017
0