- Used Zammad version: 4.1.x
- Used Zammad installation type: package
- Operating system: Ubuntu 16.04.7
- Browser + version: Chrome 92.0.4515.131
Be able to query and dump users table.
Doing a select * and trying to dump the user table to repair it causes MySQL to always crash at the same row.
Switch the power off to your server until the data is corrupted
So after many hours of troubleshooting I figured out that my
users table has become corrupted due to a power failure and my server ungracefully shutting down.
I’ve tried to dump the table as a way of repairing it, but I can’t even get it to dump the table even with
innodb_force_recovery=1. It keeps crashing MySQL at exactly the same row every time.
I have around 23000 users in the table and have with trial and error managed to get a successful SELECT to run up to around
id=19200, after which it causes MySQL to crash.
The plan now is to dump
"WHERE id<19201" and then drop the table and restore the
My question is, what else do I have to consider, since there will be a few relational issues where other tables reference the users that are about to be lost.
I would presume that the
groups_users would simply require me to delete the rows that reference the users I’ve lost.
What about tickets? I haven’t checked yet but assume it also has a
user_id column, can that be set to
null? What would be the correct way be to still have the tickets in the system but not delete them?