meteohub.de

I've just completed the upgrade to v2.1 - Phew!

After the Restore I noticed that on the Settings page the time zone hadn't been reset, nor had the Workgroup. No big deal, but I just thought I'd mention it.

One other thing upgrade related thing - I had a bit of a panic when I checked the 'log' file on the 'small' USB stick after building the Meteohub USB stick. The log didn't mention bytes copied (as I think it did when I first installed), but it did include the message \"No space left on device\"! However when I booted up v2.1 was there, so panic over. :) :)

Hi,
the \"no space left on devices\" indicates that the USB stick image is too large for your target usb stick. As a result the upper end of the data filesystem might be corrupt. May be things are working fine in the beginning, but later you may find Meteohub struggling with a corrupt file system.

What Image did you use, 2GB or 4GB? (It is coded in the name of the rar-file)

What USB stick are you using?

The log file should look like this:

admin wrote:What Image did you use, 2GB or 4GB? (It is coded in the name of the rar-file)

meteohub-v2.1-4GB.rar

What USB stick are you using?

FREECOM 4GB

Exactly the same stick as was holding the earlier 4GB version, originally installed a few days ago. I didn't do anything to that stick before trying to install the newer image. Should I have?

The log file should look like this:

That is just as I recall from the original install - though I think the figures were more like 76... than 38...

Here is the Storage section from the System Info page

Here is my log file for the 2.1 update:

stickit started.
Sun Mar 9 21:50:34 UTC 2008
accepted file:/media/sda1/meteohub-v2.1-2GB.rar
waiting for target stick ... found.
unrar and copy /media/sda1/meteohub-v2.1-2GB.rar to /dev/sdb/ ...
3870707+23 records in
3870707+23 records out
done.
shutdown

Not excactly the same numbers as in Boris´ post, but still in the 38'-Region.

Update went fine but took some time (copying from one usb stick to the other took about 1 h alone)

Arnd.

David,
do you have ssh access to your meteohub?

If so,
you can flood your data partition and see if this causes file-system trouble.

\"cp /dev/zero /data/zero\" floods the partition.
after a while a \"no space on device left error should occure. delete it with \"rm /data/zero\".
when no file system errors are reported you can assume your stick is working ok.

maybe the freecom has a bit less storage than expected. partitions in the image are a bit smaller than the image itself, so if the very last bytes from the image did not fit onto your stick, this might not be a problem.

admin wrote:David,
do you have ssh access to your meteohub?

If so,
you can flood your data partition and see if this causes file-system trouble.

Yes, I have PuTTY.
Using that I did as you described and just got the "no space" error, so hopefully it was a false alarm.

maybe the freecom has a bit less storage than expected. partitions in the image are a bit smaller than the image itself, so if the very last bytes from the image did not fit onto your stick, this might not be a problem.

That seems to be the case.
Odd though that exactly the same stick had a 'normal' log the first time it was written to?