On Sun, Jun 23, 2024 at 12:19:15PM +0000, Anon Loli wrote: > On Sun, Jun 23, 2024 at 11:56:18AM +0000, Anon Loli wrote: > > On Sat, Jun 22, 2024 at 03:28:37PM -0300, Crystal Kolipe wrote: > > > On Sat, Jun 22, 2024 at 06:03:06PM -0000, Stuart Henderson wrote: > > > > If this is really important, I suggest going to buy another drive to > > > > plug in and dd to rather than trying to do anything complicated. > > > > > > Definitely. If the only copy of the key is in RAM, then time is of the > > > essence. > > > > I know.. I have a spare drive that I can enable if only I were to not have a > > problem with the computer detecting the drives (they aren't in /dev at all, > > but > > dmesg is reading them OK), as it is said in the other mailing thread > > "Installer..." > > > > I'll get back to you guys after we fix that issue (if we do, otherwise I'll > > have to do a different approach to enabling the hard drive which would be > > bad > > becaues I want that drive to work as it is, in that computer) > > > > Okay, I've enabled the drive now, how do I approach this?
Connect an external USB storage device to the machine that has the disk that you overwrote, and use dd to copy the raw sd3c device to a file on that new disk. Anything more complicated than that is likely to be a waste of time, and could prejudice your chances of copying the data elsewhere before you lose the encryption key. > I want the drive that's receiving the data copy to be encrypted, and it'll > have > to be over ssh, so I'm assuming some combination of DD and SCP? Forget it. > I've looked on the internet now, and it seems like dump/restore are perfect > for > this (and even faster than dd?) Seriously, forget it.
