Mysql crash - Status: { DRDY ERR } error: {IDNF}

Issues related to applications and software problems
Post Reply
exop
Posts: 3
Joined: 2018/08/28 13:02:34

Mysql crash - Status: { DRDY ERR } error: {IDNF}

Post by exop » 2019/09/16 16:28:03

Hello,

My mySQL server crashed today because of a corrupted physical disk.
I changed the disk and we could rebuild it with the raid 10.

But the error is still here.

Any idea?
2019-09-16 18_23_56-Window.png
2019-09-16 18_23_56-Window.png (82.94 KiB) Viewed 2001 times

User avatar
TrevorH
Site Admin
Posts: 33216
Joined: 2009/09/24 10:40:56
Location: Brighton, UK

Re: Mysql crash - Status: { DRDY ERR } error: {IDNF}

Post by TrevorH » 2019/09/16 16:57:42

I'd say you either replaced the wrong disk or you have a second dead one.

No idea why you considered it necessary to obscure parts of the error messages. Even the hostname isn't exactly sensitive information.
The future appears to be RHEL or Debian. I think I'm going Debian.
Info for USB installs on http://wiki.centos.org/HowTos/InstallFromUSBkey
CentOS 5 and 6 are deadest, do not use them.
Use the FAQ Luke

exop
Posts: 3
Joined: 2018/08/28 13:02:34

Re: Mysql crash - Status: { DRDY ERR } error: {IDNF}

Post by exop » 2019/09/17 08:59:03

I fixed my problem.
TrevorH wrote:
2019/09/16 16:57:42
I'd say you either replaced the wrong disk or you have a second dead one.

No idea why you considered it necessary to obscure parts of the error messages. Even the hostname isn't exactly sensitive information.
It was not a problem with the new disk.

It was an IDB file that was damaged by the first disk problem that was blocking the mysql service to restart.
Restoring the file with the associated RFM file solved the problem.

thanks anyway.

Sincerely,

User avatar
avij
Retired Moderator
Posts: 3046
Joined: 2010/12/01 19:25:52
Location: Helsinki, Finland
Contact:

Re: Mysql crash - Status: { DRDY ERR } error: {IDNF}

Post by avij » 2019/09/17 10:29:01

The errors you saw were hardware errors. When you restored the file from backup the file got probably written to a different part of the disk. It would be a good idea to do a read test of your RAID array, like with dd if=/dev/sda of=/dev/null bs=1048576 conv=sync,noerror. It is possible that there are still unreadable sectors on your RAID array.

Post Reply