-
Notifications
You must be signed in to change notification settings - Fork 96
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
How to explore/extract a partition backup? #105
Comments
By default the image file name should not just like sda8.aa. How did you choose the options so that it's saved as that? Steven |
...
from the log, I did this like 1 year ago so I do not remember Now for the second one, as I said, i can decompress with zstdcat for example, then I cannot mount it, and no idea how |
You should run that command as root, or using root privilege, e.g., Which command did you use to mount the 2nd file? What's the error message? Steven |
For the second file, I used partclone and it said "invalid image" or smthg like that. I've found another command that uses |
Have you check this FAQ? BTW, I am really curious about the Clonezilla live version you are using. Which one do you have? Steven |
Not sure which one I used I quickly checked the page but it does not seem to correspond to my file name |
Please use the latest stable or testing Clonezilla live. Maybe the issue was fixed and it's easier for us to fix if there is any bug. Steven |
??? i cannot remake a year old backup, i'm not that powerful of a magician |
Hello, I spent 2 hours trying various commands to try to mount an image made with clonezilla in order to compare the files from my backup to my current HDD
I could not figure it out because my backups are not the same as everybody else. I have two of them:
They are partition backups.
I've found a command to restore the second backup but I just want to explore it, not restore it.
Other commands are using partclone and it doesn't recognize these as valid image.
So how can I proceed, please? @stevenshiau
The text was updated successfully, but these errors were encountered: