hi guys, i was running my mariadb 5.2.4 and i got some problems (i think it´s a harddisk problem...) check the errorlog

120615 21:38:48 mysqld_safe Starting mysqld daemon with databases from /home/mysql/data/local/
120615 21:38:49 [Warning] '-skip-locking' is deprecated and will be removed in a future release. Please use '-skip-external-locking' instead.
120615 21:38:49 [Warning] '-log_slow_queries' is deprecated and will be removed in a future release. Please use ''slow_query_log'/'-log-slow-file'' inste
ad.
120615 21:38:49 [Note] PrimeBase XT (PBXT) Engine 1.0.11-7 Pre-GA loaded...
120615 21:38:49 [Note] Paul McCullagh, PrimeBase Technologies GmbH, http://www.primebase.org
InnoDB: The InnoDB memory heap is disabled
InnoDB: Mutexes and rw_locks use GCC atomic builtins
InnoDB: Compressed tables use zlib 1.2.3
120615 21:38:49 InnoDB: highest supported file format is Barracuda.
120615 21:38:50 Percona XtraDB (http://www.percona.com) 1.0.13-11.6 started; log sequence number 45356
120615 21:38:50 [Note] Event Scheduler: Loaded 0 events
120615 21:38:50 [Note] ./bin/mysqld: ready for connections.
Version: '5.2.4-MariaDB-log' socket: '/tmp/mysql.BH.sock' port: 3307 (MariaDB - http://mariadb.com/)

============ here the error:

120628 19:05:18 [ERROR] Got error 134 when reading table './raja_comercial/est_mov'
120628 19:08:42 [ERROR] Got error 134 when reading table './raja_comercial/est_mov'

============ here i turned mysqld down

120703 15:18:12 [Note] ./bin/mysqld: 'Shutdown' normal

120703 15:18:12 [Note] Event Scheduler: Purging the queue. 0 events
120703 15:18:13 InnoDB: Starting shutdown...
120703 15:18:14 InnoDB: Shutdown completed; log sequence number 45356
120703 15:18:14 [Note] PrimeBase XT Engine shutdown...
120703 15:18:14 [Note] ./bin/mysqld: 'Shutdown' completo

120703 15:18:14 mysqld_safe mysqld from pid file /home/mysql/pid/local.pid ended
120703 16:19:50 mysqld_safe Starting mysqld daemon with databases from /home/mysql/data/local/
120703 16:19:50 [Warning] '-skip-locking' is deprecated and will be removed in a future release. Please use '-skip-external-locking' instead.
120703 16:19:50 [Warning] '-log_slow_queries' is deprecated and will be removed in a future release. Please use ''slow_query_log'/'-log-slow-file'' inste
ad.
120703 16:19:51 [Note] PrimeBase XT (PBXT) Engine 1.0.11-7 Pre-GA loaded...
120703 16:19:51 [Note] Paul McCullagh, PrimeBase Technologies GmbH, http://www.primebase.org
InnoDB: The InnoDB memory heap is disabled
InnoDB: Mutexes and rw_locks use GCC atomic builtins
InnoDB: Compressed tables use zlib 1.2.3
120703 16:19:51 InnoDB: highest supported file format is Barracuda.
120703 16:19:52 Percona XtraDB (http://www.percona.com) 1.0.13-11.6 started; log sequence number 45356

120703 16:19:52 [Note] Event Scheduler: Loaded 0 events
120703 16:19:52 [Note] ./bin/mysqld: ready for connections.
Version: '5.2.4-MariaDB-log' socket: '/tmp/mysql.BH.sock' port: 3307 (MariaDB - http://mariadb.com/)

================= here the error begin more constant:

120703 16:42:05 [ERROR] Got error 134 when reading table './raja_comercial/est_mov'
120703 16:42:05 [ERROR] Got error 134 when reading table './raja_comercial/est_mov'
120703 16:42:34 [ERROR] Got error 134 when reading table './raja_comercial/est_mov'
120703 16:42:34 [ERROR] Got error 134 when reading table './raja_comercial/est_mov'

....

this continue about 5 times per minute

....
i runned REPAIR TABLE est_mov in raja_comercial database....
and... :'(

120703 20:38:02 [Note] Found 1220320 of 5315703 rows when repairing './raja_comercial/est_mov'

anyidea what could happened with my data?

i got this information at perror:

[root@raja2 log]# perror 134
MySQL error code 134: Record was already deleted (or record file crashed)

any idea?