D-Link Forums
The Graveyard - Products No Longer Supported => DNS-323 => D-Link Storage => Beta code! => Topic started by: deca66 on August 09, 2009, 02:20:27 PM
-
Hello,
I have installed successfully twonky Media Server 5.0.65 on my DNS-323 with a Freebox router.
Then I have given the folders to scan. The indexing worked fine but several problems arose :
- On the PC, I have lost the network folders. When I try to connect them again, easy Search utility cannot map them again. I have to stop twonky and relaunch the DNS-323 to be able to remap again.
- Using the media manager of the web interface, I can browse within the folders, but I do not see any file inside.
Thanks for any help !
--
deca66
-
I think this board will be more suitable for such questions:
http://forum.dsmg600.info/viewforum.php?id=3
D-Link Forum doesn't offer support for fun_plug hacks and similar modifications.
-
Hi,
I did the same configuration, and had the same problem.
The admin page works fine, but the drive cannot be mounted by the DNS software once Twonky is started.
The red light are blinking for the HDD
I fixed it by desactivating the TwonkyMedia server, using the following preocedure :
- connect to the DNS using telnet
- edit the fun_plug file (using VI for ex.)
- find the line that "starts" the Twonkymedia server (/mnt/HD_a2/starttwonky.sh), and comment (placing a # sign at the beginning of the line.)
- restart the DNS using the http Admin interface
... then you can connect again to your drive (but twonky is deactivated...)
... hope this helps
-
Hi,
I did the same configuration, and had the same problem.
The admin page works fine, but the drive cannot be mounted by the DNS software once Twonky is started.
The red light are blinking for the HDD
...
I fixed it by desactivating the TwonkyMedia server, using the following preocedure :
...
... hope this helps
Hi darkhib,
I also did this desactivation but, unfortunately, this does not help me to run twonky ;-)
I try on the other forum suggested by Piotr.
-
Hi all,
Just tried version http://www.twonkyforum.com/unsupported/4.4.11/ and it works better.
I now can see my pictures via the freebox HD (french ADSL modem / UPnP client).
But I still cannot view videos nore listen to music.
Any ideas ?
Thanks
-
Don't run this version of Twonky :) It will screw up the NAS -- at least it did for me. See the forums over at twonkymedia
http://www.twonkyforum.com/viewtopic.php?f=16&t=6605#p24333
For now, version 4 is the only thing I can run reliably.
-
Don't run this version of Twonky :) It will screw up the NAS -- at least it did for me. See the forums over at twonkymedia
http://www.twonkyforum.com/viewtopic.php?f=16&t=6605#p24333
For now, version 4 is the only thing I can run reliably.
Which version screwed up your NAS ? You say that version 4 is reliable and I have installed 4.4.11.
Thanks
-
Which version screwed up your NAS ? You say that version 4 is reliable and I have installed 4.4.11.
Thanks
The 5.* versions - I can't get them to run on my DNS-323. The 4.* versions seem to work fine. When I say "screw up my NAS", it causes an issue where I can no longer access it as a network drive - similar to what was mentioned above.
Sorry that I missed you were running 4.* now :)
-
Good luck getting v5 of Twonky working. I think someone effed up something in the DNS-323 build for the v5 branch. Afterall, haven't you noticed they have typos all over the place? e.g. the default name is Twonky DNS-232...
I've tried 5.0.65, 5.0.67, and 5.1.08 and they all are broken. I get the same problem with every release.
It seems that somewhere in the compiled binary they have an invalid path. I keep seeing references to data directories like /mnt for the root of the twonkymedia folder. /mnt doesn't exist per se as a place where Twonky should explore, it should be /mnt/HD_a2 as the starting place - plus I don't get any logging out of the logfile.. it's like the filesystem access in Twonky is completely broken.
But they don't seem interested in fixing it. At least they updated the v4 branch to 4.4.18. But D-Link's 1.08 UPnP server honestly does a great job in and of itself-- there isn't a reason anymore to use Twonky once 1.08 goes live.
-
Good luck getting v5 of Twonky working. ...
But they don't seem interested in fixing it. At least they updated the v4 branch to 4.4.18. But D-Link's 1.08 UPnP server honestly does a great job in and of itself-- there isn't a reason anymore to use Twonky once 1.08 goes live.
Many thanks for all these infos. I was not aware of 1.08. What are the news in this version ?
-
TMS 5.0.65 has been working great for me without any issue.
To make it work you will need to do the followings:
(I have funplug installed and I don't know if it would work without funflug)
First create one directory and one file like these:
/mnt/HD_a2/twonky_work/twonkymedia (this is a directory)
/mnt/HD_a2/twonky_work/TwonkyMediaServer-log.txt (this is a file)
Then edit the TMS startup script "starttwonky.sh" and add the following two lines to create two symbolic links before "twonkymedia" is starting up:
ln -s /mnt/HD_a2/twonky_work/twonkymedia /var
ln -s /mnt/HD_a2/twonky_work/TwonkyMediaServer-log.txt /tmp
Unlike v4, v5 stores all database files and log file in /var and /tmp which are actually located in the flash memory of your DNS323.
Once the flash memory filled up while the database is being built, the box will stop responding.
Another problem is that you will loose your license file and settings every time the box is rebooted because /var will be reset during each reboot.
Doing the symbolic links will put everything back to your HD so that flash memory will not be touched at all.
-
Many thanks for all these infos. I was not aware of 1.08. What are the news in this version ?
Cannot find 1.08 for DNS-323. Where did you find it ?
http://www.dlink.fr/cs/Satellite?c=TechSupport_C&childpagename=DLinkEurope-FR%2FDLTechProduct&cid=1197319419291&p=1197318961474&packedargs=locale%3D1195806373344&pagename=DLinkEurope-FR%2FDLWrapper
-
Cannot find 1.08 for DNS-323. Where did you find it ?
http://www.dlink.fr/cs/Satellite?c=TechSupport_C&childpagename=DLinkEurope-FR%2FDLTechProduct&cid=1197319419291&p=1197318961474&packedargs=locale%3D1195806373344&pagename=DLinkEurope-FR%2FDLWrapper
1.08 is not currently available as a general release, it is only in Beta and is posted at the top of the forum as stickies. Until the firmware is official it is not distributed to our other branches worldwide (normally).
-
1.08 is not currently available as a general release, it is only in Beta and is posted at the top of the forum as stickies. Until the firmware is official it is not distributed to our other branches worldwide (normally).
OK, I understand...I have read the release note of this beta version : do you really have to backup all the content of the DNS-323 before installing the beta installation ?
-
Well that all depends on how much value you place on your data. If it is mission critical data you shouldn't run beta code anyways. You should always have a backup somewhere.
-
If it is mission critical data you shouldn't run beta code anyways. You should always have a backup somewhere.
Is it the same for official release ?
-
Is it the same for official release ?
Of course! Just because you may have a RAID-1 configured on your DNS-323, it doesn't mean you're completely protected.
For example: What if lightening struck your DNS-323? No RAID will protect you from that. Where is your backup? How will you get that data back? How about if a fire occurred? What if both drives failed simultaneously due to defect?
There are many many more reasons why RAID isn't a replacement for a backup. RAID-1 is only purposed to create resiliency in the case of a single drive failure. RAID also doesn't protect against accidental deletion by a user.
Realistically, however the odds of both drives failing simultaneously or being destroyed by natural disaster are amazingly low. But like anything in life, if you take a moment to prepare for the worst -- IF it ever happens, you'll at least have a place to pick up the pieces and start over without losing everything.
-
I've managed to stuff my NAS the same way.
Thanks for the post, it fixed my problem.
------------------------------------------------
Update
I'm really grateful someone found out about this, as I would have been well stuffed otherwise.
It is a shame that people who can write such decent software end up causing such grief.
Hi,
I did the same configuration, and had the same problem.
The admin page works fine, but the drive cannot be mounted by the DNS software once Twonky is started.
The red light are blinking for the HDD
I fixed it by desactivating the TwonkyMedia server, using the following preocedure :
- connect to the DNS using telnet
- edit the fun_plug file (using VI for ex.)
- find the line that "starts" the Twonkymedia server (/mnt/HD_a2/starttwonky.sh), and comment (placing a # sign at the beginning of the line.)
- restart the DNS using the http Admin interface
... then you can connect again to your drive (but twonky is deactivated...)
... hope this helps