Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

First Red ball

Featured Replies

I just had my first red ball drive.  I haven't touched the server so I'm pretty sure it's not a cable.  I was trying to delete a Music folder from it yesterday so not sure if that could be the issue.  It's showing 576 errors.  I attached the last part of the syslog.  Please help and tell me what I should do. 

 

I should also mention a Parity check just finished earlier today.

syslog-2014-11-01.txt

You should be able to access the disk from a client machine. (e.g., //tower/disk4). It is being simulated by parity and the other disks in the array. I always like to make sure I can access the simulated disk. If there is some absolutely critical data you want from the machine, now is a good time to grab it. Your chance of data loss is low, but this is the time to copy those priceless family pictures if you don't have a backup!

 

After that quick check and any emergency copying, stop the array.

 

Take a copy of the complete syslog if you don't already have it.

 

Take a backup of your flash config directory (with server stopped). Its unlikely you will need it but under some unusual conditions it could come in handy.

 

Reboot.

 

The disk will NOT be re-inserted into the array, but you should now be able to grab a smart report for the drive.

 

Post the smart report.

 

I had a similar issue recently. See HERE.

  • Author

can you remind me how to get a smart report.  It's been a long time

Try ...

 

smartctl -a -d ata /dev/sdZ

 

and if that doesn't work try ...

 

smartctl -a -A /dev/sdZ

 

Where sdZ is the drive's device ID (should find on the unRAID main page).

  • Author

here it is, guessing it doesn't look good.  What are my options?  I don't have a replacement drive right now.

 

=== START OF INFORMATION SECTION ===
Model Family:     Seagate Barracuda 7200.14 (AF)
Device Model:     ST3000DM001-1CH166
Serial Number:    W1F1N8ZG
LU WWN Device Id: 5 000c50 05ce3c755
Firmware Version: CC24
User Capacity:    3,000,592,982,016 bytes [3.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: 3.0 Gb/s)
Local Time is:    Sat Nov  1 23:10:04 2014 EDT

==> 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: 		(  592) 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: 	 ( 334) 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   117   099   006    Pre-fail  Always       -       145775353
  3 Spin_Up_Time            0x0003   094   094   000    Pre-fail  Always       -       0
  4 Start_Stop_Count        0x0032   100   100   020    Old_age   Always       -       495
  5 Reallocated_Sector_Ct   0x0033   100   100   010    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x000f   071   060   030    Pre-fail  Always       -       4307710891
  9 Power_On_Hours          0x0032   081   081   000    Old_age   Always       -       16725
10 Spin_Retry_Count        0x0013   100   100   097    Pre-fail  Always       -       0
12 Power_Cycle_Count       0x0032   100   100   020    Old_age   Always       -       15
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   099   099   000    Old_age   Always       -       1
188 Command_Timeout         0x0032   100   100   000    Old_age   Always       -       0 0 0
189 High_Fly_Writes         0x003a   080   080   000    Old_age   Always       -       20
190 Airflow_Temperature_Cel 0x0022   072   064   045    Old_age   Always       -       28 (Min/Max 20/35)
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       -       8
193 Load_Cycle_Count        0x0032   074   074   000    Old_age   Always       -       52579
194 Temperature_Celsius     0x0022   028   040   000    Old_age   Always       -       28 (0 13 0 0 0)
197 Current_Pending_Sector  0x0012   100   100   000    Old_age   Always       -       24
198 Offline_Uncorrectable   0x0010   100   100   000    Old_age   Offline      -       24
199 UDMA_CRC_Error_Count    0x003e   200   200   000    Old_age   Always       -       0
240 Head_Flying_Hours       0x0000   100   253   000    Old_age   Offline      -       1543h+54m+48.588s
241 Total_LBAs_Written      0x0000   100   253   000    Old_age   Offline      -       50540982184
242 Total_LBAs_Read         0x0000   100   253   000    Old_age   Offline      -       256578376077

SMART Error Log Version: 1
ATA Error Count: 1
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 1 occurred at disk power-on lifetime: 16712 hours (696 days + 8 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 f0 ff ff ff 4f 00  20d+18:45:44.579  READ FPDMA QUEUED
  60 00 08 ff ff ff 4f 00  20d+18:45:44.579  READ FPDMA QUEUED
  60 00 00 ff ff ff 4f 00  20d+18:45:44.578  READ FPDMA QUEUED
  60 00 08 ff ff ff 4f 00  20d+18:45:44.577  READ FPDMA QUEUED
  60 00 a8 ff ff ff 4f 00  20d+18:45:44.575  READ FPDMA QUEUED

SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Short offline       Completed without error       00%        93         -
# 2  Short offline       Completed without error       00%        93         -

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.

root@Tower:~# 

Not so bad.

 

Appears you have a cabling problem, which should be easy to fix with a new SATA cable (or maybe just reseating the one you have).

 

Worse is 24 pending sectors. A pending sector means that the disk has identified a problem at that sector but it has not yet reallocated the sector. A preclear cycle on the disk might force the pending sectors to be reallocated, or I've even seen the pending sectors go away and never cause a problem.

 

If possible I think I'd replace the disk with a new or spare disk, and then run the preclear cycles on this one until the pending sectors are cleared or the problems get worse implying the disk is failing.

  • Author

How can it be a cable issue when I haven't touched it for months?  So I should try and reseat the cable and power it back on and do a parity check?

 

I don't have a spare drive to replace it with right now, I know I should but I was waiting for Christmas to get some more.

Cables can and do shake loose and go bad.

 

You could try rebuilding the disk on top of itself. The rebuild might very well clear the pending sectors or cause the remap to occur. I listed my first choice in the prior post, but in your situation I would likely re-secure (or replace) the SATA cable and then do a rebuild on top if itself.

 

To do the rebuild, you'd have to unassign the disk from the slot, start the array, stop the array, then reassign the disk to the slot, and then start the array. The rebuild should start. This shuffle is needed for force unRAID to forget that the problematic disk was ever in the slot, so that it is recognized as a different disk to do the rebuild onto.

  • Author

OK, I will try that.

 

Thanks for your help, I really appreciate it.

  • Author

It looks like it rebuilt the data OK, it's back to green.  I ran another smart report.  going run a parity check now

 

=== START OF INFORMATION SECTION ===
Model Family:     Seagate Barracuda 7200.14 (AF)
Device Model:     ST3000DM001-1CH166
Serial Number:    W1F1N8ZG
LU WWN Device Id: 5 000c50 05ce3c755
Firmware Version: CC24
User Capacity:    3,000,592,982,016 bytes [3.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: 3.0 Gb/s)
Local Time is:    Sun Nov  2 09:00:51 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: 		(  592) 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: 	 ( 334) 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   117   099   006    Pre-fail  Always       -       145791441
  3 Spin_Up_Time            0x0003   094   094   000    Pre-fail  Always       -       0
  4 Start_Stop_Count        0x0032   100   100   020    Old_age   Always       -       496
  5 Reallocated_Sector_Ct   0x0033   100   100   010    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x000f   071   060   030    Pre-fail  Always       -       4307754436
  9 Power_On_Hours          0x0032   081   081   000    Old_age   Always       -       16736
10 Spin_Retry_Count        0x0013   100   100   097    Pre-fail  Always       -       0
12 Power_Cycle_Count       0x0032   100   100   020    Old_age   Always       -       16
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   099   099   000    Old_age   Always       -       1
188 Command_Timeout         0x0032   100   100   000    Old_age   Always       -       0 0 0
189 High_Fly_Writes         0x003a   079   079   000    Old_age   Always       -       21
190 Airflow_Temperature_Cel 0x0022   074   064   045    Old_age   Always       -       26 (Min/Max 26/31)
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       -       8
193 Load_Cycle_Count        0x0032   074   074   000    Old_age   Always       -       52586
194 Temperature_Celsius     0x0022   026   040   000    Old_age   Always       -       26 (0 13 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      -       1553h+59m+38.043s
241 Total_LBAs_Written      0x0000   100   253   000    Old_age   Offline      -       56473835744
242 Total_LBAs_Read         0x0000   100   253   000    Old_age   Offline      -       256578376724

SMART Error Log Version: 1
ATA Error Count: 1
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 1 occurred at disk power-on lifetime: 16712 hours (696 days + 8 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 f0 ff ff ff 4f 00  20d+18:45:44.579  READ FPDMA QUEUED
  60 00 08 ff ff ff 4f 00  20d+18:45:44.579  READ FPDMA QUEUED
  60 00 00 ff ff ff 4f 00  20d+18:45:44.578  READ FPDMA QUEUED
  60 00 08 ff ff ff 4f 00  20d+18:45:44.577  READ FPDMA QUEUED
  60 00 a8 ff ff ff 4f 00  20d+18:45:44.575  READ FPDMA QUEUED

SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Short offline       Completed without error       00%        93         -
# 2  Short offline       Completed without error       00%        93         -

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.

root@Tower:~#                                                                                                      

 

All of the pending sectors are gone and none got remapped.

 

This is actually a relative common outcome of pending sectors - and it usually is not a sign of a failing disk.

 

Looks like all is well for the moment.

 

You should use myMain (gratuitous plug since I wrote it), or something else to monitor your smart data. Smart attributes often give warnings of upcoming failure and monitoring them in conjunction with monthly parity checks is the best way to avoid drive failures (i.e., gives you info to replace them before they physically fail).

  • Author

Thanks, makes me feel better.  I do use mymain but I don't always look at it since I don't really know what i'm looking at.

  • Author

Parity checked just finished with no errors.  Thanks again for the help bjp999

 

 

Archived

This topic is now archived and is closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.