accidentally overwrote first 512 bytes of wrong disk with dd. Yes 512 bytes not kilobytes or megabytes
I did this when I was changing the password I hope that it will overwrite the old header after It processed the new header with new password. If embedded backup header is ok I can mount my drive, PIM is laaarge so it takes 24hours to test if backup header is ok. I do not have backup header file. How do I fix the main header with the embedded backup one? Volume contains ext4 filesystem and since only first sector it overwritten I was lucky. The first 512 bytes don't hold fs (ext4) so it is still fine. Is re creating the volume the safest option. I don't want to always use backup, because then I don't have backup for that. I know I can copy the embedded backup to main header with dd but then I don't have plausible deniability.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Answer to the B: header wipe didn't happen destructively. I can still open the volume, but the A: is still unanswered. And now I know that the backup header is ok.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
When an extremely stupid people (me) ask a question before trying "restore volume header..." to see that the default is to use embedded backup as input. LOL problem solved.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
accidentally overwrote first 512 bytes of wrong disk with dd. Yes 512 bytes not kilobytes or megabytes
I did this when I was changing the password I hope that it will overwrite the old header after It processed the new header with new password. If embedded backup header is ok I can mount my drive, PIM is laaarge so it takes 24hours to test if backup header is ok. I do not have backup header file. How do I fix the main header with the embedded backup one? Volume contains ext4 filesystem and since only first sector it overwritten I was lucky. The first 512 bytes don't hold fs (ext4) so it is still fine. Is re creating the volume the safest option. I don't want to always use backup, because then I don't have backup for that. I know I can copy the embedded backup to main header with dd but then I don't have plausible deniability.
Still the same.
A:How do I fix main header using the embedded one in the volume?
B: when changing password how/when is the header wipe done?
Answer to the B: header wipe didn't happen destructively. I can still open the volume, but the A: is still unanswered. And now I know that the backup header is ok.
good thing you caught it early
When an extremely stupid people (me) ask a question before trying "restore volume header..." to see that the default is to use embedded backup as input. LOL problem solved.
So how did you do it? Did you use the rescue disk? or how do you access the backup header?