#2006 - MySQL server has gone away

I got trouble with the server mysql (( #2006 - MySQL server has gone away) , I tried deleting it, uninstall it , to increase the session in the file my.cnf , but it doesn’t change anything, the demon mysql after gets restarted every second and it makes every operation impossibile .
More than increasing max_allowed_packet , is it possible to do anything ese ?

No is 1.2.9 version , log file is empty
var/log
0 -rw-r----- 1 mysql adm 0 Oct 13 16:43 mysql.err
0 -rw-r----- 1 mysql adm 0 Oct 15 06:27 mysql.log

var/log/mysql

-rw-r----- 1 mysql adm 0 Oct 15 06:27 mysql.log

Oct 15 08:52:03 bsbitaliansoldiers mysqld: InnoDB: Error: tried to read 16384 bytes at offset 0 21331968.
Oct 15 08:52:03 bsbitaliansoldiers mysqld: InnoDB: Was only able to read -1.
Oct 15 08:52:03 bsbitaliansoldiers mysqld: 151015 8:52:03 InnoDB: Operating system error number 5 in a file operation.
Oct 15 08:52:03 bsbitaliansoldiers mysqld: InnoDB: Error number 5 means 'Input/output error'.
Oct 15 08:52:03 bsbitaliansoldiers mysqld: InnoDB: Some operating system error numbers are described at
Oct 15 08:52:03 bsbitaliansoldiers mysqld: InnoDB: http://dev.mysql.com/doc/refma…g-system-error-codes.html
Oct 15 08:52:03 bsbitaliansoldiers mysqld: InnoDB: File operation call: 'read'.
Oct 15 08:52:03 bsbitaliansoldiers mysqld: InnoDB: Cannot continue operation.
Oct 15 08:52:03 bsbitaliansoldiers mysqld_safe: Number of processes running now: 0
Oct 15 08:52:03 bsbitaliansoldiers mysqld_safe: mysqld restarted
Oct 15 08:52:03 bsbitaliansoldiers mysqld: 151015 8:52:03 [Warning] Using unique option prefix key_buffer instead of key_buffer_size is deprecated and will be removed in a future release. Please use the full name instead.
Oct 15 08:52:03 bsbitaliansoldiers mysqld: 151015 8:52:03 [Note] /usr/sbin/mysqld (mysqld 5.5.44-0+deb7u1) starting as process 28815 ...
Oct 15 08:52:03 bsbitaliansoldiers mysqld: 151015 8:52:03 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead.
Oct 15 08:52:03 bsbitaliansoldiers mysqld: 151015 8:52:03 [Note] Plugin 'FEDERATED' is disabled.
Oct 15 08:52:03 bsbitaliansoldiers mysqld: 151015 8:52:03 InnoDB: The InnoDB memory heap is disabled
Oct 15 08:52:03 bsbitaliansoldiers mysqld: 151015 8:52:03 InnoDB: Mutexes and rw_locks use GCC atomic builtins
Oct 15 08:52:03 bsbitaliansoldiers mysqld: 151015 8:52:03 InnoDB: Compressed tables use zlib 1.2.7
Oct 15 08:52:03 bsbitaliansoldiers mysqld: 151015 8:52:03 InnoDB: Using Linux native AIO
Oct 15 08:52:03 bsbitaliansoldiers mysqld: 151015 8:52:03 InnoDB: Initializing buffer pool, size = 128.0M
Oct 15 08:52:03 bsbitaliansoldiers mysqld: 151015 8:52:03 InnoDB: Completed initialization of buffer pool
Oct 15 08:52:03 bsbitaliansoldiers mysqld: 151015 8:52:03 InnoDB: highest supported file format is Barracuda.
Oct 15 08:52:03 bsbitaliansoldiers mysqld: InnoDB: Log scan progressed past the checkpoint lsn 60751980359
Oct 15 08:52:03 bsbitaliansoldiers mysqld: 151015 8:52:03 InnoDB: Database was not shut down normally!
Oct 15 08:52:03 bsbitaliansoldiers mysqld: InnoDB: Starting crash recovery.
Oct 15 08:52:03 bsbitaliansoldiers mysqld: InnoDB: Reading tablespace information from the .ibd files...
Oct 15 08:52:03 bsbitaliansoldiers mysqld: InnoDB: Restoring possible half-written data pages from the doublewrite
Oct 15 08:52:03 bsbitaliansoldiers mysqld: InnoDB: buffer...
Oct 15 08:52:03 bsbitaliansoldiers mysqld: InnoDB: Doing recovery: scanned up to log sequence number 60751980908
Oct 15 08:52:03 bsbitaliansoldiers mysqld: 151015 8:52:03 InnoDB: Starting an apply batch of log records to the database...
Oct 15 08:52:03 bsbitaliansoldiers mysqld: InnoDB: Progress in percents: 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99
Oct 15 08:52:03 bsbitaliansoldiers mysqld: InnoDB: Apply batch completed
Oct 15 08:52:04 bsbitaliansoldiers mysqld: 151015 8:52:04 InnoDB: Waiting for the background threads to start
Oct 15 08:52:05 bsbitaliansoldiers mysqld: 151015 8:52:05 InnoDB: 5.5.44 started; log sequence number 60751980908
Oct 15 08:52:05 bsbitaliansoldiers mysqld: 151015 8:52:05 [Note] Server hostname (bind-address): '127.0.0.1'; port: 3306
Oct 15 08:52:05 bsbitaliansoldiers mysqld: 151015 8:52:05 [Note] - '127.0.0.1' resolves to '127.0.0.1';
Oct 15 08:52:05 bsbitaliansoldiers mysqld: 151015 8:52:05 [Note] Server socket created on IP: '127.0.0.1'.
Oct 15 08:52:05 bsbitaliansoldiers mysqld: 151015 8:52:05 [Note] Event Scheduler: Loaded 0 events
Oct 15 08:52:05 bsbitaliansoldiers mysqld: 151015 8:52:05 [Note] /usr/sbin/mysqld: ready for connections.
Oct 15 08:52:05 bsbitaliansoldiers mysqld: Version: '5.5.44-0+deb7u1' socket: '/var/run/mysqld/mysqld.sock' port: 3306 (Debian)

run , is hdd problem

possible that several files have been deleted for the operation of the server?