My Unraid Build


Recommended Posts

So after a few posts i think it is time to Introduce myself and my build.

 

I am a new Unraid user for about 2 months now, enjoying the software very much (the disks i use a littlebit less, but that will be resolved quickly i hope).

 

My Build:

 

- Fractal Design Node 804

- Intel i5 (1151 - 6600K)

- 64GB DDR4

- MSI Motherboard

- LSI Logic SAS9211 controller (flashed in IT Mode)

 

Disks:

 

3x Samsung EVO 850 500GB Cache disks (750GB usable)

4x 8TB Seagate ST8000AS0002 (2 parity 2 data disks)

2x 8TB Western Digital 8TB (third one on the way)

2x 4TB Seagate

1x 4TB WD Red

Total 36TB Storage usable (for now)

 

I Run a couple of Docker applications:

 

- Plex Media server (plexpass)

- Couchpotato

- Sonarr

- Plex Request.net

- PlexPy

- SabNZBD

- CAdvisor - Docker monitoring

 

And Run 2 Server 2016 VM's (1 ActiveDirectory and 1 Delivery controller for my XenApp test environment)

 

Why i am not completely happy with the disks is that the Seagate 8TB Disks already are broken for 2 of the 4 drives, 1 is returned for RMA, i will wait when this one gets back and then will send the other one). For now i ordered a 8TB WD Red disk to replace one of the Seagate Disks.

 

Pictures will be added

Link to comment

What was your evidence that "the Seagate 8TB Disks already are broken for 2 of the 4 drives"?

 

I have no real evidence or at least proven evidence. But the following was done:

 

Changed the PSU (already wanted a more powerfull one (corsair rmx550). So that solves the whole powercable thing. And tried to move the disk from the lsi logic controller to the onboard controller (thus also used another sata cable, because the lsi uses sas cables). But all of this results in the same error.

 

So no real prove, but i think that the things i did for at least 80% would sum things out. I still could have used the Seagate software on another PC, but i didn't do that because i was done with the problems returning and being afraid for my data.

Link to comment

Normally we would at least look at the SMART for the drive before deciding it was bad. This is easy to access in the V6 webUI by going to Main and clicking on the drive to get to its page, then going to Attributes. Also, the Dashboard will indicate bad SMART for the most important attributes, and you will also get Notifications for this if you have Notifications setup (you should).

 

Very often read/write issues are due to some problem other than the drive.

Link to comment

Definitely agree you should have looked at the SMART data on those drives to see if there was any indication of failure.

 

As you noted in the Seagate 8TB thread, you've already changed the cables -- but your explanation here shows that you not only changed the cabling, but also which controller the drive was on, so that's even better.

 

A 550w unit SHOULD be enough for 12 drives (you only listed 9 disks in the other thread) ... but I'd be inclined to try a higher capacity unit just to be sure.  If you're having a startup current issue, that's not going to go away until you provide better power.

 

One other thing that jumps out a bit => You're running a board with unbuffered memory with 4 high-capacity memory modules installed.  This is a VERY high load on the data and address buses, and results in very degraded signaling waveforms.  You may simply be having memory issues.    Remove two of those modules (one from each channel so you're still running dual channel) ... and see if there's an improvement in your reliability.

 

 

 

Link to comment

Check the temp of the LSI controller, also.  Those things are designed for use in rack servers that have concentrated air flow.  They can and do overheat in low airflow cases, and all manner of strange things happen then.

 

thanks for the tip, i will look into that. It could be so simple but i think it is strange that the same disks have this problem, my 2 8TB WD reds never had any problems (thus far).

 

In the Seagate disks thread i uploaded the result of the smart test, this is for 1 of the 2 disks that were disabled...

Link to comment
  • 10 months later...

So after a couple of broken (or not) disks again (all replaced under warranty by seagate) I thought why not continue this thread. Today added my replaced 2nd parity disk and when rebuilding that parity disk another disk had the error status, here is the smart test: (short, the long version is still running)

 

ATA Error Count: 2
	CR = Command Register [HEX]
	FR = Features Register [HEX]
	SC = Sector Count Register [HEX]
	SN = Sector Number Register [HEX]
	CL = Cylinder Low Register [HEX]
	CH = Cylinder High Register [HEX]
	DH = Device/Head Register [HEX]
	DC = Device Command Register [HEX]
	ER = Error register [HEX]
	ST = Status register [HEX]
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.

Error 2 occurred at disk power-on lifetime: 4242 hours (176 days + 18 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 00 ff ff ff 0f  Error: UNC at LBA = 0x0fffffff = 268435455

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 00 00 ff ff ff 4f 00  15d+07:00:37.069  READ FPDMA QUEUED
  60 00 00 ff ff ff 4f 00  15d+07:00:37.059  READ FPDMA QUEUED
  60 00 00 ff ff ff 4f 00  15d+07:00:37.046  READ FPDMA QUEUED
  60 00 00 ff ff ff 4f 00  15d+07:00:37.037  READ FPDMA QUEUED
  60 00 00 ff ff ff 4f 00  15d+07:00:37.036  READ FPDMA QUEUED

Error 1 occurred at disk power-on lifetime: 3745 hours (156 days + 1 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 00 ff ff ff 0f  Error: UNC at LBA = 0x0fffffff = 268435455

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 00 00 ff ff ff 4f 00  31d+07:15:46.331  READ FPDMA QUEUED
  60 00 00 ff ff ff 4f 00  31d+07:15:46.330  READ FPDMA QUEUED
  60 00 00 ff ff ff 4f 00  31d+07:15:46.330  READ FPDMA QUEUED
  60 00 00 ff ff ff 4f 00  31d+07:15:46.329  READ FPDMA QUEUED
  60 00 00 ff ff ff 4f 00  31d+07:15:46.328  READ FPDMA QUEUED
Edited by willis
Link to comment
3 hours ago, willis said:

So after a couple of broken (or not) disks again (all replaced under warranty by seagate) I thought why not continue this thread. Today added my replaced 2nd parity disk and when rebuilding that parity disk another disk had the error status, here is the smart test: (short, the long version is still running)

 


ATA Error Count: 2
	CR = Command Register [HEX]
	FR = Features Register [HEX]
	SC = Sector Count Register [HEX]
	SN = Sector Number Register [HEX]
	CL = Cylinder Low Register [HEX]
	CH = Cylinder High Register [HEX]
	DH = Device/Head Register [HEX]
	DC = Device Command Register [HEX]
	ER = Error register [HEX]
	ST = Status register [HEX]
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.

Error 2 occurred at disk power-on lifetime: 4242 hours (176 days + 18 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 00 ff ff ff 0f  Error: UNC at LBA = 0x0fffffff = 268435455

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 00 00 ff ff ff 4f 00  15d+07:00:37.069  READ FPDMA QUEUED
  60 00 00 ff ff ff 4f 00  15d+07:00:37.059  READ FPDMA QUEUED
  60 00 00 ff ff ff 4f 00  15d+07:00:37.046  READ FPDMA QUEUED
  60 00 00 ff ff ff 4f 00  15d+07:00:37.037  READ FPDMA QUEUED
  60 00 00 ff ff ff 4f 00  15d+07:00:37.036  READ FPDMA QUEUED

Error 1 occurred at disk power-on lifetime: 3745 hours (156 days + 1 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 00 ff ff ff 0f  Error: UNC at LBA = 0x0fffffff = 268435455

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 00 00 ff ff ff 4f 00  31d+07:15:46.331  READ FPDMA QUEUED
  60 00 00 ff ff ff 4f 00  31d+07:15:46.330  READ FPDMA QUEUED
  60 00 00 ff ff ff 4f 00  31d+07:15:46.330  READ FPDMA QUEUED
  60 00 00 ff ff ff 4f 00  31d+07:15:46.329  READ FPDMA QUEUED
  60 00 00 ff ff ff 4f 00  31d+07:15:46.328  READ FPDMA QUEUED

 

Post the rest of the smart report. 

 

I'd like to see if there are accompanying SMART issues. 

 

The LBA is odd at 0x0fffffff.

Link to comment

smartctl 6.5 2016-05-07 r4318 [x86_64-linux-4.9.30-unRAID] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Seagate Archive HDD
Device Model:     ST8000AS0002-1NA17Z
Serial Number:    Z840PX0K
LU WWN Device Id: 5 000c50 0927261d8
Firmware Version: AR17
User Capacity:    8,001,563,222,016 bytes [8.00 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    5980 rpm
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   ACS-2, ACS-3 T13/2161-D revision 3b
SATA Version is:  SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:    Tue Oct 24 07:49:09 2017 CEST
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:  (0x82)    Offline data collection activity
                    was completed without error.
                    Auto Offline Data Collection: Enabled.
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:         (    0) seconds.
Offline data collection
capabilities:              (0x7b) SMART execute Offline immediate.
                    Auto Offline data collection on/off support.
                    Suspend Offline collection upon new
                    command.
                    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:      ( 942) minutes.
Conveyance self-test routine
recommended polling time:      (   2) minutes.
SCT capabilities:            (0x30b5)    SCT Status supported.
                    SCT Feature Control supported.
                    SCT Data Table 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   117   099   006    Pre-fail  Always       -       118814504
  3 Spin_Up_Time            0x0003   091   091   000    Pre-fail  Always       -       0
  4 Start_Stop_Count        0x0032   100   100   020    Old_age   Always       -       22
  5 Reallocated_Sector_Ct   0x0033   100   100   010    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x000f   056   055   030    Pre-fail  Always       -       1516262572060
  9 Power_On_Hours          0x0032   094   094   000    Old_age   Always       -       5779
 10 Spin_Retry_Count        0x0013   100   100   097    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   020    Old_age   Always       -       22
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   098   098   000    Old_age   Always       -       2
188 Command_Timeout         0x0032   100   099   000    Old_age   Always       -       1
189 High_Fly_Writes         0x003a   100   100   000    Old_age   Always       -       0
190 Airflow_Temperature_Cel 0x0022   071   058   045    Old_age   Always       -       29 (Min/Max 27/29)
191 G-Sense_Error_Rate      0x0032   100   100   000    Old_age   Always       -       0
192 Power-Off_Retract_Count 0x0032   095   095   000    Old_age   Always       -       11770
193 Load_Cycle_Count        0x0032   088   088   000    Old_age   Always       -       24626
194 Temperature_Celsius     0x0022   029   042   000    Old_age   Always       -       29 (0 21 0 0 0)
195 Hardware_ECC_Recovered  0x001a   117   099   000    Old_age   Always       -       118814504
197 Current_Pending_Sector  0x0012   100   100   000    Old_age   Always       -       8
198 Offline_Uncorrectable   0x0010   100   100   000    Old_age   Offline      -       8
199 UDMA_CRC_Error_Count    0x003e   200   193   000    Old_age   Always       -       12
240 Head_Flying_Hours       0x0000   100   253   000    Old_age   Offline      -       3260 (6 125 0)
241 Total_LBAs_Written      0x0000   100   253   000    Old_age   Offline      -       36254910880
242 Total_LBAs_Read         0x0000   100   253   000    Old_age   Offline      -       339594453127

SMART Error Log Version: 1
ATA Error Count: 2
    CR = Command Register [HEX]
    FR = Features Register [HEX]
    SC = Sector Count Register [HEX]
    SN = Sector Number Register [HEX]
    CL = Cylinder Low Register [HEX]
    CH = Cylinder High Register [HEX]
    DH = Device/Head Register [HEX]
    DC = Device Command Register [HEX]
    ER = Error register [HEX]
    ST = Status register [HEX]
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.

Error 2 occurred at disk power-on lifetime: 4242 hours (176 days + 18 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 00 ff ff ff 0f  Error: UNC at LBA = 0x0fffffff = 268435455

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 00 00 ff ff ff 4f 00  15d+07:00:37.069  READ FPDMA QUEUED
  60 00 00 ff ff ff 4f 00  15d+07:00:37.059  READ FPDMA QUEUED
  60 00 00 ff ff ff 4f 00  15d+07:00:37.046  READ FPDMA QUEUED
  60 00 00 ff ff ff 4f 00  15d+07:00:37.037  READ FPDMA QUEUED
  60 00 00 ff ff ff 4f 00  15d+07:00:37.036  READ FPDMA QUEUED

Error 1 occurred at disk power-on lifetime: 3745 hours (156 days + 1 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 00 ff ff ff 0f  Error: UNC at LBA = 0x0fffffff = 268435455

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 00 00 ff ff ff 4f 00  31d+07:15:46.331  READ FPDMA QUEUED
  60 00 00 ff ff ff 4f 00  31d+07:15:46.330  READ FPDMA QUEUED
  60 00 00 ff ff ff 4f 00  31d+07:15:46.330  READ FPDMA QUEUED
  60 00 00 ff ff ff 4f 00  31d+07:15:46.329  READ FPDMA QUEUED
  60 00 00 ff ff ff 4f 00  31d+07:15:46.328  READ FPDMA QUEUED

SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Extended offline    Completed: read failure       80%      5779         3747684768

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.

Link to comment

Drive is certainly showing some signs of failure, mainly the 8 pending sectors. This can't be caused by controllers - only the drive. Certainly that is a bad issue. Also seeing reporting uncorrect and a few other issues. The normalized value for the seek error rate is also weak. The drive is certainly not in great shape.

 

But I am also also seeing 12 CRC errors. This is caused by bad or loose cables. You should be using hot-swap cages, which once installed and burned in, virtually eliminate the chance of cabling issues as you add and replace drives. CRC errors do produce errors in unRaid, so may be associated with some symptoms you were seeing.

 

 

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.