magnumdoomguy

Hi everyone, I'm able to get Link Aggregation working properly on my Unraid box (which has two Intel GigE NICs in it)-- and have a Cisco SG300 switch (Layer 3) that supports it. I can get that working fine via Unraid's web gui without issue. I'm using 802.3ad for the aggregation. I can also get Jumbo frames working fine (by editing the MTU in network.cfg), and all my equipment end to end supports that (the lowest common denominator MTU I can use is 7168 bytes). Setting MTU=7168 in the network.cfg file does than just fine. If I turn both on LAG and Jumbo frames, I can't connect anymore via CIFS or the web gui. SSH, Telnet, and NFS will all still connect. Is there any trick to get the both turned on together? And please, no replies about Jumbo frames being horrible or useless.

True on the price (although Essentials is actually $500). The trial is 180 days though, and much like Winrar doesn't actually do anything when the trial period is up. I get free licenses from my college. And I know Linux, thanks (on the Dean's list). Was the attitude really necessary?

Thank you for saying this. It's tiresome to see so many people poo-poo the idea of dual-parity because "what are the odds of two drives going simultaneously?" The main benefit of dual-parity is piece of mind during the rebuild of a single disk going. I ran hardware RAID5 prior to switching to Unraid, and only had to rebuild once -- and it was a nerve-racking process. Sure I had backups, but restoring is never fun, and the time window between then and the last backup would have been lost. With dual-parity rebuilding would be a lot less stressful. I agree than no other upgrade could be greater than this for Unraid at the moment.

Hi guys, I've successfully (for the most part) setup folder redirection with my network and Windows 2012 R2 and Unraid. I can log into any of my Windows clients and get the exact same desktop, settings and media libraries for every machine without any fussing with settings on individual machines. Only have two small issues. Most of the folders are redirected to 2012 R2 server, only the media libraries are redirected to Unraid. They somewhat work but have two issues. 1. $RECYCLE.BIN and desktop.ini show up in each of these folders. And before anyone suggests it -- turning off or on hidden files and folders have no effect (nor should it -- the NTFS hidden property is not there). Also configuring recycle bin to not be used on those folders also changes nothing (but doesn't matter, since I don't want it turned off -- the windows recycle bin on the Unraid shares actually works, and I want to keep it). Now, I know how to fix this.... I just don't know how to implement the fix. Samba can be configured in SMB.conf to ignore certain files and folders, and can easily be set to hide these files. Problem is, I can't find smb.conf in Unraid. It's not in /etc (where it typically lives). And running find comes up empty handed. I'm guessing it has a different name and location in Unraid. Can anyone direct me where to find the samba config in Unraid? 2. Permissions appear to be an issue. No problem creating files in the media libraries or subfolders in them. No problem deleting folders within the media libraries. No problem deleting files in subfolders. Files in the root of each library (and thus the root of each share), cannot be deleted. It's a permissions thing and Explorer says I need permission from UNRAID\doomguy to delete. The domain account name for this user is doomguy, and otherwise works anywhere else in the same share / media library. If I change the group policy on the 2012 R2 server back to normal and just map the Unraid share to a network drive, I can delete in root no problem. And it's only files in root -- folders in root can be deleted. Anybody here doing folder redirection with Active Directory? Any hints? Also the Unraid machine is not joined to my active directory.

This looks very exciting. Thanks for doing this. I tried this evening to install, but no love thus far. UNRAID:3000 or 192.168.3.9:3000 gives "Unable to connect".

I know there are a few people here who use WHS either on baremetal or virtualized -- primarily for the awesome backup it provides. And I'm sure there are a few disappointed faces in that product reaching End of Life. I just wanted to mention that Windows Server 2012 R2 has that awesome functionality in it. One of the roles that can be installed on 2012 R2 is "Windows Server Essentials Experience" which has a bunch of stuff in it -- including the awesome backup power that WHS had. Just thought this would be a "good to know" thing for some of the users here.

That script sounds awesome... I'll hunt for it. Definitely preferable to cranking the fans 24/7. I also replaced the rear fans (and yes, they're definitely exhausting )... Also with Noctuas (love Noctua -- so powerful, yet so quiet). Thanks for the tip on the script. That would be a great feature to make standard.

I have a new Norco with the single power back planes. Someone else on this forum posted a pic so thankfully I don't have to go through the trouble: http://lime-technology.com/forum/index.php?topic=29274.0 So single power connections is the only option. No splitters, and each is on it's own cable (I read somewhere that that was preferable if possible). I googled Seagate and SMARTCTL and found that the numbers they use for Raw Read Error are really messed up -- it's a bit of math to convert the raw value into something meaningful to a human. So it turns out all the raw read errors on the Seagates are unimportant (after doing the math). So I'm down to just the four (ahem, now 5) red balls. I decided to wipe the array config last night and set it up the same again, told it to trust the parity, started up, then ran a parity check. Went well for a while then drive 11 just flat out disappeared. Got a redball and that drive wasn't even listed anymore. I should have captured the syslog at that point, but didn't unfortunately. I noticed the temps were quite high (most of the drives in the sixties and my two 1.5TB drives [which have always run hotter than the others] were in the seventies). I powered down, opened the window (which is pretty close to the NAS) and let the Canadian winter bring it down to a cooler temp for a while. After cooling down, did the same procedure again, and it's nearly down now (75% in, with only the 4TB drives less so the speed has increased dramatically). The red ball issues have happened during parity checks or a rebuild, so I think I'm just plain getting too hot. I have the optional 120mm fan plate for the Norco with 3 Noctua fans on it. I'm not using the low noise adapters (which limit the speed to 1300RPM max). I did put a low noise setting on the BIOS though. I'm figuring since the drives are before the intake fans and the motherboard setting is using the system ambient temp to decide fan speeds, it's going lower than the hard drives need. I'll try (once the parity check completes), hooking up a screen and going back into the bios and choosing a more aggressive fan setting (bye bye sleep -- this is in my bedroom).

You can do it via command line. Instructions are here: http://lime-technology.com/wiki/index.php/Troubleshooting#Capturing_your_syslog

Okay, ran smartctl on every drive and have attached all the ones that came up with errors (11!). I compared them with the main screen of Unraid to look for patterns. All the problem drives save one are Seagates (of various sizes and bought at different times). The exception is a Samsung 1TB. And not only are they all Seagates (save one) they are also the entirety of Seagate drives that I have. All the problem drives save one are on the SUPERMICRO AOC-SAS2LP-MV8 PCI-Express 2.0 x8 SATA / SAS 8-Port Controller Cards. The other controller card only has 3 drives on it though and two are Western Digitals. The one Seagate on it is problematic. Can anyone help? I'm at a loss. smartctl.zip

Just checked the cables, everything seems pretty snug. Now that it has rebooted smartctl works on the latest red balled drive. SMART Attributes Data Structure revision number: 16 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail Always - 0 3 Spin_Up_Time 0x0027 181 179 021 Pre-fail Always - 5908 4 Start_Stop_Count 0x0032 099 099 000 Old_age Always - 1681 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0 7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always - 0 9 Power_On_Hours 0x0032 095 095 000 Old_age Always - 4377 10 Spin_Retry_Count 0x0032 100 100 000 Old_age Always - 0 11 Calibration_Retry_Count 0x0032 100 253 000 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 50 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 18 193 Load_Cycle_Count 0x0032 198 198 000 Old_age Always - 7551 194 Temperature_Celsius 0x0022 119 076 000 Old_age Always - 31 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0 197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0030 200 200 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0008 200 200 000 Old_age Offline - 0 Looks fine to me. Going to try a long test on it now.

Not using any power splitters. Will power down now and check the cables though.

My Apologies: CORSAIR HX Series HX850 850W ATX12V 2.3 / EPS12V 2.91 SLI Ready CrossFire Ready 80 PLUS GOLD Certified Modular Active PFC Power Supply New 4th Gen CPU Certified Haswell Ready http://www.newegg.ca/Product/Product.aspx?Item=N82E16817139011 21 drives in the array including parity and cache (ssd). Do you think the power supply might be the culprit?

Here's the third drive that red balled: SMART Attributes Data Structure revision number: 16 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail Always - 0 3 Spin_Up_Time 0x0027 166 157 021 Pre-fail Always - 6700 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 252 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0 7 Seek_Error_Rate 0x002e 100 253 000 Old_age Always - 0 9 Power_On_Hours 0x0032 054 054 000 Old_age Always - 33850 10 Spin_Retry_Count 0x0032 100 100 000 Old_age Always - 0 11 Calibration_Retry_Count 0x0032 100 100 000 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 172 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 24 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 248 194 Temperature_Celsius 0x0022 115 081 000 Old_age Always - 35 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0 197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0030 200 200 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 4 200 Multi_Zone_Error_Rate 0x0008 200 200 000 Old_age Offline - 0 Have a UDMA CRC error of 4 on that one, but otherwise looks okay I think. And the second red balled drive: SMART Attributes Data Structure revision number: 10 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000f 118 099 006 Pre-fail Always - 190616536 3 Spin_Up_Time 0x0003 094 093 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 729 5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail Always - 0 7 Seek_Error_Rate 0x000f 073 060 030 Pre-fail Always - 12955017484 9 Power_On_Hours 0x0032 092 092 000 Old_age Always - 7279 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 153 183 Runtime_Bad_Block 0x0032 100 100 000 Old_age Always - 0 184 End-to-End_Error 0x0032 100 100 099 Old_age Always - 0 187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 0 188 Command_Timeout 0x0032 100 100 000 Old_age Always - 0 0 0 189 High_Fly_Writes 0x003a 100 100 000 Old_age Always - 0 190 Airflow_Temperature_Cel 0x0022 069 049 045 Old_age Always - 31 (2 8 45 30 0) 191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 0 192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 138 193 Load_Cycle_Count 0x0032 023 023 000 Old_age Always - 155328 194 Temperature_Celsius 0x0022 031 051 000 Old_age Always - 31 (128 0 0 0 0) 197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0 240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 6655h+38m+34.307s 241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 28251950231 242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 33782756058 None of the three culprits listed in the Unraid wiki (Reallocated sector count, current pending sector, or UDMA) but a very high Raw Read Error And here's a green ball drive with a high Raw Read Error Rate: SMART Attributes Data Structure revision number: 10 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000f 106 099 006 Pre-fail Always - 11741173 3 Spin_Up_Time 0x0003 100 100 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 099 099 020 Old_age Always - 1592 5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 0 7 Seek_Error_Rate 0x000f 072 060 030 Pre-fail Always - 18178653 9 Power_On_Hours 0x0032 073 073 000 Old_age Always - 23865 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 561 183 Runtime_Bad_Block 0x0032 100 100 000 Old_age Always - 0 184 End-to-End_Error 0x0032 100 100 099 Old_age Always - 0 187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 0 188 Command_Timeout 0x0032 100 099 000 Old_age Always - 12885098500 189 High_Fly_Writes 0x003a 092 092 000 Old_age Always - 8 190 Airflow_Temperature_Cel 0x0022 073 036 045 Old_age Always In_the_past 27 (0 111 40 26 0) 194 Temperature_Celsius 0x0022 027 064 000 Old_age Always - 27 (0 17 0 0 0) 195 Hardware_ECC_Recovered 0x001a 051 021 000 Old_age Always - 11741173 197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0 240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 10823317607033 241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 2091198126 242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 1459779639

Been running 5.0.3 for about a month now. Decided to run a parity check last night, and got my fourth red ball. The second and third are here: http://lime-technology.com/forum/index.php?topic=30972.msg279030#msg279030 Running smartctl -a -A /dev/sdq on the latest failed drive gives: A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options. I tried running smartctl on a few of the other drives (which are otherwise functioning fine): smartctl 6.2 2013-07-26 r3841 [i686-linux-3.9.11p-unRAID] (local build) Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Family: Seagate Barracuda 7200.14 (AF) Device Model: ST2000DM001-9YN164 Serial Number: Z1E1DSN7 LU WWN Device Id: 5 000c50 04e618f6f Firmware Version: CC4B User Capacity: 2,000,398,934,016 bytes [2.00 TB] Sector Sizes: 512 bytes logical, 4096 bytes physical Rotation Rate: 7200 rpm Device is: In smartctl database [for details use: -P show] ATA Version is: ATA8-ACS T13/1699-D revision 4 SATA Version is: SATA 3.0, 6.0 Gb/s (current: 6.0 Gb/s) Local Time is: Sun Jan 5 13:38:41 2014 EST ==> WARNING: A firmware update for this drive may be available, see the following Seagate web pages: http://knowledge.seagate.com/articles/en_US/FAQ/207931en http://knowledge.seagate.com/articles/en_US/FAQ/223651en SMART support is: Available - device has SMART capability. SMART support is: Enabled === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED General SMART Values: Offline data collection status: (0x00) Offline data collection activity was never started. Auto Offline Data Collection: Disabled. Self-test execution status: ( 0) The previous self-test routine completed without error or no self-test has ever been run. Total time to complete Offline data collection: ( 584) seconds. Offline data collection capabilities: (0x73) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. No Offline surface scan supported. Self-test supported. Conveyance Self-test supported. Selective Self-test supported. SMART capabilities: (0x0003) Saves SMART data before entering power-saving mode. Supports SMART auto save timer. Error logging capability: (0x01) Error logging supported. General Purpose Logging supported. Short self-test routine recommended polling time: ( 1) minutes. Extended self-test routine recommended polling time: ( 228) minutes. Conveyance self-test routine recommended polling time: ( 2) minutes. SCT capabilities: (0x3085) SCT Status supported. SMART Attributes Data Structure revision number: 10 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000f 119 099 006 Pre-fail Always - 226787296 3 Spin_Up_Time 0x0003 094 094 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 438 5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 0 7 Seek_Error_Rate 0x000f 078 060 030 Pre-fail Always - 65645134 9 Power_On_Hours 0x0032 092 092 000 Old_age Always - 7620 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 385 183 Runtime_Bad_Block 0x0032 100 100 000 Old_age Always - 0 184 End-to-End_Error 0x0032 100 100 099 Old_age Always - 0 187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 0 188 Command_Timeout 0x0032 100 099 000 Old_age Always - 0 0 1 189 High_Fly_Writes 0x003a 052 052 000 Old_age Always - 48 190 Airflow_Temperature_Cel 0x0022 071 052 045 Old_age Always - 29 (Min/Max 25/38) 191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 0 192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 68 193 Load_Cycle_Count 0x0032 008 008 000 Old_age Always - 185919 194 Temperature_Celsius 0x0022 029 048 000 Old_age Always - 29 (0 15 0 0 0) 197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0 240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 6410h+40m+47.547s 241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 177072791022439 242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 57907602430615 SMART Error Log Version: 1 No Errors Logged SMART Self-test log structure revision number 1 No self-tests have been logged. [To run self-tests, use: smartctl -t] SMART Selective self-test log data structure revision number 1 SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS 1 0 0 Not_testing 2 0 0 Not_testing 3 0 0 Not_testing 4 0 0 Not_testing 5 0 0 Not_testing Selective self-test flags (0x0): After scanning selected spans, do NOT read-scan remainder of disk. If Selective self-test is pending on power-up, resume after 0 minute delay. While not all of my drives, I do appear to be getting high raw read error rates on a few drives. At this point I'm wondering if I should start suspecting the hardware. I have a Norco 4224 with the following: NORCO C-SFF8087-D SFF-8087 to SFF-8087 Internal Multilane SAS Cable (x3) http://www.newegg.ca/Product/Product.aspx?Item=N82E16816133034 SUPERMICRO AOC-SASLP-MV8 PCI-Express x4 Low Profile SAS RAID Controller http://www.newegg.ca/Product/Product.aspx?Item=N82E16816101358 SUPERMICRO MBD-X9SCM-O LGA 1155 Intel C204 Micro ATX Intel Xeon E3 Server Motherboard http://www.newegg.ca/Product/Product.aspx?Item=N82E16813182254 SUPERMICRO AOC-SAS2LP-MV8 PCI-Express 2.0 x8 SATA / SAS 8-Port Controller Card (x2) http://www.newegg.ca/Product/Product.aspx?Item=N82E16816101792 Any recommendations or suggestions? syslog.zip