DNS-323 and TMS v5 series problems

[ttmcmurry]

I've been trying to figure out what the difference is between the v4 and the v5 TMS for NAS. When I use v4, everything is juuust fine. But v5 doesn't seem to do much of anything useful.

The only reason I want to go with v5 is because of v4's inherent problem with .m2ts length being improperly reported to UPnP clients... 999:99:99 just doesn't seem ... right. It prevents me from using fast forward on my PS3 and WMP 12 isn't fond of it either.

Plus, with firmware 1.08 for DNS-323 coming out soon, it looks like (from my personal use) 1.08 fixes everything that's been wrong or missing with the built-in UPnP and makes puchasing TMS a moot issue if v5 doesn't work.

Having said that-- what I'm seeing wrong with v5 is it isn't saving settings at all, locks up when clicking "restart server," even when manually editing twonkymedia-server.ini and specifying the settings I want, it still loads defaults. The log file in /tmp/TwonkyMediaServer-log.txt is useless. Nothing is saved there.. empty file. I'm installing v4 & v5 as root.

I've tried 4.4.11, 4.4.18, 5.0.65, 5.0.67, and 5.1.08. None of the v5 series works. My best guess is something isn't reading the root of the DNS-323 correctly -- like a typo -- e.g. the .ini files point to /mnt as the content directory, which isn't true, it should be /mnt/HD_a2 on most setups.

[newTwonkyuser]

just posted this on another thread, but re-posting here might be more appropriate....

i just installed TM 5.1 for my DLink DNS323 NAS. It worked but noticed a few things:
1) after playing a a couple videos (about 1.5hrs later), the drive lights on the NAS went pink and my computers were not able to access the NAS drives anymore. my media player (ps3) could continue to navigate the shared folders
i think the lights looking "pink" is a result of blinking really quickyl between blue (normal) and yellow (error).

2) after rebooting the nas, the twonky settings were wiped and had to be re-configured

the first problem is more serious and a potential dealbreaker here. anyone encounter the same issue?

[ju55i]

I've got the same problem. I think this surfaced with the 5.1.2 version. I think the problem is that Twonky writes to /var/twonkymedia directory and it fills the partition very quickly (because it is really small). This basicly breaks the whole system.

[ju55i]

I remedied the problem for now with following steps:
1. Telnet to DNS-323
2. Kill the twonkymedia processes (killall twonkymediaserver)
3. Delete the /var/twonkymedia directory (rm -fr /var/twonkymedia)
4. Create a symlink to twonky directory from /var/twonkymedia (ln -s /mnt/HD_a2/twonky /var/twonkymedia)
5. Restart the system

[newTwonkyuser]

hmmm, i will give that a try.
thnx

[mgillespie]

I've got the same problem. I think this surfaced with the 5.1.2 version. I think the problem is that Twonky writes to /var/twonkymedia directory and it fills the partition very quickly (because it is really small). This basicly breaks the whole system.

Read the documentation, for NAS/Embedded devices, you need to specifiy where the application should store it's data, using the appdata commandline switch.

It's pretty well documented.

[newTwonkyuser]

I was busy but finally have time to revisit this again...
I'm unable to locate documentation specific to NAS builds for either version 4.4.18 or 5.1.2
Can you point me in the right direction?

Thnx!

[5t3v0]

Hi
I'm having the same issue with TMS v5 on my DNS-323 and have read several different suggested solutions. Please could someone recommend the best permanent solution and link to a decent guide on how to implement it.
Thanks

Edit - Been reading about the disks not spinning down with v5 on the DNS-323 so have decided not to bother upgrading just now.