StevenD

Well, I tried that and it didnt work. I tried adding the following lines to both smb.conf and smb-extra.conf (separately, of course) and neither one worked. dos filemode = yes dos filetime resolution = yes dos filetimes = yes fake directory create times = yes

Thank you! i will give that a try.

I'm unable to change the "Last Modified Time" on folders on unRAID. I have a PowerShell script that I want to run, but I discovered that I cannot change the last modified time on some folders. I think I have figured out that I cannot change the last modified time or creation date to before the folder was actually created on unRAID. Ive tried with powershell and a couple other utilities. Everything works just fine if I'm working with folders on a Windows Server. In its simplest form, here is a script to change a date in PowerShell: PS D:\scripts> $folder = get-item '\\nas\TV\Breaking Bad' PS D:\scripts> $folder.LastWriteTime <<<<------- Displays current time Monday, September 30, 2013 8:13:35 AM PS D:\scripts> $folder.LastWriteTime = "10/01/2007" <<<<------- Sets the time you want PS D:\scripts> $folder.LastWriteTime <<<<------- Displays current time (see, it didnt change to the date I wanted) Sunday, September 15, 2013 11:53:02 PM Any ideas? Thanks.

Just a reminder, CR2032 batteries (the type most BIOS's use) are dirt cheap in quantity. http://www.amazon.com/CR2032-Lithium-Batteries-card-Cards/dp/B0043SAFK0/ref=sr_1_9?ie=UTF8&qid=1383056058&sr=8-9&keywords=cr2032

Honestly, not really. I consider my ESXi SAN to need HA, but not unRAID.

Yes

It really depends on what your swicth supports. Mine all support 802.3ad, so that's what I run.

http://lime-technology.com/forum/index.php?topic=5446.0

One of the reasons I went with two 4TB drives was I wouldnt have to buy a new parity for quite some time, no matter what size data drives I buy.

Thats how DHCP works! "The renewal process occurs when a client already has a lease, and needs to renew that lease with the server. To ensure that addresses are not left in an assigned state when they are no longer needed, the DHCP server places an administrator-defined time limit, known as a lease duration, on the address assignment. Halfway through the lease period, the DHCP client requests a lease renewal, and the DHCP server extends the lease. If a computer stops using its assigned IP address (for example, if a computer is moved to another network segment or is removed), the lease expires and the address becomes available for reassignment."

You are limited to the speed of the parity drive and the speed on a SINGLE data drive. You get improved speed on MULTIPLE drive writes with a RAID0 Parity. And, yes, while the odds of you losing a Parity drive faster because of the RAID0, remember that a parity drive is no more important than any other drive in unRAID. For this reason, I also run bonded NICs. I get improvement on multiple reads and writes.

That is 100% incorrect! I ran an ARC-1210 with two 4TB Hitachi's on it for about a year. Configured a 4TB RAID0 for Parity and a 1TB RAID1 for Cache. I worked beautifully! I got great speeds. I removed the Areca card when I reconfigured my server recently. However, I may go back to this configuration.

I dont know that anybody has gotten AD security to work properly.

The cards I listed are used, but I don't really care. NICs don't go bad that often.

Dont spend that kind of money! Ive been buying these and they work just fine in unRAID and ESXi. http://www.ebay.com/itm/Intel-EXPI9402PT-Pro-1000-PT-DELL-X3959-Dual-Port-PCI-E-x4-Server-Adapter-/171119497681?pt=US_Internal_Network_Cards&hash=item27d78451d1

If you upgraded from 4.7, did you run the "New Permissions" script ?

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!!

Expect a several failures at once at some point.

Does the price include a flash with license?

There are no references to Plex in m go script either.

Yes. Go look at my build thread: http://lime-technology.com/forum/index.php?topic=10158.0 Its changed since then, but the fans are the same.

I use the stock power supplies.

I have this case. You can run 1, 2 or 3 psu's. if you don't care about redundancy, you can get by on one, most likely. You do have to actually pop them out as an alarm will sound if its installed but not plugged in.

looks like you better find your original email from Tom.

Try copying that key to the root and rebooting. Thats where mine are.