Zeiva

Members
  • Posts

    7
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

Zeiva's Achievements

Noob

Noob (1/14)

0

Reputation

  1. Yes, its more related to how unRAID "installs" itself into ram rather than actually running from the USB. And yes if you don't stop the array you wont have this problem alexw. But when you DO stop the array (to change the array or power down the server etc) make sure no UPnP devices are active or using it. A graceful way of shutting down MediaTomb would be the ideal solution though. If there is a shutdown script somewhere that can be manipulated to include a shutdown of MediaTomb that would be one acceptable solution.
  2. It is as Biggy2872 says. It still annoys me that we've yet to find a solution to the de-sync of parity problem when stopping the array though. That is quite a serious issue acutally and when combined with the forced shutdown that has to follow it can cause some heavy dataloss.
  3. I've been trying to get proFTPd working for the last 2 days but I keep running into the same problem as Biggy2872 where I cant get any deeper than the first folder or download any files even from the very first folder. It just says "DOWNLOAD FAIL" in the syslog. Started out using the 1.2.10 version but have now moved on to the 1.3.2 version since it seems to work just as well on unRAID 4.4.2 (even if I still cant get any files or navigate any depper). A few observations are: I cant WRITE files without a problem but these then dissapear instantly from view and access. I can not see folders any depper than the first folder (aka ftp://ip/disk1 I can still see stuff but not in ftp://ip/disk1/folder1) I cant download any file, even in the disk1 folder (assume its the same problem preventing me from seeing any deeper) The login seems to work, the FTP client used does not matter (IE, FF, FileZilla etc) and the version of proFTPd also seems irrelevant. Currently only tried using the proftpd.conf file posted by xbit and a modifed 1.3.2 proftpd.conf file. I currently suspect the problem is with the server wanting to run as the user "nobody" and the group "nogroup". I can imagine this conflicing with the unRAID Basic licence which is what I'm using for my current setup. If there is a way to run the server as root with one of the built in groups I guess this hurdle could be dealt with. Hoping for a reply by some savy user.
  4. Double posting here but I've found another issue now that I've solved the first one and wanted to hear your toughts on it. If I stream from the MediaTomb server and want to Stop the array at the same time it wont stop, fair enough, but the problem is that it also gets out of sync with the parity and hence has to do a parity check. Also it wont Stop properly after failing the first time even if you turn off the streaming so you must do a hard-reboot or possibly shut it down from a terminal.
  5. Sounds good. I only added that line because I wasn't able to edit the go script without stopping the server once. Seems to work now so I guess that must have been some other issue or me being to fast to open it after a reboot of the server. Corrected this part now. I was under the impression that screen was not possible in stock unRAID but I'll give it a go. It would be preferable to keep this guide as simple as possible in the end so if there are other ways of just hiding the script and letting it run in the background that would be good as well. (Guess that's kind of what screen ultimately does) I really wanted to use WordPad but to me it seemed like it couldn't add stuff to the file, just view it. Notepad was the only program actually able to edit the file which is why I used it but I'll keep an eye on WordPad to see if I can get it running, much more user friendly handling of .xml files to begin with. (Using Vista if that carries any importance even though I doubt it). I'll do some editing and cleanup of this How-To until we got a solid way of doing it. On the fix list right now is Changing NotePad to WordPad Done Trying screen and the tips from NAS and Joe L. Done
  6. Sounds like a plan and I'll give it a go. Otherwise I just did some research of my own and adding "&" after the last line also seemed to let you reach the login without any apparent (other than scrambeling the text on the screen a bit first) problems and the UPnP media device can still access the server. I'll give your way a testrun as well because I like the point you brought up about giving the drives time to spin up.
  7. So first of all hi to the forums since this is my first post. Now that that's over with I'll get to the business of posting a little How To to get UPnP running on unRAID. I know quite a few people have UPnP media devices that want to play their content from unRAID and I happend to know one of them who needed help. I'm sure there are plenty of ways to get this working and that its been discussed before but I could honestly not find a good simple guide for it on these forums or linked from this great wiki entry: http://lime-technology.com/wiki/index.php?title=UnRAID_Topical_Index I'm aware of Twonky and the PS3mediaserver solutions but Twonky is not free and PS3mediaserver went over my head and also was not geared towards generic UPnP devices. I choose MediaTomb in the end and this is how I got it working. How-To Version 1.2 1: Download MediaTomb from http://mediatomb.cc/pages/download and get the Static Binaries for i368. Most current right now (8 April 2009) is "mediatomb-static-0.11.0-r2-linux-uclibc-i386.tar.gz" 2: Extract the .gz and the .tar file using 7-zip or whatever unpacking utility works for you until you get to the "mediatomb" folder. Copy this folder to the root of the unRAID flashdrive. 3: To start Mediatomb when you boot you need to edit the Go file found in the config folder. Please use WordPad to edit this file since WordPad is Linux/Unix friendly unlike Notepad or Word and won't "ruin" the file. Now add the following to the file at the bottom cd /boot/mediatomb echo "./mediatomb.sh" | at now + 1 minute and save the file. The reason for navigating to the folder using cd first is that the mediatomb.sh script wont run properly if its not run from the correct folder. Using echo at the start hides the script from the consol so it wont look strange and the "at now + 1 minute" part delays the start of the script. The delay is there to make sure unRAID has time to mount all the drives properly and establish a network connection. 4: Reboot the server so that MediaTomb can start up once and create all its needed configuration files. 5: Getting support for international characters such as åäö. You will need to add the following lines to the config.xml file that was created during the reboot in step 4. You will find it in "flash\mediatomb\config\". <filesystem-charset>UTF-8</filesystem-charset> <metadata-charset>UTF-8</metadata-charset> Add them to the top of the Import function, namely after "<import hidden-files="no">". Again please use WordPad when editing this file for the reasons mentioned above, also NotePad and the rest tend to have problems displaying .xml files in a easy-to-read manner. 6: Reboot once again to impose the UTF-8 changes. Once its all started again you can configure MediaTomb from http://unraid-servers-ip:49152/ and also add/remove content from its database. It could be other ports if the default 49152 is taken, usually it tries going one port higher until it finds a free port so just start upping the port until you find it. Post-Install support of UTF-8: If you already have MediaTomb installed in some manner and want to add the UTF-8 support you have to delete the database file mediatomb.db found in "flash\mediatomb\config\" first so that MediaTomb can rebuilt it with the correct UTF-8 characters when rebooting. End of How-To Known Bugs in Version 1.0-1.2 configuration The current configurations has one big problem and that is you cant stop the array when the UPnP server is being used. This will cause the parity to get unsynced and you'll be forced to do a hard-reboot of the array (alternatively shut it down from the terminal) so please keep that in mind and make sure all UPnP devices are inactive before stopping the array. Suggestions on how to fix this would be appreciated. The ability to run code when stopping the array will apparently be added to unRAID 5.X, until then just remember to turn of any UPnP devices before stopping the array. Changelog of guide: 1.0: Initial guide, had known problems and was more of a betatest. 1.1: Fixed all known problems from 1.0 with starting script and other flaws such as spelling, wording and changed from NotePad to WordPad as suggested editor. Found the de-sync bug in this configuration for the first time, its assumed to be in the 1.0 configuration as well. Special thanks goes to [glow=green,2,300]Joe L.[/glow] and [glow=green,2,300]RobJ[/glow] for their help with this version of the guide. 1.2: Guide missed the reboot step before adding UTF-8 support, hard to change a file that's not there. De-sync bug still not fixed but also the only known bug, solution supposedly on its way in 5.X.