obs, is it possible to restore the database using the files under "/var/lib/mysql" ?

Possibly it depends how corrupt things are and what format the tables were in. InnoDB is a lot easier than MyISAM. Either way it's not something I can instruct over a forum.

_________________
Paid support
How to ask for help
1. Give details of your problem
2. Post any errors
3. Post relevant logs.
4. Don't hide details i.e. your domain, it just makes things harder
5. Be polite or you'll be eaten by a grue

Just wondering, maybe it´s a good idea to sign up for another linode, fresh WAMP setup and try to move all my site´s files and recover the database, what do you think?
My Ubuntu version is 12.04, do you think it is worth to install Ubuntu 14, would that make the migration harder?

How do you plan on recovering the database? Just copying /var/lib/mysql to a new node won't help and upgrading to 14.04 will make things more complicated

_________________
Paid support
How to ask for help
1. Give details of your problem
2. Post any errors
3. Post relevant logs.
4. Don't hide details i.e. your domain, it just makes things harder
5. Be polite or you'll be eaten by a grue

I was planning to do something like in this tutorial:
http://www.thegeekstuff.com/2014/04/rec ... odb-mysql/

What do you suggest? I´m lost.
Thank you.

That only applies if the innodb log file is corrupt which probably won't help you since you've not shown any errors about innodb and unless you know what innodb is I doubt you're using it. Without looking at the server I can't make any suggestions.

For the future you should test backups regularly.

_________________
Paid support
How to ask for help
1. Give details of your problem
2. Post any errors
3. Post relevant logs.
4. Don't hide details i.e. your domain, it just makes things harder
5. Be polite or you'll be eaten by a grue

What do you mean by testing backups?
I have backups enabled daily and always take a snapshot before an upgrade. It´s so strange that this time even my 2 months old snapshot didn´t work. The site "died" 2 weeks ago.
I can´t pay much obs, but could you help me?
Thanks

Testing backups means restoring them to another node and making sure they work. In your case you should at least have a cron that runs

mysqldump --single-transaction -A > /root/backup.sql

before the backup runs before the Linode backups that way you have an easily to restore backup of the database.

Ping me an email at admin@rwky.net with your ssh details and I'll take a quick look, odds are I'll be able to tell you how knackered it is within a few minutes.

_________________
Paid support
How to ask for help
1. Give details of your problem
2. Post any errors
3. Post relevant logs.
4. Don't hide details i.e. your domain, it just makes things harder
5. Be polite or you'll be eaten by a grue

Thanks a lot obs.
Sent you the email.

Thank you obs, you saved my life!

Where do i place:

mysqldump --single-transaction -A > /root/backup.sql

Is it inside "crontab -e"?

Yep that would do, for Ubuntu/Debian this would back up the database at 5am every day

0 5 * * * /usr/bin/mysqldump --defaults-extra-file=/etc/mysql/debian.cnf --single-transaction -A > /root/backup.sql

Obviously you'll want to change the time of day so it's just before your Linode backup window.

Also on another note, Linode backups are stored in the same DC as the host server so if there's a major inccident i.e. a fire you can potentiallly lose both the live site. You should copy your site files and database dump perodically to somewhere off site. At a minimum using rsync or sftp to download them to your local machine would do.

_________________
Paid support
How to ask for help
1. Give details of your problem
2. Post any errors
3. Post relevant logs.
4. Don't hide details i.e. your domain, it just makes things harder
5. Be polite or you'll be eaten by a grue

Thanks Rowan, great tips too.