| View previous topic :: View next topic |
| Author |
Message |
Gladdle
Guru
Joined: 27 Jul 2008
Posts: 313
Location: Cleebronn, Germany
|
 Posted: Tue Mar 29, 2016 8:48 pm Post subject: SD Crash => MySQL startet nicht mehr |
 |
|
Vorgeschichte: Vor kurzem crashte mein Gentoo auf meinem Banana Pi. Ich habe die meisten Daten wiederhergestellt und auf eine neue SD Karte kopiert. Ebenfalls das Verzeichniss mit dem MySQL Dateien (/var/lib/mysql). Nun will er nicht mehr starten: | Code: | /etc/init.d/mysql restart
* Checking mysqld configuration for mysql ... [ ok ]
* Starting mysql ...
* start-stop-daemon: caught an interrupt
* start-stop-daemon: /usr/sbin/mysqld died [ !! ]
* ERROR: mysql failed to start |
Das Logfile sagt folgendes: | Code: | 160329 21:28:37 [Warning] No argument was provided to --log-bin and neither --log-basename or --log-bin-index where used; This may cause repliction to break when this server acts as a master and has its hostname changed! Please use '--log-basename=g28piserver' or '--log-bin=mysqld-bin' to avoid this problem.
160329 21:28:37 [Note] InnoDB: Using mutexes to ref count buffer pool pages
160329 21:28:37 [Note] InnoDB: The InnoDB memory heap is disabled
160329 21:28:37 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
160329 21:28:37 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
160329 21:28:37 [Note] InnoDB: Compressed tables use zlib 1.2.8
160329 21:28:37 [Note] InnoDB: Using Linux native AIO
160329 21:28:37 [Note] InnoDB: Not using CPU crc32 instructions
160329 21:28:37 [Note] InnoDB: Initializing buffer pool, size = 128.0M
160329 21:28:37 [Note] InnoDB: Completed initialization of buffer pool
160329 21:28:37 [Note] InnoDB: Highest supported file format is Barracuda.
160329 21:28:38 [Note] InnoDB: 128 rollback segment(s) are active.
160329 21:28:38 [Note] InnoDB: Waiting for purge to start
InnoDB: Error: tablespace id is 427 in the data dictionary
InnoDB: but in file ./g28owncloud/oc_file_locks.ibd it is 533!
2016-03-29 21:28:38 9ca93450 InnoDB: Assertion failure in thread 2628334672 in file fil0fil.cc line 635
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.6/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
160329 21:28:38 [ERROR] 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.
To report this bug, see http://kb.askmonty.org/en/reporting-bugs
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.
Server version: 10.0.23-MariaDB-log
key_buffer_size=16777216
read_buffer_size=262144
max_used_connections=0
max_threads=153
thread_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 135817 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x0x0
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = 0x0 thread_stack 0x48000
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash. |
Da mein Dateisystem gecrasht ist bezweifle ich, das es ein "Bug" ist.
Ich habe hier ein paar Informationen gefunden, kann aber nichts mit ihnen anfangen. Gibt es eine Möglichkeit, den MySQL Server zu starten, ohne das ich die Datenbank verliere? Ich habe "innodb_force_recovery = 1" schon versucht. Hat jemand Ideen? |
|
| Back to top |
|
 |
bbgermany
Veteran
Joined: 21 Feb 2005
Posts: 1844
Location: Oranienburg/Germany
|
| Posted: Wed Mar 30, 2016 7:48 am Post subject: |
|
|
Hi,
vielleicht hilft dir der Artikel weiter:
https://www.percona.com/blog/2011/05/13/connecting-orphaned-ibd-files/
MfG. Stefan
_________________
Desktop: Ryzen 5 5600G, 32GB, 2TB, RX7600
Notebook: Dell XPS 13 9370, 16GB, 1TB
Server #1: Ryzen 5 Pro 4650G, 64GB, 16.5TB
Server #2: Ryzen 4800H, 32GB, 22TB |
|
| Back to top |
|
|
Klaus Meier
Advocate
Joined: 18 Apr 2005
Posts: 2908
Location: Bozen
|
| Posted: Wed Mar 30, 2016 11:58 am Post subject: |
|
|
Hat jetzt nichts direkt mit deinem aktuellen Problem zu tun, aber es verhindert den nächsten Crash, der ansonsten vor der Tür steht.
USB-Sticks sind keine SSDs. Man kann sie nicht sehr oft beschreiben. Wenn man darauf etwas anderes als ein Live-System installiert, also ein System, welches auch auf den Stick schreibt, dann sind die sehr schnell hin. Benutze da besser eine Festplatte, auch wenn es etwas aufwändiger ist. Diese leidvolle 'Erfahrung haben inzwischen schon viele machen müssen. |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Deutsches Forum (German)
