<html><head></head><body><div style="font-family: Verdana;font-size: 12.0px;"><div>
<div>Hallo Bernd,</div>
<div>ich habe im FHEM-Forum gelesen das dort auch einige User Probleme mit den SD-Karten hatten.</div>
<div>Bei denen war es so, das die Karten nach einer gewissen Zeit vom Raspi "kaputt-geschrieben" wurden.</div>
<div> </div>
<div>Als Abhilfe wurden die Runtimedaten auf einen USB-Stick ausgelagert, danach hatten sie keine Problem mehr.</div>
<div>In unserem Fall wäre das wohl min. die MySQL Datenbank.</div>
<div> </div>
<div>Ich schau mal ob ich den Link noch finde.</div>
<div> </div>
<div>Gruß Markus</div>
<div>
<div name="quote" style="margin:10px 5px 5px 10px; padding: 10px 0 10px 10px; border-left:2px solid #C3D9E5; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">
<div style="margin:0 0 10px 0;"><b>Gesendet:</b> Sonntag, 13. Oktober 2013 um 11:42 Uhr<br/>
<b>Von:</b> "Bernd Gewehr" <bernd@gewehr.net><br/>
<b>An:</b> "users volkszaehler.org -" <volkszaehler-users@lists.volkszaehler.org><br/>
<b>Betreff:</b> [vz-users] Der Friedhof der SD-Karten ... ;-(</div>
<div name="quoted-content">Hallo,<br/>
<br/>
ich vermute dies ist der nächste Tod einer SD, damit hätte ich dann 4, die noch nie funktioniert haben und 2 tote und ca. einige Stunden Reparaturfummelei in wenigen Monaten.<br/>
<br/>
Gibt es auch eine stabile Kombination, die man nicht ständig reparieren muss oder deute ich das hier alles falsch?<br/>
<br/>
Oct 13 11:32:38 raspberrypi kernel: [225085.614100] EXT4-fs error (device mmcblk0p2): __ext4_ext_check_block:475: inode #3988: comm rs:main Q:Reg: bad header/extent: invalid magic - magic 6f64, entries 24941, max 28265(0), depth 26144(0)<br/>
Oct 13 11:32:39 raspberrypi kernel: [225086.266721] EXT4-fs error (device mmcblk0p2): __ext4_ext_check_block:475: inode #3988: comm rs:main Q:Reg: bad header/extent: invalid magic - magic 6f64, entries 24941, max 28265(0), depth 26144(0)<br/>
Oct 13 11:32:39 raspberrypi kernel: [225086.991721] EXT4-fs error (device mmcblk0p2): __ext4_ext_check_block:475: inode #3988: comm rs:main Q:Reg: bad header/extent: invalid magic - magic 6f64, entries 24941, max 28265(0), depth 26144(0)<br/>
Oct 13 11:32:40 raspberrypi kernel: [225087.363583] EXT4-fs error (device mmcblk0p2): __ext4_ext_check_block:475: inode #3988: comm rs:main Q:Reg: bad header/extent: invalid magic - magic 6f64, entries 24941, max 28265(0), depth 26144(0)<br/>
Oct 13 11:32:40 raspberrypi kernel: [225087.683640] EXT4-fs error (device mmcblk0p2): __ext4_ext_check_block:475: inode #3988: comm rs:main Q:Reg: bad header/extent: invalid magic - magic 6f64, entries 24941, max 28265(0), depth 26144(0)<br/>
Oct 13 11:32:40 raspberrypi kernel: [225088.003475] EXT4-fs error (device mmcblk0p2): __ext4_ext_check_block:475: inode #3988: comm rs:main Q:Reg: bad header/extent: invalid magic - magic 6f64, entries 24941, max 28265(0), depth 26144(0)<br/>
Oct 13 11:32:41 raspberrypi kernel: [225088.303840] EXT4-fs error (device mmcblk0p2): __ext4_ext_check_block:475: inode #3988: comm rs:main Q:Reg: bad header/extent: invalid magic - magic 6f64, entries 24941, max 28265(0), depth 26144(0)<br/>
Oct 13 11:32:41 raspberrypi kernel: [225088.601049] EXT4-fs error (device mmcblk0p2): __ext4_ext_check_block:475: inode #3988: comm rs:main Q:Reg: bad header/extent: invalid magic - magic 6f64, entries 24941, max 28265(0), depth 26144(0)<br/>
Oct 13 11:32:41 raspberrypi kernel: [225088.926375] EXT4-fs error (device mmcblk0p2): __ext4_ext_check_block:475: inode #3988: comm rs:main Q:Reg: bad header/extent: invalid magic - magic 6f64, entries 24941, max 28265(0), depth 26144(0)<br/>
Oct 13 11:32:42 raspberrypi kernel: [225089.249455] EXT4-fs error (device mmcblk0p2): __ext4_ext_check_block:475: inode #3988: comm rs:main Q:Reg: bad header/extent: invalid magic - magic 6f64, entries 24941, max 28265(0), depth 26144(0)<br/>
Oct 13 11:32:42 raspberrypi kernel: [225089.683415] EXT4-fs error (device mmcblk0p2): __ext4_ext_check_block:475: inode #3988: comm rs:main Q:Reg: bad header/extent: invalid magic - magic 6f64, entries 24941, max 28265(0), depth 26144(0)<br/>
Oct 13 11:32:42 raspberrypi kernel: [225090.013780] EXT4-fs error (device mmcblk0p2): __ext4_ext_check_block:475: inode #3988: comm rs:main Q:Reg: bad header/extent: invalid magic - magic 6f64, entries 24941, max 28265(0), depth 26144(0)<br/>
Oct 13 11:32:55 raspberrypi kernel: [225102.750472] EXT4-fs error (device mmcblk0p2): __ext4_ext_check_block:475: inode #3988: comm rs:main Q:Reg: bad header/extent: invalid magic - magic 6f64, entries 24941, max 28265(0), depth 26144(0)<br/>
Oct 13 11:32:55 raspberrypi kernel: [225103.040918] EXT4-fs error (device mmcblk0p2): __ext4_ext_check_block:475: inode #3988: comm rs:main Q:Reg: bad header/extent: invalid magic - magic 6f64, entries 24941, max 28265(0), depth 26144(0)<br/>
Oct 13 11:33:20 raspberrypi mysqld_safe: Number of processes running now: 0<br/>
Oct 13 11:33:20 raspberrypi mysqld_safe: mysqld restarted<br/>
Oct 13 11:33:22 raspberrypi mysqld: 131013 11:33:22 [Warning] The syntax '--log-slow-queries' is deprecated and will be removed in a future release. Please use '--slow-query-log'/'--slow-query-log-file' instead.<br/>
Oct 13 11:33:22 raspberrypi mysqld: 131013 11:33:22 [Note] Plugin 'FEDERATED' is disabled.<br/>
Oct 13 11:33:22 raspberrypi mysqld: 131013 11:33:22 InnoDB: The InnoDB memory heap is disabled<br/>
Oct 13 11:33:22 raspberrypi mysqld: 131013 11:33:22 InnoDB: Mutexes and rw_locks use GCC atomic builtins<br/>
Oct 13 11:33:22 raspberrypi mysqld: 131013 11:33:22 InnoDB: Compressed tables use zlib 1.2.7<br/>
Oct 13 11:33:22 raspberrypi mysqld: 131013 11:33:22 InnoDB: Using Linux native AIO<br/>
Oct 13 11:33:23 raspberrypi mysqld: 131013 11:33:23 InnoDB: Initializing buffer pool, size = 128.0M<br/>
Oct 13 11:33:25 raspberrypi mysqld: 131013 11:33:25 InnoDB: Completed initialization of buffer pool<br/>
Oct 13 11:33:25 raspberrypi mysqld: 131013 11:33:25 InnoDB: highest supported file format is Barracuda.<br/>
Oct 13 11:33:25 raspberrypi mysqld: InnoDB: Log scan progressed past the checkpoint lsn 15272018191<br/>
Oct 13 11:33:25 raspberrypi mysqld: 131013 11:33:25 InnoDB: Database was not shut down normally!<br/>
Oct 13 11:33:25 raspberrypi mysqld: InnoDB: Starting crash recovery.<br/>
Oct 13 11:33:25 raspberrypi mysqld: InnoDB: Reading tablespace information from the .ibd files...<br/>
Oct 13 11:33:25 raspberrypi mysqld: InnoDB: Restoring possible half-written data pages from the doublewrite<br/>
Oct 13 11:33:25 raspberrypi mysqld: InnoDB: buffer...<br/>
Oct 13 11:33:26 raspberrypi mysqld: InnoDB: Doing recovery: scanned up to log sequence number 15272018201<br/>
Oct 13 11:33:30 raspberrypi mysqld: 131013 11:33:30 InnoDB: Waiting for the background threads to start<br/>
Oct 13 11:33:31 raspberrypi mysqld: 131013 11:33:31 InnoDB: 5.5.31 started; log sequence number 15272018201<br/>
Oct 13 11:33:31 raspberrypi mysqld: 131013 11:33:31 [Note] Server hostname (bind-address): '127.0.0.1'; port: 3306<br/>
Oct 13 11:33:31 raspberrypi mysqld: 131013 11:33:31 [Note] - '127.0.0.1' resolves to '127.0.0.1';<br/>
Oct 13 11:33:31 raspberrypi mysqld: 131013 11:33:31 [Note] Server socket created on IP: '127.0.0.1'.<br/>
Oct 13 11:33:32 raspberrypi mysqld: 131013 11:33:32 [Note] Event Scheduler: Loaded 1 event<br/>
Oct 13 11:33:32 raspberrypi mysqld: 131013 11:33:32 [Note] /usr/sbin/mysqld: ready for connections.<br/>
Oct 13 11:33:32 raspberrypi mysqld: Version: '5.5.31-0+wheezy1-log' socket: '/var/run/mysqld/mysqld.sock' port: 3306 (Debian)<br/>
Oct 13 11:33:32 raspberrypi mysqld: 131013 11:33:32 [Note] Event Scheduler: scheduler thread started with id 1<br/>
Oct 13 11:33:32 raspberrypi mysqld: 131013 11:33:32 InnoDB: Assertion failure in thread 2785219680 in file fsp0fsp.c line 2102<br/>
Oct 13 11:33:32 raspberrypi mysqld: InnoDB: Failing assertion: inode<br/>
Oct 13 11:33:32 raspberrypi mysqld: InnoDB: We intentionally generate a memory trap.<br/>
Oct 13 11:33:32 raspberrypi mysqld: InnoDB: Submit a detailed bug report to <a href="http://bugs.mysql.com" target="_blank">http://bugs.mysql.com</a>.<br/>
Oct 13 11:33:32 raspberrypi mysqld: InnoDB: If you get repeated assertion failures or crashes, even<br/>
Oct 13 11:33:32 raspberrypi mysqld: InnoDB: immediately after the mysqld startup, there may be<br/>
Oct 13 11:33:32 raspberrypi mysqld: InnoDB: corruption in the InnoDB tablespace. Please refer to<br/>
Oct 13 11:33:32 raspberrypi mysqld: InnoDB: <a href="http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html" target="_blank">http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html</a><br/>
Oct 13 11:33:32 raspberrypi mysqld: InnoDB: about forcing recovery.<br/>
Oct 13 11:33:32 raspberrypi mysqld: 09:33:32 UTC - mysqld got signal 6 ;<br/>
Oct 13 11:33:32 raspberrypi mysqld: This could be because you hit a bug. It is also possible that this binary<br/>
Oct 13 11:33:32 raspberrypi mysqld: or one of the libraries it was linked against is corrupt, improperly built,<br/>
Oct 13 11:33:32 raspberrypi mysqld: or misconfigured. This error can also be caused by malfunctioning hardware.<br/>
Oct 13 11:33:32 raspberrypi mysqld: We will try our best to scrape up some info that will hopefully help<br/>
Oct 13 11:33:32 raspberrypi mysqld: diagnose the problem, but since we have already crashed,<br/>
Oct 13 11:33:32 raspberrypi mysqld: something is definitely wrong and this may fail.<br/>
Oct 13 11:33:32 raspberrypi mysqld:<br/>
Oct 13 11:33:32 raspberrypi mysqld: key_buffer_size=16777216<br/>
Oct 13 11:33:32 raspberrypi mysqld: read_buffer_size=131072<br/>
Oct 13 11:33:32 raspberrypi mysqld: max_used_connections=0<br/>
Oct 13 11:33:32 raspberrypi mysqld: max_threads=151<br/>
Oct 13 11:33:32 raspberrypi mysqld: thread_count=1<br/>
Oct 13 11:33:32 raspberrypi mysqld: connection_count=0<br/>
Oct 13 11:33:32 raspberrypi mysqld: It is possible that mysqld could use up to<br/>
Oct 13 11:33:32 raspberrypi mysqld: key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 346080 K bytes of memory<br/>
Oct 13 11:33:32 raspberrypi mysqld: Hope that's ok; if not, decrease some variables in the equation.<br/>
Oct 13 11:33:32 raspberrypi mysqld:<br/>
Oct 13 11:33:32 raspberrypi mysqld: Thread pointer: 0x0<br/>
Oct 13 11:33:32 raspberrypi mysqld: Attempting backtrace. You can use the following information to find out<br/>
Oct 13 11:33:32 raspberrypi mysqld: where mysqld died. If you see no messages after this, something went<br/>
Oct 13 11:33:32 raspberrypi mysqld: terribly wrong...<br/>
Oct 13 11:33:32 raspberrypi mysqld: stack_bottom = 0 thread_stack 0x30000<br/>
Oct 13 11:33:32 raspberrypi mysqld: The manual page at <a href="http://dev.mysql.com/doc/mysql/en/crashing.html" target="_blank">http://dev.mysql.com/doc/mysql/en/crashing.html</a> contains<br/>
Oct 13 11:33:32 raspberrypi mysqld: information that should help you find out what is causing the crash.<br/>
<br/>
Gruß<br/>
<br/>
Bernd</div>
</div>
</div>
</div></div></body></html>