roberth58

Updated and problem solved. thanks

My main media share is showing 857TB free space. The dashboard shows correct sizes 133TB of 191TB. used. If I click compute it shows size of 127TB and all the disks show correct size and free space. I checked the disk shares and they all display the correct size and free space. Any ideas on where to look? I'm running 12.2.2. thanks

bonienl, thank you so much, this script made it so easy to switch my 10gig card to eth0. I just added a ifconfig after the script to assign an IP to the built in 1gig in hopes of using it for WOL, unfortunately it didn't work.

John_M, Not 100% true, my IPMI connection is eth0 and unraid has no problem configuring my 10gig card which is eth1. I would like to enable the second onboard 1gig and try to use it for WOL as 10gig cards don't support it. I think I have the udev rules sorted out but how do I get the file into the etc/udev/rules.d folder at bootup? thanks

Nope, PCI means PCI. PEG=PCI express graphics slot 1, PEG2= PCI express graphics slot 2.

Fireball, check your BIOS there is usually an option to pick PCIE or PCI for the videocard.

I've been running Connectx-2 EN cards for a while. The drivers are already in unraid and they are dirt cheap on ebay.

Are you sure that your moving enough data when you test the LACP? Say copying large 1-2G files to an SSD cache from 2+ clients at the same time.

name is eth2. Common jumbo frames setting is 9000. However jumbo frames can be a bugger, you have to make sure everything supports the jumbo frames value you want to use. Some old switches/routers only supported 4k, 6k or 8k. Unless you have some old hardware you probably will see a very small speed boost (if any) using jumbo frames, not worth the bother.

Or you could get a couple of the 2008 clones, Dell, IBM etc on ebay. Flash them to IT and you have 16 ports for $100 tops.

If the client is win8.1 or win10 won't server side copy stop this problem as long as the source and destination are in the same share. I have found unraid to be a bit weird with SSD cache drives as far as speed. Copying to a cache only share I get 250-300MB/s (10Gb connection) but if I copy to a share with cache enabled it can drop to 60MB/s.

A LSI 1068 is built in to my MB and it definitely does not support drives over 2.2TB. For larger drives you need a LSI 2008 chip, as used in the 9211 card and Dell 310.

the minimum free space is set to 0 for the cached share and the cache only share. As for validating, I looked at \\tower\cache and could see the files I had just copied to Z: (my media share). Unless it starts to slow down again lets chalk it up to gremlins and get on with our day.

Well problem solved at least for now. As suggested I shutdown all my dockers and VM's. Started everything back one at a time and checked transfer speeds and they are now close. After everything was loaded again I checked it with LAN Speed Test and it is showing only about 10% slower writing to the cached share and almost no difference reading between the 2 shares. Hopefully a one time glitch. thanks

And you'd be surprised how many people think MB/s and Mb/s are the same thing. Obviously you know the difference. My mistake on the "writing directly to the cache drive" statement. Again, sorry I can't be of more help than to say that writing to a "cache enabled" share on my server I can saturate GigE. What are the specs of your system? Supermicro SC846 case with Tyan S7025 with dual xeon 5650's and 32gig, 40+TB of mixed WD red and HGST deskstar NAS, using HGST 7200rpm 6TB for parity drive and 500Gig Samsung 850 EVO for cache. Drives are connected to LSI2008 controllers, Mellanox Connectx-2 10Gig network.