+- Foro de ayuda y soporte técnico de Sysme Software (https://www.sysme.net/foro)
+-- Foro: Software Sysme (Español) (https://www.sysme.net/foro/forumdisplay.php?fid=3)
+--- Foro: Sysme Tpv (https://www.sysme.net/foro/forumdisplay.php?fid=4)
+---- Foro: Resolución de Problemas con Sysme Tpv (https://www.sysme.net/foro/forumdisplay.php?fid=18)
+---- Tema: Base de datos dañada (/showthread.php?tid=9718)
Base de datos dañada - Tarydium - 04-05-2022
Buenas tardes,
Esta mañana se me ha apagado el equipo mientras estaba trabajando y al volverlo a encender me ha dado error de conexión. He revisado el fichero de errores y parece que la base de datos se ha corrompido. He restaurado desde una copia, pero es de enero. Os pido ayuda para ver si hay posibilidad de reparar la base y recuperar aunque sea la facturación.
Os copio las ultimas líneas del fichero de error:
þþ)N’Z¢;InnoDB: End of page dump
220504 17:20:15 InnoDB: Page checksum 1655880802, prior-to-4.0.14-form checksum 2886548763
InnoDB: stored checksum 1655880802, prior-to-4.0.14-form stored checksum 3439263273
InnoDB: Page lsn 0 1318170187, low 4 bytes of lsn at page end 1318214306
InnoDB: Page number (if stored to page already) 5,
InnoDB: space id (if created with >= MySQL-4.1.1 and stored already) 0
InnoDB: Database page corruption on disk or a failed
InnoDB: file read of page 5.
InnoDB: You may have to recover from a backup.
InnoDB: It is also possible that your operating
InnoDB: system has corrupted its own file cache
InnoDB: and rebooting your computer removes the
InnoDB: error.
InnoDB: If the corrupt page is an index page
InnoDB: you can also try to fix the corruption
InnoDB: by dumping, dropping, and reimporting
InnoDB: the corrupt table. You can use CHECK
InnoDB: TABLE to scan your table for corruption.
InnoDB: See also InnoDB: http://dev.mysql.com/doc/refman/5.0/en/forcing-recovery.html
InnoDB: about forcing recovery.
InnoDB: Ending processing because of a corrupt database page.
InnoDB: Log scan progressed past the checkpoint lsn 0 1318216677
220504 17:40:09 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: Doing recovery: scanned up to log sequence number 0 1318218158
InnoDB: Database page corruption on disk or a failed
InnoDB: file read of page 5.
InnoDB: You may have to recover from a backup.
220504 17:40:09 InnoDB: Page dump in ascii and hex (16384 bytes):
len 16384; hex 62b2bc62000000050000000000000000000000004e91ae4b
.
.
.
220504 17:40:09 InnoDB: Page checksum 1655880802, prior-to-4.0.14-form checksum 2886548763
InnoDB: stored checksum 1655880802, prior-to-4.0.14-form stored checksum 3439263273
InnoDB: Page lsn 0 1318170187, low 4 bytes of lsn at page end 1318214306
InnoDB: Page number (if stored to page already) 5,
InnoDB: space id (if created with >= MySQL-4.1.1 and stored already) 0
InnoDB: Database page corruption on disk or a failed
InnoDB: file read of page 5.
InnoDB: You may have to recover from a backup.
InnoDB: It is also possible that your operating
InnoDB: system has corrupted its own file cache
InnoDB: and rebooting your computer removes the
InnoDB: error.
InnoDB: If the corrupt page is an index page
InnoDB: you can also try to fix the corruption
InnoDB: by dumping, dropping, and reimporting
InnoDB: the corrupt table. You can use CHECK
InnoDB: TABLE to scan your table for corruption.
InnoDB: See also InnoDB: http://dev.mysql.com/doc/refman/5.0/en/forcing-recovery.html
InnoDB: about forcing recovery.
InnoDB: Ending processing because of a corrupt database page.
Si lo necesitais os puedo enviar la carpeta data.
Muchas gracias por todo
RE: Base de datos dañada - sysme - 04-05-2022
Buenas Tarydium,
Tiene mala pinta, habrá que revisar que ficheros han quedado dañados y si se pueden reemplazar, enviame la carpeta data, la reviso y te hago una valoración de si se podría
a info @ sysme.net (sin espacios)