You are here

Nanostation M2 XW low flash space

5 posts / 0 new
Last post
AJ6GZ
Nanostation M2 XW low flash space

Tried an update to daily 80-014217a on an NS M2 XW, reinstalled Tunnel, and it's back on the air ok.  I noticed free space for flash = 68K.  I don't recall what it might have shown before. iirc, this node went from 3.17RC1 thru a few dailies up to old 176. Not sure where it started as far as Air OS.  Could it be related to this https://www.arednmesh.org/content/bad-rocket-m5  ?

Filesystem           1K-blocks      Used Available Use% Mounted on
/dev/root                 5120      5120         0 100% /rom
tmpfs                    30092       212     29880   1% /tmp
/dev/mtdblock5            1216      1148        68  94% /overlay
overlayfs:/overlay        1216      1148        68  94% /
tmpfs                      512         0       512   0% /dev

This node had a habit of not re-establishing the tunnel and OLSR stopping after the slightest outage over the internet (like when the cable co reboots something in the middle of the night), often requiring a hard boot. Maybe related if it's running out of space?  Will watch it over the next couple days.

Recovery? Bad flash memory? Replace unit?

Ian

 

AJ6GZ
File

File

AE6XE
AE6XE's picture
Ian,   The OpenWrt group

Ian,   The OpenWrt group increased the 'NOR' flash storage space, showing up as /rom, for the initial image on flash memory.   This is what the node reverts back to when holding the reset button (while booted) for ~15 seconds.   This increase took away from our local custom configuration settings and add-on package space, showing as the overlay.   The overlay keeps a delta of file changes on top of the /rom .    It is good that there is enough space to install the tunnel packages :) .  This flash is used like a disk drive on a typical computer -- it is long term storage and slower memory generally. 

This issue with OLSR and other issues are unrelated.  Generally these are due to lack of RAM memory, a different sized chip than 'flash',  for the program and linux kernel to run and/or defects/scalability issues with OLSR. 

Be sure to only run the nightly builds on a device with 64Mb RAM.   We've not gone through to make changes that reduce the usage of RAM yet.  32Mb RAM devices are unstable.  The NS M2 XW is a 64Mb RAM device, so you're OK on this device to run the nightly builds.

Joe AE6XE
 

AJ6GZ
So is the space an issue on

So is the space an issue on this node?  I'll check my other NS M2 XW tonight which is still at nightly176.  I don't run anything on the nodes except a tunnel here and there and a meshchat API-only. I can move those two to a different node at this site thought it might bring up the slugbug since there is no RF conn on the other node just yet.
 

AE6XE
AE6XE's picture
These XW devices have

These XW devices have upgraded RAM to 64Mb from the 32Mb XM devices, so you have sufficient RAM.      The flash memory to store the image is big enough for the firmware + tunnel packages.  If you wanted to add more packages, e.g. meshchat or something else, there may not be enough space to install.  This is the space that is limited.  This is not necessarily a bad thing.   Loading functionality on to a mesh node beyond its core function will take cpu and memory resources away.   It is preferable to install meshchat and other services on other devices, e.g. a rasPI.  

Theme by Danetsoft and Danang Probo Sayekti inspired by Maksimer