Only problems with my MBPro. **solved**

[MeteoLeudal]

Hello,

For several months I have only problems with my MBPro with V2.9 and also with V3.0
- When I reboot Wifi AP then it come no further than the landing page. On network tab can't see my SSID anymore.
- Display after a few minutes going on black and stays there after reboot the same story.
- No data is stored on the Internal USB storage. The history date table remains empty.
- On history tab gives an System Message Error: Can't open database: disk I/O error
- After every reboot history data is empty.
Even an factory reset does’t make any improvement. Hope that the admin has a solution otherwise the MBPro will go back for warranty to the supplier.

System messages gives:
oled (10.07.2016 10:25:38): process started.
database (10.07.2016 12:27:00): process started.
wnetd (10.07.2016 12:27:00): process started.
database (10.07.2016 12:27:00): Can't open database: disk I/O error
database (10.07.2016 12:27:00): process stopped.
logger (10.07.2016 12:27:00): can't open database: disk I/O error
database (10.07.2016 12:27:00): cannot prepare init database: out of memory
logger (10.07.2016 12:27:00): Historical data loaded (0 records).
logger (10.07.2016 12:27:00): data logger (version 5.0q, build 10055) started.
logger (10.07.2016 12:27:02): connect station 0 (Vantage via USB serial).
logger (10.07.2016 12:27:02): connect station 9 (System Data via Plug-in).
logger (10.07.2016 12:27:02): wakeup sent.
logger (10.07.2016 12:27:02): internal logger activated.
logger (10.07.2016 12:27:02): syncing.
test5m (10.07.2016 12:27:03): database daemon stalled, will be restarted now.
database (10.07.2016 12:27:03): process started.
database (10.07.2016 12:27:03): Can't open database: disk I/O error
database (10.07.2016 12:27:03): process stopped.
logger (10.07.2016 12:27:12): gettime request sent.
logger (10.07.2016 12:27:12): no Vantage time offset.
logger (10.07.2016 12:27:12): eeprom request sent.
logger (10.07.2016 12:27:12): rain collector size 0.2 mm per tick.
logger (10.07.2016 12:27:12): transmitter 1 active as station type (#0) "ISS".
logger (10.07.2016 12:27:12): transmitter 2 active as station type (#4) "Wind".
logger (10.07.2016 12:27:12): firmware version request sent.
logger (10.07.2016 12:27:12): firmware version 1.90
logger (10.07.2016 12:27:12): no reading of Vantage's internal logger.
test5m (10.07.2016 12:30:17): database daemon stalled, will be restarted now.
database (10.07.2016 12:30:17): process started.
database (10.07.2016 12:30:17): Can't open database: disk I/O error
database (10.07.2016 12:30:17): process stopped.
test5m (10.07.2016 12:35:31): database daemon stalled, will be restarted now.
database (10.07.2016 12:35:31): process started.
database (10.07.2016 12:35:31): Can't open database: disk I/O error
database (10.07.2016 12:35:31): process stopped.
test5m (10.07.2016 12:41:35): database daemon stalled, will be restarted now.
database (10.07.2016 12:41:35): process started.
database (10.07.2016 12:41:35): Can't open database: disk I/O error
database (10.07.2016 12:41:35): process stopped.
test5m (10.07.2016 12:46:13): database daemon stalled, will be restarted now.
database (10.07.2016 12:46:13): process started.
database (10.07.2016 12:46:13): Can't open database: disk I/O error
database (10.07.2016 12:46:13): process stopped.
test5m (10.07.2016 12:50:47): database daemon stalled, will be restarted now.
database (10.07.2016 12:50:47): process started.
database (10.07.2016 12:50:47): Can't open database: disk I/O error
database (10.07.2016 12:50:47): process stopped.
test5m (10.07.2016 12:56:23): database daemon stalled, will be restarted now.
database (10.07.2016 12:56:23): process started.
database (10.07.2016 12:56:23): Can't open database: disk I/O error
database (10.07.2016 12:56:23): process stopped.
logger (10.07.2016 12:57:18): write persist data to "/tmp/mnt/persist/thb0temp" failed: No such file or directory
test5m (10.07.2016 13:00:28): database daemon stalled, will be restarted now.
database (10.07.2016 13:00:28): process started.
database (10.07.2016 13:00:28): Can't open database: disk I/O error
database (10.07.2016 13:00:28): process stopped.
test5m (10.07.2016 13:05:37): database daemon stalled, will be restarted now.
database (10.07.2016 13:05:37): process started.
database (10.07.2016 13:05:37): Can't open database: disk I/O error
database (10.07.2016 13:05:37): process stopped.
test5m (10.07.2016 13:10:24): database daemon stalled, will be restarted now.
database (10.07.2016 13:10:24): process started.
database (10.07.2016 13:10:24): Can't open database: disk I/O error
database (10.07.2016 13:10:24): process stopped.
test5m (10.07.2016 13:15:22): database daemon stalled, will be restarted now.
database (10.07.2016 13:15:22): process started.
database (10.07.2016 13:15:22): Can't open database: disk I/O error
database (10.07.2016 13:15:22): process stopped.
test5m (10.07.2016 13:20:24): database daemon stalled, will be restarted now.
database (10.07.2016 13:20:24): process started.
database (10.07.2016 13:20:24): Can't open database: disk I/O error
database (10.07.2016 13:20:24): process stopped.

Thanks Peter.

[Bruce]

I can't say when it started but my system has started showing the following errors, that I would think are not normal behavior. Attached image shows system details (versions, etc.)

wnetd (09.07.2016 02:09:21): process started.
logger (09.07.2016 02:09:21): Historical data loaded (23 records).
logger (09.07.2016 02:09:21): data logger (version 5.0q, build 10055) started.
logger (09.07.2016 02:09:22): connect station 0 (WH-1080/3080 via USB HID).
logger (09.07.2016 09:22:24): Bad wind0(0) sensor data, "gust speed x10" (3967) out of range [0:900]
logger (09.07.2016 11:32:48): Bad thb0(0) sensor data, "pressure x10" (46) out of range [4000:12000]
logger (09.07.2016 11:32:48): Bad wind0(0) sensor data, "average speed x10" (2656) out of range [0:800]
logger (09.07.2016 17:42:23): Bad th0(0) sensor data, "temperature x10" (21760) out of range [-500:2000]
logger (09.07.2016 17:42:23): Bad thb0(0) sensor data, "temperature x10" (10270) out of range [-500:2000]
logger (09.07.2016 18:15:59): Bad thb0(0) sensor data, "pressure x10" (46) out of range [4000:12000]
logger (09.07.2016 18:15:59): Bad wind0(0) sensor data, "average speed x10" (2656) out of range [0:800]
logger (09.07.2016 22:07:11): Bad thb0(0) sensor data, "pressure x10" (46) out of range [4000:12000]
logger (09.07.2016 22:07:11): Bad wind0(0) sensor data, "average speed x10" (2656) out of range [0:800]
logger (10.07.2016 08:07:59): Bad thb0(0) sensor data, "pressure x10" (46) out of range [4000:12000]
logger (10.07.2016 08:07:59): Bad wind0(0) sensor data, "average speed x10" (2656) out of range [0:800]
logger (10.07.2016 09:15:10): Bad thb0(0) sensor data, "pressure x10" (46) out of range [4000:12000]
logger (10.07.2016 09:15:10): Bad wind0(0) sensor data, "average speed x10" (2656) out of range [0:800]
logger (10.07.2016 15:16:46): Bad thb0(0) sensor data, "pressure x10" (46) out of range [4000:12000]
logger (10.07.2016 15:16:46): Bad wind0(0) sensor data, "average speed x10" (2656) out of range [0:800]
logger (10.07.2016 17:35:10): Bad thb0(0) sensor data, "pressure x10" (46) out of range [4000:12000]
logger (10.07.2016 17:35:10): Bad wind0(0) sensor data, "average speed x10" (2656) out of range [0:800]
logger (10.07.2016 21:59:58): Bad thb0(0) sensor data, "pressure x10" (46) out of range [4000:12000]
logger (10.07.2016 21:59:58): Bad wind0(0) sensor data, "average speed x10" (2656) out of range [0:800]
logger (11.07.2016 06:19:57): Bad thb0(0) sensor data, "pressure x10" (46) out of range [4000:12000]
logger (11.07.2016 06:19:57): Bad wind0(0) sensor data, "average speed x10" (2656) out of range [0:800]
logger (11.07.2016 08:00:45): Bad thb0(0) sensor data, "pressure x10" (46) out of range [4000:12000]
logger (11.07.2016 08:00:45): Bad wind0(0) sensor data, "average speed x10" (2656) out of range [0:800]
logger (11.07.2016 09:37:33): Bad thb0(0) sensor data, "pressure x10" (46) out of range [4000:12000]
logger (11.07.2016 09:37:33): Bad wind0(0) sensor data, "average speed x10" (2656) out of range [0:800]
logger (11.07.2016 15:09:33): Bad thb0(0) sensor data, "pressure x10" (46) out of range [4000:12000]
logger (11.07.2016 15:09:33): Bad wind0(0) sensor data, "average speed x10" (2656) out of range [0:800]


Can someone confirm if these are something I should be concerned about? WU seems to still be updating normally even though the system page on the unit shows the errors.

[admin]

As discussed in the other thread your internal USB storage has probably failed.
Please do the check recommended in the other thread to make sure.

Apart from this, a new release of 3.0 came out today that also improves situation,
but cannot heal hardware defects (while it will reduce load and thereby failure
rate of USB storage dramatically for the future), sorry.

[Bruce]

Okay, I understand the issue with the limitations of flash write cycle life as I encountered this on a embedded modem project myself a few years ago.

One question I have is which thread is the check you are referring to?

Also, for the TP-LINK TL-MR3020 that I am using, is what you are telling me is that it's internal hardware may have failed, and needs to be replaced?

Incidentally, just wanted to say that this configuration has been very stable, and self maintaining since I switched to the TP-LINK TL-MR3020.

Until recently, the only intermittent issue I have had is with the Ambient Weather Station WS-2080 locking up it's USB link to the TP-LINK TL-MR3020.

[admin]

No, TL-MR3020 doe snot have internal USB storage, therefore no problems there.
That the weather station reports bad data being blocked by Meteobridge here and there
might indicate that USB connection is troublesome or the console itself might not work too
good. Is it properly powered?

[Bruce]

After further investigation, the WS-2080 Console is failing, as you suggest. I had to get a replacement console.

BTW just realized this is on the wrong thread... I apologize for that...

System back up and running now.