NSLU2-Linux
view · edit · print · history

FAQ.WebUpgradeErrors History

Hide minor edits - Show changes to markup

February 09, 2008, at 12:33 AM by macnet --
Changed lines 29-33 from:

2007-12-31: I initially got the "no enough free space" error from the admin upgrade page running R72 and trying to install the debian image. Connecting a USB drive formated ext3 (the format utility on the factory slug will do the right thing) cleared the problem (FAT/NTFS did not work).

to:

2007-12-31: I initially got the "no enough free space" error from the admin upgrade page running R72 and trying to install the debian image. Connecting a USB drive formated ext3 (the format utility on the factory slug will do the right thing) cleared the problem (FAT/NTFS did not work).


2008-02-09: I had the same problem when trying to upgrade my NSLU2 v1.2 with factory default firmware (V2.3R24) to V2.3R29 and V2.3R64 firmwares. The problem was solved by shutting down the NSLU2, removing the USB flash drive attached and booting up.

December 31, 2007, at 10:19 PM by RjS -- avoiding some unexpected wikification
Changed line 29 from:

2007-12-31: I initially got the "no enough free space" error from the admin upgrade page running R72 and trying to install the debian image. Connecting a USB drive formated EXT3? (the format utility on the factory slug will do the right thing) cleared the problem (FAT/NTFS did not work).

to:

2007-12-31: I initially got the "no enough free space" error from the admin upgrade page running R72 and trying to install the debian image. Connecting a USB drive formated ext3 (the format utility on the factory slug will do the right thing) cleared the problem (FAT/NTFS did not work).

December 31, 2007, at 10:16 PM by RjS -- Avoid \"no enough free space\" by connecting an ext3 formatted drive
Added lines 26-29:

2007-12-31: I initially got the "no enough free space" error from the admin upgrade page running R72 and trying to install the debian image. Connecting a USB drive formated EXT3? (the format utility on the factory slug will do the right thing) cleared the problem (FAT/NTFS did not work).

August 12, 2007, at 03:54 PM by jamesN --
Added lines 23-25:

i have the same problem, i get that error when i try to upgrade to unsung 6.8. i am running the linsys V2.3R72 at the moment. i really do not want to use the erase all tool! i have tried rebooting and going straight to the admin page but i still get the error! what else can i do, i am able to telnet to the redboot, can i do it from there?

April 12, 2007, at 08:01 AM by Trurl --
Changed lines 21-22 from:

2007-04-11, Trurl: I was trying to upgrade to unslung 6.8 from R72. But got a message "not enough memory". So I tried to downgrade to R63. But still receive the same message. So I decided (with Heart Beating Very Laud And Not Breathing At All) to use eraseall utility to downgrade to R63. And it worked out :-). Then having NSLU2 with R63 installed I've upgraded to unslung 6.8 without any problems.

to:

2007-04-11, Trurl: I was trying to upgrade to unslung 6.8 from R72. But got a message "not enough memory". So I tried to downgrade to R63. But still receive the same message. So I decided (with Heart Beating Very Laud And Not Breathing At All) to use eraseall utility to downgrade to R63. And it worked out :-) (disk were not connected while re-booting the NSLU2 before using the utility). Then having NSLU2 with R63 installed I've upgraded to unslung 6.8 without any problems.

April 11, 2007, at 07:54 PM by Trurl --
Changed lines 21-22 from:

2007-04-11, Trurl: I was trying to upgrade to unslung 6.8 from R72. But got a meesage "not enough memory". So I tried to downgrade to R63. But still receive the same message. So I decided (with Hart Beating Very Laud And Not Breathing At All) to use eraseall utility to downgrade to R63. And it worked out :-). Then having NSLU2 with R63 installed I've upgraded to unslung 6.8 without any problems.

to:

2007-04-11, Trurl: I was trying to upgrade to unslung 6.8 from R72. But got a message "not enough memory". So I tried to downgrade to R63. But still receive the same message. So I decided (with Heart Beating Very Laud And Not Breathing At All) to use eraseall utility to downgrade to R63. And it worked out :-). Then having NSLU2 with R63 installed I've upgraded to unslung 6.8 without any problems.

April 11, 2007, at 07:53 PM by Trurl --
Changed lines 21-22 from:

2007-04-11, Trurl: I was trying to upgrade unslung 6.8 from R72. But got a meesage "not enough memory". So I've tried to downgrade to R63. But receive the same message. So I decided to use eraseall utility to downgrade. I worked out. And having NSLU2 with R63 installed I upgraded to unslung without eny problems.

to:

2007-04-11, Trurl: I was trying to upgrade to unslung 6.8 from R72. But got a meesage "not enough memory". So I tried to downgrade to R63. But still receive the same message. So I decided (with Hart Beating Very Laud And Not Breathing At All) to use eraseall utility to downgrade to R63. And it worked out :-). Then having NSLU2 with R63 installed I've upgraded to unslung 6.8 without any problems.

April 11, 2007, at 07:51 PM by Trurl --
Added lines 18-22:

2007-04-11, Trurl: I was trying to upgrade unslung 6.8 from R72. But got a meesage "not enough memory". So I've tried to downgrade to R63. But receive the same message. So I decided to use eraseall utility to downgrade. I worked out. And having NSLU2 with R63 installed I upgraded to unslung without eny problems.

March 12, 2007, at 10:42 PM by kilgore -- Added \\\"no enough memory\\\" to main heading
Changed lines 1-4 from:

When I try to upgrade the firmware on my NSLU2 it reports "No Space Left on Device" or "Not enough Memory".

If you are running with a USB flash or hard disk with unmodified firmware, this is the result of the Linksys upgrade application thinking that the NSLU2 has run out of memory (it hasn't really - it's just being temporarily used for buffers and caching, and is still available for any programs that need it, but the Linksys upgrade application is not smart enough to know that). Turning off the NSLU2, removing ALL drives, rebooting without any disks connected and then going straight into the Admin webpage for the firmware upgrade should get rid of the error.

to:

When I try to upgrade the firmware on my NSLU2 it reports "No Space Left on Device", "Not enough Memory", or "upgrade: no enough free space" (sic).

If you are running with unmodified firmware, this is the result of the Linksys upgrade application thinking that the NSLU2 has run out of memory (it hasn't really - it's just being temporarily used for buffers and caching, and is still available for any programs that need it, but the Linksys upgrade application is not smart enough to know that). Turning off the NSLU2, removing ALL drives, rebooting without any disks connected and then going straight into the Admin webpage for the firmware upgrade should get rid of the error.


Deleted lines 10-12:

I found something similar - when I tried to upgrade my V2.3R24 slug to Unslung, I got an dialog saying "upgrade: no enough free space" (sic). However, the Linksys help page linked to above recommends using EraseAll to install the R63 firmware... which is not only apparently dangerous (as per the page on this Wiki about EraseAll) but was, at least for me, unnecessary - I was able to install the R63 firmware from the R24 web admin pages without problems, and then installing Unslung on top of that worked as per the README.

Added lines 13-16:

I found something similar - when I tried to upgrade my V2.3R24 slug to Unslung, I got an dialog saying "upgrade: no enough free space" (sic). However, the Linksys help page linked to above recommends using EraseAll to install the R63 firmware... which is not only apparently dangerous (as per the page on this Wiki about EraseAll) but was, at least for me, unnecessary - I was able to install the R63 firmware from the R24 web admin pages without problems, and then installing Unslung on top of that worked as per the README.


January 28, 2007, at 09:45 PM by RichF --
Changed line 15 from:

While trying to upgrade from 2.3R24 to NSLU2 (di-nslu2.bin) I got the error "Upgrade: no enough free space." I was however able to upgrade to 2.3R63 successfully (without resetting the NSLU2), and with 2.3R63 installed, I could then upgrade to NSLU2.

to:

While trying to upgrade from 2.3R24 to Debian/NSLU2 (di-nslu2.bin) I got the error "Upgrade: no enough free space." I was however able to upgrade to 2.3R63 successfully (without resetting the NSLU2), and with 2.3R63 installed, I could then upgrade to Debian/NSLU2.

January 28, 2007, at 09:41 PM by RichF --
Changed lines 11-15 from:

I found something similar - when I tried to upgrade my V2.3R24 slug to Unslung, I got an dialog saying "upgrade: no enough free space" (sic). However, the Linksys help page linked to above recommends using EraseAll to install the R63 firmware... which is not only apparently dangerous (as per the page on this Wiki about EraseAll) but was, at least for me, unnecessary - I was able to install the R63 firmware from the R24 web admin pages without problems, and then installing Unslung on top of that worked as per the README.

to:

I found something similar - when I tried to upgrade my V2.3R24 slug to Unslung, I got an dialog saying "upgrade: no enough free space" (sic). However, the Linksys help page linked to above recommends using EraseAll to install the R63 firmware... which is not only apparently dangerous (as per the page on this Wiki about EraseAll) but was, at least for me, unnecessary - I was able to install the R63 firmware from the R24 web admin pages without problems, and then installing Unslung on top of that worked as per the README.


While trying to upgrade from 2.3R24 to NSLU2 (di-nslu2.bin) I got the error "Upgrade: no enough free space." I was however able to upgrade to 2.3R63 successfully (without resetting the NSLU2), and with 2.3R63 installed, I could then upgrade to NSLU2.

November 12, 2006, at 02:21 AM by gilesthomas -- Getting there, sorry about the endless edits...
Changed line 11 from:

I found something similar - when I tried to upgrade my V2.3R24 slug to Unslung, I got an dialog saying "upgrade: no enough free space" (sic). However, the Linksys help page linked to above recommends using EraseAll to install the R63 firmware... which is not only apparently dangerous (as per the page on this Wiki about EraseAll) but was, at least for me, unnecessary - I was able to instally the R63 firmware from the R24 web admin pages without problems, and then installing Unslung on top of that worked as per the README.

to:

I found something similar - when I tried to upgrade my V2.3R24 slug to Unslung, I got an dialog saying "upgrade: no enough free space" (sic). However, the Linksys help page linked to above recommends using EraseAll to install the R63 firmware... which is not only apparently dangerous (as per the page on this Wiki about EraseAll) but was, at least for me, unnecessary - I was able to install the R63 firmware from the R24 web admin pages without problems, and then installing Unslung on top of that worked as per the README.

November 12, 2006, at 02:20 AM by gilesthomas --
Changed line 11 from:

I found something similar - when I tried to upgrade my V2.3R24 slug to Unslung, I got an dialog saying "upgrade: no enough free space" (sic). However, the Linksys help page linked to above recommends using EraseAll? to install the R63 firmware... which is not only apparently dangerous (as per the page on this Wiki about EraseAll?) but was, at least for me, unnecessary - I was able to instally the R63 firmware from the R24 web admin pages without problems, and then installing Unslung on top of that worked as per the README.

to:

I found something similar - when I tried to upgrade my V2.3R24 slug to Unslung, I got an dialog saying "upgrade: no enough free space" (sic). However, the Linksys help page linked to above recommends using EraseAll to install the R63 firmware... which is not only apparently dangerous (as per the page on this Wiki about EraseAll) but was, at least for me, unnecessary - I was able to instally the R63 firmware from the R24 web admin pages without problems, and then installing Unslung on top of that worked as per the README.

November 12, 2006, at 02:20 AM by gilesthomas --
Changed line 11 from:

I found something similar - when I tried to upgrade my V2.3R24 slug to Unslung, I got an dialog saying "upgrade: no enough free space" (sic). However, the Linksys help page linked to above recommends using EraseAll? to install the R63 firmware... which is not only apparently dangerous (as per the page on this Wiki about EraseAll?) but was, at least for me, unnecessary - I was able to instally the R63 firmware from the R24 web admin pages without problems, and then installing Unslung on top of that worked as per the README.

to:

I found something similar - when I tried to upgrade my V2.3R24 slug to Unslung, I got an dialog saying "upgrade: no enough free space" (sic). However, the Linksys help page linked to above recommends using EraseAll? to install the R63 firmware... which is not only apparently dangerous (as per the page on this Wiki about EraseAll?) but was, at least for me, unnecessary - I was able to instally the R63 firmware from the R24 web admin pages without problems, and then installing Unslung on top of that worked as per the README.

November 12, 2006, at 02:16 AM by gilesthomas --
Changed line 11 from:

I found something similar - when I tried to upgrade my V2.3R24 slug to Unslung, I got an dialog saying "upgrade: no enough free space" (sic). However, the Linksys help page linked to above recommends using EraseAll? to install the R63 firmware... which is not only apparently dangerous (as per the page on this Wiki about EraseAll?) but was, at least for me, unnecessary - I was able to instally the R63 firmware from the R24 web admin pages without problems, and then installing Unslung on top of that worked as per the README.

to:

I found something similar - when I tried to upgrade my V2.3R24 slug to Unslung, I got an dialog saying "upgrade: no enough free space" (sic). However, the Linksys help page linked to above recommends using EraseAll? to install the R63 firmware... which is not only apparently dangerous (as per the page on this Wiki about EraseAll?) but was, at least for me, unnecessary - I was able to instally the R63 firmware from the R24 web admin pages without problems, and then installing Unslung on top of that worked as per the README.

November 12, 2006, at 02:15 AM by gilesthomas --
Changed line 11 from:

I found something similar - when I tried to upgrade my V2.3R24 slug to Unslung, I got an dialog saying "upgrade: no enough free space" (sic). However, the Linksys help page linked to above recommends using [eraseall|EraseAll?] to install the R63 firmware... which is not only apparently dangerous (as per the page on this Wiki about [eraseall|EraseAll?]) but was, at least for me, unnecessary - I was able to instally the R63 firmware from the R24 web admin pages without problems, and then installing Unslung on top of that worked as per the README.

to:

I found something similar - when I tried to upgrade my V2.3R24 slug to Unslung, I got an dialog saying "upgrade: no enough free space" (sic). However, the Linksys help page linked to above recommends using EraseAll? to install the R63 firmware... which is not only apparently dangerous (as per the page on this Wiki about EraseAll?) but was, at least for me, unnecessary - I was able to instally the R63 firmware from the R24 web admin pages without problems, and then installing Unslung on top of that worked as per the README.

November 12, 2006, at 02:15 AM by gilesthomas --
Changed line 11 from:

I found something similar - when I tried to upgrade my V2.3R24 slug to Unslung, I got an dialog saying "upgrade: no enough free space" (sic). However, the Linksys help page linked to above recommends using [eraseall|EraseAll?] to install the R63 firmware... which is not only apparently dangerous (as per the page on this Wiki about [eraseall|EraseAll?]) but was, at least for me, unnecessary - I was able to instally the R63 firmware from the R24 web admin pages without problems, and then installing Unslung on top of that worked as per the README.

to:

I found something similar - when I tried to upgrade my V2.3R24 slug to Unslung, I got an dialog saying "upgrade: no enough free space" (sic). However, the Linksys help page linked to above recommends using [eraseall|EraseAll?] to install the R63 firmware... which is not only apparently dangerous (as per the page on this Wiki about [eraseall|EraseAll?]) but was, at least for me, unnecessary - I was able to instally the R63 firmware from the R24 web admin pages without problems, and then installing Unslung on top of that worked as per the README.

November 12, 2006, at 02:15 AM by gilesthomas --
Added lines 10-11:

I found something similar - when I tried to upgrade my V2.3R24 slug to Unslung, I got an dialog saying "upgrade: no enough free space" (sic). However, the Linksys help page linked to above recommends using [eraseall|EraseAll?] to install the R63 firmware... which is not only apparently dangerous (as per the page on this Wiki about [eraseall|EraseAll?]) but was, at least for me, unnecessary - I was able to instally the R63 firmware from the R24 web admin pages without problems, and then installing Unslung on top of that worked as per the README.

October 22, 2006, at 12:24 AM by bdm --
Changed lines 9-11 from:

If all of the above still does not work, it may be due to a SLUG using an older Linksys FW. My 2nd SLUG had the .24 version and faced this issue even after a factory reset and going straight to the download page. Linksys has a help page that will walk you through upgrading to the .63 FW. Once I did this, upgrading to the Unslung FW was per the FAQs?.

...Brian

to:

If all of the above still does not work, it may be due to a SLUG using an older Linksys FW. My 2nd SLUG had the .24 version and faced this issue even after a factory reset and going straight to the download page. Linksys has a help page that will walk you through upgrading to the .63 FW. Once I did this, upgrading to the Unslung FW was per the install guide.

October 22, 2006, at 12:22 AM by bdm --
Added lines 6-11:

If all of the above still does not work, it may be due to a SLUG using an older Linksys FW. My 2nd SLUG had the .24 version and faced this issue even after a factory reset and going straight to the download page. Linksys has a help page that will walk you through upgrading to the .63 FW. Once I did this, upgrading to the Unslung FW was per the FAQs?.

...Brian

August 22, 2005, at 03:14 PM by tman --
Changed lines 1-2 from:

4. When I try to upgrade the firmware on my NSLU2 it reports "No Space Left on Device" or "Not enough Memory".

to:

When I try to upgrade the firmware on my NSLU2 it reports "No Space Left on Device" or "Not enough Memory".

August 22, 2005, at 03:13 PM by tman --
Added lines 1-5:

4. When I try to upgrade the firmware on my NSLU2 it reports "No Space Left on Device" or "Not enough Memory".

If you are running with a USB flash or hard disk with unmodified firmware, this is the result of the Linksys upgrade application thinking that the NSLU2 has run out of memory (it hasn't really - it's just being temporarily used for buffers and caching, and is still available for any programs that need it, but the Linksys upgrade application is not smart enough to know that). Turning off the NSLU2, removing ALL drives, rebooting without any disks connected and then going straight into the Admin webpage for the firmware upgrade should get rid of the error.

Received the "Not enough Memory" message while updating a brand new untouched NSLU2 with the latest Linksys firmware (NSLU2_V23R63.bin) from the Linksys support site. NSLU2 had no disks attached at the time. Followed the above advice and flash completed OK.

view · edit · print · history · Last edited by macnet.
Based on work by RjS, jamesN, Trurl, kilgore, RichF, gilesthomas, bdm, and tman.
Originally by tman.
Page last modified on February 09, 2008, at 12:33 AM