This was a faulty disk after all. I just did not see any errors, when
running smartd. However, they showed up when looking on the system
I am currently replacing the disk.
On 8/3/07, George F. Crewe <george.crewe@stripped> wrote:
> Hello everybody,
> I am looking for some help on my mysql server crashes.
> I run version 5.0.27 on Fedora 6.
> However, suddenly mysql server starting crashing. I revised the log
> and it is telling me that is having a input/output operating system
> error on a read operation.
> The error shows up like this on the log:
> 070803 00:29:12 mysqld started
> 070803 0:29:12 InnoDB: Started; log sequence number 0 210331564
> 070803 0:29:12 [Note] /usr/libexec/mysqld: ready for connections.
> Version: '5.0.27' socket: '/var/lib/mysql/mysql.sock' port: 3306
> Source distribution
> InnoDB: Error: tried to read 16384 bytes at offset 0 29802496.
> InnoDB: Was only able to read -1.
> 070803 0:29:43 InnoDB: Operating system error number 5 in a file operation.
> InnoDB: Error number 5 means 'Input/output error'.
> InnoDB: Some operating system error numbers are described at
> InnoDB: http://dev.mysql.com/doc/refman/5.0/en/operating-system-error-codes.html
> InnoDB: File operation call: 'read'.
> InnoDB: Cannot continue operation.
> I check my disk with smartd utility and it passes the test.
> I do not know where to look. Any help will be greatly appreciated.
> George Crewe