[Debian-mysql] Mysql start niet na wijzigen datadir

[Simkin]

Ik dacht dat het erg eenvoudig was om de Mysql datadir te wijzigen door de volgende stappen uit te voeren:

1. /etc/init.d/mysql stop
2. cp -rp /var/lib/mysql /mnt/data/mysql/
3. vi /etc/mysql/my.cnf --> datadir = /mnt/data/mysql
4. /etc/init.d/mysql start

Maar dit lijkt toch lastiger als ik dacht aangezien de daemon niet meer start:
[FAIL] Starting MySQL database server: mysqld . . . . . . . . . . . . . . failed!

De rechten van de nieuwe datadir zijn exact hetzelfde als de originele locatie.

Log:

code:

Sep 12 09:03:07 vault13 mysqld_safe: Starting mysqld daemon with databases from /mnt/data/mysql
Sep 12 09:03:07 vault13 mysqld: 130912  9:03:07 [Note] Plugin 'FEDERATED' is disabled.
Sep 12 09:03:07 vault13 mysqld: 130912  9:03:07 InnoDB: The InnoDB memory heap is disabled
Sep 12 09:03:07 vault13 mysqld: 130912  9:03:07 InnoDB: Mutexes and rw_locks use GCC atomic builtins
Sep 12 09:03:07 vault13 mysqld: 130912  9:03:07 InnoDB: Compressed tables use zlib 1.2.7
Sep 12 09:03:07 vault13 mysqld: 130912  9:03:07 InnoDB: Using Linux native AIO
Sep 12 09:03:07 vault13 mysqld: 130912  9:03:07 InnoDB: Initializing buffer pool, size = 128.0M
Sep 12 09:03:08 vault13 mysqld: 130912  9:03:08 InnoDB: Completed initialization of buffer pool
Sep 12 09:03:08 vault13 mysqld: 130912  9:03:08 InnoDB: highest supported file format is Barracuda.
Sep 12 09:03:08 vault13 mysqld: 130912  9:03:08  InnoDB: Operating system error number 22 in a file operation.
Sep 12 09:03:08 vault13 mysqld: InnoDB: Error number 22 means 'Invalid argument'.
Sep 12 09:03:08 vault13 mysqld: InnoDB: Some operating system error numbers are described at
Sep 12 09:03:08 vault13 mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.5/en/operating-system-error-codes.html
Sep 12 09:03:08 vault13 mysqld: InnoDB: File name ./ib_logfile0
Sep 12 09:03:08 vault13 mysqld: InnoDB: File operation call: 'aio write'.
Sep 12 09:03:08 vault13 mysqld: InnoDB: Cannot continue operation.
Sep 12 09:03:08 vault13 mysqld_safe: mysqld from pid file /var/run/mysqld/mysqld.pid ended
Sep 12 09:03:22 vault13 /etc/init.d/mysql[25752]: 0 processes alive and '/usr/bin/mysqladmin --defaults-file=/etc/mysql/debian.cnf ping' resulted in
Sep 12 09:03:22 vault13 /etc/init.d/mysql[25752]: #007/usr/bin/mysqladmin: connect to server at 'localhost' failed
Sep 12 09:03:22 vault13 /etc/init.d/mysql[25752]: error: 'Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)'
Sep 12 09:03:22 vault13 /etc/init.d/mysql[25752]: Check that mysqld is running and that the socket: '/var/run/mysqld/mysqld.sock' exists!
Sep 12 09:03:22 vault13 /etc/init.d/mysql[25752]:

Dit probleem lijkt ook voor te komen bij Ubuntu distros maar heeft daar te maken met de App Armor configuratie link maar nmw heeft mijn Debian installatie geen App Armor enabled.

Ik kom er niet uit en zou het prijs stellen als iemand me verder kan helpen.

Distro details:

code:

root@vault13:/var/lib# cat /proc/version
Linux version 3.2.0-4-amd64 ([e-mail]) (gcc version 4.6.3 (Debian 4.6.3-14) ) #1 SMP Debian 3.2.46-1+deb7u1