Right. trust me to open my big mouth. One of my boxes died over the weekend. Tracked it down to a faulty mirror drive, which was trying to rebuild on reboot, and locking up at 58% every time. Now this box has been giving me trouble for a while, losing network connectivity, so it was an excuse for a quick trip to the shops for a new drive and a new nas box, and I eventally got it all working again.... ...Leaving me with a spare, possibly iffy, drive and box. Just right for playing with tinky on without upsetting the rest of the network again, before I call up the warranty... So. Some observations on migrating from MRT firmware to tinky-ls... since the drive I have available thinks it's part of a raid 1 mirror, it loads up as /dev/md1, and automatically mounted on /mnt/MD1. I note a lot of the changes in the scripts for twonky server &etc. are hard coded for /mnt/IDE1 ... I presme this is why lots of stuff in the webgui don't seem to work quite right.. It seems, from my other boxes, that 'mdadm' is the program to use to maintain the 'md' raid devices. But this is missing in tinky. I did get it over to this box by wget'ing it from my webspace, but it vanished again on a reboot. However all this linux raid stff is beyond me really; most of my history is with FreeBSD which does things in different ways... And with only one drive I don't need it ocnfigred as a mirror anyway. So.. How can I simply wipe the disc and get it back to default using just the tools on the nas box? (The data on it is scrambled, anyway, being only a partial rebuild of the original data..) cheers, Rob.