Hi Mike,

That is what i tried (doing it manually) and it didnt work.

However after searching a little, am i supposed to be editing the mount.sh with
my slugos usb pen inserted, or the mount.sh file without my usb pen inserted?

You say that automount will be removed, does this mean theres another way of
achieving what i require?

I dont really see how it can be a useful tool without the automounting of
drives, as i wouldnt want to log in and mount stuff everytime i turn it on. I
know the idea is to leave it on all the time but thats not possible at the
moment.

--- In nslu2-general@yahoogroups.com, Mike Westerhof <mwester@...> wrote:
>
> chris_jaz wrote:
> > Hi, Sorry,
> > This is the wiki link
> > http://www.nslu2-linux.org/wiki/HowTo/AutoMountNTFSDrives
> >
> > And the errors i got, the first one was bad.src which i believe means bad
source file (although the dates etc matched the ones at top of the patch), and
the second time was a error at line 15. But i wasnt sure if that was line 15 of
the patch or line 15 of mounts.sh
> >
> > Im quite new to linux, so i dont even know if i was trying to apply the
patch in the correct way, so even if someone could give me a breakdown of how to
apply the patch, i could go back... try it and report back again.
>
> Normally you would cut and paste to create a patch file from the text in
> the wiki article, then use the patch command to apply it... but in this
> case, I'd just use a text editor to apply the patch manually.  I'm not
> in a position to test anything right now, so I can't tell you exactly
> what/how to do this.
>
> Also, I'm not exactly sure what SlugOS release this is for - hopefully
> it will work for the latest one.  Make sure that the context (around the
> "+" and "-" lines in the patch) match up correctly.
>
> -Mike (mwester)
>
> PS: I should note that the automount feature will be removed in the next
> SlugOS release entirely.  It causes more problems than it solves...
>

chris_jaz wrote:
> Hi Mike,
>
> That is what i tried (doing it manually) and it didnt work.
>
> However after searching a little, am i supposed to be editing the mount.sh
with my slugos usb pen inserted, or the mount.sh file without my usb pen
inserted?
>
I presume by "usb pen" you mean the usb flash device to which you did
the "turnup" operation?  If so, then yes - you must edit the mount.sh
file on that device.

But the distinction shouldn't matter to you, if you just boot normally
-- whatever "normal" means given your configuration -- and edit the
/etc/udev/script/mount.sh file, you'll be editing the correct file.
> You say that automount will be removed, does this mean theres another way of
achieving what i require?
>
Yes.  Normally, you would edit the /etc/fstab file so that each time the
device boots, it will automatically mount the identified device (which
you would identify by UUID or label, not by /dev/sdNN) into the correct
place, with the correct mount options.  If you are adding the device
after-the-fact, then put the line into the fstab with the "noauto"
keyword, so that it does not attempt to mount it at boot time.  Then
simply log in and type the correct commands when you plug the disk/flash
in ("mount /mydisk1" or "mount /mymusicdisk", or whatever), and of
course before you pull it out again ("umount /mydisk1", or whatever).

The existing automount mechanism is planned to be removed, because of
many minor problems.  Each problem is, in itself, solvable -- but like
fixing ancient plumbing, each time a leak is fixed, a new leak pops up
somewhere else.  The most serious issues are that the existing mechanism
can cause devices to be mounted multiple times, with conflicting options
- bad news.  The existing mechanism relies on /dev/sdNN identification
-- which is worse than useless, since the device ID assigned can vary,
resulting in the potential for disaster and data loss (consider plugging
in two disks -- one containing your financial records, the other a
scratch device you use for temporary space... do you feel comfortable
knowing that at any given time, either one of the two could be called
/media/sda1?).  Other issues include knowing how to map user ids for
NTFS partitions; this might be different for different disk drives or
flash devices.

Yet another problem is that the existing solution is only half a
solution -- it does nothing at all to help with the process of safe
device removal.

Solutions to all of this do exist; desktop Linux distros have solved
this to a great extent.  But it does not seem to be something solvable
with udev, which is how the current script works.  If anyone knows of a
good embedded package that handles automounting of storage devices --
something with a small footprint, no assumption of a console nor an
X-windows user session, let me know. :)

> I dont really see how it can be a useful tool without the automounting of
drives, as i wouldnt want to log in and mount stuff everytime i turn it on. I
know the idea is to leave it on all the time but thats not possible at the
moment.
It sounds to me that all you really need is to add the correct lines to
the /etc/fstab, and you're all set.

-Mike (mwester)

Hello all and a happy new year!

I've been happily using (again) rtorrent on my Maxtor MSS II for the last 3-4
months, instead of enhanced-ctorrent. The reason I avoided rtorrent was the fact
that it did not have an option to preallocate files. This feature was added to
rtorrent and on September 2009 an apk with this new functionality was available
in optware, leading to much less fragmented files. Worked like a charm on
rtorrent/libtorrent 0.8.5/0.12.5. At that time I confirmed that preallocation
worked, but did not do much downloads.

I started some heavy downloading right after rtorrent/libtorrent was upgraded in
optware to versions 0.8.6/0.12.6. Ever since, I've been downloaded torrents with
ludicrously fast speeds (~630 kbytes, at the limit of my 6Mbps line), unseen
previously. Guess I was not a heavy user and/or did not encounter up to that
point torrents with good seed/leech ratios. Problem is that after reaching these
top speeds, rtorrent has managed to consistently crash again and again. In some
cases it managed to turn my MSS II off!

Some questions to all:

1) Is there some way one can locate .apk files older than the currently
available ones? I'd certainly would like to see whether the previous
rtorrent/libtorrent (ie 0.8.5/0.12.5) which was available during October, also
crashes under heavy load.

2) Has anyone experienced these problems with the latest rtorrent versions?

Thank you in advance for any information provided!

I am looking for some feedback/advice - I put this NSLU2 in place of an
energy hog windows tower since it's primary purpose was for samba
sharing.     So the new NSLU2 works ok, I get pretty decent throughput, but
I find for some reason I am no longer able to reliably stream video (1-2gb
divx files).   Usually the video will start and play for a while - could be
5 minutes, could be 30 minutes, then it gets jumpy, or stops/hangs.  I never
had this problem with the tower.

The NSLU2 has the resistor removed so it is running at 266, and I am running
debian on it.   The drive with the video has noatime set, and is ext2.   The
only extra I installed is ftp.    I think I have it pretty well optimized,
so it seems like it should be more reliable.

Any thoughts or advice?

Thanks!


[Non-text portions of this message have been removed]

As I recall, when hard wired to a switch that the client was also on, my NSLU2
could transfer data at about 50 mbit/sec when it was clocked at 266 mhz, while
also running several other services. That is plenty fast to stream video. Is
your client wireless, or wired?

1-2 GB divx doesn't really tell us much.  If it is 1-2 GB and 15 minutes worth
of video it is fairly high def, and your NSLU2 probably can not handle it.   If
it 1-2 GB and a couple of hours worth of video, I would think that would be
fine.  I have my NSLU2 over clocked as well.  I then stream the files over wifi.
If I see stuttering or such I usually blame the wifi connection.  But I have
found about 1200 kbps (+384 kbps for audio) seems to be the magical rate.  If I
encode my videos at a higher bit rate, I am more likely to notice skips and
such.  Although I have successfully played high definition videos at 2400 kbps,
I just can't do it consistently.

The other consideration is the client.   The normal windows samba drivers are
not well optimized.  They add significant overhead.  They also seem a bit flaky.
It is not uncommon to see my samba transfer rates under Windows Vista to drop by
a factor 10.  e.g. I'll copy a file to my external drive that should take about
10 minutes and it will decide that day it will take 100 minutes.

I do much better using NFS or streaming HTTP.

However, some devices such as Network Media Tanks have very well optimized
drivers.  Movies play the same on my NMT regardless if I use NFS, Samba, or
HTTP.  So I typically stream my movies to my media player using HTTP (apache),
because it allows me to directly access the files from a web menu.

Bill

--- In nslu2-general@yahoogroups.com, SSzretter <sszretter@...> wrote:
>
> I am looking for some feedback/advice - I put this NSLU2 in place of an
> energy hog windows tower since it's primary purpose was for samba
> sharing.     So the new NSLU2 works ok, I get pretty decent throughput, but
> I find for some reason I am no longer able to reliably stream video (1-2gb
> divx files).   Usually the video will start and play for a while - could be
> 5 minutes, could be 30 minutes, then it gets jumpy, or stops/hangs.  I never
> had this problem with the tower.
>
> The NSLU2 has the resistor removed so it is running at 266, and I am running
> debian on it.   The drive with the video has noatime set, and is ext2.   The
> only extra I installed is ftp.    I think I have it pretty well optimized,
> so it seems like it should be more reliable.
>
> Any thoughts or advice?
>
> Thanks!
>
>
> [Non-text portions of this message have been removed]
>

I did some testing with dd reading and writing to the drive, I saw numbers of
7.1 and 10.9MB/s , so that seems pretty good?

Copying one of the video files across to a windows machine (2 hour movie -
1gig), ifconfig shows no dropped packets or other errors.

I am streaming to an xbox running xbmc.  It has worked great for a long time
when streaming from a windows tower - same cables / switches.

I did get somewhat decent performance by shutting down extra stuff - I had
apache and rtorrent running.  Without those, it at least stays playing the whole
1-2 hours, but I still had some jitters which I did not before...

Maybe I should run a different distro?   I am running the latest debian, is
there something else that is better in peoples experience?



--- In nslu2-general@yahoogroups.com, "colinnwn" <colin@...> wrote:
>
> As I recall, when hard wired to a switch that the client was also on, my NSLU2
could transfer data at about 50 mbit/sec when it was clocked at 266 mhz, while
also running several other services. That is plenty fast to stream video. Is
your client wireless, or wired?
>

My network is all wired,100base.  My tests were running at 2.5 to 4 MB I
believe.   But it is as if something else is happening at some point to
interrupt it while streaming...


[Non-text portions of this message have been removed]

As an xbox user I *highly* recommend installing the latest ccxstream
package on your slug and attaching your xbmc sources through xbmsp.

I've been streaming all sorts of media for years with xbmc (running on
xbox + pc) without any problems - even though I'm still using an old
133MHz slug running a transmission daemon and other stuff at the same
time.

See http://www.nslu2-linux.org/wiki/Optware/Ccxstream?from=Unslung.Ccxstream

Good luck!


> I did some testing with dd reading and writing to the drive, I saw numbers
> of 7.1 and 10.9MB/s , so that seems pretty good?
>
> Copying one of the video files across to a windows machine (2 hour movie -
> 1gig), ifconfig shows no dropped packets or other errors.
>
> I am streaming to an xbox running xbmc.  It has worked great for a long
> time when streaming from a windows tower - same cables / switches.
>
> I did get somewhat decent performance by shutting down extra stuff - I had
> apache and rtorrent running.  Without those, it at least stays playing the
> whole 1-2 hours, but I still had some jitters which I did not before...
>
> Maybe I should run a different distro?   I am running the latest debian,
> is there something else that is better in peoples experience?
>
>
>
> --- In nslu2-general@yahoogroups.com, "colinnwn" <colin@...> wrote:
>>
>> As I recall, when hard wired to a switch that the client was also on, my
>> NSLU2 could transfer data at about 50 mbit/sec when it was clocked at
>> 266 mhz, while also running several other services. That is plenty fast
>> to stream video. Is your client wireless, or wired?
>>
>
>
>

I'm trying to setup a simple website, using the NSLU2.

So far, I've setup the device, and can open it with my browser locally, using
"http://stein_server/FLASH_1_1_1/website/index.html". Works fine.

Next, I set the firewall on my router (2Wire, model 2701 HG-S) to open TCP Port
80 to the NAT address of the NAS. The tool
(https://www.dyndns.com/support/tools/openport.html) confirms that it is open.

Then, I set up an address here at DynDNS.com, "samanthazone.gotdns.com", and
have installed the DynDNS Updater utility (without Internet Guide, as I am using
OpenDNS on the router).

However, when I try to access "http://www.samanthazone.gotdns.com/", I get a
"Not Loading" error.

Same for
"http://www.samanthazone.gotdns.com//stein_server/FLASH_1_1_1/website/index.html\
".

What am I doing wrong?


--Johnathan

Check to see if your ISP is blocking ports, if 80 is blocked try setting things
up to use 81 or 8080.

Are you trying to access it from within your same LAN as the slug is located on?
Sometimes that can be an issue but you can see it from a browser outside your
LAN.

The good news is if you can see it locally the slug is set up correctly.

--- In nslu2-general@yahoogroups.com, "JohnathanStein" <JohnathanStein@...>
wrote:
>
> I'm trying to setup a simple website, using the NSLU2.
>
> So far, I've setup the device, and can open it with my browser locally, using
"http://stein_server/FLASH_1_1_1/website/index.html". Works fine.
>
> Next, I set the firewall on my router (2Wire, model 2701 HG-S) to open TCP
Port 80 to the NAT address of the NAS. The tool
(https://www.dyndns.com/support/tools/openport.html) confirms that it is open.
>
> Then, I set up an address here at DynDNS.com, "samanthazone.gotdns.com", and
have installed the DynDNS Updater utility (without Internet Guide, as I am using
OpenDNS on the router).
>
> However, when I try to access "http://www.samanthazone.gotdns.com/", I get a
"Not Loading" error.
>
> Same for
"http://www.samanthazone.gotdns.com//stein_server/FLASH_1_1_1/website/index.html\
".
>
> What am I doing wrong?
>
>
> --Johnathan
>

Interesting product from the CES; it could be a SLUG on steroids:

http://ces.cnet.com/8301-31045_1-10424491-269.html?tag=mncol;txt
<http://ces.cnet.com/8301-31045_1-10424491-269.html?tag=mncol;txt>





[Non-text portions of this message have been removed]

Definitely sounds interesting.   Although, I would like to know about what it is
running inside, and how easy it would be to flash something different.  For
example, my media is currently all index by web pages to be served by apache.  
While having a UPnP server sounds interesting, the one's I have tried in the
past could not deliver the same rich content without out considerable effort on
my part.   So naturally my #1 requirement is to be able to run either apache or
something equivalent.  The other service I really depend on my NSLU2's for is
dnsmasq.  But if necessary I could always run that on one of my wireless
routers.

More importantly, I would not want something that would lock me into proprietary
firmware.  Most vendors go out of business or end of life consumer products way
too soon.

Bill


--- In nslu2-general@yahoogroups.com, "James Todd" <jtg-0812@...> wrote:
>
> Interesting product from the CES; it could be a SLUG on steroids:
>
> http://ces.cnet.com/8301-31045_1-10424491-269.html?tag=mncol;txt
> <http://ces.cnet.com/8301-31045_1-10424491-269.html?tag=mncol;txt>
>
>
>
>
>
> [Non-text portions of this message have been removed]
>

Hi,

I have problem to setup the hardware clock on my SlugOS/BE 5.3 (2.6.27.28)
When I run hwclock I get
hwclock: can't open '/dev/misc/rtc': No such file or directory

It look's like device doesn't exist because in dmesg I have
dmesg | grep rtc
drivers/rtc/hctosys.c: unable to open rtc device (rtc0)

and as well trc(rtc0) is not in /dev/ folder

I tried
mknod /dev/rtc c 254 0
which doesn't work as well.

Funny is, when I run the same SlugOS (remove system USB key) on my second
NSLU2 everything works perfectly.

Any ideas?
Thanks

--
View this message in context:
http://old.nabble.com/hwclock%3A-can%27t-open-%27-dev-misc-rtc%27-tp27074528p270\
74528.html
Sent from the Nslu2 - General mailing list archive at Nabble.com.

enso wrote:
> Hi,
>
> I have problem to setup the hardware clock on my SlugOS/BE 5.3 (2.6.27.28)
> When I run hwclock I get
> hwclock: can't open '/dev/misc/rtc': No such file or directory
>
> It look's like device doesn't exist because in dmesg I have
> dmesg | grep rtc
> drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
>
> and as well trc(rtc0) is not in /dev/ folder
>
> I tried
> mknod /dev/rtc c 254 0
> which doesn't work as well.
>
> Funny is, when I run the same SlugOS (remove system USB key) on my second
> NSLU2 everything works perfectly.
>
> Any ideas?
>

There are many cases reported where the RTC for the NSLU2 fails for some
reason or another (see the mailing list archives).  IIRC, you will have
to open up the device, and remove and/or replace the battery on the
circuit board to make the RTC work again.

-Mike (mwester)

Hi all,

Well im struggling along and learning alot with this, and ive now found that
really i need to have my slug running from a hard drive rather than a usb pen.

Id rather not start again and copy back all my config, so is there a command so
that i can move my slugos from usb pen to the usb hard drive?

Thanks.

There are many cases reported where the RTC for the NSLU2 fails for some
reason or another (see the mailing list archives).  IIRC, you will have
to open up the device, and remove and/or replace the battery on the
circuit board to make the RTC work again.

-Mike (mwester)

Hi Mike,
Thanks for reply...
Honestly, I tried to reset the RTC by removing the battery (for 2 hours)
(even before I wrote to the forum) but it doesn't help.
Now, I tried to measure the voltage (Vbat) directly on chip and thatway I
pulled the residential voltage (of some capacitors) down and when I connect
the battery back, it works perfectly.
BTW: The real clock chip is ISL12026IBZ...

Thanks ;)


--
View this message in context:
http://old.nabble.com/hwclock%3A-can%27t-open-%27-dev-misc-rtc%27-tp27074528p271\
17206.html
Sent from the Nslu2 - General mailing list archive at Nabble.com.

chris_jaz wrote:
> Hi all,
>
> Well im struggling along and learning alot with this, and ive now found that
really i need to have my slug running from a hard drive rather than a usb pen.
>
> Id rather not start again and copy back all my config, so is there a command
so that i can move my slugos from usb pen to the usb hard drive?

I didn't see an answer pass by -- did you get an answer to this, or find
the answer in the mailing list archives?  (I know this question was
answered in the past, possibly in the nslu2-linux archives)

-Mike (mwester)

I'm interested in monitoring an unslung nslu2 using Munin server. Someone have
compiled or know how to use Munin to monitor the nslu2 unslung.

thx

Hi,

I have an issue that enabling USB2 causes a hang after some (usually quite
short) period of external HDD activity.

I've tried the latest Debian and OpenWRT releases and both behave the same.

I've tried two different NSLU2s that both measure good PSU's.
I've tried multiple HDD's some of which appear in the tested device list.
I've tried different filesystems (EXT2,3 and FAT32) and connectivity options
(Samba and NTFS).
I've tried setting the USB parameter max_transfer from low values to high values
with no effect.
I've tried adding a USB2 hub but this made no difference.

The system boots and all the devices I have tried have all been recognised; if I
format on the NSLU2 the format will hang part way through.

If I transfer files, part way through the NSLU2 will hang, sometimes I can still
access the root and see smbd is hung in IO wait state (-D), sometimes the NSLU2
will hang completely.
Disabling the ehci_hcd module will give me a stable system at USB1.1 speeds.

I tried Unslung too but had quite a few issues with format and compatability
that I gave up and moved to Debian.

Is there an issue with the latest kernel and USB2 support on the NSLU2?

Any ideas?

Thanks

I'm sorry I don't buy it.

I regularly get 3.0+MB/s (quoting rsync's --progress) between slugs with two
hard-drives each. All four of my slugs are de-underclocked, and all of their
hard drives are externally powered. I started with Maxtors but lately use
internal harddrives upended in BlacX.

I did have compression enabled once, because I am silly, and the speed dropped
into the KB-ish range. (Compressing compressed files only expands time...)

Cheers!
--
CZ

--- In nslu2-general@yahoogroups.com, "Mike (mwester)" <mwester@...> wrote:
>
> docbillnet wrote:
> > Hello,
> >
> > I just purchased a couple of NSLU2 from tigerdirect.ca, and I have
> > followed the instructions for installing Linux on one.   Overall, it
> > seems to be working well, especially since I cut the resistor.
> > However, I wanted to backup data from three 500 GB drives to a 1.5 TB
> > drive.   However, when I used the --progress option with rsync, it
> > reported the transfer speed is 2.0 MB/s.   After a quick back of the
> > envelope calculation, I concluded it will take 8 days to copy my data
> > from the three drives.
> >
> > So, I shutdown the NSLU2, and plugged the same drives and USB hub into
> > my laptop.   I issued the same rsync command, and my transfer rate is
> > 20 MB/s.
> >
> > Is this a typical transfer speed with an NSLU2?  If not, how do I go
> > about determining the problem and speeding up the transfer?  From what
> > I've seen in this forum, I would expect a transfer speed between
> > drives of about 6 MB/s, but I can't be certain since the messages were
> > all related to how long it took to transfer files between a usb drive
> > and the network.   Perhaps, the USB bus is much slower when it is both
> > reading and writing at the same time.   Or perhaps rsync has too much
> > overhead, and I need to use a different program to copy data.
> >
> > Bill
>
> What firmware did you install?
> How are the drives mounted (can you provide the output from the mount
> command)?
> What exactly is the rsync command you issued?
>
> Mike (mwester)
>

*BUMP*

Can someone please provide some for the following (at least)? I want to download
rtorrent and libtorrent but not the currently available in optware versions;
rather some older ones (the previous versions to be precise).

Any hints/info someone?


> 1) Is there some way one can locate .apk files older than the currently
available ones? I'd certainly would like to see whether the previous
rtorrent/libtorrent (ie 0.8.5/0.12.5) which was available during October, also
crashes under heavy load.

Hi there, i've been using rtorrent on the nslu for about 2 years now and have
noticed that it can manage only 5 to 6 torrents before getting a segmentation
fault error and crashing. It also has this problem if one of the files is large,
say 20gb plus. Bandwidth is good for download but uploads have to be capped to
80-90% of available. Otherwise the little slugger just falls over, it is only
using a usb connected laptop hard drive after all.

I also looked for an older compiled version but couldn't (the latest version has
zero'd all the console rates so its hard to know what its doing) but i will keep
an eye out.
yours
Kaputnik


--- In nslu2-general@yahoogroups.com, reqman@... wrote:
>
>
> *BUMP*
>
> Can someone please provide some for the following (at least)? I want to
download rtorrent and libtorrent but not the currently available in optware
versions; rather some older ones (the previous versions to be precise).
>
> Any hints/info someone?
>
>
> > 1) Is there some way one can locate .apk files older than the currently
available ones? I'd certainly would like to see whether the previous
rtorrent/libtorrent (ie 0.8.5/0.12.5) which was available during October, also
crashes under heavy load.
>

I have connected a second 500GB Seagate USB Drive to my disk2 port. After
sometime I start getting Access denied when I try logging on to my slug....Until
I remove this disk2 & reboot it wont let me in...
the disk2 is ext 3 format....

I've never managed to keep torrents running for long on my NSLU2.   I've always
attributed to having insufficient memory or such.   Generally when I want to run
a torrent on my NSLU2 I wrap the process in a script that keeps looping after
each crash.

However, in general I usually avoid doing torrents on my NSLU2 because I haven't
figured out a good way to automate bandwidth limitations and to keep track of
sharing ratios across crashes.  So when I run torrents on my NSLU2 I end-up
being a leach big time.  As soon as I have a complete download that is the end
of the sharing process.   When I run the torrent from an interactive desktop,
provided what I downloaded is worthwhile, I can continue sharing until my upload
to download ratio is well above 1.

Bill


--- In nslu2-general@yahoogroups.com, reqman@... wrote:
>
>
> Hello all and a happy new year!
>
> I've been happily using (again) rtorrent on my Maxtor MSS II for the last 3-4
months, instead of enhanced-ctorrent. The reason I avoided rtorrent was the fact
that it did not have an option to preallocate files. This feature was added to
rtorrent and on September 2009 an apk with this new functionality was available
in optware, leading to much less fragmented files. Worked like a charm on
rtorrent/libtorrent 0.8.5/0.12.5. At that time I confirmed that preallocation
worked, but did not do much downloads.
>
> I started some heavy downloading right after rtorrent/libtorrent was upgraded
in optware to versions 0.8.6/0.12.6. Ever since, I've been downloaded torrents
with ludicrously fast speeds (~630 kbytes, at the limit of my 6Mbps line),
unseen previously. Guess I was not a heavy user and/or did not encounter up to
that point torrents with good seed/leech ratios. Problem is that after reaching
these top speeds, rtorrent has managed to consistently crash again and again. In
some cases it managed to turn my MSS II off!
>
> Some questions to all:
>
> 1) Is there some way one can locate .apk files older than the currently
available ones? I'd certainly would like to see whether the previous
rtorrent/libtorrent (ie 0.8.5/0.12.5) which was available during October, also
crashes under heavy load.
>
> 2) Has anyone experienced these problems with the latest rtorrent versions?
>
> Thank you in advance for any information provided!
>

vi_sharan wrote:
> I have connected a second 500GB Seagate USB Drive to my disk2 port. After
sometime I start getting Access denied when I try logging on to my slug....Until
I remove this disk2 & reboot it wont let me in...
> the disk2 is ext 3 format....
>
I'm going to take a guess here that you are running Unslung.  Perhaps
you have run into the issue described in the section on the wiki about
which port to use?  (You'll have to search; I don't have the page handy).

If that's not it, then you'll have to provide additional information.
Where do you see this message?  Are you logging in via telnet, ssh, or
web server?  What firmware?  What, precisely, do you mean by "the dis2
is ext 3 format" -- did you format it on the slug using the Unslung web
gui, or was it formatted on another Linux system?

-Mike (mwester)

Hi everyone,
Im not very linux savy but love my slug. My current setup is running the latest
Unslung firmware with a 750GB WD my book connected to Disk 1, for packages I use
Ushare and take advantage of the FTP capabilities by remotely connecting, and
run a crappy lil website. My question is can the slug perform disk-disk backups
(raid?) on 1TB or larger drives? (so 1TB drive on disk 1 and 1TB drive on disk
2) I recently bought a PS3 and have fallen prey to the world of HD content, and
movie files between 5-10GBs each will probably fill my 750GB HDD soon (plus all
the other crap on there), and the raid is just because Ive heard of horrible
external HDD stories where they just die. Ive done some research buts its been
difficult finding an answer.

Hi there,
I bought recently NSLU2. What I am trying now is to set it up to my nslu2.
I found how to do it with another Huawei E622, but as hardware is different I
tryed to find specificlly for this one.

What I found is in one blog post is the following:
I got a ZTE MF632 device working under Ubuntu Hardy with KPPP.

Create a new file /etc/udev/rules.d/57-zte-net.rules and put the following in it
ACTION!="add", GOTO="ZTE_End"

# Is this the ZeroCD device?
SUBSYSTEM=="usb", SYSFS{idProduct}=="2000",
SYSFS{idVendor}=="19d2", GOTO="ZTE_ZeroCD"

# Is this the actual modem?
SUBSYSTEM=="usb", SYSFS{idProduct}=="0001",
SYSFS{idVendor}=="19d2", GOTO="ZTE_Modem"

LABEL="ZTE_ZeroCD"
# This is the ZeroCD part of the card, remove
# the usb_storage kernel module so
# it does not get treated like a storage device
RUN+="/sbin/rmmod usb_storage"

LABEL="ZTE_Modem"
# This is the Modem part of the card, let's
# load usbserial with the correct vendor
# and product ID's so we get our usb serial devices
RUN+="/sbin/modprobe usbserial vendor=0x19d2 product=0x0001",
# Make users belonging to the dialout group
# able to use the usb serial devices.
MODE="660", GROUP="dialout"

LABEL="ZTE_End"
Plug your device in the USB port. This should create three new devices
/dev/ttyUSB0, /dev/ttyUSB1 and /dev/ttyUSB2. You now can use the first one to
connect to the network.
Use your favourite PPP program to configure new connection.  Don't forget to set
the following parameters:
Modem initialization string 2 = AT+CGDCONT=1,"IP","globul"
Phone = *99***1#
Username = globul
Password = globul


Can you help me if this will work?
Thanks in advance

I am logging via openssh. Checked the var/log/messages couldn't find anything
related to openssh

--- In nslu2-general@yahoogroups.com, Mike Westerhof <mwester@...> wrote:
>
> vi_sharan wrote:
> > I have connected a second 500GB Seagate USB Drive to my disk2 port. After
sometime I start getting Access denied when I try logging on to my slug....Until
I remove this disk2 & reboot it wont let me in...
> > the disk2 is ext 3 format....
> >
> I'm going to take a guess here that you are running Unslung.  Perhaps
> you have run into the issue described in the section on the wiki about
> which port to use?  (You'll have to search; I don't have the page handy).
>
> If that's not it, then you'll have to provide additional information.
> Where do you see this message?  Are you logging in via telnet, ssh, or
> web server?  What firmware?  What, precisely, do you mean by "the dis2
> is ext 3 format" -- did you format it on the slug using the Unslung web
> gui, or was it formatted on another Linux system?
>
> -Mike (mwester)
>

vi_sharan wrote:
> I am logging via openssh. Checked the var/log/messages couldn't find anything
related to openssh
>
> --- In nslu2-general@yahoogroups.com, Mike Westerhof <mwester@...> wrote:
>
>> vi_sharan wrote:
>>
>>> I have connected a second 500GB Seagate USB Drive to my disk2 port. After
sometime I start getting Access denied when I try logging on to my slug....Until
I remove this disk2 & reboot it wont let me in...
>>> the disk2 is ext 3 format....
>>>
>>>
>> I'm going to take a guess here that you are running Unslung.  Perhaps
>> you have run into the issue described in the section on the wiki about
>> which port to use?  (You'll have to search; I don't have the page handy).
>>
>> If that's not it, then you'll have to provide additional information.
>> Where do you see this message?  Are you logging in via telnet, ssh, or
>> web server?  What firmware?  What, precisely, do you mean by "the dis2
>> is ext 3 format" -- did you format it on the slug using the Unslung web
>> gui, or was it formatted on another Linux system?
>>
>> -Mike (mwester)
>>
>>

I'm still betting that you are running into the issue described in the
wiki -- you can't add a second disk device to an already-unslung system
unless you planned for it from the beginning.  I think the wiki outlines
the issue, and may provide some work-arounds.  In a nutshell, when you
add a second natively-formatted hard drive to the Linksys firmware, most
configurations will end up with the new disk's config partition
replacing the existing config partition, which causes all sorts of havoc.

-Mike (mwester)