This error seems to be related to the MySQL-Bug #58406 (status: verified).
For the moment, you can ignore that message. The process skips the table and continues as always.
Whatever, if you want to make sure that your database has not been corrupted in consequence of this error, simply force mysqldump to ignore all performance_schema-tables.
Plesk way:
“automysqlbackup: Unknown table engine ‘PERFORMANCE_SCHEMA’”Continue reading
Of course!
You can try a ‘file -s’ on the device node.
root@rescue /mnt # file -s /dev/md1 /dev/md1: Linux rev 1.0 ext4 filesystem data, UUID=e77cc8ce-ade6-4e09-ac7f-d139c80a2e4a (needs journal recovery) (extents) (large files) (huge files) root@rescue /mnt #
All you need to do is access the terminal using the installation CD/DVD of your GNU/Linux operating system or to do the boot over network with RIPLinux. Once you are in the terminal, you will have to access the ‘grub’ shell to change the grub configuration:
# grub
You will get the grub-shell prompt:
“Recovery Grub Legacy boot loader from grub-shell”Continue reading
On a non-GPT partition table you can do
sfdisk -d /dev/sda | sfdisk /dev/sdb.
But sfdisk doesn’t support GPT partition tables.
Then you shall make:
“How to copy a GPT partition scheme from one hard drive to another?”Continue reading