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

thanks for the post. I am having the solid pink LED problem after upgrading from Twonky 4.4.9 to 5.0.46. After the LEDs go pink, I can't access the drive anymore - it gets unmapped.

So i have to turn off and turn on the 323 again.

There is about a 3 minute window where I can remap the drive and access the contents. I opened starttwonky.sh with a text editor, edited it, tried to save but it said it was read-only.

can you walk me through how to save it?

I can telnet in.. can I access the files somehow? I'm poking around but don't see starttwonky.sh.

thanks!

Last edited by lament (2009-01-24 19:13:18)

I'll try to do my best to help... Let's see...

My starttwonky.sh script:

#!/bin/sh
route add -net 224.0.0.0 netmask 240.0.0.0 dev egiga0

# Let's get rid of the full rootfs problem
ln -s /mnt/HD_a2/.TwonkyMediaServer /home/root

cd /mnt/HD_a2/twonky
/mnt/HD_a2/twonky/twonkymedia &

Of course, don't forget to do a "mkdir /mnt/HD_a2/.TwonkyMediaServer"

Also remember that the Twonky media server might not be the only program filling up the root filesystem, watch the disk usage:

# df
Filesystem           1k-blocks      Used Available Use% Mounted on
rootfs                    9911      7317      2082  78% /
/dev/root                 9911      7317      2082  78% /
/dev/loop0                5632      5632         0 100% /sys/crfs
[...]

(mmm... not sure if having /sys/crfs at 100% is a good thing, but that would be another subject)

And also watch which directories might be filled up:

# cd /
# du -ks bin dev sbin tmp var default etc home lib root usr web
413     bin
6       dev
4       sbin
166     tmp
25      var
32      default
281     etc
4       home
562     lib
1       root
102     usr
75      web

(tmp, var, home and root specially)

I'm only running twonky, so I'm safe right now (steady blue leds even after several hours).

Hope this helps you, if you need anything else, just let me know.

devotee,

thanks for the info. I did not do mkdir /mnt/HD_a2/.TwonkyMediaServer so that's maybe why it didn't work.

i went back to Twonky 4.4.9 and I'm not having a problem anymore (with the exception of video times not showing up properly on the PS3), but I still want to try out your fix.

Also, with Twonky 5.0.46 installed, I'm not able to telnet in like I could with 4.4.9. Why would that be? I still have the FrodoII modified firmware 1.05 with telnet.

Last edited by lament (2009-01-26 21:40:10)

ok here's the df command..

Filesystem           1k-blocks      Used Available Use% Mounted on
/dev/ram0                 9911      7746      1653  82% /
/dev/md0             958846504  91875744 866970760  10% /mnt/HD_a2
/dev/sda4               497861        65    497796   0% /mnt/HD_a4
/dev/sdb4               497861         8    497853   0% /mnt/HD_b4

i'm still getting the pink LEDs, and i can't execute the du command..

# du -ks bin dev sbin tmp var default etc home lib root usr web
/alt/sh: du: not found

@Papaloewe - my default ini shows:

contentbase=/mnt
contentdir=+A|/
friendlyname=Twonky DNS-232
httpport=9000
enableweb=2
scantime=60
maxmem=15000
startupmb=0
norescale=1
platform=DNS323

i'm not sure about all those directories you posted. am i supposed to create those? are those specific to your NAS? remember I'm a linux newb.. go easy on me.

Last edited by lament (2009-01-27 06:52:02)

Papaloewe wrote:

Hi lament,

You don't have to create these dirs manually. They are created from the twonky-process automaticaly.
In my post are the pathes of my installation. This is not the standard.
I think the standard-path of the twonky directory is: /mnt/HD_a2/twonky.
The lines have to be added at the end. Do not delete any one.

OK sorry.. I'm still not understanding what you edited here then:

cachedir=/mnt/HD_a2/usbstorage/twonky5/db/cache
dbdir=/mnt/HD_a2/usbstorage/twonky5/db
uploadmusicdir=/mnt/HD_a2/usbstorage/twonky5/twonkymedia-server-uploaded-music
uploadpicturedir=/mnt/HD_a2/usbstorage/twonky5/twonkymedia-server-uploaded-pictures
uploadvideodir=/mnt/HD_a2/usbstorage/twonky5/twonkymedia-server-uploaded-videos
onlinedir=/mnt/HD_a2/usbstorage/twonky5/twonkymedia-server-online-data
mediastatisticsdir=/mnt/HD_a2/usbstorage/twonky5/media-statistics/

what do I need to add to my .ini file?

OK great I will try that out tonight when I get home from work. Thanks!

is there a solution already or what???

tnx

Just to update this thread.  I tried both suggestions above on my DNS-323 with Twonky 5 and only the symbolic link suggestion fixed all my Twonky issues.  The fix to add the extra lines to the *.ini file only fixes the pink LED issue and the issue where the box loses its mind after 2 minutes or so.  It did not fix my problem where the box would lose its configuration settings (share path, license key, etc.) after a NAS reboot.

The symbolic link fix, which is very easy to add, did the trick.

Thanks devotee!!!

arunbav, it really doesn't matter, just be sure that the ".TwonkyMediaServer" folder exists and the path is correct in your script. If you don't mind having a ".TwonkyMediaServer" folder lying around in your main directory, you can keep it there. If you prefer to have things more organized, you might want to put ".TwonkyMediaServer" inside the twonky directory.

Sorry for my slow reply

Hi guys. Great posts here.

I've had the exact problem ever since installing Twonky 5.1.3 (also tried 5.1.2) with rootfs going to 100% and both HDD LEDs going pink/orange.  I tried editing the starttwonky.sh script via PuTTY/vi, but still no luck.  Perhaps there is a sequence.  Here's what I have been doing:

1.  Install Twonky Media Server, but uncheck the box for "start server".

2.  After install is complete, edit starttwonky.sh script so that my script looks like:

#!/bin/sh
route add -net 224.0.0.0 netmask 240.0.0.0 dev egiga0

ln -s /mnt/HD_a2/.TwonkyMediaServer /home/root

cd /mnt/HD_a2/twonky
/mnt/HD_a2/twonky/twonkymedia &

save file and quit vi.

(Note: .TwonkyMediaServer directory already exists.)

3. Run Twonky Media Server installation, but only select the "start server" option.

I add media to the library and rescan directories.  I use df to monitor the rootfs in PuTTY and watch the rootfs fill up.  I usually uninstall Twonky before it fills up.

Is there something I'm doing wrong?

archie1810 wrote:

Papaloewe wrote:

cachedir=/mnt/HD_a2/twonky/db/cache
dbdir=/mnt/HD_a2/twonky/db
uploadmusicdir=/mnt/HD_a2/twonky/twonkymedia-server-uploaded-music
uploadpicturedir=/mnt/HD_a2/twonky/twonkymedia-server-uploaded-pictures
uploadvideodir=/mnt/HD_a2/twonky/twonkymedia-server-uploaded-videos
onlinedir=/mnt/HD_a2/twonky/twonkymedia-server-online-data
mediastatisticsdir=/mnt/HD_a2/twonky/media-statistics/

Think this should work.

This one so far solved my problem on pink/purple light on DNS-323 Drive-Lights.
My DNS-323 is running on 1.07 Firmware Date: 03/27/2009 - No, I didnt upgrade to any hack-modified firmware.
I have Fun_Plug install just to get to the Telnet session.

Thanks a millions, guys... you've done a great job here

BR, Arc.

Ooppss... too fast replying.
Nope, it doesn't work for me... my drives' lights still pink/purple colored both.
I've entered both method the soft-link and the twonkymedia-server.ini modification.
Any suggestion please?
Thanks.

BR - Arc.

archie1810 wrote:

CubanDonkeyMeat wrote:

Hi guys. Great posts here.

I've had the exact problem ever since installing Twonky 5.1.3 (also tried 5.1.2) with rootfs going to 100% and both HDD LEDs going pink/orange.  I tried editing the starttwonky.sh script via PuTTY/vi, but still no luck.  Perhaps there is a sequence.  Here's what I have been doing:

1.  Install Twonky Media Server, but uncheck the box for "start server".

2.  After install is complete, edit starttwonky.sh script so that my script looks like:

#!/bin/sh
route add -net 224.0.0.0 netmask 240.0.0.0 dev egiga0

ln -s /mnt/HD_a2/.TwonkyMediaServer /home/root

cd /mnt/HD_a2/twonky
/mnt/HD_a2/twonky/twonkymedia &

save file and quit vi.

(Note: .TwonkyMediaServer directory already exists.)

3. Run Twonky Media Server installation, but only select the "start server" option.

I add media to the library and rescan directories.  I use df to monitor the rootfs in PuTTY and watch the rootfs fill up.  I usually uninstall Twonky before it fills up.

Is there something I'm doing wrong?

After you run point #3 above, are you sure that the starttwonky.sh is not "refreshed" by the 'reinstallation' ??
I've got the same problem, let's see whether we can have some hands here...

Have you specified appdata switch. The following starttwonky.sh  works for me

#!/bin/sh
route add -net 224.0.0.0 netmask 240.0.0.0 dev egiga0

ln -s /mnt/HD_a2/.TwonkyMediaServer /home/root

cd /mnt/HD_a2/twonky
/mnt/HD_a2/twonky/twonkymedia -appdata /mnt/HD_a2/twonkydata &