switchman

Members
  • Posts

    441
  • Joined

  • Last visited

Everything posted by switchman

  1. I did not know that Unraid had a NPT server. Just synced my PC to my unraid server using its IP address. I hard code the IP in unraid as I noticed in the past that it appears to stop/start the SMB share when renewing the IP address.
  2. I was just suggesting that if the OP ever did decide to expand beyond the 5-6 drives listed, he at least has a path without throwing away any hardware. A 1200 would also give more drive mounting positions before expansion cages or a new case is required. I feel your pain on the drive cages. I purchased all three of mine up front and wired it all up at once. If I were doing it now, I would go with the new iSTAR 5in3 dock. http://www.istarusa.com/drivecages/bpndespec.php My problem is that I don't have anywhere the Norco would fit. It is to deep for my room.
  3. I would go with an AMD Athlon II X2 260 or 270 Regor CPU and a Antec 1200 case if you have room for it. The 1200 will give you more room to grow. I have a 900 and wish I had purchased a 1200. The mother board you have selected could get you to 20 drives and a 1200 could support 20 drives using 5in3 expansion cages. http://www.newegg.com/Product/Product.aspx?Item=N82E16819103953 or http://www.newegg.com/Product/Product.aspx?Item=N82E16819103873 These CPU's give you the extra processing power when you need it, but do not add much to the thermal/power load and the fan is still quite. There is also not much of a price difference. The 260 can do real time transcoding if you need it. For a test, I tried Plex on my system and it worked fine. I was streaming to my iPhone via a vpn connection from my phone to my router. Also, you should review this page if you have not already done so. http://lime-technology.com/wiki/index.php?title=Hardware_Compatibility#Recommended_Builds
  4. I have one and it works fine. The firmware is still in beta though and will only get better. I only use it as a streamer from my unraid server though. The only mod you have to make is: 1 - Load the Linux XBMC image. It comes with android on it. 2 - Plug a uSD card in it. This way you do not exceed the built in flash capacity 3 - Move the XBMC user data directory from the built in flash to to the uSD card and set a symbolic link to the new location. The entire procedure to this point takes~10 minutes. 4 - Boot it up and set paths to your media within XBMC and import your library. This takes the longest amount of time. Depending on you library size and connectivity method, it can take hours to scrape your library. 5 - No jail breaks required. You have root access to it. 6 - As far as price, I paid $115 USD shipped for mine but have seen it for as low as $99 USD on Newegg. I purchased a 32GB Class 10 uSD for $25 locally at Frys. I didn't really need 32G, but went with it any way. 16Gb would have been more than enough. A 16GB class 10 uSD card pops up at Frys for ~$10-$12 a lot. For me it was exactly what I wanted which is an appliance running XBMC without the expense of another small form factor PC.
  5. I still suggest picking up a Pivos XIOS DS, installing Linux XBMC on it. You can run either SMB or NFS shares. I currently run NFS but have used the SMB sahres on my server. It plays anything I throw at it. It does not rely on you server to to the transcoding. The DS does hardware decoding. If you go this route make sure you get the M3 hardware. It is a little faster, but has 1GB of memory vs 512MB on the M1 hardware. You can read more about it here. http://www.pivosforums.com/viewforum.php?f=25
  6. My tv does DNLA. It was an earliy generation and is a PITA. Before I got a Pivos XIOS DS to run XBMC I used my Blueray player which does support playing of of an unraid SMB share. Problem was it could not play all of the containers. I think you are going to be hardpressed to find a TV that can do what you want. It will be expensive if you do.
  7. How are pepole benchmarking internal tranfers between disks. It is obvious for a parity test as the system tells you. An upload is easy because you can measure it.
  8. I had a similar problem with the GUI no longer responding. After reading through various threads, the common consensus is the OOM_killer is killing them off when it needs some additional memory. I call this script as part of my boot sequence. It sets the "emhttp" and samba shares to not be killed off. I have not had any issues after I started using this script. As this gets logged in my syslog when it runs, I do a before and after check. It might help you and it might not depending on the source of your issues. The bottom block of code is all you really need. The other comments/info are notes to myself. #!/bin/bash # Wait 120 seconds to ensure SAMBA has started. # sleep 120 ############################################# # This adjusts the PID for UNRAID server and Shares process may never be killed in a low memory condition. ############################################# # From http://lime-technology.com/forum/index.php?topic=20013.msg200115;topicseen#msg20011 # # # From https://access.redhat.com/knowledge/docs/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/s2-proc-pid.html # and # From http://www.kernel.org/doc/man-pages/online/pages/man5/proc.5.html # # # There is also a special value of -17, which disables oom_killer for a process. # An oom_score of a value of 0, indicates that this process would not be killed. # # Use the following command to view the score. It should be "0" after running the commands below # cat /proc/[pid]/oom_score # # To see the path for where the program lives. # /usr/sbin/smbd # # To view current PID use: # pgrep -f "/usr/local/sbin/emhttp" # pgrep -f "/usr/sbin/smbd" # # Combined command to find the PID and show the score. # pgrep -f "/usr/local/sbin/emhttp" | while read PID; do cat /proc/$PID/oom_score; done # pgrep -f "/usr/sbin/smbd" | while read PID; do cat /proc/$PID/oom_score; done # ############################################# # Set UNRAID webserver is never killed off. # pgrep -f "/usr/local/sbin/emhttp" | while read PID; do echo -17 > /proc/$PID/oom_adj; done # # Set SAMBA so shares are never killed off. # pgrep -f "/usr/sbin/smbd" | while read PID; do echo -17 > /proc/$PID/oom_adj; done ############################################# # # # Uses the new oom_score_adj ############################################# # Check the OOM values before the change pgrep -f "/usr/local/sbin/emhttp" | while read PID; do cat /proc/$PID/oom_score; done pgrep -f "/usr/sbin/smbd" | while read PID; do cat /proc/$PID/oom_score; done # Set UNRAID webserver is never killed off. pgrep -f "/usr/local/sbin/emhttp" | while read PID; do echo -1000 > /proc/$PID/oom_score_adj; done # # Set SAMBA so shares are never killed off. pgrep -f "/usr/sbin/smbd" | while read PID; do echo -1000 > /proc/$PID/oom_score_adj; done # # Check the OOM values after the change pgrep -f "/usr/local/sbin/emhttp" | while read PID; do cat /proc/$PID/oom_score; done pgrep -f "/usr/sbin/smbd" | while read PID; do cat /proc/$PID/oom_score; done #############################################
  9. I just installed the latest version of Simplefeatures, v1.05. Is it normal for all of the drives LEDs to flash (at the same time) every few seconds. The stock GUI did not exhibit this behavior. It does not do it when the drives are spun down. I can't tell if its actually reading the disk for data or just accessing the drive status, ie drive temp. As the drives spin down after the timeout, I believe that it is just getting some data from the drive and not actually accessing data. If it were accessing data on the drive, I believe the drive inactivity timeout would never occur and the drives would stay spun up. Update: I just rebooted my server and noticed the following behavior. I get the LED activity when I have a web page open to the Simplefeatures GUI. If I close the browser window the activity goes away.
  10. In Settings/SMB set the Local master to Yes. Reboot the router and then all of your PCs. This way the server will take over as the Master Browser. Sometimes you can have issues in the Windows world addressing devices by their name, for example the Unraid server by //tower. You need to make sure all of the devices in your network are in the same Workgroup. You could also have master browser issues. You can Google search Windows Master Browser for more background. Scott Ogrin wrote a good utility LANscan that can give you some needed information very easily. It will tell you what Workgroup every PC is in and which one is the master browser. You can read more about it and download it here: http://scottiestech.info/2009/02/14/how-to-determine-the-master-browser-in-a-windows-workgroup/ You just extract the program to its own folder. It does not install any driver or portions of itself on your system It is a self contained program. One thing I want to point out is that when you extract it, you need to put it on your c: drive and run it from there: I put it at my root c:\ level.