MariaDB failed to start after backup

Having issues with your DietPi installation, or, found a bug? Post it here.
Post Reply
asouthernboy
Posts: 2
Joined: Mon Jun 10, 2019 8:28 pm

MariaDB failed to start after backup

Post by asouthernboy » Tue Aug 06, 2019 7:21 pm

I have dietpi running on RPI 3B+ , working smoothly for few months, software installed is Kodi , Transmission and MariaDB which i use to remotely connect to from another RPI.

Database is around 200mb and i have moves User Data to USB stick plugged to RPI.
Yesterday i tried to do backup and after its finished i couldn't start MariaDB anymore.

Is there a simpler way to fix or i need to start from scratch? I wouldn't want to loose months of data in the database.

here's part of the log
2019-08-06 19:17:06 1988513584 [Note] InnoDB: innodb_empty_free_list_algorithm has been changed to legacy because of small buffer pool size. In order to use backoff, increase buffer pool at least up to 20MB.

2019-08-06 19:17:06 1988513584 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2019-08-06 19:17:06 1988513584 [Note] InnoDB: The InnoDB memory heap is disabled
2019-08-06 19:17:06 1988513584 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2019-08-06 19:17:06 1988513584 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2019-08-06 19:17:06 1988513584 [Note] InnoDB: Compressed tables use zlib 1.2.8
2019-08-06 19:17:06 1988513584 [Note] InnoDB: Using Linux native AIO
2019-08-06 19:17:06 1988513584 [Note] InnoDB: Using generic crc32 instructions
2019-08-06 19:17:06 1988513584 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2019-08-06 19:17:06 1988513584 [Note] InnoDB: Completed initialization of buffer pool
2019-08-06 19:17:06 1988513584 [Note] InnoDB: Highest supported file format is Barracuda.
2019-08-06 19:17:06 1988513584 [Note] InnoDB: Starting crash recovery from checkpoint LSN=666858058
2019-08-06 19:17:06 1988513584 [Note] InnoDB: Restoring possible half-written data pages from the doublewrite buffer...
2019-08-06 19:17:06 1988513584 [ERROR] InnoDB: Database page corruption on disk or a failed file read of tablespace ./ibdata1 page [page id: space=0, page number=253]. You may have to recover from a backup.
2019-08-06 19:17:06 76864f30 InnoDB: Page dump in ascii and hex (16384 bytes):
len 16384; hex

Post Reply