[nabz]

Hi all,
I'm trying to migrate from 13.2 to 14.0 but I get an error upgrading mysql database from version 78 to 90. I think it's a problem on the DB Server (Dlink DNS320 NAS) but I cannot fix it.

Here is the mysql 5.5.28 error.log:
Any idea how to fix it?

Thanks in advanced.

Code:

141231 16:18:06 mysqld_safe Starting mysqld daemon with databases from /srv/mysql/datadir
141231 16:18:06 InnoDB: The InnoDB memory heap is disabled
141231 16:18:06 InnoDB: Mutexes and rw_locks use GCC atomic builtins
141231 16:18:06 InnoDB: Compressed tables use zlib 1.2.6
141231 16:18:06 InnoDB: Initializing buffer pool, size = 16.0M
141231 16:18:06 InnoDB: Completed initialization of buffer pool
141231 16:18:06 InnoDB: highest supported file format is Barracuda.
141231 16:18:07  InnoDB: Waiting for the background threads to start
141231 16:18:08 InnoDB: 1.1.8 started; log sequence number 356173679
141231 16:18:08 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
141231 16:18:08 [Note]   - '0.0.0.0' resolves to '0.0.0.0';
141231 16:18:08 [Note] Server socket created on IP: '0.0.0.0'.
141231 16:18:08 [Warning] 'user' entry 'root@ShareCenter' ignored in --skip-name-resolve mode.
141231 16:18:08 [Warning] 'proxies_priv' entry '@ root@ShareCenter' ignored in --skip-name-resolve mode.
141231 16:18:08 [Note] Event Scheduler: Loaded 0 events
141231 16:18:08 [Note] /ffp/bin/mysqld: ready for connections.
Version: '5.5.28'  socket: '/ffp/var/run/mysql/mysql.sock'  port: 3306  Source distribution
141231 16:18:42  InnoDB: Assertion failure in thread 1187906752 in file sync0rw.ic line 283
InnoDB: Failing assertion: success
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
16:18:42 UTC - mysqld got signal 6 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
We will try our best to scrape up some info that will hopefully help
diagnose the problem, but since we have already crashed,
something is definitely wrong and this may fail.

key_buffer_size=16384
read_buffer_size=262144
max_used_connections=1
max_threads=151
thread_count=1
connection_count=1
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 49437 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

141231 16:18:42 mysqld_safe Number of processes running now: 0
141231 16:18:42 mysqld_safe mysqld restarted
141231 16:18:42 InnoDB: The InnoDB memory heap is disabled
141231 16:18:42 InnoDB: Mutexes and rw_locks use GCC atomic builtins
141231 16:18:42 InnoDB: Compressed tables use zlib 1.2.6
141231 16:18:42 InnoDB: Initializing buffer pool, size = 16.0M
141231 16:18:42 InnoDB: Completed initialization of buffer pool
141231 16:18:42 InnoDB: highest supported file format is Barracuda.
InnoDB: Log scan progressed past the checkpoint lsn 356173679
141231 16:18:42  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 356977584
InnoDB: 1 transaction(s) which must be rolled back or cleaned up
InnoDB: in total 5009 row operations to undo
InnoDB: Trx id counter is 300D300
141231 16:18:44  InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents: 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99
InnoDB: Apply batch completed
InnoDB: Starting in background the rollback of uncommitted transactions
141231 16:18:45  InnoDB: Rolling back trx with id 300D101, 5009 rows to undo

InnoDB: Progress in percents: 1141231 16:18:45  InnoDB: Waiting for the background threads to start
2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61141231 16:18:46 InnoDB: 1.1.8 started; log sequence number 356977584
141231 16:18:46 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
141231 16:18:46 [Note]   - '0.0.0.0' resolves to '0.0.0.0';
141231 16:18:46 [Note] Server socket created on IP: '0.0.0.0'.
141231 16:18:46 [Warning] 'user' entry 'root@ShareCenter' ignored in --skip-name-resolve mode.
141231 16:18:46 [Warning] 'proxies_priv' entry '@ root@ShareCenter' ignored in --skip-name-resolve mode.
141231 16:18:46 [Note] Event Scheduler: Loaded 0 events
141231 16:18:46 [Note] /ffp/bin/mysqld: ready for connections.
Version: '5.5.28'  socket: '/ffp/var/run/mysql/mysql.sock'  port: 3306  Source distribution
62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100
InnoDB: Rolling back of trx id 300D101 completed
141231 16:18:47  InnoDB: Rollback of non-prepared transactions completed
141231 16:19:19  InnoDB: Assertion failure in thread 1187906752 in file sync0rw.ic line 283
InnoDB: Failing assertion: success
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
16:19:19 UTC - mysqld got signal 6 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
We will try our best to scrape up some info that will hopefully help
diagnose the problem, but since we have already crashed,
something is definitely wrong and this may fail.

key_buffer_size=16384
read_buffer_size=262144
max_used_connections=1
max_threads=151
thread_count=1
connection_count=1
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 49437 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

141231 16:19:19 mysqld_safe Number of processes running now: 0
141231 16:19:19 mysqld_safe mysqld restarted
141231 16:19:19 InnoDB: The InnoDB memory heap is disabled
141231 16:19:19 InnoDB: Mutexes and rw_locks use GCC atomic builtins
141231 16:19:19 InnoDB: Compressed tables use zlib 1.2.6
141231 16:19:20 InnoDB: Initializing buffer pool, size = 16.0M
141231 16:19:20 InnoDB: Completed initialization of buffer pool
141231 16:19:20 InnoDB: highest supported file format is Barracuda.
InnoDB: Log scan progressed past the checkpoint lsn 367389783
141231 16:19:20  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 370402580
141231 16:19:23  InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99
InnoDB: Apply batch completed
141231 16:19:27  InnoDB: Waiting for the background threads to start
141231 16:19:28 InnoDB: 1.1.8 started; log sequence number 370402580
141231 16:19:28 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
141231 16:19:28 [Note]   - '0.0.0.0' resolves to '0.0.0.0';
141231 16:19:28 [Note] Server socket created on IP: '0.0.0.0'.
141231 16:19:28 [Warning] 'user' entry 'root@ShareCenter' ignored in --skip-name-resolve mode.
141231 16:19:28 [Warning] 'proxies_priv' entry '@ root@ShareCenter' ignored in --skip-name-resolve mode.
141231 16:19:28 [Note] Event Scheduler: Loaded 0 events
141231 16:19:28 [Note] /ffp/bin/mysqld: ready for connections.
Version: '5.5.28'  socket: '/ffp/var/run/mysql/mysql.sock'  port: 3306  Source distribution