On Monday 04 of February 2013 09:13:04 Kevin Kofler wrote: > Timothy Murphy wrote: > > 130203 12:39:34 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: Error: tried to read 16384 bytes at offset 0 23822336. > > InnoDB: Was only able to read -1. > > 130203 12:39:38 InnoDB: Operating system error number 5 in a file > > operation. > > InnoDB: Error number 5 means 'Input/output error'. > > Your Akonadi MySQL database appears to be corrupt. > > To fix this, you probably need to recreate the database somehow, maybe the > Akonadi console can help? The backend database cannot be recovered from Akonadi Console. You can try using some MySQL-InnoDb recovery tools. If that does not work, the only way is to remove your Akonadi database (~/.local/share/akonadi) and it will be recreated on start up. Cheers, Dan > > Kevin Kofler > > _______________________________________________ > kde mailing list > kde@xxxxxxxxxxxxxxxxxxxxxxx > https://admin.fedoraproject.org/mailman/listinfo/kde > New to KDE4? - get help from http://userbase.kde.org -- dvratil@xxxxxxxxxx | Associate Software Engineer / BaseOS / KDE, Qt GPG Key: 0xC59D614F6F4AE348 Fingerprint: 4EC1 86E3 C54E 0B39 5FDD B5FB C59D 614F 6F4A E348
Attachment:
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ kde mailing list kde@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/kde New to KDE4? - get help from http://userbase.kde.org
