Meteo Sheeva suddenly not working

[cheffy]

Hi,

I purchased a Meteo Sheeva approximately 6 months ago and I have been running it 24/7 eversince with no major issues.  I have it connected to my home network with a static IP address.

A couple of days I unplugged it and when I went to start up again (after about 10 mins) I could not get it to connect to my home network.

The power supply still seems to be running, I have both an orange and a blue light showing when the power is connected.  When it's connected to my router the lights flash which I assume means it transferring (or trying to transfer) data.  However, I cannot seem to pick it up on the assigned IP address or any other IP address.  When I look at my router settings it just says that it is inactive.

I have checked the following things,

I have tried a number of different cables connecting to my router, but still nothing.
I have had a quick look inside, but there were no obvious signs of damage that I could notice.

It's all very strange, I am starting to wonder if the SD card has been somehow corrupted.

I did notice today the blue light did occasionally flick to a yellow light for approx 5 seconds.

Does anybody know whats going on, or how I can fix this issue??

Thanks.

[NewIT_Jason]

This does sound like the PSU, please email info@newit.co.uk

[cheffy]

Hi - I ordered a new PSU and I replaced it on the weekend, however still no change - I still cannot get it to connect to my home network.

Any ideas what might be causing this?

As mentioned previously, it had been working fine for the last 6 months and all of a sudden I loose my connection.

[NewIT_Marcus]

You should be able to establish a serial connection to the Sheevaplug with the USB cable that was supplied.

See http://www.plugcomputer.org/plugwiki/index.php/Serial_terminal_program

Once you can see messages on the console, we can begin to deduce what is going on in the plug.

[cheffy]

Ok I have managed to establish a serial connection to the Sheevaplug.

This is the message when I connect using putty.  (sorry if it's a bit long, but I have copied all the message)

After this it then asks me for a 'meteoplug login' and password, which I assumed was my meteohub login and password but it doesn't seem to work!

Message:

[   41.814424] end_request: I/O error, dev mtdblock0, sector 0
[   41.820211] Buffer I/O error on device mtdblock0, logical block 0
[   41.826491] uncorrectable error :
[   41.829729] uncorrectable error :
[   41.833167] end_request: I/O error, dev mtdblock0, sector 8
[   41.838950] Buffer I/O error on device mtdblock0, logical block 1
[   41.845201] uncorrectable error :
[   41.848443] uncorrectable error :
[   41.851875] end_request: I/O error, dev mtdblock0, sector 16
[   41.857741] Buffer I/O error on device mtdblock0, logical block 2
[   41.863990] uncorrectable error :
[   41.867234] uncorrectable error :
[   41.870656] end_request: I/O error, dev mtdblock0, sector 24
[   41.876524] Buffer I/O error on device mtdblock0, logical block 3
[   41.882798] uncorrectable error :
[   41.886044] uncorrectable error :
[   41.889465] end_request: I/O error, dev mtdblock0, sector 0
[   41.895245] Buffer I/O error on device mtdblock0, logical block 0
Assembling MD arrays...done (no arrays found in config file or automatically).
Checking file systems...fsck 1.41.3 (12-Oct-2008)
e2fsck 1.41.3 (12-Oct-2008)
/dev/mmcblk0p3: clean, 144/165312 files, 60280/661168 blocks
done.
Setting kernel variables (/etc/sysctl.conf)...done.
Mounting local filesystems...done.
Activating swapfile swap...done.
rm: cannot remove `.X*-lock': Read-only file system
rm: cannot remove `/tmp/.clean': Read-only file system
bootclean: Failure deleting '/tmp/.clean'. failed!
rm: cannot remove `./watchdog.pid': Read-only file system
rm: cannot remove `./crond.reboot': Read-only file system
rm: cannot remove `./crond.pid': Read-only file system
rm: cannot remove `./mdadm/monitor.pid': Read-only file system
rm: cannot remove `./ntpd.pid': Read-only file system
rm: cannot remove `./samba/unexpected.tdb': Read-only file system
rm: cannot remove `./samba/gencache.tdb': Read-only file system
rm: cannot remove `./samba/locking.tdb': Read-only file system
rm: cannot remove `./samba/brlock.tdb': Read-only file system
rm: cannot remove `./samba/sessionid.tdb': Read-only file system
rm: cannot remove `./samba/smbd.pid': Read-only file system
rm: cannot remove `./samba/connections.tdb': Read-only file system
rm: cannot remove `./samba/nmbd.pid': Read-only file system
rm: cannot remove `./samba/messages.tdb': Read-only file system
rm: cannot remove `./rsyncd.pid': Read-only file system
rm: cannot remove `./meteonet.pid': Read-only file system
rm: cannot remove `./loggerd.pid': Read-only file system
rm: cannot remove `./sshd.pid': Read-only file system
rm: cannot remove `./dbus/pid': Read-only file system
rm: cannot remove `./rsyslogd.pid': Read-only file system
rm: cannot remove `./dropbear.pid': Read-only file system
rm: cannot remove `./smbd.pid': Read-only file system
rm: cannot remove `./ntp.pid': Read-only file system
rm: cannot remove `./motd': Read-only file system
rm: cannot remove `./sm-notify.pid': Read-only file system
rm: cannot remove `./rpc.statd.pid': Read-only file system
rm: cannot remove `./portmap_mapping': Read-only file system
rm: cannot remove `./portmap.pid': Read-only file system
rm: cannot remove `./dhclient.eth0.pid': Read-only file system
bootclean: Failure cleaning /var/run. failed!
rm: cannot remove `/var/lock/.clean': Read-only file system
bootclean: Failure deleting '/var/lock/.clean'. failed!
/etc/rcS.d/S36udev-mtab: line 23: /etc/udev/rules.d/70-persistent-net.rules: Read-only file system
Setting up networking....
Configuring network interfaces...ifup: failed to open statefile /etc/network/run/ifstate: Read-only file system
failed.
Starting portmap daemon....
Starting NFS common utilities: statd failed!
rm: cannot remove `.X*-lock': Read-only file system
rm: cannot remove `/tmp/.clean': Read-only file system
bootclean: Failure deleting '/tmp/.clean'. failed!
rm: cannot remove `./watchdog.pid': Read-only file system
rm: cannot remove `./crond.reboot': Read-only file system
rm: cannot remove `./crond.pid': Read-only file system
rm: cannot remove `./mdadm/monitor.pid': Read-only file system
rm: cannot remove `./ntpd.pid': Read-only file system
rm: cannot remove `./samba/unexpected.tdb': Read-only file system
rm: cannot remove `./samba/gencache.tdb': Read-only file system
rm: cannot remove `./samba/locking.tdb': Read-only file system
rm: cannot remove `./samba/brlock.tdb': Read-only file system
rm: cannot remove `./samba/sessionid.tdb': Read-only file system
rm: cannot remove `./samba/smbd.pid': Read-only file system
rm: cannot remove `./samba/connections.tdb': Read-only file system
rm: cannot remove `./samba/nmbd.pid': Read-only file system
rm: cannot remove `./samba/messages.tdb': Read-only file system
rm: cannot remove `./rsyncd.pid': Read-only file system
rm: cannot remove `./meteonet.pid': Read-only file system
rm: cannot remove `./loggerd.pid': Read-only file system
rm: cannot remove `./sshd.pid': Read-only file system
rm: cannot remove `./dbus/pid': Read-only file system
rm: cannot remove `./rsyslogd.pid': Read-only file system
rm: cannot remove `./dropbear.pid': Read-only file system
rm: cannot remove `./smbd.pid': Read-only file system
rm: cannot remove `./ntp.pid': Read-only file system
rm: cannot remove `./motd': Read-only file system
rm: cannot remove `./sm-notify.pid': Read-only file system
rm: cannot remove `./rpc.statd.pid': Read-only file system
rm: cannot remove `./portmap_mapping': Read-only file system
rm: cannot remove `./portmap.pid': Read-only file system
rm: cannot remove `./dhclient.eth0.pid': Read-only file system
bootclean: Failure cleaning /var/run. failed!
rm: cannot remove `/var/lock/.clean': Read-only file system
bootclean: Failure deleting '/var/lock/.clean'. failed!
Setting console screen modes and fonts.
/etc/rcS.d/S55bootmisc.sh: line 29: /var/run/utmp: Read-only file system
rm: cannot remove `/var/lib/urandom/random-seed': Read-only file system
chmod: changing permissions of `/var/run/screen': Read-only file system
rm: cannot remove `/data/export/wswin-*.tmp': No such file or directory
rm: cannot remove `/data/export/wd-*.tmp': No such file or directory
mkdir: cannot create directory `/var/run/meteohub': Read-only file system
mkdir: cannot create directory `/var/run/meteohub': Read-only file system
rm: cannot remove `/data/uploads': No such file or directory
ln: creating symbolic link `/data/uploads': Read-only file system
cp: cannot stat `/data/myweb/uploads/wdlv5_04.*': No such file or directory
cp: cannot stat `/data/myweb/uploads/wdlive.html': No such file or directory
cp: cannot stat `/data/myweb/uploads/wdlconfig.xml': No such file or directory
cp: cannot stat `/data/myweb/uploads/swfobject.js': No such file or directory
cp: cannot stat `/data/myweb/uploads/dashboard.*': No such file or directory
rm: cannot remove `/srv/www/live': Read-only file system
ln: cannot remove `/srv/www/live': Read-only file system
rm: cannot remove `/var/mail/root': Read-only file system
rm: cannot remove `/etc/udev/rules.d/70-persistent-net.rules': Read-only file system
ln: cannot remove `/var/run/ntp.pid': Read-only file system
ln: cannot remove `/var/run/dropbear.pid': Read-only file system
ln: cannot remove `/var/run/smbd.pid': Read-only file system
ln: cannot remove `/var/log/messages': Read-only file system
rm: cannot remove `/usr/sbin/led': Read-only file system
ln: creating symbolic link `/usr/sbin/led': File exists
rm: cannot remove `/etc/udev/rules.d/70-persistent-net.rules': Read-only file system
 Removing any system startup links for /etc/init.d/exim4 ...
 Removing any system startup links for /etc/init.d/atd ...
 Removing any system startup links for /etc/init.d/mdm ...
 Removing any system startup links for /etc/init.d/mdm-raid ...
chmod: changing permissions of `/var/run/': Read-only file system
chmod: changing permissions of `/var/run/screen': Read-only file system
chmod: changing permissions of `/var/spool': Read-only file system
chmod: changing permissions of `/var/spool/ntp.drift': Read-only file system
chmod: changing permissions of `/var/run/screen': Read-only file system
[   44.939603] usbcore: registered new interface driver usbserial
[   44.952352] USB Serial support registered for generic
[   44.960528] usbcore: registered new interface driver usbserial_generic
[   44.967139] usbserial: USB Serial Driver core
[   44.986536] USB Serial support registered for pl2303
[   44.996553] usbcore: registered new interface driver pl2303
[   45.002192] pl2303: Prolific PL2303 USB to serial adaptor driver
[   45.419870] USB Serial support registered for cp210x
[   45.429904] usbcore: registered new interface driver cp210x
[   45.435538] cp210x: v0.09:Silicon Labs CP210x RS232 serial adaptor driver
[   45.556844] USB Serial support registered for FTDI USB Serial Device
[   45.568320] usbcore: registered new interface driver ftdi_sio
[   45.574134] ftdi_sio: v1.5.0:USB FTDI Serial Converters Driver
[   45.693032] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
/etc/rc.boot/initsensors: line 134: /etc/profile.new: Read-only file system
/etc/rc.boot/initsensors: line 135: /etc/profile.new: Read-only file system
/etc/rc.boot/initsensors: line 136: /etc/profile.new: Read-only file system
/etc/rc.boot/initsensors: line 137: /etc/profile.new: Read-only file system
mv: cannot stat `/etc/profile.new': No such file or directory
/etc/rc.boot/initsensors: line 139: /home/meteohub/meteohubhw.txt: Read-only file system
cp: cannot create regular file `/home/meteohub/wmr928fulleval.conf': Read-only file system
INIT: Entering runlevel: 2itsensors exited
Starting watchdog keepalive daemon: wd_keepalive.
Starting enhanced syslogd: rsyslogdrm: cannot remove `/home/meteohub/eth0con': Read-only file system
/sbin/ifdown: failed to open statefile /etc/network/run/ifstate: Read-only file system
/sbin/ifdown: failed to open statefile /etc/network/run/ifstate: Read-only file system
/home/meteohub/checketh0: line 16: sleep1: command not found
[   34.806481] xor: measuring software checksum speed
[   34.851575]    arm4regs  :  1084.400 MB/sec
[   34.901575]    8regs     :   804.000 MB/sec
[   34.951575]    32regs    :   900.400 MB/sec
[   34.955781] xor: using function: arm4regs (1084.400 MB/sec)
[   35.141752] raid6: int32x1     78 MB/s
[   35.312133] raid6: int32x2    103 MB/s
[   35.481737] raid6: int32x4    124 MB/s
[   35.651761] raid6: int32x8    110 MB/s
[   35.655525] raid6: using algorithm int32x4 (124 MB/s)
[   35.694655] md: raid6 personality registered for level 6
[   35.699997] md: raid5 personality registered for level 5
[   35.705374] md: raid4 personality registered for level 4
Success: loaded module raid456.
Success: loaded module raid5.
Success: loaded module raid6.
[   35.841166] md: raid10 personality registered for level 10
Success: loaded module raid10.
done.
Begin: Assembling all MD arrays ... [   35.923893] uncorrectable error :
[   35.927134] uncorrectable error :
[   35.930557] end_request: I/O error, dev mtdblock0, sector 0
[   35.936337] Buffer I/O error on device mtdblock0, logical block 0
[   35.942626] uncorrectable error :
[   35.945865] uncorrectable error :
[   35.949286] end_request: I/O error, dev mtdblock0, sector 8
[   35.955068] Buffer I/O error on device mtdblock0, logical block 1
[   35.961322] uncorrectable error :
[   35.964572] uncorrectable error :
[   35.967999] end_request: I/O error, dev mtdblock0, sector 16
[   35.973868] Buffer I/O error on device mtdblock0, logical block 2
[   35.980118] uncorrectable error :
[   35.983372] uncorrectable error :
[   35.986800] end_request: I/O error, dev mtdblock0, sector 24
[   35.992668] Buffer I/O error on device mtdblock0, logical block 3
[   35.998940] uncorrectable error :
[   36.002189] uncorrectable error :
[   36.005617] end_request: I/O error, dev mtdblock0, sector 0
[   36.011399] Buffer I/O error on device mtdblock0, logical block 0
[   36.064751] uncorrectable error :
[   36.067997] uncorrectable error :
[   36.071419] end_request: I/O error, dev mtdblock0, sector 0
[   36.077201] Buffer I/O error on device mtdblock0, logical block 0
[   36.083488] uncorrectable error :
[   36.086728] uncorrectable error :
[   36.090149] end_request: I/O error, dev mtdblock0, sector 8
[   36.095930] Buffer I/O error on device mtdblock0, logical block 1
[   36.102186] uncorrectable error :
[   36.105423] uncorrectable error :
[   36.108845] end_request: I/O error, dev mtdblock0, sector 16
[   36.114712] Buffer I/O error on device mtdblock0, logical block 2
[   36.120964] uncorrectable error :
[   36.124216] uncorrectable error :
[   36.127645] end_request: I/O error, dev mtdblock0, sector 24
[   36.133513] Buffer I/O error on device mtdblock0, logical block 3
[   36.139784] uncorrectable error :
[   36.143036] uncorrectable error :
[   36.146463] end_request: I/O error, dev mtdblock0, sector 0
[   36.152244] Buffer I/O error on device mtdblock0, logical block 0
mdadm: No arrays found in config file or automatically
Failure: failed to assemble all arrays.
done.
Begin: Waiting for udev to process events ... done.
done.
Begin: Running /scripts/local-premount ... done.
Begin: Running /scripts/local-bottom ... done.
done.
Begin: Running /scripts/init-bottom ... done.
INIT: version 2.86 booting
Starting the hotplug events dispatcher: udevd[   37.450612] udevd version 125 started
.
Synthesizing the initial hotplug events...done.
Waiting for /dev to be fully populated...done.
Setting the system clock.
Activating swap...[   40.009624] Adding 134532k swap on /dev/mmcblk0p2.  Priority:-1 extents:1 across:134532k SS
done.
Checking root file system...fsck 1.41.3 (12-Oct-2008)
e2fsck 1.41.3 (12-Oct-2008)
/dev/mmcblk0p1: clean, 40590/54544 files, 166135/218139 blocks
done.
mount: / not mounted already, or bad option
Setting the system clock.
Cleaning up ifupdown...rm: cannot remove `/etc/network/run/ifstate': Read-only file system
Loading kernel modules...[   41.503330] loop: module loaded
done.
[   41.807736] uncorrectable error :
[   41.810982] uncorrectable error :
[   41.814424] end_request: already started.
Removing stale PID file /var/run/dbus/pid..
rm: cannot remove `/var/run/dbus/pid': Read-only file system
Starting OpenBSD Secure Shell server: sshd[  347.805334] NET: Registered protocol family 10
[  347.811372] lo: Disabled Privacy Extensions
.
Starting loggerd... done.
Starting meteonetdstart-stop-daemon: Unable to open pidfile `/var/run/loggerd.pid' for writing: Read-only file system (Read-only file system)
.
start-stop-daemon: Unable to open pidfile `/var/run/meteonet.pid' for writing: Read-only file system (Read-only file system)
Starting NFS common utilities: statd failed!
Not starting internet superserver: no services enabled.
Starting rsyncd.
start-stop-daemon: Unable to open pidfile `/var/run/rsyncd.pid' for writing: Read-only file system (Read-only file system)
Starting Samba daemons: nmbd failed!
Starting thttpd/data/log/thttpd.log: No such file or directory
.
Starting NTP server: ntpdlockfile creation failed
.
Starting MD monitoring service: mdadm --monitorcannot create pid file: Read-only file system
.
Starting periodic command scheduler: crond/usr/sbin/cron: can't open or create /var/run/crond.pid: Read-only file system
 failed!
Stopping watchdog keepalive daemon: wd_keepalive.
Starting watchdog daemon: watchdog.

Debian GNU/Linux 5.0 meteoplug ttyS0

meteoplug login:

[NewIT_Marcus]

There are a few things about Meteohub that are useful to bear in mind:

• It never boots from NAND, it simply loops whilst trying to boot from SD card
• The web interface user & password is not the same as your system username & password
• The default password for the system root account is meteohub
• Because it boots from SD card, there may be long-term issues with wear

See http://www.newit.co.uk/forum/index.php/topic,238.0.html

The messages that you copied & pasted are far from normal.

These errors:

Code:

end_request: I/O error, dev mtdblock0, sector 0

relate to NAND memory, and can be ignored for the time being. They may simply relate to an issue that the SD card system has with accessing the NAND hardware.

Although I don't see it declared that the SD card partitions are being mounted read-only; there are many messages that suggest this:

Code:

Read-only file system

And this is why you can't connect via your network:

Code:

Setting up networking....
Configuring network interfaces...ifup: failed to open statefile /etc/network/run/ifstate: Read-only file system
failed.

Errors were identified during the boot process such that the SD card was judged not to be safe to mount for read/write. It was, however, mounted read-only. You *might* be able to log in with the credentials supplied above, but with the file system in its current condition I can't say for sure.

EITHER the SD card has been subject to wear, which is normal, but to such an extent that it can no longer support write operations, which might not be normal - depending upon the qualities of the card and/or your usage, OR a differnet kind of problem, not related to wear, has triggered the issue.

The best way forward is for you to prepare a new card with the Meteohub software - you can download a suitable SD card image form the Meteohub website, if you don't have your own backup - and test that card. It should work, or at least if it doesn't we could say that maybe it is the Sheevaplug that has the issue.

If a new SD card works, you may be able to get more use out of the original by reformatting or rewriting an image to it. But this can not be guaranteed at all, and for the moment you should regard the card as suspect, and unlikely to perform.

[cheffy]

Thanks for your help - I did wonder if I had issues with the SD card.

I might try and reformat my original SD card and then try re-image the meteohub software - it probably won't work but I thought I could at least give it a try.  If it doesn't, then I will purchase a new SD card and try that.

One other question, any suggestions on which is the best software to use to put the meteohub image on to the SD card - I have never done this before.

Thanks again.

[NewIT_Marcus]

One other question, any suggestions on which is the best software to use to put the meteohub image on to the SD card - I have never done this before.

Your Meteohub won't boot from NAND; the Meteohub environment variables ensure that. So you probably wont' be using the Sheevaplug to rewrite your SD card. The answer to your question depends upon what systems and hardware you have available.

Under linux, use dd. Under Windows, I can't help - I never found anything that worked, but I only have 2 SD card readers and it may be that the software I tested unsuccessfully would work with other readers.

[cheffy]

Great news - I have it working!!

I reformatted the original SD card, then I re-imaged the Meteohub software on to the card (using a program called 'roadkil') - then I fired the sheevaplug back up and it worked first time!

I am aware might current SD card might not be stable, so I am planning on getting a new one just in case - but it's good to know that the sheevaplug is ok and the issue was with the SD card.

Thanks again for all your help.

[NewIT_Marcus]

Roadkil is one of the Windows programs that I had tried without good results.

Thank you for letting us know the outcome. It is the best we could have hoped for, and you are right, the card should be regarded as suspect now, but at least you have some warning of this. One of the reasons why we think booting from SD card is the best choice for the Sheevaplug is that although we know that wear will occur, the cost is bearable. (And once NAND is worn out, it is not user-replaceable).