Possible corrupted file system on my VDS

[soja]

Copy paste from my ticket, asking me to post here:

I know support on unmanaged systems is very little, however I have no other options.

I ran a command that was supposed to give me performance numbers on my SSD partition(stupid of me).
That exact command was:
dd if=/dev/zero of=/dev/xvdb1 bs=512 count=99000 oflag=direct

The command appeared to have finished, then my VDS went down and I cannot get it to boot as normal. I get the message "Superblock invalid, trying backup blocks...." then on the next line "Bad magic number in super-block while trying to open /dev/xvdb1".

I have tried all of the backup blocks as recommended on many websites and none have worked. My other file systems are mounted and I can access them fine. my /ssd mount shows as empty, and that is where all of my important(and irreplaceable) data is stored. Again, my stupidity, I have no backups of the data on my SSD partition.

Is there any way from an administration level you can see/recover the data on the ssd partition??

[Edge100x]

The command that you ran overwrote the first ~48 MB of your /dev/xvdb1 partition, which would be your mounted SSD space. In doing this, you likely overwrote important filesystem information in an unrecoverable way. If you didn't keep your own backups, then this will make recovery tough. However, you may have some luck by using "testdisk" type utilities: http://www.debian-administration.org/articles/420

If your VDS was just copied to another machine within the last few hours, giving us two copies of it temporarily, then we could also replace that partition on our end with the old version.

[soja]

Wasn't able to recover anything.

My community response is better than I could of hoped for, they all understand stuff happens, and are focused on rebuilding instead of dwelling on my mistake.

To anyone reading this, learn from my mistakes before you run into a situation like this

BACK EVERYTHING UP

I will be setting up comprehensive backups across all 3 of my VDS servers, as well as my OVH dedicated server in CA and my home PC. I will never let this happen again!