Hallo,
"normalerweise" fahre ich den PI vor dem Ausschalten schon sauber herunter. Ich habe an die GPIO auch einen Taster fürs herunterfahren angebracht der über ein Python Script ein "shuddown -h now" auslöst. Ausschließen kann ich es natürlich nicht, das ich mal zu früh den Stecker gezogen habe. Ein mal mit den Gedanken woanders und schon ist es passiert.
Das wichtigste für mich wäre jetzt die Info ob es ein paar wenige Befehle gibt mit denen man das System "reparieren" kann, notfalls auch nur Übergangsweise damit es erst mal wieder läuft. Dann hätte ich Zeit mir eine vernünftige Speicherkarte zu besorgen (ich tendiere zu SanDisk Extreme PRO) und danach in Ruhe das System neu aufzusetzen. Morgen soll die Kiste erst mal wieder laufen. Wenn ich es nicht repariert bekomme müsste ich au die aktuelle Karte neu installieren. Das ist eine Karte die in einem Raspberry Set dabei war. Keine Ahnung was die für eine Qualität hat. Hersteller ist keiner aufgedruckt.
Wenn ich auf dem jetzigen System einfach die Datenbank neu installieren möchte, was müsste ich vorher alles deinstallieren?
Ich hatte damals laut Tutorial folgendes installiert:
Code: Alles auswählen
sudo apt-get install python2.7 libpython2.7 python-setuptools python-ldap python-mysqldb python-memcache python-urllib3 python-pil python-certifi python-idna python-requests mariadb-server-10.0 sqlite3
Einfach die komplette Zeile mit "purge" anstelle "install"?? Oder reichen einzelne Pakete daraus. Ich denke das ganze Python-Zeugs kann man drau lassen, oder?
Noch ein Wort zum Datenverlust bei dieser Methode:
Es handelt sich um einen Seafile-Cloudserver. Die Daten sind auf die Rechner synchronisiert, außerdem gibt es eine aktuelle Sicherung der Dateien. Ein kompletter Datenbankverlust würde nur den Verlust der Dateiversionierung des Cloudservers zur Folge haben. Diese habe ich ohnehin noch nie verwendet. Der effektive Datenverlust wäre also null. Allerdings existiert auch ein aktueller Dump der drei Seafile-Datenbanken. Also lässt sich vermutlich auch dieser Verlust vermeiden. die Rücksicherung dieser Dumps ergibt aber aktuell auch Fehler (siehe oben).
ergibt:
Code: Alles auswählen
Apr 12 01:31:38 server mysqld[888]: 200412 1:31:38 [Note] InnoDB: The log sequence numbers 1623589 and 1623589 in ibdata files do not match the log sequence number 4745655 in the ib_logfiles!
-- Logs begin at Sun 2020-04-12 01:31:19 CEST, end at Sun 2020-04-12 09:07:32 CEST. --
Apr 12 01:31:36 server systemd[1]: Starting LSB: Start and stop the mysql database server daemon...
Apr 12 01:31:37 server mysqld[888]: 200412 1:31:37 [Note] /usr/sbin/mysqld (mysqld 10.0.28-MariaDB-2+b1) starting as process 887 ...
Apr 12 01:31:37 server mysqld[888]: 200412 1:31:37 [Note] InnoDB: Using mutexes to ref count buffer pool pages
Apr 12 01:31:37 server mysqld[888]: 200412 1:31:37 [Note] InnoDB: The InnoDB memory heap is disabled
Apr 12 01:31:37 server mysqld[888]: 200412 1:31:37 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
Apr 12 01:31:37 server mysqld[888]: 200412 1:31:37 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
Apr 12 01:31:37 server mysqld[888]: 200412 1:31:37 [Note] InnoDB: Compressed tables use zlib 1.2.8
Apr 12 01:31:37 server mysqld[888]: 200412 1:31:37 [Note] InnoDB: Using Linux native AIO
Apr 12 01:31:37 server mysqld[888]: 200412 1:31:37 [Note] InnoDB: Not using CPU crc32 instructions
Apr 12 01:31:37 server mysqld[888]: 200412 1:31:37 [Note] InnoDB: Initializing buffer pool, size = 128.0M
Apr 12 01:31:37 server mysqld[888]: 200412 1:31:37 [Note] InnoDB: Completed initialization of buffer pool
Apr 12 01:31:38 server mysqld[888]: 200412 1:31:38 [Note] InnoDB: Highest supported file format is Barracuda.
Apr 12 01:31:38 server mysqld[888]: 200412 1:31:38 [Note] InnoDB: The log sequence numbers 1623589 and 1623589 in ibdata files do not match the log sequence number 4745655 in the ib_logfiles!
Apr 12 01:31:38 server mysqld[888]: 200412 1:31:38 [Note] InnoDB: Database was not shutdown normally!
Apr 12 01:31:38 server mysqld[888]: 200412 1:31:38 [Note] InnoDB: Starting crash recovery.
Apr 12 01:31:38 server mysqld[888]: 200412 1:31:38 [Note] InnoDB: Reading tablespace information from the .ibd files...
Apr 12 01:31:38 server mysqld[888]: 200412 1:31:38 [Note] InnoDB: Restoring possible half-written data pages
Apr 12 01:31:38 server mysqld[888]: 200412 1:31:38 [Note] InnoDB: from the doublewrite buffer...
Apr 12 01:31:38 server mysqld[888]: InnoDB: Database page corruption on disk or a failed
Apr 12 01:31:38 server mysqld[888]: InnoDB: file read of page 279.
Apr 12 01:31:38 server mysqld[888]: InnoDB: You may have to recover from a backup.
Apr 12 01:31:38 server mysqld[888]: 2020-04-12 01:31:38 b6f3f210 InnoDB: Page dump in ascii and hex (16384 bytes):
Apr 12 01:31:38 server mysqld[888]: len 16384; hex ccfab26b000001170000000000000000000000000048566f0006000000000000000000000000fffffffe0000000000000015000001cc1f24000001cc007800000000000000f31a72000001a2000001ccfffffffffffffffffffffffff
Apr 12 01:31:38 server mysqld[888]: fffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff
Apr 12 01:31:38 server mysqld[888]: fffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff
Apr 12 01:31:38 server mysqld[888]: fffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff
Apr 12 01:31:38 server mysqld[888]: fffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff
Apr 12 01:31:38 server mysqld[888]: fffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff
Apr 12 01:31:38 server mysqld[888]: fffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff
Apr 12 01:31:38 server mysqld[888]: fffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff
Apr 12 01:31:38 server mysqld[888]: fffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff
Apr 12 01:31:38 server mysqld[888]: 000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
Apr 12 01:31:38 server mysqld[888]: 000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
Apr 12 01:31:38 server mysqld[888]: 000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
Apr 12 01:31:38 server mysqld[888]: 000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
Apr 12 01:31:38 server mysqld[888]: 000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
Apr 12 01:31:38 server mysqld[888]: 000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
Apr 12 01:31:38 server mysqld[888]: 000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
Apr 12 01:31:38 server mysqld[888]: 000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
Apr 12 01:31:38 server mysqld[888]: 000000000000000000000000000000000000000000000000000000000000000020000000000000000000000000000100000000000000000000001000088008000000000000000000002000000000000000000000000000040000000000040000400000000
Apr 12 01:31:38 server mysqld[888]: 008000000000000000000000000000000000101000000000000000000000000000000000000000000000000000000000000000000000000800000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
Apr 12 01:31:38 server mysqld[888]: 000000000008000000000000001000000000000000000000000000000000000000200000000020000000000000000000000000400080000002000000000000000000000000000000000000000000000000000000000000010000000000000000000000000
Apr 12 01:31:38 server mysqld[888]: 000100000008000800000000000000000000000000000200000000000000000000000000000000000000000000000000000000000008000000000001000008000000000000000000000000000000180000000000000000080000000000000001000000000
Apr 12 01:31:38 server mysqld[888]: 000000000000000000000000000000000000000000000000000000000008000000000000000000000001000000000000000000000000000000000080000000000000000000000100000000000040000000000000004000008000000000010000000000000
Apr 12 01:31:38 server mysqld[888]: 000000000000008008000000000000000000000000008000000000000000000000100080000000000000000400004000000000000000000000000000000000000000000040000000000010000000000004000044000000000000008000000000000000000
Apr 12 01:31:38 server mysqld[888]: 000000020800000000800000000000000000000200000000000000000000000000000000004000000000000000000000000000000000000000000000008000000000000000000000000000000004000000040000000004000000020000000000000000000
Apr 12 01:31:38 server mysqld[888]: 0000000800000000000000080000000000008000200000008000000000000001000000000000000000000000000000000000000000000000000002010000000000000000000000000000000000000080000000000000a0000000004000000000000000000
Apr 12 01:31:38 server mysqld[888]: 000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
Apr 12 01:31:38 server mysqld[888]: 000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
Apr 12 01:31:38 server mysqld[888]: 000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
Apr 12 01:31:38 server mysqld[888]: 000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
Apr 12 01:31:38 server mysqld[888]: 000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
Apr 12 01:31:38 server mysqld[888]: 000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
Apr 12 01:31:38 server mysqld[888]: 000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
Apr 12 01:31:38 server mysqld[888]: 000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
Apr 12 01:31:38 server mysqld[888]:
Apr 12 01:31:38 server mysqld[888]:
Apr 12 01:31:38 server mysqld[888]:
Apr 12 01:31:38 server mysqld[888]:
Apr 12 01:31:38 server mysqld[888]:
Apr 12 01:31:38 server mysqld[888]:
Apr 12 01:31:38 server mysqld[888]:
Apr 12 01:31:38 server mysqld[888]:
Apr 12 01:31:38 server mysqld[888]:
Apr 12 01:31:38 server mysqld[888]:
Apr 12 01:31:38 server mysqld[888]: $ A @ @ @
Apr 12 01:31:38 server mysqld[888]: @ @ @ @
Apr 12 01:31:38 server mysqld[888]: @
Apr 12 01:31:38 server mysqld[888]:
Apr 12 01:31:38 server mysqld[888]:
Apr 12 01:31:38 server mysqld[888]:
Apr 12 01:31:38 server mysqld[888]:
Apr 12 01:31:38 server mysqld[888]: InnoDB: End of page dump
Apr 12 01:31:38 server mysqld[888]: 2020-04-12 01:31:38 b6f3f210 InnoDB: uncompressed page, stored checksum in field1 3438981739, calculated checksums for field1: crc32 2290587878, innodb 2717101534, none 3735928559, stored checksum in f
Apr 12 01:31:38 server mysqld[888]: InnoDB: Page may be a system page
Apr 12 01:31:38 server mysqld[888]: InnoDB: Database page corruption on disk or a failed
Apr 12 01:31:38 server mysqld[888]: InnoDB: file read of page 279.
Apr 12 01:31:38 server mysqld[888]: InnoDB: You may have to recover from a backup.
Apr 12 01:31:38 server mysqld[888]: InnoDB: It is also possible that your operating
Apr 12 01:31:38 server mysqld[888]: InnoDB: system has corrupted its own file cache
Apr 12 01:31:38 server mysqld[888]: InnoDB: and rebooting your computer removes the
Apr 12 01:31:38 server mysqld[888]: InnoDB: error.
Apr 12 01:31:38 server mysqld[888]: InnoDB: If the corrupt page is an index page
Apr 12 01:31:38 server mysqld[888]: InnoDB: you can also try to fix the corruption
Apr 12 01:31:38 server mysqld[888]: InnoDB: by dumping, dropping, and reimporting
Apr 12 01:31:38 server mysqld[888]: InnoDB: the corrupt table. You can use CHECK
Apr 12 01:31:38 server mysqld[888]: InnoDB: TABLE to scan your table for corruption.
Apr 12 01:31:38 server mysqld[888]: InnoDB: See also http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
Apr 12 01:31:38 server mysqld[888]: InnoDB: about forcing recovery.
Apr 12 01:31:38 server mysqld[888]: InnoDB: Ending processing because of a corrupt database page.
Apr 12 01:31:38 server mysqld[888]: 2020-04-12 01:31:38 b6f3f210 InnoDB: Assertion failure in thread 3069440528 in file buf0buf.cc line 4527
Apr 12 01:31:38 server mysqld[888]: InnoDB: We intentionally generate a memory trap.
Apr 12 01:31:38 server mysqld[888]: InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
Apr 12 01:31:38 server mysqld[888]: InnoDB: If you get repeated assertion failures or crashes, even
Apr 12 01:31:38 server mysqld[888]: InnoDB: immediately after the mysqld startup, there may be
Apr 12 01:31:38 server mysqld[888]: InnoDB: corruption in the InnoDB tablespace. Please refer to
Apr 12 01:31:38 server mysqld[888]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
Apr 12 01:31:38 server mysqld[888]: InnoDB: about forcing recovery.
Apr 12 01:31:38 server mysqld[888]: 200412 1:31:38 [ERROR] mysqld got signal 6 ;
Apr 12 01:31:38 server mysqld[888]: This could be because you hit a bug. It is also possible that this binary
Apr 12 01:31:38 server mysqld[888]: or one of the libraries it was linked against is corrupt, improperly built,
Apr 12 01:31:38 server mysqld[888]: or misconfigured. This error can also be caused by malfunctioning hardware.
Apr 12 01:31:38 server mysqld[888]:
Apr 12 01:31:38 server mysqld[888]: To report this bug, see https://mariadb.com/kb/en/reporting-bugs
Apr 12 01:31:38 server mysqld[888]:
Apr 12 01:31:38 server mysqld[888]: We will try our best to scrape up some info that will hopefully help
Apr 12 01:31:38 server mysqld[888]: diagnose the problem, but since we have already crashed,
Apr 12 01:31:38 server mysqld[888]: something is definitely wrong and this may fail.
Apr 12 01:31:38 server mysqld[888]:
Apr 12 01:31:38 server mysqld[888]: Server version: 10.0.28-MariaDB-2+b1
Apr 12 01:31:38 server mysqld[888]: key_buffer_size=16777216
Apr 12 01:31:38 server mysqld[888]: read_buffer_size=131072
Apr 12 01:31:38 server mysqld[888]: max_used_connections=0
Apr 12 01:31:38 server mysqld[888]: max_threads=153
Apr 12 01:31:38 server mysqld[888]: thread_count=0
Apr 12 01:31:38 server mysqld[888]: It is possible that mysqld could use up to
Apr 12 01:31:38 server mysqld[888]: key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 351246 K bytes of memory
Apr 12 01:31:38 server mysqld[888]: Hope that's ok; if not, decrease some variables in the equation.
Apr 12 01:31:38 server mysqld[888]:
Apr 12 01:31:38 server mysqld[888]: Thread pointer: 0x0x0
Apr 12 01:31:38 server mysqld[888]: Attempting backtrace. You can use the following information to find out
Apr 12 01:31:38 server mysqld[888]: where mysqld died. If you see no messages after this, something went
Apr 12 01:31:38 server mysqld[888]: terribly wrong...
Apr 12 01:31:38 server mysqld[888]: stack_bottom = 0x0 thread_stack 0x30000
Apr 12 01:31:38 server mysqld[888]: The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
Apr 12 01:31:38 server mysqld[888]: information that should help you find out what is causing the crash.
Apr 12 01:31:38 server mysqld_safe[929]: mysqld from pid file /var/run/mysqld/mysqld.pid ended
Apr 12 08:02:27 server /etc/init.d/mysql[1342]: 0 processes alive and '/usr/bin/mysqladmin --defaults-file=/etc/mysql/debian.cnf ping' resulted in
Apr 12 08:02:27 server /etc/init.d/mysql[1342]: [61B blob data]
Apr 12 08:02:27 server /etc/init.d/mysql[1342]: error: 'Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2 "No such file or directory")'
Apr 12 08:02:27 server /etc/init.d/mysql[1342]: Check that mysqld is running and that the socket: '/var/run/mysqld/mysqld.sock' exists!
Apr 12 08:02:27 server /etc/init.d/mysql[1342]:
Apr 12 08:02:27 server mysql[621]: Starting MariaDB database server: mysqld . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . failed!
Apr 12 08:02:27 server systemd[1]: mysql.service: Control process exited, code=exited, status=1/FAILURE
Apr 12 08:02:27 server systemd[1]: mysql.service: Failed with result 'exit-code'.
Apr 12 08:02:27 server systemd[1]: Failed to start LSB: Start and stop the mysql database server daemon.