DSM-G600, DNS-3xx and NSA-220 Hack Forum

That log result was also described and resolved here. Doesn't know if that also solves the freezing.

Forgot to mention, I have B1 revision of DNS320 wit 1.03b FW.

Hello, jucca.

Personally, I'd install Debian Squeeze (get it from here) and go with Deluge (get it from here). I've never tested Transmission, but I'm extremely happy with Deluge. It has web interface, magnet links support, individual upload/download speed limit and many more.

To get deluge up and running, you'll need deluge-common, deluged and deluge-web. After installing Debian Squeeze, login (as root, of course) and run the following commands:

apt-get update
apt-get dist-upgrade
apt-get upgrade
wget http://main.mepis-deb.org/mepiscr/testrepo/pool/test/d/deluge/deluge-common_1.3.6-0mcr110+1_all.deb
wget http://main.mepis-deb.org/mepiscr/testrepo/pool/test/d/deluge/deluged_1.3.6-0mcr110+1_all.deb
wget http://main.mepis-deb.org/mepiscr/testrepo/pool/test/d/deluge/deluge-web_1.3.6-0mcr110+1_all.deb
dpkg -i deluge-common_1.3.6-0mcr110+1_all.deb deluged_1.3.6-0mcr110+1_all.deb deluge-web_1.3.6-0mcr110+1_all.deb
apt-get -f install

Ignore dpkg's errors; the last line is there to fix them dependencies Don't be afraid to install all the suggested packages; they're all needed.

You'd also like to install nano to edit files (if it's not already installed: apt-get install nano)

To enable the daemon:

nano /etc/default/deluged

Change ENABLE_DELUGED from 0 to 1 and save the file (Ctrl+o and Enter, Ctrl+x).

To run Deluge:

/usr/bin/deluged
/usr/bin/deluge-web --fork #Don't forget "--fork"; otherwise, the web interface will not daemonize itself

If you want to run Deluge at startup, add the two lines at the bottom of your /boot/linuxrc (using nano, of course: nano /boot/linuxrc).

To login on the web interface, access http://<your_NAS_IP>:8112/ via your web browser (I recommend Google Chrome or FireFox - IE 10 fails miserably). The default password is deluge. Connect to the daemon, access "Preferences" and set the torrent client as your heart desires.

Personally, I've created a "Torrents" folder on "Volume_1" and pointed "Download to:" to it (/mnt/HD/HD_a2/Torrents).

Don't forget to alter the "Queue" values to fit your needs. Tweaking your bandwidth (FAQ, guide) is also a very good idea.

In order to move the downloaded files, you have to run a chmod -R 777 /mnt/HD/HD_a2/Torrents first (replace /mnt/HD/HD_a2/Torrents with the location you've chosen to store your torrents).

Hope it helps

Last edited by baltzatu (2013-10-27 09:57:39)

Uff, luckily, I managed to return it to factory settings. I phisicaly removed first disk (Volume_1), then after rebooting my NAS, I've hot-pluged it in, then managed to remove fun_plug.
Will try again, but maybe it is not compatible with B revision of my DNS-320.
What revision do you have?

As I said in post earlier, I had to remove HDD as with fun_plug loaded I could not access my NAS anymore, no metter in which way, even WEB managment didn't worked. i have that script from earlier and after hot-plug HDD1 in, I've put that script.
Thanks, will try now.

You're welcome. Glad I could help

The config files are in /root/.config/deluge/. But the installation is not volatile; as long as Squeeze is there and fun_plug points to it, it will start automatically.

If you want Deluge to start automatically, add the following lines at the bottom of your /boot/linuxrc file (using nano /boot/linuxrc):

/usr/bin/deluged
/usr/bin/deluge-web --fork

Last edited by baltzatu (2013-09-14 15:07:41)

You're welcome, man. Glad I could help

Hello, cdpereira.

First of all, check if Debian's fun_plug is present in the root of your "Volume_1" share. If it's not or it isn't the right one, then this is the reason your Debian doesn't start. If you need to check and/or restore it, here's the content:

#!/bin/sh

# Root DISK1
export DISK1=/mnt/HD/HD_a2
export DISTDIR=squeeze

cd $DISK1

mount --bind $DISK1 $DISTDIR$DISK1
mount --bind / $DISTDIR/mnt/root
mount --bind /dev $DISTDIR/dev
mount --bind /sys  $DISTDIR/sys
#mount --bind /sys/crfs $DISTDIR/sys/crfs
#mount --bind /web $DISTDIR/web
mount --bind /proc $DISTDIR/proc

cp -f /proc/mounts $DISTDIR/etc/mtab
rm -f $DISTDIR/etc/fstab
touch $DISTDIR/etc/fstab
cp -f /etc/resolv.conf $DISTDIR/etc
hostname >$DISTDIR/etc/hostname
cp -f /etc/hosts $DISTDIR/etc

$DISK1/$DISTDIR/boot/chroot $DISK1/$DISTDIR /boot/linuxrc

Restore it if necessary, reboot your NAS via its web administration interface and check if you can access it via SSH and that everything works.

If SSH still fails to connect, investigate the possible network connections issues. Does your NAS have a static IP address? DHCP may play tricks every now and then.

So... if fun_plug is OK and you can access your NAS via its web administration interface, but not via SSH, go to "Management" -> "Network Management" and check if everything is OK. Change the IP address to static if necessary, reboot the NAS (just in case) and try to connect again via SSH (PuTTY) using the newly assigned IP address.

If SSH still fails to connect (telnet wasn't supposed to, anyway, unless you use Fonz fun_plug), then probably your Debian is broken somehow

In this case, here's what I'd do (actually did a couple of times, since I've managed to broke Debian):

0. Download the Debian archive (it seems that D-Link's FTP sites where it was available don't exist anymore so use this link) and unpack it on your computer - don't use your NAS' "Volume_1" share just yet.
-------------------------------------------------------------------------------------
1. Use Fonz fun_plug to access your device. The instructions are here, but you don't have to go all the way; you just need a mean to access your NAS via telnet:
1.1 Put this file and this file in the root of your "Volume_1" share;
1.2 Reboot your NAS;
1.3 Wait a little (the archive has to be unpacked) and use telnet to log on.
-------------------------------------------------------------------------------------
2. If telnet is working, then you can start working on restoring Deluge:
2.1 Rename your old Debian folder:

mv /mnt/HD/HD_a2/squeeze /mnt/HD/HD_a2/squeeze_OLD

2.2 Follow the instructions found inside the archive you've downloaded and unpacked in step 0 in order to get a fresh Squeeze install;
2.3 Exit telnet and restart your NAS via the web administration interface;
2.4 Access your NAS via SSH.

If SSH works, then install Deluge, configure the daemon, start the service, then stop it:

service deluged start
service deluged stop

Restore your settings by copying them from your previous Squeeze installation:

mv /root/.config/deluge /root/.config/deluge_NEW
cp -rf /mnt/HD/HD_a2/squeeze_OLD/root/.config/ /root/

Now start the deluged service again with service deluged start, the web interface with deluge-web --fork and enjoy

If everything works fine, you can delete the old Squeeze by running the rm -rf /mnt/HD/HD_a2/squeeze_OLD command. Please keep in mind that the operation is irreversible and the files will be lost forever (sort of, since recovering them will take an eternity).

Good luck!

Last edited by baltzatu (2014-02-15 08:52:55)

Hello.

You should've asked here before formatting... even when you're surrounded by Windows computers, there are ways to fix issues/recover data from Linux partitions. You can use one of the million flavors of Live Linux CDs, or something more Windows-y, like Ext2 Volume Manager, which works flawlessly on my Win 7 Pro x64 PC.

You might want to check BitTorrent Sync (BitTorrent based - how-to).

You're welcome

Last edited by baltzatu (2014-02-24 22:33:21)

Well... it could've been avoided, but what's done is done. Let's just hope it won't be a second time.

You're welcome

Last edited by baltzatu (2014-02-25 09:56:21)