don't do ai and code kids
don't do ai and code kids
You're viewing a single thread.
277 comments
-
How the fuck can it not recover the files?
Fun fact, files don't just get instantly nuked when you delete them, those areas are just marked with a deleted flag and only when you start adding new files it gets overwritten.
That why some people send a bunch of 0s to their partition to completely wipe it.
https://unix.stackexchange.com/questions/636677/filling-my-hard-drive-with-zeros
-
How the fuck can it not recover the files?
Nobody on StackExchange told it the commands to do so.
-
How the fuck can it not recover the files?
Undeleting files typically requires low-level access to the drive containing the deleted files.
\ Do you really want to give an AI, the same one that just wiped your files, that kind of access to your data? -
Then 1s, then a pattern of 1s and 0s, then the inverse of that pattern, then another pattern, for a number of cycles.
Data can actually be recovered beyond multiple overwrites, if enough time and money is thrown at it.
-
If there is something on your disk that a state actor is going to use magnetic microscopy to try to recover, it seems absurd to worry about still being able to use that hard drive and not just crush/melt it to be sure.
-
They keep saying that but those Bitcoins are still in the dump. (I'm aware it's not comparable since having the drive in hand versus missing is a huge difference. Just a little joke.)
-
-
On some filesystems the data is still there but the filenames associated with it are gone or mangled. That makes it harder to recover things. In addition, while it's true that the contents are only overwritten when you write data to the disk, data is constantly being written to the disk. Caches are being updated, backup files are being saved, updates are being downloaded, etc. If you only delete one file the odds are decent that that part of the disk might not be used next. But, if you nuke the entire drive, then you're probably going to lose something.
-
On the upside, they specified D: drive which is typically a lesser used bulk storage drive, so less activity to potentially overwrite the files marked as deleted
-
It's not necessarily a "bulk storage" drive, it's just not the main system drive. It would probably have less activity than the "C" drive, but other than the OS, plenty of other things might be installed on that drive. If it happens to be where someone installed their web browser, there could be plenty of churn there.
-
-
-
Because it doesn't have that kind of access to the file system. It can pull and push files from the system but that's it. It has to interact with the file system via an API, it's not got direct access.
-
It was given permission to use rm and it rm'd an entire drive and you want to give it permissions to access hardware sectors.
-
277 comments