> 1. I had a drive SSD sd2a which had a 200G crypto volume sd3i which was mounted
> on /mnt/ssd, all 1 partition
Why did you have your crypto volume as an 'i' partition?
How did you create the filesystem that was on sd3i?
> 2. I did a `dd if=/dev/urandom of=/dev/rsd3c bs=1m`
> for a little over 74M then I stopped approximately 7 seconds later
You are screwed.
> 3. After the DD, I couldn't access /mnt/ssd, it said no such file or directory
>
> 4. I now have a HDD which I repurposed to be my backup,
> and I copied /dev/rsd3i over to the HDD as an image
How exactly did you 'copy /dev/rsd3i as an image'?
> 4.5. and verified with sha512 that rsd3i is same as /mnt/hdd/ssdimage, even
> though the ssdimage on the backup drive is 19G larger in size
No. If one is 19G greater that the other, they cannot have the same hash.
So what exactly do you mean by the sizes? Where did you get them?
> 5. Whilst writing this e-mail I realized that I might have made
> a fatal mistake. I think that I backed up rsd3i instead of rsd3c
Tools differ. Some might work with an image of the (broken) filesystem,
which is what you have. (What filesystem was it?) Some expect an image
of the entire disk.
> (I was being extremely careful)
LOL
No comments:
Post a Comment