MB PRO: database disk image is malformed *solved*

[tofe]

Hello
I have found today that in export log parameters completely missing (00:00 to 23:59). In the history I get the parameters thb0seapress at the chosen hour following error message "Sytemnachricht: Database Error: Can not read thb0seapress_min (0 tries, 1ms): database disk image is malformed". Other hours are available, even in the visible day graphics a value for the hour 0 is present. What happened here? More importantly, how can such be avoided?

Current version: Meteobridge 2.8 (Mar 26 2016, build 9654), FW 1.4
Problem was even with previously installed version "released March 11, 2016" available.

[DAP]

I am getting the same errors. I tried repairing the database, but that also failed:
dbrepair (31.03.2016 22:17:00): database size is 138.7M
dbrepair (31.03.2016 22:17:00): test integrity of database
dbrepair (01.04.2016 05:17:15): database has integrity errors, rebuild started
dbrepair (01.04.2016 05:46:08): database export done, build new database
dbrepair (01.04.2016 06:24:33): new database too small (138.7M) to replace old one
database (31.03.2016 23:24:36): process started.

I also don't see any way to delete the database.

Platform: Meteobridge PRO
RAM: 61500 kB total, 17744 kB free (71% used)
Storage: Internal 6809 MB total, 6574 MB free (3% used)
SW Version: Meteobridge 2.8 (Mar 29 2016, build 9684), FW 1.4
Uptime: 1 hours, 43 minutes Buffer Usage: 0 items (0%)
Power Data: 5.47V 369mA 2.02W (Box Climate: 42.4°C 13%)

[DAP]

There was a software updated posted, so I tried rebooting my meteobridge pro with the database rebuild option checked.
This time the rebuild worked:
oled (02.04.2016 03:30:35): process started.
database (01.04.2016 20:32:15): process started.
wnetd (01.04.2016 20:32:15): process started.
logger (01.04.2016 20:32:15): database connected.
logger (01.04.2016 20:32:15): Historical data loaded (46 records).
logger (01.04.2016 20:32:15): data logger (version 5.0p, build 9721) started.
logger (01.04.2016 20:32:17): connect station 0 (Meteostick Vantage via USB serial).
logger (01.04.2016 20:32:17): connect station 9 (System Data via Plug-in).
logger (01.04.2016 20:32:19): transmitter 1 registered as ISS
logger (01.04.2016 20:32:19): Meteostick Version 2.4
logger (01.04.2016 20:32:19): debug off
logger (01.04.2016 20:32:19): verbose off
logger (01.04.2016 20:32:19): output raw (8 bytes)
logger (01.04.2016 20:32:19): output raw (10 bytes)
logger (01.04.2016 20:32:19): filter on
logger (01.04.2016 20:32:19): rx threshold set to -70db
logger (01.04.2016 20:32:19): listening to transmitter 1
logger (01.04.2016 20:32:19): bandwidth narrow
logger (01.04.2016 20:32:19): chip authentication ok: 14
logger (01.04.2016 20:32:19): frequency band 915MHz (US)


Platform: Meteobridge PRO
RAM: 61500 kB total, 25372 kB free (58% used)
Storage: Internal 6809 MB total, 6572 MB free (3% used)
SW Version: Meteobridge 2.8 (Apr 2 2016, build 9721), FW 1.4
Uptime: 0 hours, 38 minutes Buffer Usage: 0 items (0%)
Power Data: 5.48V 357mA 1.96W (Box Climate: 45.9°C 13%)

The log is no longer being flooded with database errors.

[admin]

@tofe: you have a PM. I would like to inspect your system in more detail.