StevenD

Thanks!

But there was absolutely no indication that it was actually downloading. Nor had it ever taken more than a minute to download and install before.

Well, I let it sit for about 10 minutes this morning and it finally updated. Thanks.

Im sorry to hear that, have you tried restarting the thing. (By design it retrys Downloading untill sucess, something we should probably inform about) Several times. I even deleted and rebuilt the container. Is there a way to manually update the container since its not able to download the new version for some reason?

VERSION="plexpass" is not working for me. I have let it sit for about 10 minutes and it never downloads. ----------------------------------- GID/UID ----------------------------------- User uid: 99 User gid: 100 ----------------------------------- Useing version: 0.9.12.16.1509-8e31408 from Plexpass latest Upgradeing from version: 0.9.12.13.1464-4ccd2ca to version: 0.9.12.16.1509-8e31408

This is what I do as well. MCM gives you a lot of control over the metadata. If I let Plex figure stuff out, I get a lot mismatches. I never used Emby for downloading metadata since MCM does my "filing" as well.

I do ot to save wear and tear on my ssd. Might be a ridiculous reason, but, ive got enough ram and it works great.

Still works fine with -RC5.

I updated to RC5 this morning and Open-VM-Tools for unRAID 6.0-rc3 (9.10.0-2476743-5) is working just fine. The kernel did not change, so there's no reason why it wouldn't work.

I dont know, but this is on my plugins page: Open-VM-Tools for unRAID 6.0-rc3 (9.10.0-2476743-5) The Open Virtual Machine Tools are a set of guest operating system virtualization components that enhance performance and user experience of virtual machines. Open-VM-Tools requires the Powerdown plugin. This version will work on 6.0-rc3 Read More Zeron 2015.05.20-5 up-to-date

Zeron has already released vmtools for kernel 4.0.4.

Since updating to -beta15, I can no longer mount my vmdk boot drive. All the way back to unraid 5.x, I have run this in my go file: #mount boot vm hd mkdir /mnt/boothdd mount -w -t vfat /dev/sda1 /mnt/boothdd 2>&1 However, I no longer see the VMDK at all...not via the command line or via the GUI. Any ideas?? root@nas:/dev# hdparm -I /dev/sd* | grep "Model Number:" Model Number: Crucial_CT512M550SSD1 Model Number: Crucial_CT512M550SSD1 Model Number: HGST HDN724040ALE640 Model Number: HGST HDN724040ALE640 Model Number: Hitachi HDS724040ALE640 Model Number: Hitachi HDS724040ALE640 Model Number: HGST HDN724040ALE640 Model Number: HGST HDN724040ALE640 Model Number: Hitachi HDS724040ALE640 Model Number: Hitachi HDS724040ALE640 Model Number: HGST HDS724040ALE640 Model Number: HGST HDS724040ALE640 Model Number: HGST HDS724040ALE640 Model Number: HGST HDS724040ALE640 Model Number: Hitachi HDS724040ALE640 Model Number: Hitachi HDS724040ALE640 Model Number: HGST HDS724040ALE640 Model Number: HGST HDS724040ALE640 Model Number: HGST HDS724040ALE640 Model Number: HGST HDS724040ALE640 Model Number: HGST HDS724040ALE640 Model Number: HGST HDS724040ALE640 Model Number: HGST HDS724040ALE640 Model Number: HGST HDS724040ALE640 Model Number: HGST HDS724040ALE640 Model Number: HGST HDS724040ALE640 Model Number: Hitachi HDS724040ALE640 Model Number: Hitachi HDS724040ALE640

Thanks a lot, Zeron! Works great on -beta14 and ESXi 5.5.

I got three transcoded streams running successfully. Of course, I do have 16GB allocated to unRAID right now.

Thanks. I will implement this when I get home today.

Just a reminder... http://support.code42.com/CrashPlan/Latest/Configuring/Configuring_A_Headless_Client

Very nice!

Anybody using the Kingston G4 yet? The G3s are getting hard to find. http://www.amazon.com/Kingston-Digital-MobileLite-Multi-Function-FCR-MLG4/dp/B00KX4TORI

"CrashPlan uses seven data centers: three in the US (two in Minneapolis, MN, and one in Atlanta, GA) and one each in Japan, Ireland, Australia, and Singapore. "

I received some new HGST "NAS" drives this week. Model # H3IKNAS40003272SN (0S03664). This the fastest pre-clear I have seen on a spinner.

Working great! Thanks!

Those temps are a little high. Mine dont go over 36 degrees during a parity check. I know thats a cool looking case and a fun project, but I'd be concerned about the reliability and the cooling ability.

Well, after many, many changes (got rid of all 1.5TB drives, upgraded MV8 to a pair of M1015s, removed Areca controller, added Intel 525 SSD cache) and re-running this script a couple of times, I'm finally happy with my parity check speeds again! Duration: 10 hours, 27 minutes, 11 seconds. Average speed: 106.3 MB/sec Previously, my parity check times were around 15 hours. I do regret breaking up my RAID0 parity drive though. It was NOT the root cause of my slow parity checks. I may do that again in the future, but with a 6 Gbps (SATA 3) controller. The Areca I had was only a 3 Gbps (SATA 2) controller. I have no idea if it will make any improvements or not, but I want to try this again with the "vm.highmem_is_dirtyable=1" and limiting unRAID memory to 4095MB. Here are the results from the Tunables script: unRAID Tunables Tester v2.2 by Pauven --- FULLY AUTOMATIC TEST PASS 1 (Rough - 20 Sample Points @ 3min Duration)--- Test 1 - md_sync_window=512 - Completed in 179.433 seconds = 118.1 MB/s Test 2 - md_sync_window=640 - Completed in 181.565 seconds = 123.8 MB/s Test 3 - md_sync_window=768 - Completed in 179.441 seconds = 124.9 MB/s Test 4 - md_sync_window=896 - Completed in 179.459 seconds = 125.6 MB/s Test 5 - md_sync_window=1024 - Completed in 179.456 seconds = 125.8 MB/s Test 6 - md_sync_window=1152 - Completed in 179.438 seconds = 125.8 MB/s Test 7 - md_sync_window=1280 - Completed in 179.435 seconds = 125.9 MB/s Test 8 - md_sync_window=1408 - Completed in 179.451 seconds = 125.8 MB/s Test 9 - md_sync_window=1536 - Completed in 179.448 seconds = 125.8 MB/s Test 10 - md_sync_window=1664 - Completed in 179.446 seconds = 125.8 MB/s Test 11 - md_sync_window=1792 - Completed in 179.454 seconds = 125.8 MB/s Test 12 - md_sync_window=1920 - Completed in 179.469 seconds = 125.8 MB/s Test 13 - md_sync_window=2048 - Completed in 179.482 seconds = 125.8 MB/s Test 14 - md_sync_window=2176 - Completed in 179.442 seconds = 125.8 MB/s Test 15 - md_sync_window=2304 - Completed in 179.448 seconds = 125.8 MB/s Test 16 - md_sync_window=2432 - Completed in 179.451 seconds = 125.8 MB/s Test 17 - md_sync_window=2560 - Completed in 179.441 seconds = 125.8 MB/s Test 18 - md_sync_window=2688 - Completed in 179.436 seconds = 125.8 MB/s Test 19 - md_sync_window=2816 - Completed in 179.444 seconds = 125.8 MB/s Test 20 - md_sync_window=2944 - Completed in 179.447 seconds = 125.6 MB/s --- Targeting Fastest Result of md_sync_window 1280 bytes for Final Pass --- --- FULLY AUTOMATIC TEST PASS 2 (Final - 16 Sample Points @ 4min Duration)--- Test 21 - md_sync_window=1160 - Completed in 239.569 seconds = 86.2 MB/s Test 22 - md_sync_window=1168 - Completed in 239.567 seconds = 84.2 MB/s Test 23 - md_sync_window=1176 - Completed in 239.579 seconds = 86.4 MB/s Test 24 - md_sync_window=1184 - Completed in 239.627 seconds = 84.0 MB/s Test 25 - md_sync_window=1192 - Completed in 239.584 seconds = 97.0 MB/s Test 26 - md_sync_window=1200 - Completed in 239.587 seconds = 125.7 MB/s Test 27 - md_sync_window=1208 - Completed in 239.598 seconds = 125.7 MB/s Test 28 - md_sync_window=1216 - Completed in 239.603 seconds = 125.7 MB/s Test 29 - md_sync_window=1224 - Completed in 239.605 seconds = 125.8 MB/s Test 30 - md_sync_window=1232 - Completed in 239.593 seconds = 125.8 MB/s Test 31 - md_sync_window=1240 - Completed in 239.600 seconds = 125.8 MB/s Test 32 - md_sync_window=1248 - Completed in 239.584 seconds = 125.7 MB/s Test 33 - md_sync_window=1256 - Completed in 239.595 seconds = 125.8 MB/s Test 34 - md_sync_window=1264 - Completed in 239.587 seconds = 125.8 MB/s Test 35 - md_sync_window=1272 - Completed in 239.592 seconds = 125.8 MB/s Test 36 - md_sync_window=1280 - Completed in 239.595 seconds = 125.8 MB/s Completed: 2 Hrs 7 Min 53 Sec. Press ENTER To Continue Best Bang for the Buck: Test 4 with a speed of 125.6 MB/s Tunable (md_num_stripes): 1920 Tunable (md_write_limit): 896 Tunable (md_sync_window): 896 These settings will consume 82MB of RAM on your hardware. Unthrottled values for your server came from Test 29 with a speed of 125.8 MB/s Tunable (md_num_stripes): 2720 Tunable (md_write_limit): 1224 Tunable (md_sync_window): 1224 These settings will consume 116MB of RAM on your hardware. This is -27MB less than your current utilization of 143MB. NOTE: Adding additional drives will increase memory consumption. Thanks again, Pauven!!

Sounds like your Areca is not the problem. 60 MB/s write speeds is phenomenal for an unRAID server. Hopefully we can tune your write speeds soon for even better performance! Yeah, not much sense in running your script right now. Ill wait until I get my "final" config. All controllers will be 6Gbps, no drives smaller that 2TB. Cache drive has been upgraded to a 180GB Intel SSD. Hopefully we will have the cache pool shortly. I have another 180GB drive ready to add to it for redundancy. Once I get everything working how I want, I will then move it to ESXi. I have two ESXi servers already, with a fibre channel SAN. It would be nice to have one more host for failovers.

My guess is your Areca card... try using the parity disc on the SAS2LP as well. Why use this RAID card anyway? Well, just for grins, I moved my parity to a 6Gpbs on-board SATA port and I'm not very happy with the results. I lost 20MB/s on my array write speeds. I'm down to 40MB/s again. I thought I would be installing my M1015 this weekend, but my existing cables are about an inch too short! Looks like it will be Friday before I'm able to migrate to the M1015s. In the meantime, Ive been able to pull out one 1.5TB drive and Im working on the other two this week. I replaced one with a 4TB drive and the other two are just being distributed to other drives in the array for now. If the new config doesnt give me at least 60MB/s sustained array writes, I will be re-installing my Areca. Or getting a new Areca that supports 6Gbps.