Why are "Offline_Uncorrectable" sectors not remapped?

fillg1 · Nov 15, 2015

Hi folks
I have a ZFS raidz1 volume of three disks, one of the disks shows uncorrectable sectors

sudo smartctl -x /dev/ada1

Code:

smartctl 6.3 2014-07-26 r3976 [FreeBSD 9.3-RELEASE-p28 amd64] (local build)
Copyright (C) 2002-14, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Western Digital Caviar Green (AF)
Device Model:     WDC WD10EARS-00Z5B1
Serial Number:    WD-WMAVU2939857
LU WWN Device Id: 5 0014ee 6555e92c4
Firmware Version: 80.00A80
User Capacity:    1,000,204,886,016 bytes [1.00 TB]
Sector Size:      512 bytes logical/physical
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   ATA8-ACS (minor revision not indicated)
SATA Version is:  SATA 2.6, 3.0 Gb/s
Local Time is:    Sun Nov 15 09:30:36 2015 CET
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
AAM level is:     128 (quiet), recommended: 128
APM feature is:   Unavailable
Rd look-ahead is: Enabled
Write cache is:   Enabled
ATA Security is:  Disabled, frozen [SEC2]
Wt Cache Reorder: 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:      ( 114)	The previous self-test completed having
					the read element of the test failed.
Total time to complete Offline 
data collection: 		(27480) 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: 	 (   2) minutes.
Extended self-test routine
recommended polling time: 	 ( 315) minutes.
Conveyance self-test routine
recommended polling time: 	 (   5) minutes.
SCT capabilities: 	       (0x3031)	SCT Status supported.
					SCT Feature Control supported.
					SCT Data Table supported.

SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAGS    VALUE WORST THRESH FAIL RAW_VALUE
  1 Raw_Read_Error_Rate     POSR-K   200   200   051    -    0
  3 Spin_Up_Time            POS--K   185   180   021    -    5733
  4 Start_Stop_Count        -O--CK   100   100   000    -    953
  5 Reallocated_Sector_Ct   PO--CK   200   200   140    -    0
  7 Seek_Error_Rate         -OSR-K   200   200   000    -    0
  9 Power_On_Hours          -O--CK   093   093   000    -    5161
 10 Spin_Retry_Count        -O--CK   100   100   000    -    0
 11 Calibration_Retry_Count -O--CK   100   253   000    -    0
 12 Power_Cycle_Count       -O--CK   100   100   000    -    77
192 Power-Off_Retract_Count -O--CK   200   200   000    -    41
193 Load_Cycle_Count        -O--CK   182   182   000    -    54793
194 Temperature_Celsius     -O---K   116   102   000    -    34
196 Reallocated_Event_Count -O--CK   200   200   000    -    0
197 Current_Pending_Sector  -O--CK   200   200   000    -    5
198 Offline_Uncorrectable   ----CK   200   200   000    -    5
199 UDMA_CRC_Error_Count    -O--CK   200   200   000    -    0
200 Multi_Zone_Error_Rate   ---R--   200   200   000    -    1
                            ||||||_ K auto-keep
                            |||||__ C event count
                            ||||___ R error rate
                            |||____ S speed/performance
                            ||_____ O updated online
                            |______ P prefailure warning

General Purpose Log Directory Version 1
SMART           Log Directory Version 1 [multi-sector log support]
Address    Access  R/W   Size  Description
0x00       GPL,SL  R/O      1  Log Directory
0x01           SL  R/O      1  Summary SMART error log
0x02           SL  R/O      5  Comprehensive SMART error log
0x03       GPL     R/O      6  Ext. Comprehensive SMART error log
0x06           SL  R/O      1  SMART self-test log
0x07       GPL     R/O      1  Extended self-test log
0x09           SL  R/W      1  Selective self-test log
0x10       GPL     R/O      1  NCQ Command Error log
0x11       GPL     R/O      1  SATA Phy Event Counters
0x80-0x9f  GPL,SL  R/W     16  Host vendor specific log
0xa0-0xa7  GPL,SL  VS      16  Device vendor specific log
0xa8-0xb7  GPL,SL  VS       1  Device vendor specific log
0xc0       GPL,SL  VS       1  Device vendor specific log
0xc1       GPL     VS      93  Device vendor specific log
0xe0       GPL,SL  R/W      1  SCT Command/Status
0xe1       GPL,SL  R/W      1  SCT Data Transfer

SMART Extended Comprehensive Error Log Version: 1 (6 sectors)
Device Error Count: 240 (device log contains only the most recent 24 errors)
	CR     = Command Register
	FEATR  = Features Register
	COUNT  = Count (was: Sector Count) Register
	LBA_48 = Upper bytes of LBA High/Mid/Low Registers ]  ATA-8
	LH     = LBA High (was: Cylinder High) Register    ]   LBA
	LM     = LBA Mid (was: Cylinder Low) Register      ] Register
	LL     = LBA Low (was: Sector Number) Register     ]
	DV     = Device (was: Device/Head) Register
	DC     = Device Control Register
	ER     = Error register
	ST     = Status register
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 240 [23] occurred at disk power-on lifetime: 5151 hours (214 days + 15 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER -- ST COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  40 -- 51 00 10 00 00 74 70 68 90 40 00  Error: UNC at LBA = 0x74706890 = 1953523856

  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  60 00 10 00 a8 00 00 74 70 68 90 40 08     04:59:35.037  READ FPDMA QUEUED
  2f 00 00 00 01 00 00 00 00 00 10 40 08     04:59:35.036  READ LOG EXT
  60 00 10 00 a8 00 00 74 70 68 90 40 08     04:59:31.920  READ FPDMA QUEUED
  2f 00 00 00 01 00 00 00 00 00 10 40 08     04:59:31.919  READ LOG EXT
  60 00 10 00 a8 00 00 74 70 68 90 40 08     04:59:28.803  READ FPDMA QUEUED

Error 239 [22] occurred at disk power-on lifetime: 5151 hours (214 days + 15 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER -- ST COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  40 -- 51 00 10 00 00 74 70 68 90 40 00  Error: UNC at LBA = 0x74706890 = 1953523856

  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  60 00 10 00 a8 00 00 74 70 68 90 40 08     04:59:31.920  READ FPDMA QUEUED
  2f 00 00 00 01 00 00 00 00 00 10 40 08     04:59:31.919  READ LOG EXT
  60 00 10 00 a8 00 00 74 70 68 90 40 08     04:59:28.803  READ FPDMA QUEUED
  2f 00 00 00 01 00 00 00 00 00 10 40 08     04:59:28.802  READ LOG EXT
  60 00 10 00 a8 00 00 74 70 68 90 40 08     04:59:25.686  READ FPDMA QUEUED

Error 238 [21] occurred at disk power-on lifetime: 5151 hours (214 days + 15 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER -- ST COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  40 -- 51 00 10 00 00 74 70 68 90 40 00  Error: UNC at LBA = 0x74706890 = 1953523856

  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  60 00 10 00 a8 00 00 74 70 68 90 40 08     04:59:28.803  READ FPDMA QUEUED
  2f 00 00 00 01 00 00 00 00 00 10 40 08     04:59:28.802  READ LOG EXT
  60 00 10 00 a8 00 00 74 70 68 90 40 08     04:59:25.686  READ FPDMA QUEUED
  2f 00 00 00 01 00 00 00 00 00 10 40 08     04:59:25.685  READ LOG EXT
  61 00 10 00 a8 00 00 74 70 6a 90 40 08     04:59:22.594  WRITE FPDMA QUEUED

Error 237 [20] occurred at disk power-on lifetime: 5151 hours (214 days + 15 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER -- ST COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  40 -- 51 00 10 00 00 74 70 68 90 40 00  Error: UNC at LBA = 0x74706890 = 1953523856

  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  60 00 10 00 a8 00 00 74 70 68 90 40 08     04:59:25.686  READ FPDMA QUEUED
  2f 00 00 00 01 00 00 00 00 00 10 40 08     04:59:25.685  READ LOG EXT
  61 00 10 00 a8 00 00 74 70 6a 90 40 08     04:59:22.594  WRITE FPDMA QUEUED
  61 00 10 00 a8 00 00 00 40 02 90 40 08     04:59:22.568  WRITE FPDMA QUEUED
  60 00 10 00 a0 00 00 74 70 6a 90 40 08     04:59:22.556  READ FPDMA QUEUED

Error 236 [19] occurred at disk power-on lifetime: 5151 hours (214 days + 15 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER -- ST COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  40 -- 51 00 10 00 00 74 70 68 90 40 00  Error: WP at LBA = 0x74706890 = 1953523856

  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  61 00 10 00 a8 00 00 74 70 6a 90 40 08     04:59:22.594  WRITE FPDMA QUEUED
  61 00 10 00 a8 00 00 00 40 02 90 40 08     04:59:22.568  WRITE FPDMA QUEUED
  60 00 10 00 a0 00 00 74 70 6a 90 40 08     04:59:22.556  READ FPDMA QUEUED
  60 00 10 00 98 00 00 74 70 68 90 40 08     04:59:22.556  READ FPDMA QUEUED
  60 00 10 00 90 00 00 00 40 02 90 40 08     04:59:22.556  READ FPDMA QUEUED

Error 235 [18] occurred at disk power-on lifetime: 5146 hours (214 days + 10 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER -- ST COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  40 -- 51 01 00 00 00 74 70 68 90 40 00  Error: UNC at LBA = 0x74706890 = 1953523856

  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  60 01 00 00 88 00 00 74 70 68 00 40 08     00:05:15.512  READ FPDMA QUEUED
  2f 00 00 00 01 00 00 00 00 00 10 40 08     00:05:15.433  READ LOG EXT
  60 01 00 00 88 00 00 74 70 68 00 40 08     00:05:12.305  READ FPDMA QUEUED
  2f 00 00 00 01 00 00 00 00 00 10 40 08     00:05:12.220  READ LOG EXT
  60 01 00 00 88 00 00 74 70 68 00 40 08     00:05:09.084  READ FPDMA QUEUED

Error 234 [17] occurred at disk power-on lifetime: 5146 hours (214 days + 10 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER -- ST COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  40 -- 51 01 00 00 00 74 70 68 90 40 00  Error: UNC at LBA = 0x74706890 = 1953523856

  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  60 01 00 00 88 00 00 74 70 68 00 40 08     00:05:12.305  READ FPDMA QUEUED
  2f 00 00 00 01 00 00 00 00 00 10 40 08     00:05:12.220  READ LOG EXT
  60 01 00 00 88 00 00 74 70 68 00 40 08     00:05:09.084  READ FPDMA QUEUED
  2f 00 00 00 01 00 00 00 00 00 10 40 08     00:05:09.007  READ LOG EXT
  60 01 00 00 88 00 00 74 70 68 00 40 08     00:05:05.877  READ FPDMA QUEUED

Error 233 [16] occurred at disk power-on lifetime: 5146 hours (214 days + 10 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER -- ST COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  40 -- 51 01 00 00 00 74 70 68 90 40 00  Error: UNC at LBA = 0x74706890 = 1953523856

  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  60 01 00 00 88 00 00 74 70 68 00 40 08     00:05:09.084  READ FPDMA QUEUED
  2f 00 00 00 01 00 00 00 00 00 10 40 08     00:05:09.007  READ LOG EXT
  60 01 00 00 88 00 00 74 70 68 00 40 08     00:05:05.877  READ FPDMA QUEUED
  2f 00 00 00 01 00 00 00 00 00 10 40 08     00:05:05.794  READ LOG EXT
  60 01 00 00 88 00 00 74 70 68 00 40 08     00:05:02.683  READ FPDMA QUEUED

SMART Extended Self-test Log Version: 1 (1 sectors)
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Extended offline    Completed: read failure       20%      5160         1953523856
# 2  Short offline       Completed: read failure       10%      5156         1953523856
# 3  Short offline       Completed: read failure       60%      5140         1953523856
# 4  Short offline       Completed: read failure       60%      5117         1953523856
# 5  Short offline       Completed: read failure       60%      5093         1953523856
# 6  Extended offline    Completed: read failure       20%      5076         1953523856
# 7  Short offline       Completed: read failure       60%      5069         1953523856
# 8  Short offline       Completed: read failure       60%      5045         1953523856
# 9  Short offline       Completed: read failure       60%      5021         1953523856
#10  Short offline       Completed: read failure       60%      4998         1953523856
#11  Extended offline    Completed: read failure       20%      4994         1953523856
#12  Short offline       Completed: read failure       60%      4974         1953523856
#13  Conveyance offline  Completed without error       00%      4957         -
#14  Short offline       Completed without error       00%      4950         -
#15  Short offline       Completed without error       00%      4926         -
#16  Extended offline    Completed without error       00%      4909         -
#17  Short offline       Completed without error       00%      4902         -
#18  Short offline       Completed without error       00%      4880         -

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.

SCT Status Version:                  2
SCT Version (vendor specific):       258 (0x0102)
SCT Support Level:                   1
Device State:                        Active (0)
Current Temperature:                    34 Celsius
Power Cycle Min/Max Temperature:     23/38 Celsius
Lifetime    Min/Max Temperature:     34/48 Celsius
Under/Over Temperature Limit Count:   0/0

SCT Temperature History Version:     2
Temperature Sampling Period:         1 minute
Temperature Logging Interval:        1 minute
Min/Max recommended Temperature:      0/60 Celsius
Min/Max Temperature Limit:           -41/85 Celsius
Temperature History Size (Index):    478 (25)

Index    Estimated Time   Temperature Celsius
  26    2015-11-15 01:33    38  *******************
 ...    ..(165 skipped).    ..  *******************
 192    2015-11-15 04:19    38  *******************
 193    2015-11-15 04:20    37  ******************
 ...    ..(  3 skipped).    ..  ******************
 197    2015-11-15 04:24    37  ******************
 198    2015-11-15 04:25    36  *****************
 ...    ..(  8 skipped).    ..  *****************
 207    2015-11-15 04:34    36  *****************
 208    2015-11-15 04:35    35  ****************
 ...    ..(  8 skipped).    ..  ****************
 217    2015-11-15 04:44    35  ****************
 218    2015-11-15 04:45    34  ***************
 219    2015-11-15 04:46    34  ***************
 220    2015-11-15 04:47    35  ****************
 221    2015-11-15 04:48    34  ***************
 ...    ..(  3 skipped).    ..  ***************
 225    2015-11-15 04:52    34  ***************
 226    2015-11-15 04:53    38  *******************
 ...    ..(208 skipped).    ..  *******************
 435    2015-11-15 08:22    38  *******************
 436    2015-11-15 08:23    37  ******************
 ...    ..( 12 skipped).    ..  ******************
 449    2015-11-15 08:36    37  ******************
 450    2015-11-15 08:37    38  *******************
 ...    ..( 52 skipped).    ..  *******************
  25    2015-11-15 09:30    38  *******************

SCT Error Recovery Control command not supported

Device Statistics (GP Log 0x04) not supported

SATA Phy Event Counters (GP Log 0x11)
ID      Size     Value  Description
0x0001  2            0  Command failed due to ICRC error
0x0002  2            0  R_ERR response for data FIS
0x0003  2            0  R_ERR response for device-to-host data FIS
0x0004  2            0  R_ERR response for host-to-device data FIS
0x0005  2            0  R_ERR response for non-data FIS
0x0006  2            0  R_ERR response for device-to-host non-data FIS
0x0007  2            0  R_ERR response for host-to-device non-data FIS
0x000a  2            2  Device-to-host register FISes sent due to a COMRESET
0x000b  2            0  CRC errors within host-to-device FIS
0x8000  4        52147  Vendor specific

zpool -v status

Code:

  pool: Data
 state: ONLINE
  scan: scrub repaired 0 in 4h56m with 0 errors on Sun Nov 15 04:57:17 2015
config:

	NAME                                            STATE     READ WRITE CKSUM
	Data                                            ONLINE       0     0     0
	  raidz1-0                                      ONLINE       0     0     0
	    gptid/73a0c542-d524-11e4-9d3e-001999791cf9  ONLINE       0     0     0
	    gptid/748248f6-d524-11e4-9d3e-001999791cf9  ONLINE       0     0     0
	    gptid/7501a3a0-d524-11e4-9d3e-001999791cf9  ONLINE       0     0     0

errors: No known data errors

  pool: System
 state: ONLINE
  scan: scrub repaired 0 in 3h20m with 0 errors on Wed Nov 11 03:20:16 2015
config:

	NAME                                          STATE     READ WRITE CKSUM
	System                                        ONLINE       0     0     0
	  gptid/5ddd523c-352d-11e4-993d-001999791cf9  ONLINE       0     0     0

errors: No known data errors

  pool: freenas-boot
 state: ONLINE
  scan: scrub repaired 0 in 0h7m with 0 errors on Thu Oct 22 23:09:57 2015
config:

	NAME        STATE     READ WRITE CKSUM
	freenas-boot  ONLINE       0     0     0
	  da0p2     ONLINE       0     0     0

errors: No known data errors

Since thrre are only a few bad sectors, why are'nt these sectors remapped by the drives firmware ?
I've tried to force a remap using dd as suggested here, but no success.

Should I replace this disk ?

hugovsky · Nov 15, 2015

fillg1 said:
Should I replace this disk ?

You should. Your disk is failing.

jgreco · Nov 15, 2015

fillg1 said:
Since thrre are only a few bad sectors, why are'nt these sectors remapped by the drives firmware ?

Because that's not how it works. Drives shouldn't do that. What happens if it just magically remaps the MBR to a new (blank) sector? Reporting a read error is what's supposed to happen if the drive can't read the sector.

I've tried to force a remap using dd as suggested here, but no success.

Did you do it right? The big trick is that you need to remember that the LBA reported by the disk is sometimes a little dodgy, and when you start to consider issues like disk partitioning, playing find-the-actual-offset becomes this strange thing where arrogance about proficiency and experience sometimes knifes you in the back.

So what I usually like to do is to probe around and see if I can determine the bad sector with dd. Yours is at LBA 1953523856 on a disk with 512 byte sectors. Try this:

# dd if=/dev/da${foo} of=/dev/null bs=512 skip=1953520000

Now hopefully it craps out and kicks out something like "3856 records in". Add that number to the "skip" and repeat.

# dd if=/dev/da${foo} of=/dev/null bs=512 skip=1953523856

Now you want to see a "0 records in" there, which means that sector is not reading. If not, figure out your mistake.

Next you can try a very specific nuke of that sector.

# dd if=/dev/zero of=/dev/da${foo} bs=512 count=1 seek=1953523856

Make DAMN sure you have the "count=1" in there. Then go back to the previous read dd's and see if it now reads the sector. If it does, it'll just keep plowing on, which you want to do to test the rest of the disk anyways. If you are on the console, you can use control-T to see dd's status.

Should I replace this disk ?

If you can't force it to remap the sector by writing to it, yes. This doesn't look like that, yet, though.

mav@ · Nov 15, 2015

As I understand, this disk has Advanced Format (4K physical sectors). For that reason writes for remapping should be 4K instead of 512 in size. Just be careful that dd specifies offsets in blocks, so if you set bs=4K, you'll have to recalculate offsets respectively.

jgreco · Nov 15, 2015

Interesting, it says 512, but, yes, if so, that's correct.

danb35 · Nov 15, 2015

Unrelated to the subject of this thread, but your SMART data shows the load cycle count is awfully high. Check into using wdidle3.exe to take care of that.

fillg1 · Nov 15, 2015

Thanks for your help

jgreco said:
Interesting, it says 512, but, yes, if so, that's correct.

I am a little bit confused, does this mean to use
# dd if=/dev/zero of=/dev/ada1 bs=512 count=8 seek=1953523856

??

mav@ · Nov 15, 2015

fillg1 said:
I am a little bit confused, does this mean to use
# dd if=/dev/zero of=/dev/ada1 bs=512 count=8 seek=1953523856 ??

No. This may not work, since dd will send 8 separate 512-byte write requests, and attempt to handle each of them separately by disk may fail. It is better to do:
# dd if=/dev/zero of=/dev/ada1 bs=4k count=1 seek=244190482

fillg1 · Nov 15, 2015

danb35 said:
Unrelated to the subject of this thread, but your SMART data shows the load cycle count is awfully high. Check into using wdidle3.exe to take care of that.

Should I increase the HDD standby time?

fillg1 · Nov 15, 2015

Hey, the number of Current_Pending_Sectors is decreasing

Thanks for your help !!!!

jgreco · Nov 15, 2015

fillg1 said:
Should I increase the HDD standby time?

Disable standby entirely if you can.

DrKK · Nov 15, 2015

jgreco said:
Disable standby entirely if you can.

No matter how many times we say it, ***EVERYONE*** seems to want to try to set up their drives to "spin down".

Awesome! by spinning down the drives, you have saved 18 cents per month in electricity, and have caused $40 of wear-and-tear to the drive! Good trade!
:)

jgreco · Nov 15, 2015

If you're desperate to hear the lovely sound of drives spinning up and down, I've got some failed drives that repeatedly do so while trying to get up to speed. Lovely whirrrr...click...whizzz... click click click... whoooorrrrriiiii.... click... whirrr.. repeat

Bidule0hm · Nov 15, 2015

jgreco said:
If you're desperate to hear the lovely sound of drives spinning up and down, I've got some failed drives that repeatedly do so while trying to get up to speed. Lovely whirrrr...click...whizzz... click click click... whoooorrrrriiiii.... click... whirrr.. repeat

Ok guys, I think we've definitely lost jgreco...

BigDave · Nov 15, 2015

Bidule0hm said:
Ok guys, I think we've definitely lost jgreco...

You're just envious of his ability to bring sounds accurately to the written page :p

jgreco · Nov 15, 2015

I can't do the 5.25" drives, those emit some sounds like writing on a chalkboard.

fillg1 · Nov 15, 2015

Like the good old ST-506? ;-)

jgreco · Nov 15, 2015

fillg1 said:
Like the good old ST-506? ;-)

Naw, I've got quite the collection of things that you could conceivably hook up to a modern system. The neat thing about SCSI is that there are PCI adapters for it, so that means I can probably dig up some old CDC Wren IV's (half the guys here weren't *born* when CDC sold itself off) or Micropolis 1936-21's ...

Ericloewe · Nov 16, 2015

BigDave said:
You're just envious of his ability to bring sounds accurately to the written page :p

jgreco said:
If you're desperate to hear the lovely sound of drives spinning up and down, I've got some failed drives that repeatedly do so while trying to get up to speed. Lovely whirrrr...click...whizzz... click click click... whoooorrrrriiiii.... click... whirrr.. repeat

jgreco · Nov 16, 2015

Still waiting for the sequel.

Important Announcement for the TrueNAS Community.

Why are "Offline_Uncorrectable" sectors not remapped?

Dabbler

Guru

Resident Grinch

iXsystems

Resident Grinch

Hall of Famer

Dabbler

iXsystems

Dabbler

Dabbler

Resident Grinch

FreeNAS Generalissimo

Resident Grinch

Server Electronics Sorcerer

FreeNAS Enthusiast

Resident Grinch

Dabbler

Resident Grinch

Server Wrangler

Resident Grinch

Important Announcement for the TrueNAS Community.

Related topics on forums.truenas.com for thread: "Why are "Offline_Uncorrectable" sectors not remapped?"

Similar threads