JPrez

Just a quick update, decided to downgrade to 6.3.5 with a new clean install and see if it worked...and it works fine with LACP/802.3AD. A clean install with 6.4.1 fails. Whatever the issue is, appears to be within 6.4.1.

Hey All - I think I may have stumbled upon a bug or timing issue or some other incompatibility. Details: 6.4.1 UnRaid Supermicro X10-SL7F Board with Dual Intel Gigabit NICs Ubiquiti Enterprise Switch (supports LACP/802.3AD) Clean install - switch configured with LACP turned off. UnRaid will obtain its normal IP addresses via DHCP without issue. No problem there. 1. After initial boot, login to the UnRaid GUI and configure bonding in the unRaid GUI (802.3 AD (4)) and save changes 2. Configure the switch to re-enable LACP) 3. Reboot switch - allow time for switch to complete boot 4. Reboot UnRaid 5. No DHCP provided - a generic 169 IP address appears on the console. From the shell, can't ping out, no IP present if your ifconfig Workaround: In the shell, issue: /etc/rc.d/rc.inet1 stop followed by /etc/rc.d/rc.inet1 start server then obtains a DHCP IP without issue and the bond is present (IP is assigned to the BR interface). However, if you reboot or powercycle the same issue is present again until you re-run the commands above. I do not believe it's a hardware issue as the same hardware worked fine with bonding on FreeNAS without issue. Any idea what's occurring here? Thanks

Hey All - So I'm curious what people are getting with regards to read performance on unRaid 6 in general if I could. My hardware is as follows: SuperMicro XL7-F Board with a Xeon E31276 CPU @ 3.60 GHz with 32 GB of ECC Ram 8x4TB WD Red 5400 RPM HDD My array is complete and parity built but I am lucky to pull down between 70-80MB/s via Windows file explorer. The same hardware running FreeNAS pulls 112MB/s+ consistently. I understand UnRaid is slower on the write (faster if you have a cache drive) but wasn't expecting a slower read response. I don't believe it's hardware since the same hardware on FreeNAS performs much faster. Is there a setting I'm missing or is that just the nature of unRaid? Thanks

Thanks - I'll wait for the parity build to stop before trying again - about 3 days to complete apparently. On a related note, would changing the Disk Settings -> md write method to "reconstruct write" help with write performance even with a cache SSD drive or should I remove and not use the cache drive with this feature turned on? Thanks

Hey All - Still trialing out my unRaid build and seem to have run into an issue. While I understand unRaid is slow to write files to the array (hence a cache disk) I was under the impression that read speeds were not affected. On the same equipment I was getting 112mb/s down without an issue all night and day....however, with unRaid I'm lucky to get 5-7mb/s down. I read several posts and did the common things, I checked the ethernet card and rate via ethtool: Advertised pause frame use: Symmetric Advertised auto-negotiation: Yes Speed: 1000Mb/s Duplex: Full Port: Twisted Pair The device I'm using to pull files from the server is also connected via ethernet and with a gigabit link. For testing, I was downloading a 20gig file from the server and the sustainted speed was around 5mb/s Hardware wise, it's a SuperMicro SL7-F board with 8 (4TB) WD Red drives (6 in array, 2 for parity) and a SSD drive for cache. 32 Gigs of ECC ram and dual Intel NICs. The parity is still undergoing a rebuild (about 30% complete since it's a new install) but that shouldn't affect the download from the server should it? Thanks

Thanks for the reply, for grins and giggles decided to go to my local Staples store and buy another USB flash drive...a PNY brand. Thought I'd try it again, working like a champ now and just registered for my trial key. Very strange but so far it seems to like the PNY brand.

Yes, same error as original poster. Using a SuperMicro X10SL7-F with BIOS 3.0a and an Intel Xeon E31276 CPU, also using a SanDisk 16GB Ultra Fit USB 3.0 flash drive.

Hey Gang - New install here on a SuperMicro board, same error message as reported in this thread. I'm using the latest UnRaid build, 6.4.1 and have tried several USB sticks - no joy. I changed various settings in the BIOS (Legacy OpROM to UEFI Only, various USB settings also) but no change. Only way I got it to work was to install 6.3.5 instead. Does this mean I am stuck with regards to being able to upgrade to future versions of the software? Thanks

Thanks - One last question that comes to mind....as part of the UnRaid install process....will it evaluate each drive for health during the format (or shortly thereafter)? I don't suspect any drive problems but would prefer the fresh OS to evaluate the drives (or is there a process I can manually kickoff) before I start moving data over? Thanks

Hey All - Three questions I'd like to get feedback/comments on please: 1) I'm in the process of potentially moving to UnRaid from FreeNAS and have been exploring UnRaid for a few weeks. I noticed in the blog that release 6.4.0 contains SSL support and encryption and it got me thinking....with my FreeNAS box, it's also secured via SSL (the web front end that I pay for yearly) and is exposed to the Internet via a static public IP. Is UnRaid hardened with regards to public IP exposure or is the best practice to keep the server on the LAN segment only? I ask these questions as I currently have a plex server running in a freenas jail and some other items that require a public IP and allows for administration just about anywhere. 2) I plan to use a SuperMicro X10SL7 board with a Xeon E3 1276 v3 CPU, 32 GB of RAM and 8 (4TB each) WD Red drives connected to the built in Intel SATA controller on the motherboard. Any recommendations with regards to hardware or drive configuration? Not sure I am fully up to speed on the parity drive and cache drive yet but I am still reading about it. 3) The encryption options in UnRaid appear to be significantly larger than FreeNAS, what is the best practice/recommendation on filesystem type since it will be next to impossible for me to change once I format and move all my data over. I was leaning to XFS since it appears to be more common from what I've read. Thanks!