Bug #96776 | The database crashes and restarts automatically.Then keep this status.. | ||
---|---|---|---|
Submitted: | 6 Sep 2019 9:18 | Modified: | 10 Sep 2019 8:23 |
Reporter: | Jhonson Leo | Email Updates: | |
Status: | Not a Bug | Impact on me: | |
Category: | MySQL Server: DML | Severity: | S1 (Critical) |
Version: | 5.6.32 | OS: | CentOS (CentOS release 6.9 (Final)) |
Assigned to: | MySQL Verification Team | CPU Architecture: | Any |
[6 Sep 2019 9:18]
Jhonson Leo
[6 Sep 2019 9:42]
Jhonson Leo
Dear, Has anyone met it? Although there is no evidence, I think it may be a hardware problem. And I'm sure the disk still has storage. As follow:$ df -hl Filesystem Size Used Avail Use% Mounted on /dev/sdb1 1.8T 1.4T 354G 80% / tmpfs 32G 629M 31G 2% /dev/shm /dev/sda2 190M 39M 142M 22% /boot /dev/sda1 200M 264K 200M 1% /boot/efi /dev/sdc1 1.8T 68M 1.7T 1% /new Is there a solution? Best Regards. Leo.
[6 Sep 2019 15:27]
MySQL Verification Team
Hi, For start you really should upgrade to latest 5.6. Now, this I/O error looks like a hardware error. Please check what dmesg and syslog have to say. all best
[10 Sep 2019 2:14]
Jhonson Leo
Dear Bogdan Kecman, Thanks for your reply! We replaced the hard disk of the server first.But it seems to be the same problem that prevents the database from being copied.So we created a new database and restored the original backup. According to what you said, I did the corresponding environment check.It has been confirmed that it is a hardware problem. [root@$ ~]# badblocks -s -v /dev/sdb1 正在检查从 0 到 1953513471的块 Checking for bad blocks (read-only test): 968188800one, 3:22:11 elapsed 968188836one, 3:23:15 elapsed 968188837one, 3:23:36 elapsed 968188838one, 3:23:57 elapsed 968188839one, 3:24:19 elapsed 969017368one, 3:24:53 elapsed 969017424one, 3:25:36 elapsed 969017425one, 3:25:57 elapsed 969017426one, 3:26:19 elapsed 969017427one, 3:26:40 elapsed 完成 Pass completed, 10 bad blocks found. [root@$ ~]# dmesg | tail ata2.00: configured for UDMA/133 sd 1:0:0:0: [sdb] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE sd 1:0:0:0: [sdb] Sense Key : Medium Error [current] [descriptor] Descriptor sense data with sense descriptors (in hex): 72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00 73 84 18 a0 sd 1:0:0:0: [sdb] Add. Sense: Unrecovered read error - auto reallocate failed sd 1:0:0:0: [sdb] CDB: Read(10): 28 00 73 84 18 a0 00 00 08 00 end_request: I/O error, dev sdb, sector 1938036896 ata2: EH complete [root@$ ~]# cat /var/log/messages |tail Sep 9 10:27:36 $ kernel: ata2.00: configured for UDMA/133 Sep 9 10:27:36 $ kernel: sd 1:0:0:0: [sdb] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE Sep 9 10:27:36 $ kernel: sd 1:0:0:0: [sdb] Sense Key : Medium Error [current] [descriptor] Sep 9 10:27:36 $ kernel: Descriptor sense data with sense descriptors (in hex): Sep 9 10:27:36 $ kernel: 72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00 Sep 9 10:27:36 $ kernel: 73 84 18 a0 Sep 9 10:27:36 $ kernel: sd 1:0:0:0: [sdb] Add. Sense: Unrecovered read error - auto reallocate failed Sep 9 10:27:36 $ kernel: sd 1:0:0:0: [sdb] CDB: Read(10): 28 00 73 84 18 a0 00 00 08 00 Sep 9 10:27:36 $ kernel: end_request: I/O error, dev sdb, sector 1938036896 Sep 9 10:27:36 $ kernel: ata2: EH complete Thanks again for your advice! Best Regards, Leo.
[10 Sep 2019 8:23]
MySQL Verification Team
Thanks for the update, good luck with it. all best