Hi all,

I must first confess I am a a complete ignoramus when it comes to how data
bases work.
I have been quite happily using mythtv and gallery 2, which both use mysql,
having followed directions to get the database bit set up. All has been
happy for 2 years or so.
However out of the blue it was pointed out to me that the gallery was not
working, on investigation I found the mysqld was not starting. Trying to
start it manually results in this error

[sid@server ~]$ sudo mysqld
[sudo] password for sid:
111119 22:20:12 InnoDB: Initializing buffer pool, size = 8.0M
111119 22:20:12 InnoDB: Completed initialization of buffer pool
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
111119 22:20:12 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
InnoDB: 1 transaction(s) which must be rolled back or cleaned up
InnoDB: in total 1698 row operations to undo
InnoDB: Trx id counter is 0 14081792
InnoDB: Starting in background the rollback of uncommitted transactions
111119 22:20:13 InnoDB: Rolling back trx with id 0 14081350, 1698 rows to
undo

InnoDB: Progress in percents: 1InnoDB: Error: tried to read 16384 bytes at
offset 0 770048.
InnoDB: Was only able to read -1.
111119 22:20:50 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.1/...-system-error-
codes.html
InnoDB: File operation call: 'read'.
InnoDB: Cannot continue operation.
[sid@server ~]$

Any one here have a clue as to how to fix this?

--
sid
RLU 300284
2010.2

On Sat, 19 Nov 2011 22:34:55 +0000, sid wrote:
Buy a new disk, restore from offline backup. 'Input/output error' is
not a good sign for the longevity of this disk.

--
The trouble with things that extend your lifespan is that they happen
at wrong end. I'd hate to be wearing Depends at 85 and thinking "I gave
up booze and cigarettes for three more years of this."

sid <sidshouse (AT) thecrap (DOT) blueyonder.co.uk> wrote:

InnoDB could not read from disk. Check the syslog (I assume this
is Linux?) for additional info. This could be a logical error
(InnoDB corruption or file system corruption) too.

Was there any unusual activity in the recent past? System crash?
Power loss? File system crash?


XL

Peter H. Coffin wrote:

<snip error>

Thanks for answering Peter, it's not the answer I wanted to here but thanks
anyway.

what offline backups would that be then? :-(

--
sid
RLU 300284
2010.2