On Sun, Jun 23, 2024 at 04:22:12PM -0300, Crystal Kolipe wrote: > On Sun, Jun 23, 2024 at 07:03:36PM +0000, Anon Loli wrote: > > Okay, I now have a fresh big chunky encrypted drive on another machine and > > can > > transfer the image/files from the corrupted sd3i to it, but when I tried to > > run > > `dd if=/dev/sd3i | ssh destination "dd of=/mnt/somewhere/ssdimage bs=1m" > > or even to a regular file on the same machine, I got this: > > "dd: /dev/sd3i: Device busy" > > Because that partition is mounted. > > Since the system is potentially in an unstable state, I wouldn't try > unmounting it. > > Either use the character device rsd3i, or the whole disc 'c' partition. > > Also, once the image is copied over to the destination, check that it's more > or > less the expected size before finally resetting the source machine or doing > anything else to lose the key. >
Okay, I'm not worried with the resetting of the source machine, it can run 24/7. What I'm worried about, though, is how do I use the copy on the destination machine to make a filesystem out of it, and do it on an crypto volume of the destination machine? Maybe makefs(8)? And what do I do with the missing 74M? do I truncate that from the copy on the destination machine? This must feel like when doctors do a surgery... I did similar stuff with FreeBSD's encrypted volume, but it was just the metadata that was deleted (that time it wasn't me that was the culprit but some program on another OS) and other stuff I forgot.. I like this, this is, I bet, how one learns stufff and remembers them because well they're traumatic :)
