I originally had both drives working using a spare 1.0 hub I had lying around, but it was dog slow. So I bought a 2.0 hub. This worked for the first couple of gigs it copied across from another disk, but then reported errors. It appeared the device just decided to unmount and remount in a different place.

I went and bought another hub today, from a different shop. Same problems. I think they are actually the same hub in different packaging, but another 2.0 hub I have lying about fails worse - the drives don’t even mount to begin with.

So I went for plan D. It seems that the USB controller chip used can drive up to 5 USB ports, so I cut a USB extension cable, and wired it onto the board in the correct locations. Didn’t work. Disconnecting made it work again.

Finally, I was able to get it to work by not using the power connections on the other port, but the +5V and GND locations elsewhere on the board. This was the only way I was able to get the NSLU2 to still boot with the extra port connected.

I may have been able to use unpowered ports. That might be cooler. I just thought that the PSU might not be +5V, in which case stuff could go badly wrong. Better check…

First of all, use dmesg to ensure the disk has been recognised and mounted. I had to change from my USB2.0 hub to a USB1.0 hub. I’ll get a new 2.0 hub in the next few days to try that out. Apparently some of them don’t work.

From dmesg, the hub has been recognised:

usb 2-1.1: new full speed USB device using ohci_hcd and address 3
usb 2-1.1: not running at top speed; connect to a high speed hub

The new disk has been mounted as an NTFS (dirty) disk:

NTFS volume version 3.1.
NTFS-fs error (device sdc1): load_system_files(): $LogFile is not clean. Mounting read-only. Mount in Windows.

Things to note: the device name in this case is /dev/sdc1. This is the third USB device in my chain. /dev/sda(1,2,3) are the root, swap and user partitions on the boot disk, /dev/sdb1 is the first 250GB drive I bought.

nslu2:~ root$ umount /media/sdc1/

nslu2:~ root$ fdisk /dev/sdc1/

Then you will need to delete the partition (d), and create a new one (n). (p): Primary partition, #1, accept default start and end blocks. Then use (w) to write the partition out to disk.

nslu2:~ root$ reboot

Wait for the machine to reboot fully.

nslu2:~ root$ umount /media/sdc1/
nslu2:~ root$ mkfs.ext3 /dev/sdc1
mke2fs 1.38 (30-Jun-2005)
...

It takes a while to process. Worthwhile rebooting after this just to be sure. All done.

However, the power failure must have caused some sort of a problem with my NSLU2 server. For some reason, I was no longer able to connect to it in any way shape or form. Samba connections failed, and even SSH-ing in didn’t work, with any of the users I had set up.

I finally figured out that it had something to do with not being able to boot off the disk properly. It was booting up, then beeping loudly three times (two different tones). Then, it was responding to pings, and accepting ssh connections, but not authenticating.

So I connected using the root account and the default password, and it worked. And, true to form, the disks were recognised, but for some reason not mounted.

I tried the turnup disk /dev/sda1 command, which doesn’t do anything destructive, but tells the machine to boot up from that device. It failed, with the following error:

turnup: /dev/sda1: partition does not seem to be a valid root partition
The partition must contain a full operating system. To ensure that
this is the case it is checked for the following, all of which must
exist for the bootstrap to work:

1) A directory /mnt.
2) A command line interpreter program in /bin/sh.
3) The program chroot in /sbin or /usr/sbin.
4) The program init in /sbin, /etc or /bin.

One or more of these items is missing. Mount /dev/sda1 on /mnt
and examine its contents. You can use turnup disk|nfs -i -f
to copy this operating system onto the disk, but it may overwrite
files on the disk.

Okay, that might help. A quick mount /dev/sda1 /mnt/sda1 showed that the partition was valid. But no /mnt directory inside there. Create one, then run the turnup disk /dev/sda1 command again. Then shutdown -r now.

Upon reboot, only a single beep (which, IIRC, I put there!), and everything is normal. Phew!

See, when you access a directory, or copy files using the Finder, and you are copying to a non-HFS disk, it creates a file ._Filename.ext that stores meta-data, the new version of the Resource Fork, for all of you old-school Mac heads.

So, I thought, if I use:

veto files = /._*/.DS_Store/

then I won’t have any problems with these files littering up the directory structure.

But, this won’t work. It doesn’t allow for the creation of these files, which causes the Finder to choke:

Removing the veto (I moved it into hide files, which should prevent other clients from seeing them) fixed the problem.

For search engines, the text of the dialog box is:

You cannot copy some of these items to the destination because their names are too long or contain invalid characters for the destination. Do you want to skip copying these items and continue copying the other items?

It took me quite a while to figure out why this was happening…

Then I came across Slugging, which shows how to deal with this exact problem: remove the busybox and busybox-links stanzas from the file /usr/lib/ipkg/status.

Thanks, z0mbi3. Even though I hate l33tsp33k.

Took me a while to figure out this was why my script to auto-start a new torrent was being “Terminated.”

Not sure how it works out which processes to kill, or if there’s a way to reduce memory use.

Then I came across a HOWTO: Add Additional Swap Space. Should fix stuff a bit.

Just a note: it takes ages for the file to be created, apparently.

Kissing A Fool • George Michael • Ladies & Gentlemen : The Best Of George Michael ★★

Edit: using ps x o %mem 0 command, I can see that each enhanced-ctorrent process grabs about 5 meg, while the 10 or so kaid processes each use up 2.1Mb. Since I haven’t started using kaid yet, maybe I should stop it auto-starting…

*/5 * * * * root /path/to/script/autoTorrent.py

I could make a resident version, that uses a time.sleep() to call the main function every 5 minutes. Then this could be added to the /opt/etc/init-d/ directory.

#! /usr/bin/env python

import os, time

# Any .torrent file placed in $base/source will be downloaded.
# When it's complete, it will be moved from $base/work to $base/target

base_dir = "/home/user/torrent"
source_dir = os.path.join(base_dir,"source")
target_dir = os.path.join(base_dir,"target")
work_dir = os.path.join(base_dir,"work")

torrent_cmd = "enhanced-ctorrent"
torrent_args = "-S localhost:2780 >/dev/null &"

def getTorrents(path):
    os.chdir(path)
    data = os.popen("ls -1 *.torrent").read()
    torrents = data.split("\n")[:-1]
    for i in range(len(torrents)):
        torrents[i] = os.path.join(path, torrents[i])
    return torrents

def getNewTorrents(path, oldTorrents):
    allTorrents = getTorrents(path)
    newTorrents = []
    for each in allTorrents:
        if each not in oldTorrents:
            newTorrents.append(each)
    return newTorrents

def startTorrent(torrent):
    os.chdir(work_dir)
    cmd = " ".join((torrent_cmd, os.path.join(source_dir,torrent), torrent_args))
    os.system(cmd)
    #print cmd

def getRunningTorrents():
    # do'h, ps on nslu2 is broken.  Had to install procps.
    cmd = "ps axwwo command | grep enhanced"
    data = os.popen(cmd).readlines()
    runningTorrents = []
    for each in data:
        if each.split()[0] == "enhanced-ctorrent":
           runningTorrents.append(each.split()[1])
    return runningTorrents

def startIdleTorrents():
    torrents = getNewTorrents(source_dir, getRunningTorrents())

    # since we get some CPU usage issues on starting several torrents at the same time,
    # just start the first torrent in the list.  Then we can rely on the idea we'll
    # be called by a cron-job or something to start the next.

    startTorrent(torrents[0])

if __name__ == "__main__":
   startIdleTorrents()

This is what should happen.

• Monitor a certain directory. If a .torrent file is added to this directory, add it to the queue.
• When a torrent is complete, move the file(s) to a completed directory. Send an email, or something. Perhaps add an item to an RSS feed. Remove the .torrent from the download queue, but keep it seeded.
• When neither of the other computers is turned on, download the next .torrent in the queue.
• If the download total of the running torrents is less than 80% of the available, start the next .torrent in the queue.
• If more than one .torrent is running and bandwidth use is greater than 90%, then stop the lowest in the queue that is running.
• Have a nice web interface that allows for changing the queue order.

There is a torrent ipkg for nslu2, which I’ve downloaded, but I may write my own. It’s show day tomorrow, so that might be a good start.

Annoying…

Yay!