Problems

[dcspicer]

Last night my meteohub stops reporting and now I can NOT connect to it. I've reboot the meteohub and still can not connect to it. I running on a NLSU2 and I have the power and network lights on. From what I can tell everything looks correct. How can I get this fixed?:(

[dcspicer]

Here is some more Information. When I press the power button I here a low beep, few seconds later I hear high,high, low and then after boot(power and network lights are on steady) I hear 3 low beeps. I take that as it is getting ready to read out the IP, but that is as far as I get. I'm starting to wondering if my usb stick died on me last night. If so is there any way to retrieve the stored info on it?

[d_l]

If so is there any way to retrieve the stored info on it

Funny you should ask as I've just completed rebuilding my data on a new USB stick. If you are a WinXP user and you have been diligently making Application Data backups and your backups weren't corrupted by the drive problem, then you should be able to access and copy to a folder on your computer the "meteohub.backup" file in the large partition (probably named Linux native Volume 2) of the flash drive with this program: http://www.diskinternals.com/linux-reader/. Once you get that copied off the bad drive, you would then copy it from your computer in to the NSLU2's Samba share\\public folder on your NSLU2. Then you can do an Application Data restore. If you have a lot of data, the recompute for this will take a considerable time.

If you haven't done any Application Data backups, then it may be possible to extract the individual monthly folders with their raw data files from the Linux native Volume 2's weather folder to your computer and then copy them to NSLU2's Samba share\\public\\weather folder. Then you would need to do a recompute of your Aggregated Weather Data. Boris will have to advise if this procedure will work correctly as I haven't tried it.

I'm curious as to what brand of USB stick you were using and how long it has been in use?

When I had problems with the bad USB stick in my NSLU2, the GUI was often inaccessible after a while (maybe after an automatic reboot), but was otherwise recording and uploading data properly. I couldn't power it down with the button, but I could pull the power cord, plug it in, power up with the button, and have the GUI access restored. Before I decided to replace the bad USB stick, I re-gained access to the GUI for one last time and made an Application Data Backup and a Settings Backup. During this whole bad USB drive period, the Samba share was totally inaccessible.

[dcspicer]

The stick that I had is an Imation 2gb. I've only been using it for a little while now.

Well I went and baught some new stick. PNY 2gb. I reloaded the software using the usb stick image and still didn't fix the problem. I tried to reload the firmware and still nothing. When it boots up it does not beep out the IP but using the IPscan tool it still shows that IP that it was assigned. I try to connect to that IP and nothing. Makes me wondering if my NSLU2 is screwed up?

[cbhiii]

Over time the NSLU2 units have not been very bullet proof. I ran one for almost a year and had to rebuilt a few times over that period. I used different USB drives, but all seem to corrupt at one time or another. I have been frustrated too many times by this sudden failure that leaves everything broken.

The only recommendation I can give is moving to a new hardware platform such as an eBox-3300 like I did or a similar one.

Though I've only been running mine a short while, others here believe that are more stable for the long run.

The compact flash or other storage medium also should help with reliability.

Best of luck.

[d_l]

When it boots up it does not beep out the IP but using the IPscan tool it still shows that IP that it was assigned.

I guess you have tried accessing it on the altenate IP, 192.168.1.77 and the alternate port, 7777? Those didn't work for me either.

When you re-made the stick image from the RAR file did you use the NSLU2 or Windows method? Your access problems sounded a lot like those I was having, but once I re-made a 4 GB stick with the NSLU2 method, I had access.

[dcspicer]

I have only been able to get the windows method to work. I have tried the NSLU method but have not been successful. Here is how I've been doing it. No devices connect except my 256meg usb stick with the meteohub-v4.1-2gb.rar file on it. I power it on and the yellow light goes out, but the disk2 light never blinks. What am I doing wrong? I would like to try this method to hopefully restore my device.

[sevenless]

Quick guess, but perhaps a key problem here is that you're using the 2GB disk image on a 256mb stick?

I'm a bit confused about how exactly you're installing the software based on what you described above -- are you using dd to install the disk image onto the physical disk partition of the USB stick, as explained in the disk image how-to?

[dcspicer]

I have used the program called disk image to load the 2gb application onto my 2gb stick. This method works, but can not get access to my device. I'm thinking that if I can the NSLU2 load the application program for me that maybe it would allow me to log in, but every time I follow the instruction for copy the meteohub runtime envirtonment on to my usb stick it does not copy.

[admin]

Do you have access to a windows PC (not vista)? Then DiskImage is the bullet proof way to setup a stick.

[dcspicer]

Yes I do. I have Xp on my laptop and built the stick. Still can not get access to my device. Again upon boot, it does not beep out the IP address, but with IPscan I can see the IP address. I try to access it through that IP and I get page can not be displayed. I can not ping it either.

[d_l]

Here is how I've been doing it. No devices connect except my 256meg usb stick with the meteohub-v4.1-2gb.rar file on it. I power it on and the yellow light goes out, but the disk2 light never blinks.

How long have you neen waitng for the disk2 LED to blink? I never timed it, but it seems like it takes at least 20-30 seconds.

BTW, is your NSLU2 a 133 or 266 MHz version?

That time I quoted above is for a 266 MHz NSLU2. A 133 MHz might take longer to start blinking.