twonkyserver not operational anymore

thn

Hi,

I have a 12 TB USB drive connected to the rear USB-1 connector of my NAS326 and defined it as under the share name "extern". It is well visible in the configuration, with a green (healthy) indicator, and I can well browse it on the NAS' file browser and also from my LAN devices. Internally (telnet) it's recognized as /dev/sdb1 and also mounted under /e-data/

/home $ dmesg | grep sdb
sd 2:0:0:0: [sdb] Spinning up disk...
sd 2:0:0:0: [sdb] Very big device. Trying to use READ CAPACITY(16).
sd 2:0:0:0: [sdb] 23437770751 512-byte logical blocks: (12.0 TB/10.9 TiB)
sd 2:0:0:0: [sdb] Write Protect is off
sd 2:0:0:0: [sdb] Mode Sense: 4f 00 00 00
sd 2:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sd 2:0:0:0: [sdb] Very big device. Trying to use READ CAPACITY(16).
sdb: sdb1
sd 2:0:0:0: [sdb] Very big device. Trying to use READ CAPACITY(16).
sd 2:0:0:0: [sdb] Attached SCSI disk
tntfs info (device sdb1, pid 3412): ntfs_fill_super(): fail_safe is enabled
tntfs info (device sdb1, pid 3412): load_system_files(): NTFS volume version 3.1 (cluster_size 4096, PAGE_CACHE_SIZE 4096).
/home $ mount | grep sdb
/dev/sdb1 on /e-data/08f0ff8ac5f69d5c694656065eb4c548 type tntfs (rw,iostreaming,fmask=000,dmask=000,umask=000,uid=99,nls=utf8)
/home $

It's the only folder/drive that I have also given to twonkyserver to share (which is well activated and configured in the NAS).

BUT, since some days, without any change, twonkyserver has completely stopped working. I get no answer from http://nas326:9001/ anymore and I cannot see the media server from my LAN devices. I have made several hard and soft reboots to no avail. I have no error messages in dmesg.

How can I completely reset twonky to it's defaults and/or further isolate the problem?

Thanks.

thn

Well, by further playing around, I "kind of" solved it…

I installed the Logitech Media Server from the App center to see if I could get that one up and running instead. Well, it kind of worked but does not seem to support only audio, not video. I could connect to it under the IP address and port previously assigned to Twonky (http://nas326:9001/) and at the same time the port of Twonky miraculously switched to 9000 and was again reachable and configured with an empty configuration. So I could again define my external drive as to be shared and twonky started to index it as expected.

I stopped and uninstalled Logitech again and have now my Twonky back as before, but under the new port 9000 instead of 9001.

Although its not that important, but how can I give back port 9001 to Twonky???

THN

thn

PS:

When I do

/ $ ps | grep twonky
5532 root      1832 S    /usr/local/dmsf/binary/twonkystarter -appdata /i-data/.media/twonkymedia
5533 root     21056 S    /usr/local/dmsf/binary/twonkyserver -appdata /i-data/.media/twonkymedia

it seems that twonky is running well but I still get nothing from http://nas326:9001/

thn

Well, by further playing around, I "kind of" solved it…

I installed the Logitech Media Server from the App center to see if I could get that one up and running instead. Well, it kind of worked but does not seem to support only audio, not video. I could connect to it under the IP address and port previously assigned to Twonky (http://nas326:9001/) and at the same time the port of Twonky miraculously switched to 9000 and was again reachable and configured with an empty configuration. So I could again define my external drive as to be shared and twonky started to index it as expected.

I stopped and uninstalled Logitech again and have now my Twonky back as before, but under the new port 9000 instead of 9001.

Although its not that important, but how can I give back port 9001 to Twonky???

THN