iDirect 3100 series modem, customer is trying to login however cannot.  Have them console in, it keeps rebooting.

The error message states:

ln: /var/run/idirect: No space left on device Starting falcon:cd: 150: can't cd to /var/run/idirect Initializing Falcon ... Seeding RNG... OK symlink: /var/log/idirect <-- /var/run/idirect Failed to symlink /var/run/idirect/:No space left on device Failed to ch to /var/run/idirect: No such file or directory Please ensure that falcon is correctly installed cannot access options file /etc/idirect/falcon/falcon.opt: No such file or directory. Starting with default options. Loading startup manifest: /etc/idirect/startup_bsp_manifest.xml looking for sig file: /etc/idirect/startup_sigs.sig falcon Warning: This board is incapable of being a 'Boot'! OK  Starting falcon_monitor:cd: 150: can't cd to /var/run/idirect OK   ln: /var/run/idirect: No space left

iDirectServices74 wrote on Sep 30^th, 2008 at 8:35pm:

Warning: This board is incapable of being a 'Boot'! OK

i think that message alone tells you that the flash on the device is busted (bad) and you should send this modem to iDirect for repair.

in the meantime this may help:

https://www.scribd.com/doc/443072/Troubleshooting-Guide-for-iDirect-Remote-Site?autodown=pdf  

ya it says netmodem II but they are both pretty much identical at least in the core.

also this guide (its better than the above one)
https://tinyurl.com/3gb59d

What iDS version?

Asking that because some iDS versions require a BSP and/or an upgrade prep package when loading the software on the unit.

Thanks so much.

Version is 7.1.1.

TDMAMike hit the nail on the head AGAIN!!
This software version requires the BSP package to be loaded before the image package.  One of the things the BSP (Cumulative Update) does is move swap space around on the box, this enable s the options etc to be loaded correctly.

you need to run the recovery again, full recovery with image and options, but this time use the BSP update as the first image, then load 7.1.1 image, then load options and then reset.  

Once you have done this, you can telnet 0, then run versions_report you will see near the top the BSP version.

you can also check the version of BSP in the Linux shell to ensure you are running an old one and this is the problem by searching for cumulative_update and running the more command on that file.  off the top of my head I can't remember where it is stored.  Sorry.

They have loaded the cumulative first, and they've done it at least three times now.

I've given them the recovery procedure (THANKS!) and he's working on it right now.

Hopefully this'll work.

Hopefully it all works out.  Scout, thanks for expounding...couldnt have said it better myself.  

r/
M

When they load the images in order, make sure you wait at least 2 minutes from the time iSite says Done.  IT IS NOT DONE.  iSite reports done before the unit completes the flash, if you try to load the next image or options file during the time the unit is flashing the previous image it will not work.

So load BSP - wait 2 minutes
load image - wait two minutes
load options file - reset

if you can get a console open to the unit you will see the image being loaded, when it says package flash completed on the console, that's when it's done.

rgds

Agreed.  It is always good practive to wait as long as 2-3 minutes after seeing DONE! in the window pane.  I have often seen the image bypassed (not written) due to my own expeditious efforts. :)

I, on the other hand dont agree with the 2min/3min wait ... its completely unnecessary but hey you're free to do what you want.

wrote on Oct 2^nd, 2008 at 2:52pm:

I, on the other hand dont agree with the 2min/3min wait ... its completely unnecessary but hey you're free to do what you want.

if you would like to spend time recovering remotes it is absolutely not a requirement.  please just open a telnet session, view the package download, and compare the time difference between iSite reporting Done and package flash completed being reported on the modem.  You will quite clearly see there is a difference, and in fact on different remotes, it can be a different time differential.  In the case above, I recommend two minutes plus as it has never taken longer than 1.5 minutes for me.

Stating it's completely unnecessary is not helpful.  Please feel free to talk to any of the instructors in iDirect, or in fact the more experienced engineers and TAC support guys, they may set you straight on that one.  

Scout wrote on Oct 2^nd, 2008 at 5:04pm:

if you would like to spend time recovering remotes it is absolutely not a requirement.  please just open a telnet session, view the package download, and compare the time difference between iSite reporting Done and package flash completed being reported on the modem.  You will quite clearly see there is a difference, and in fact on different remotes, it can be a different time differential.  In the case above, I recommend two minutes plus as it has never taken longer than 1.5 minutes for me. Stating it's completely unnecessary is not helpful.  Please feel free to talk to any of the instructors in iDirect, or in fact the more experienced engineers and TAC support guys, they may set you straight on that one.

well i said this based on experience. i've never had a terminal break on me by not waiting. and i've upgraded/downgraded a whole bunch.

if isite has a bug or is missing a feature that should force you to wait then why not tell iDirect?

as you know (from my other posts) i DO KNOW how to telnet into the modem as well console. I am a linux certified system admin so i know what i am doing when it comes to linux as well as telneting.

thanks

wrote on Oct 2^nd, 2008 at 2:52pm:

I, on the other hand dont agree with the 2min/3min wait ... its completely unnecessary but hey you're free to do what you want.

I totally agree with the wait, because it may not be done IN the modem.  I've seen proof of this when I have had to preconfigure modems.  In the telnet window it would state "PKG Flash Complete" however that would be after two minutes after iSite states "done".

That recovery procedure worked, BTW.  Thank you so much!  We had another recovery procedure, however he tried that way three times and it did not work.  Even when I told him to watch the telnet session before moving on to the next step.