MoneroForum
Monerica468x60_v1Your ad here
Social Lounge Started Sep 1, 2026 5:24 PM

Would this destroy the server?

1 replies - 40 views - 0 thanks - 0 tippers - 2 watchers

Sep 1, 2026 5:24 PM
#1
Data Destruction

84a82da9-5877-4492-a4f9-c6607afaa6d6
root@ser872889331500:~/backup# shred -n 35 -z -v /dev/vda shred: /dev/vda: pass 1/36 (random)... shred: /dev/vda: pass 1/36 (random)...121MiB/40GiB 0% shred: /dev/vda: pass 1/36 (random)...177MiB/40GiB 0% shred: /dev/vda: pass 1/36 (random)...228MiB/40GiB 0% shred: /dev/vda: pass 1/36 (random)...462MiB/40GiB 1% shred: /dev/vda: pass 1/36 (random)...520MiB/40GiB 1% shred: /dev/vda: pass 1/36 (random)...1.0GiB/40GiB 2% shred: /dev/vda: pass 1/36 (random)...1.1GiB/40GiB 2% shred: /dev/vda: pass 1/36 (random)...1.2GiB/40GiB 3% shred: /dev/vda: pass 1/36 (random)...1.3GiB/40GiB 3% shred: /dev/vda: pass 1/36 (random)...1.4GiB/40GiB 3% shred: /dev/vda: pass 1/36 (random)...1.5GiB/40GiB 3% shred: /dev/vda: pass 1/36 (random)...2.1GiB/40GiB 5% shred: /dev/vda: pass 1/36 (random)...2.2GiB/40GiB 5% shred: /dev/vda: pass 1/36 (random)...2.3GiB/40GiB 5% shred: /dev/vda: pass 1/36 (random)...2.4GiB/40GiB 6% shred: /dev/vda: pass 1/36 (random)...2.5GiB/40GiB 6% shred: /dev/vda: pass 1/36 (random)...2.6GiB/40GiB 6% shred: /dev/vda: pass 1/36 (random)...3.0GiB/40GiB 7% shred: /dev/vda: pass 1/36 (random)...3.1GiB/40GiB 7% shred: /dev/vda: pass 1/36 (random)...3.2GiB/40GiB 8% shred: /dev/vda: pass 1/36 (random)...3.3GiB/40GiB 8%
Is this a way to destroy the server?

Signature

A cute cat-girl who knows a bit about anonymity techniques.
Personal PGP fingerprint: 77E9454AEC3265F44DC9F633642B427879C25A49

0 thanks - 0 tippers - 2 watchers
Monerica468x60_v1Your ad here

Replies

Page 1 of 1 - 1 total
Sep 1, 2026 7:37 PM
#2

Is this a VPS? If it is, and they use an SSD, then you aren't guaranteeing that you delete anything, and you could be writing to a totally different area of the disk due to SSD wear levelling, so you're mostly just wearing down the provider's equipment. If your host uses thin provisioning (we do, at least, and many hosts do), then it may be very difficult to reconstruct the data anyway, because you aren't necessarily mapped to a 40 GB sequential block on the drive, and it could be fragmented, though that is not a guarantee.

If you're storing sensitive things on a VPS, then you should ideally encrypt them before uploading, since even disk encryption on virtual servers is partially flawed: the host can pull the decryption key from memory and image your VPS while it is running, to read with that key later. It doesn't hurt, though, since it can at least protect against one attack, which is if the disk image is taken without the copy of the key. It also means that when you cancel your service, the data on the disk is useless without the decryption key.

Signature

Ko-Net - Privacy focused, free-speech VPS hosting.

0 thanks - 0 tippers
Login to tip

Post A Reply

You must be logged in to reply. Login or register.