NSLU2-Linux
view · edit · print · history

HowTo.FailSambaInformation History

Hide minor edits - Show changes to markup

September 15, 2011, at 12:16 PM by duke9985 -- Configuration of dns and default gateway in comman line
Added lines 19-32:

EASIR WAY TO CONFIGURE DEFAULT GW AND DNS:

If you don't want to flash again the nslu2 but you cannot configure the dns and default gateway via the web interface. 1) connect via ssh to the slug 2) add your dns to /etc/resolv.conf

   $ nameserver write.your.dns.ip

3) add a default route

   $ route add default gateway your.default.gw.ip ixp0

February 22, 2010, at 03:16 PM by Erwin --
Changed line 50 from:

I used Unslung-6.10-beta-firmware for a long time without problems, when suddenly this error showed up. It was a problem because I couldn't make any changes using the web GUI (i.e. the default gateway). I tried Peter's fix (copying CGI_ds.conf etc), but that didn't work for me. I tried the sercomm upgrade utility to 'upgrade' to the stock firmware but the error kept showing up. Because the redboot thing was to advanced for me, I finally used the EraseAll utility from linksys to 'upgrade' with the stock firmware and that solved everything.

to:

I used Unslung-6.10-beta-firmware for a long time without problems, when suddenly this error showed up. It was a problem because I couldn't make any changes using the web GUI (i.e. the default gateway). I tried Peter's fix (copying CGI_ds.conf etc), but that didn't work for me. Restore Ddefault Config didn't work for me neither. I tried the sercomm upgrade utility to 'upgrade' to the stock firmware but the error kept showing up. Because the redboot thing was to advanced for me, I finally used the EraseAll utility from linksys to 'upgrade' with the stock firmware and made the error go away.

February 22, 2010, at 03:13 PM by Erwin --
Changed lines 46-53 from:

--Mark Smith

to:

Mark Smith


I used Unslung-6.10-beta-firmware for a long time without problems, when suddenly this error showed up. It was a problem because I couldn't make any changes using the web GUI (i.e. the default gateway). I tried Peter's fix (copying CGI_ds.conf etc), but that didn't work for me. I tried the sercomm upgrade utility to 'upgrade' to the stock firmware but the error kept showing up. Because the redboot thing was to advanced for me, I finally used the EraseAll utility from linksys to 'upgrade' with the stock firmware and that solved everything. Erwin, 22 feb 2010


September 06, 2008, at 03:44 PM by Stefan --
Changed line 40 from:

I did the same, it worked fine, the message disapeared at the first access of the web-interface, even before doing the Restore Default Config ! Much simpler than the ResetSysConfig? procedure(which also worked for me at some point, but the message came back after a while ...)

to:

I did the same, it worked fine, the message disapeared at the first access of the web-interface, even before doing the Restore Default Config ! Much simpler than the ResetSysConf procedure(which also worked for me at some point, but the message came back after a while ...)

September 05, 2008, at 10:15 PM by Stefan --
Added lines 40-42:

I did the same, it worked fine, the message disapeared at the first access of the web-interface, even before doing the Restore Default Config ! Much simpler than the ResetSysConfig? procedure(which also worked for me at some point, but the message came back after a while ...) Stefan

September 11, 2007, at 02:57 AM by Mark Smith smitty1smitty at comcast dot net --
Changed line 43 from:

Mark Smith: smitty1smitty at comcast d.t net

to:

--Mark Smith

September 11, 2007, at 02:56 AM by Mark Smith smitty1smittycomcastnet --
Added lines 39-43:

I got this error after a reflash, and was somewhat concerned since I was unable to change settings like the default gateway. I was able to solve it using part of Peter's solution (cp /usr/local/CGI_ds.conf to /etc/CGI_ds.conf), but didn't need to Restore Default Config. I just rebooted. Granted, I had not changed the IP of the device. Mark Smith: smitty1smitty at comcast d.t net

April 24, 2007, at 03:30 PM by marXman -- Everything should be working now.
Changed lines 5-6 from:

"NOTE:" Flashing your NSLU2 with Unslung after using OpenSlug is known to cause this error message. Proceed with SysConf?

to:

NOTE: Flashing your NSLU2 with Unslung after using OpenSlug is known to cause this error message. Proceed with ResetSysConf

April 24, 2007, at 03:29 PM by marXman -- Must.. edit..
Changed lines 5-6 from:
  • "NOTE:" Flashing your NSLU2 with Unslung after using OpenSlug is known to cause this error message. Proceed with ResetSysConf.
to:

"NOTE:" Flashing your NSLU2 with Unslung after using OpenSlug is known to cause this error message. Proceed with SysConf?

April 24, 2007, at 03:28 PM by marXman -- Minor corrections for my last edit
Changed lines 5-6 from:

"Note:" Flashing your NSLU2 with Unslung after using OpenSlug is known to cause this error message. Proceed with ResetSysConf.

to:
  • "NOTE:" Flashing your NSLU2 with Unslung after using OpenSlug is known to cause this error message. Proceed with ResetSysConf.
April 24, 2007, at 03:26 PM by marXman -- Note about OpenSlug -> Unslung transition side effects.
Added lines 5-6:

"Note:" Flashing your NSLU2 with Unslung after using OpenSlug is known to cause this error message. Proceed with ResetSysConf.

October 14, 2006, at 04:33 PM by Peter --
Changed line 34 from:

I tried cp /usr/local/CGI_ds.conf /etc/CGI_ds.conf and did a Restore Default Config in the web-interface.

to:

I copied /usr/local/CGI_ds.conf to /etc/CGI_ds.conf and did a Restore Default Config in the web-interface.

October 14, 2006, at 04:32 PM by Peter --
Changed line 34 from:

I tried "cp /usr/local/CGI_ds.conf /etc/CGI_ds.conf" and did a "Restore Default Config" in the web-interface.

to:

I tried cp /usr/local/CGI_ds.conf /etc/CGI_ds.conf and did a Restore Default Config in the web-interface.

October 14, 2006, at 04:31 PM by Peter --
Changed lines 34-35 from:

I tried "cp /usr/local/CGI_ds.conf /etc/CGI_ds.conf". It worked fine with unslung-fw 3.17!

to:

I tried "cp /usr/local/CGI_ds.conf /etc/CGI_ds.conf" and did a "Restore Default Config" in the web-interface. It worked fine with unslung-fw 3.17!

October 14, 2006, at 04:25 PM by Peter --
Changed line 34 from:

I tried "cp /usr/local/CGI_ds.conf /etc/CGI_ds.conf" It worked fine with unslung-fw 3.17!

to:

I tried "cp /usr/local/CGI_ds.conf /etc/CGI_ds.conf". It worked fine with unslung-fw 3.17!

October 14, 2006, at 04:24 PM by Peter --
Changed lines 30-35 from:

Robin Jacobs: ResetSysConf did not work for me, finally I decided to use the ereaseall utility of linksys, I 'ereasedall'-ed back to stock firmware, booted up verified to error was gone, then used the standard 'fresh' unslung install (update to unslung fw via the webinterface, enable telnet, unslung-ed) I know the unslung wiki warns against using the ereaseall utility (change of destroying redboot) but it works perfectly

to:

Robin Jacobs: ResetSysConf did not work for me, finally I decided to use the ereaseall utility of linksys, I 'ereasedall'-ed back to stock firmware, booted up verified to error was gone, then used the standard 'fresh' unslung install (update to unslung fw via the webinterface, enable telnet, unslung-ed) I know the unslung wiki warns against using the ereaseall utility (change of destroying redboot) but it works perfectly


I tried "cp /usr/local/CGI_ds.conf /etc/CGI_ds.conf" It worked fine with unslung-fw 3.17! Peter

July 14, 2006, at 11:42 AM by Robin Jacobs --
Changed lines 26-30 from:

Bruce Morden added that I also had this problem after flashing from 3 to 5.5 beta, and solved it by restoring the profile I had saved of the Slug prior to the upgrade procedure.

to:

Bruce Morden added that I also had this problem after flashing from 3 to 5.5 beta, and solved it by restoring the profile I had saved of the Slug prior to the upgrade procedure.


Robin Jacobs: ResetSysConf did not work for me, finally I decided to use the ereaseall utility of linksys, I 'ereasedall'-ed back to stock firmware, booted up verified to error was gone, then used the standard 'fresh' unslung install (update to unslung fw via the webinterface, enable telnet, unslung-ed) I know the unslung wiki warns against using the ereaseall utility (change of destroying redboot) but it works perfectly

March 24, 2006, at 08:17 AM by emm_is -- linksys provides a button to press to fix this
Added lines 5-6:

The first thing you consider is to reset the configuration back to the factory default using the web interface. You can find at the bottom of the Administraion -> System page a button "Restore Default Config". Probably best to do this without a disk attached.

September 26, 2005, at 08:54 PM by Bruce Morden -- Additional info
Changed lines 20-24 from:

Doing this, I got rid of the annoying error message in the web-interface the first time I tried this. Possibly, this order of actions is the right one?

to:

Doing this, I got rid of the annoying error message in the web-interface the first time I tried this. Possibly, this order of actions is the right one?


Bruce Morden added that I also had this problem after flashing from 3 to 5.5 beta, and solved it by restoring the profile I had saved of the Slug prior to the upgrade procedure.

August 28, 2005, at 05:57 PM by Rienk Harkema -- Possible tip
Changed lines 15-20 from:

Jim Tucker added that this procedure only worked for him when he detached the drive from the slug. (Earlier revisions of this page may not have mentioned this important step.)

to:

Jim Tucker added that this procedure only worked for him when he detached the drive from the slug. (Earlier revisions of this page may not have mentioned this important step.)

Rienk Harkema: I did the following after the procedure described above didn't work for me (only tried that once): I put the slug in maintenance mode from the web-interface. Then, when it rebooted to go into that mode, I cought the telnet Redboot window to erase the part of the system configuration described elsewhere. After I gave the 'reset' command at the Redboot prompt after erasing, the slug booted into maintenance mode as requested. Then, I used the Sercomm utility (probably Upslug will work also) to reflash the firmware. Doing this, I got rid of the annoying error message in the web-interface the first time I tried this. Possibly, this order of actions is the right one?

May 06, 2005, at 02:31 AM by bzhou -- fixed a typo
Changed lines 7-8 from:

NOTE: Any firmware flashing should be down without a disk attached.

to:

NOTE: Any firmware flashing should be done without a disk attached.

April 03, 2005, at 07:30 AM by bobtm --
Changed line 9 from:

Anecdotal evidence says that reflashing the firmware, followed by resetting the SysConf? area three or four times consecutively might correct the problem as well.

to:

Anecdotal evidence says that reflashing the firmware, followed by resetting the SysConf area three or four times consecutively might correct the problem as well.

April 03, 2005, at 07:29 AM by bobtm --
Changed line 11 from:

JeffreyS? stated that on his last attempt, he reflashed the firmware, and on the subsequent boot, followed the ResetSysConf instructions. Doing this, his "Fail to get samba information" NSLU2 started operating correctly.

to:

JeffreyS stated that on his last attempt, he reflashed the firmware, and on the subsequent boot, followed the ResetSysConf instructions. Doing this, his "Fail to get samba information" NSLU2 started operating correctly.

April 01, 2005, at 12:09 AM by JimTucker --
Changed lines 13-15 from:

Jim Tucker added that this procedure only worked for him when he detached the drive from the slug.

to:

Jim Tucker added that this procedure only worked for him when he detached the drive from the slug. (Earlier revisions of this page may not have mentioned this important step.)

February 19, 2005, at 01:57 AM by ByronT --
Added lines 7-8:

NOTE: Any firmware flashing should be down without a disk attached.

February 19, 2005, at 12:55 AM by Jim Tucker --
Changed lines 9-11 from:

JeffreyS? stated that on his last attempt, he reflashed the firmware, and on the subsequent boot, followed the ResetSysConf instructions. Doing this, his "Fail to get samba information" NSLU2 started operating correctly.

to:

JeffreyS? stated that on his last attempt, he reflashed the firmware, and on the subsequent boot, followed the ResetSysConf instructions. Doing this, his "Fail to get samba information" NSLU2 started operating correctly.

Jim Tucker added that this procedure only worked for him when he detached the drive from the slug.

February 16, 2005, at 09:01 PM by ByronT --
Added lines 6-9:

Anecdotal evidence says that reflashing the firmware, followed by resetting the SysConf? area three or four times consecutively might correct the problem as well.

JeffreyS? stated that on his last attempt, he reflashed the firmware, and on the subsequent boot, followed the ResetSysConf instructions. Doing this, his "Fail to get samba information" NSLU2 started operating correctly.

January 13, 2005, at 09:27 PM by uSURPER --
Changed line 1 from:

When the webinterface is telling you:"Error: fail to get samba information".

to:

When the web interface is telling you: "Error: fail to get samba information".

Changed line 3 from:

Probably something went wrong in the SysConf area.

to:

Probably something went wrong in the SysConf area. This is where the system configuration is kept.

Changed line 5 from:

Now you have to recreate the SysConf area to fix things, follow the intructions ResetSysConf

to:

You have a few choices; either attempt to find someone with NSLU2 skills who can help you fix the problem or recreate the SysConf area to fix things by following these instructions: ResetSysConf

November 18, 2004, at 10:21 AM by elutjesgmxnet --
Changed line 5 from:

Now you have to recreate the SysConf? area to fix things, follow the intructions ResetSysConf

to:

Now you have to recreate the SysConf area to fix things, follow the intructions ResetSysConf

November 18, 2004, at 10:21 AM by elutjesgmxnet --
Changed lines 1-5 from:

Describe FailSambaInformation here.

to:

When the webinterface is telling you:"Error: fail to get samba information".

Probably something went wrong in the SysConf area.

Now you have to recreate the SysConf? area to fix things, follow the intructions ResetSysConf