meteohub.de

This is shown now.

2. what do you need a cable for ?

Well, I didn't know that you could replace yourself the inside memory. I didn't see that video before....

I bought this:

https://www.allekabels.nl/searchresult. ... rd=1258217

to backup on the backside.

and this:

https://www.allekabels.nl/searchresult. ... rd=1286156

to connect to the frontside and backside. Next step is moving the database to the frontside. The cable coming from the back seems to be a bit tricky and less reliable to me.

TonvG wrote: ↑Sun Jun 11, 2023 9:50 am However, it seems something has changed. Last 2 days the Meteobridge restarted at 0:00 h. Further the 33 MB that is still left is now suddenly sufficient for 23.3 years?
Now it is SW version of June 9th. Something to do with that?

if you get such a "moon number", something is wrong with the internal calcuation, which might be due to a bug unintentionally introduced when correcting or implementing something else.
How would 33 MB hold for 23.3 years, even 2.33 appear unlikely. maybe it's just days and by some newly introduced bug it shows years instead of days.

I hope it is ging to work. My idea is to plug one in on the front and one one the back (I didn't realise first there was a micro USB connector there..). One for the database and one for regular backups.

now I see what you seem to need the cable for - but a USB 2.0 cable with a miniUSB male end should have come with the MB Pro ...

It's a good idea to connect a USB stick (or even USB external HDD/SSD) to one of USB ports and use them for regular backups.
It's however NOT so good an idea to use a USB stick to run the database from - even though technically it works - it would over time ruin the USB stick unless it's also a SLC model. An external (and externally powered) SSD would however be safe. When you want to do the latter, you don't need to upgrade your internal USB stick though

It's however NOT so good an idea to use a USB stick to run the database from - even though technically it works - it would over time ruin the USB stick unless it's also a SLC model.

On the front (and back) comes the industrial micro SD card.

TonvG wrote: ↑Sun Jun 11, 2023 11:10 am Well, I didn't know that you could replace yourself the inside memory. I didn't see that video before....

well, earlier in the thread (before you jumped in) it was imho clear that the internal USB stick was to be replaced ....

I bought this:
....
https://www.allekabels.nl/searchresult. ... rd=1286156
to connect to the frontside and backside. Next step is moving the database to the frontside.

could work, you have to try ... - looks a bit thick to be put inside ...
from the outside it should definitely work
regarding the location of the database, see my comment in my earlier post (in my opinion it should remain on the internal storage - upgraded by the USB adapter/microSD combination - it's the more reliable setup - the storage cannot be easily removed by some unwanted outside activities)

The cable coming from the back seems to be a bit tricky and less reliable to me.

unless you fix that cable coming from behind properly (e.g. with some tape), I won't trust the connection to remain stable in case of some uninteded move

TonvG wrote: ↑Sun Jun 11, 2023 11:22 am

It's however NOT so good an idea to use a USB stick to run the database from - even though technically it works - it would over time ruin the USB stick unless it's also a SLC model.

On the front (and back) comes the industrial micro SD card.

technically feasible - but not a very solid construction - replacing the internal USB stick is imho the professional, safe and reliable approach.
But of course you do as you wish. regarding the storage consumption, mine continues showing reasonable numbers (see picture), but I cannot tell what happens when you go down to a few MB only. You can also see the internal storage provided by the microSB/USB adapter. "ChipBnk" is the adapter name read by MB - it only sees the storage provided behind (size), not the microSD card product number, manufacturer etc. (which is a WD/SanDisk 8 GB XI (SLC))

Operation done and successful

Some remarks. I was always doing backups on the front USB. Now I had to move to the back.

So first I removed the USB stick from the front. Next I did a backup on the backside. I checked it and yes, ok.

Next I added the new microSD on the front and I moved the database to the front. Done and successful.

Next I wanted to move the old database to the front. it didn't see the backup anymore.

So I rebooted once more. Luckily it now recognized the backup just made and I could restore it.

I think it would be more easy, like with the database, that you could specify where to make the backup. Maybe something to include in future software?

Further I had to move some charts and the export scripts I made myself back to the Meteobridge. I had saved those too.

I agree that maybe changing the internal memory would be more professional solution. However I'm always a bit reluctant to open hardware, changing parts, pushing too hard and next you find out something broke. And besides that, maybe the system would not accept the my type of micro SD there, as it wasn't the exact described micro SD card.

But maybe to do somewhere in the coming time.

Best,

Ton

TonvG wrote: ↑Tue Jun 13, 2023 8:45 pm I think it would be more easy, like with the database, that you could specify where to make the backup. Maybe something to include in future software?

if you know Linux scripting, you can do this yourself by changing the backup script.
the MB philosophy is to have the database on the internal USB device - so no need for change

However, it's probably no longer necessary as MB now knows that one external device is the one with your database and if another external device is found, then it's considered the backup device.
Your "issue" was only intermediate - after the reboot now all should work (including backup via the 2nd USB port)...

And besides that, maybe the system would not accept the my type of micro SD there, as it wasn't the exact described micro SD card.

Afaik this check is only made with MB on RPi.

Good luck with your (storage) upgraded MB Pro.

A few more questions. Maybe not or only partly related to the 1GB USB storage topic, else it is maybe a new topic. For the moment I include it here.

Since June 9th my MB-Pro reboots every night at 0:00h. Is this standard now? I don't have anything scheduled in that way. In fact I don't like that so much as it takes several minutes and in those minutes no data is received. I would rather prefer to choose myself when to reboot. See next.

Last night the MB didn't come properly out of that reboot. The database on the front USB wasn't connected. So no data stored until I saw it this morning. However upload to weather services worked. After reboot again everything was fine, except that the database had another gap of some hours.

Boot option at the moment is set as 'no check/rebuild on reboot' . Is it maybe better to give in another option? If so which one? Can someone clarify a bit more what the difference is between those options?

Thanks.

No a reboot at midnight is not standard. Do you have a database backup scheduled at midnight? What else do you have scheduled in Events?

TonvG wrote: ↑Thu Jun 15, 2023 5:36 pm A few more questions. Maybe not or only partly related to the 1GB USB storage topic, else it is maybe a new topic. For the moment I include it here.

Since June 9th my MB-Pro reboots every night at 0:00h. Is this standard now? I don't have anything scheduled in that way. In fact I don't like that so much as it takes several minutes and in those minutes no data is received. I would rather prefer to choose myself when to reboot. See next.

not that I'm aware of - a reboot should normally only happen when you schedule it (=when you manually initiate it) - however, in case of a system overload, a reboot can happen incidentally in my experience

Last night the MB didn't come properly out of that reboot. The database on the front USB wasn't connected. So no data stored until I saw it this morning.

if the internal USB storage had been replaced, this wouldn't/couldn't have happened - didn't I mention something about safer approach for storage upgrade etc. earlier ? - you can still do this, by the way

However upload to weather services worked. After reboot again everything was fine, except that the database had another gap of some hours.

upload to Weather Networks occurs with current data - no database needed for that - the database is for storing data accumulated during the so-called loop period

Boot option at the moment is set as 'no check/rebuild on reboot' . Is it maybe better to give in another option? If so which one? Can someone clarify a bit more what the difference is between those options?

this boot option in the database section only says what to do in case of a reboot - it's not to initiate a reboot.
Reboot you do usually manually in the System --> Administration section

Unsure the details of this June 9 release but doubt it would trigger a midnight reboot by itself but now have it running, will observe what it does.

Apart from the manual reboot option a user triggered reboot script can be setup under Events @ a specified time?

Also sounds like you have the Version Control: set to "get newest on boot"?

It happened again last night, like all nights:
These are my events:
Only thing done every midnight is making two export files of the day and month.

And yes, I have selected 'get newest on boot' .

I suggest you create yourself a customized chart showing the CPU load and device temperature - and check what it shows over the past two days and week. If these values are rather high an unscheduled reboot becomes likely due to a system overload. Unfortunately the syslog of the MB gets deleted at a reboot and starts newly from scratch again, so such a script is the only way to find out ...

you can try to match such a chart with the gaps in your sensor readings

I had this myself (too many stations/sensors) and my final solution was getting a RaspberryPi install and move the multiple stations with all their sensors there. No issues ever since. With permanent one minute values. Whenever the system was overloaded a reboot occurred. Boris (the MB developer) checked that with such a script and a hardware upgrade was my only way out.

There is such a graph default in MB I saw. The laste 2 weeks:


Some things from the graph.

It is warm in The Netherlands the last weeks, as well as in Germany. Resulting in even higher system temperatures.

Daily restarts since June 9th

CPU load was really high when the system ran out of memory. Much lower at the moment 1 GB was replaced by 16 GB.

RAM usage has gone up a bit it seems.

Conclusions? I can't compare to other systems, but high CPU load doesn't look good to me. Should be better now I think.

Jun 9 2023 build 14990 has been up now for 24 hours, ran over night, no reboot occurred.