Re: NSLU2 Drops Connection to LARGE Disk
- Hmm perhaps the newer f/w does help - where did you get it...?
Also I note that you have the bigger disk on port 1 which was one thing I considered as an option as both disk ports do not appear to be created equal...
- I think I downloaded it from linksys' FTP site a few years ago. Their FTP site seems to no longer be available. Googling 'nslu2 2.3R76' will locate some download options.
The larger disk was connected to disk1 as I did not obtain the backup drive 'till a later time. My NSLU2 implementation was not planned per se, it just came together to solve a file sharing problem, which it has done well.
--- In firstname.lastname@example.org, "djmalne" <nabble.admin@...> wrote:
> Hmm perhaps the newer f/w does help - where did you get it...?
> Also I note that you have the bigger disk on port 1 which was one thing I considered as an option as both disk ports do not appear to be created equal...
- I have had connections drop with NTFS on my 80 GB USB Hard drive.
I made a topic but I kept getting emails saying "Post to mailing list still pending" and one that said "Unable to deliver your message"
- gamesharkmike wrote:
> I have had connections drop with NTFS on my 80 GB USB Hard drive.Send your emails directly to the nslu2-general email list, not via nabble.
> I made a topic but I kept getting emails saying "Post to mailing list still pending" and one that said "Unable to deliver your message"
- I copied 1 TB of files from one disk to another at the same NSLU2 (new
266MHz from factory).
My housings are both IcyBox "IB-351 StUS-B" (one purchased in mid 2008,
one in October 2009).
My disks are WD10EACS 1TB SATA (same purchase data).
OS is SlugOS/LE 5.3 with addition of the optware package, SMB and screen.
Screen is required to do such long lasting actions from ssh terminal -
otherwise one has to keep
the ssh terminal all time open and connected and the ssh guest computer
all times on.
The Slug didn't got hot.
Say 45°C instead of 38°C when idling (estimation related to my own body
So, if anybody gots problems like dnabble got, he may try my test.
If this test also fails, the Slug or the USB Disk Housings or the Power
Supply Units are scrap.
MySlug:~# sreen -r
MySlug:~# dd bs=2048k if=/dev/sdb3 of=/dev/sdc3
473862+1 records in
473862+1 records out
993761846784 bytes (994 GB) copied, 273498 seconds, 3.6 MB/s
273498 sec = 4558 min = 76 h = 3.2 days!
Okay, pretty slow. But it runs hell stable!
Without the 2MB buffer, it would be much slower ;-)
with best regards,
> There is 1 message in this issue.
> Topics in this digest:
> 1a. Re: NSLU2 Drops Connection to LARGE Disk
> From: dnabble
> 1a. Re: NSLU2 Drops Connection to LARGE Disk
> Posted by: "dnabble" david.nelson.wi@... cnczane
> Date: Wed Oct 28, 2009 4:45 am ((PDT))
> I bought a "new" (but alas discontinued) NSLU2, a pair of 1.5T internal eSATA
> drives, and a pair of "almost" matching BlackX HDD USB/eSATA "docking
> Not so prominently printed on the BlackX boxes, is the phrase: "SUPPORT UP
> TO 1TB (1,000GB) H.D.D."
> Nevertheless, I decided to try, and went ahead with formatting, figuring to
> see an error message, signaling failure.
> Formats appeared to succeed, as did unslinging (SlugOS/LE), as did rsyncing,
> for a time, and therein lies a tale.
> As the drive filled up, the rsync process would hang inexplicably, and hang
> the slug: all and any terminal sessions would become unresponsive and new
> ssh requests ignored.
> Reboots always solved the problem, and always the slug was good for whatever
> you wanted, which seems to suggest overheating was not the problem. In fact
> the hanging was always associated with an rsync copying more files inbound.
> I was worried at first that, for the first time (in 4 slugs), the
> over-clocking to 266 MHz had bit me, but (see overheating consideration
> above) the hanging should have been random and not so connected with rsync.
> The mystifier was that (1) rsync would hang during a large (1GB) file
> transfer, (2) reboot, (3) rsync might appear to complete that file transfer
> and hang during an ensuing one. The disk "fill" was at around 80% as I
> The problem also MIGHT have been related to my use of a 32MB "swapfile"
> instead of a larger, and real-er, swap "partition." (SlugOS/LE is smart
> enough managing memory to be able to get by with a smallish swapfile, in my
> understanding. [See "Install and Turnup SlugOS" at www.nslu2-linux.org]
> At any rate, my solution:
> Decide to live within the means of the BlackX docking stations and partition
> the drive with TWO sizable data partitions (91000 blocks) and a THIRD
> remainder swap partition (400 blocks).
> So far, I filled the first data partition to 82%, and have started the
> second. The acid test will come when that 2nd data partition hits around
> 80-90%, but the NSLU2 hasn't so much as burped. IF CPU or disk were
> overheating, or IF it was over-overclocked, there should've been a burp,
> because the rsync stress is identical to the first case.
- --- In email@example.com, Mike Westerhof <mwester@...> wrote:
>I didn't send an email, I used the new topic link.
> gamesharkmike wrote:
> > I have had connections drop with NTFS on my 80 GB USB Hard drive.
> > I made a topic but I kept getting emails saying "Post to mailing list still pending" and one that said "Unable to deliver your message"
> Send your emails directly to the nslu2-general email list, not via nabble.
> Mike (mwester)
So this is a newsgroup? So does that mean you can post by sending an email?