Jump to content
jbuszkie

Preclear.sh results - Questions about your results? Post them here.

2840 posts in this topic Last Reply

Recommended Posts

I ran the disk one more time.  This is what I got:

 

S.M.A.R.T. error count differences detected after pre-clear

note, some 'raw' values may change, but not be an indication of a problem

57c57

< 1 Raw_Read_Error_Rate 0x000f 099 099 051 Pre-fail Always - 5005

---

> 1 Raw_Read_Error_Rate 0x000f 099 099 051 Pre-fail Always - 5264

66c66

< 13 Read_Soft_Error_Rate 0x000e 099 099 000 Old_age Always - 4648

---

> 13 Read_Soft_Error_Rate 0x000e 099 099 000 Old_age Always - 4912

69c69

< 187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 4952

---

> 187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 9596

71c71

< 190 Airflow_Temperature_Cel 0x0022 071 067 000 Old_age Always - 29 (Lifetime Min/Max 29/33)

---

> 190 Airflow_Temperature_Cel 0x0022 068 067 000 Old_age Always - 32 (Lifetime Min/Max 29/33)

74c74

< 197 Current_Pending_Sector 0x0012 092 092 000 Old_age Always - 331

---

> 197 Current_Pending_Sector 0x0012 100 092 000 Old_age Always - 0

78c78

< 201 Soft_Read_Error_Rate 0x000a 097 097 000 Old_age Always - 228

---

> 201 Soft_Read_Error_Rate 0x000a 100 097 000 Old_age Always - 0

============================================================================

 

The Current_Pending_Sector didn't go up..  But neither did the Reallocated_Sectors??  what Happened to the 331 previous pending?

Also the Raw_Read_Error_Rate and the Read_Soft_Error_Rate both went up.. but not as much as the first time.  However the Reported_Uncorrect almost doubled.

 

I also noted a bunch of errors in the syslog from the first time I ran the test (with both disks going)  Here is a snippit of the error:

Aug 23 16:20:49 Tower2 kernel: ata1.00: exception Emask 0x0 SAct 0x7 SErr 0x0 action 0x0
Aug 23 16:20:49 Tower2 kernel: ata1.00: irq_stat 0x40000008
Aug 23 16:20:49 Tower2 kernel: ata1.00: cmd 60/00:08:18:fa:a1/02:00:62:00:00/40 tag 1 ncq 262144 in
Aug 23 16:20:49 Tower2 kernel: res 41/40:60:b8:fa:a1/85:01:62:00:00/40 Emask 0x409 (media error) 
Aug 23 16:20:49 Tower2 kernel: ata1.00: status: { DRDY ERR }
Aug 23 16:20:49 Tower2 kernel: ata1.00: error: { UNC }
Aug 23 16:20:49 Tower2 kernel: ata1.00: configured for UDMA/133
Aug 23 16:20:49 Tower2 kernel: ata1: EH complete
Aug 23 16:20:49 Tower2 kernel: sd 1:0:0:0: [sda] 2930277168 512-byte hardware sectors (1500302 MB)
Aug 23 16:20:49 Tower2 kernel: sd 1:0:0:0: [sda] Write Protect is off
Aug 23 16:20:49 Tower2 kernel: sd 1:0:0:0: [sda] Mode Sense: 00 3a 00 00
Aug 23 16:20:49 Tower2 kernel: sd 1:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Aug 23 16:20:52 Tower2 kernel: ata1.00: exception Emask 0x0 SAct 0x7 SErr 0x0 action 0x0
Aug 23 16:20:52 Tower2 kernel: ata1.00: irq_stat 0x40000008
Aug 23 16:20:52 Tower2 kernel: ata1.00: cmd 60/00:08:18:fa:a1/02:00:62:00:00/40 tag 1 ncq 262144 in
Aug 23 16:20:52 Tower2 kernel: res 41/40:60:b8:fa:a1/85:01:62:00:00/40 Emask 0x409 (media error) 
Aug 23 16:20:52 Tower2 kernel: ata1.00: status: { DRDY ERR }
Aug 23 16:20:52 Tower2 kernel: ata1.00: error: { UNC }
Aug 23 16:20:52 Tower2 kernel: ata1.00: configured for UDMA/133
Aug 23 16:20:52 Tower2 kernel: ata1: EH complete
Aug 23 16:20:52 Tower2 kernel: sd 1:0:0:0: [sda] 2930277168 512-byte hardware sectors (1500302 MB)
Aug 23 16:20:52 Tower2 kernel: sd 1:0:0:0: [sda] Write Protect is off
Aug 23 16:20:52 Tower2 kernel: sd 1:0:0:0: [sda] Mode Sense: 00 3a 00 00
Aug 23 16:20:52 Tower2 kernel: sd 1:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Aug 23 16:20:55 Tower2 kernel: ata1.00: exception Emask 0x0 SAct 0x7 SErr 0x0 action 0x0
Aug 23 16:20:55 Tower2 kernel: ata1.00: irq_stat 0x40000008
Aug 23 16:20:55 Tower2 kernel: ata1.00: cmd 60/00:08:18:fa:a1/02:00:62:00:00/40 tag 1 ncq 262144 in
Aug 23 16:20:55 Tower2 kernel: res 41/40:60:b8:fa:a1/85:01:62:00:00/40 Emask 0x409 (media error) 
Aug 23 16:20:55 Tower2 kernel: ata1.00: status: { DRDY ERR }
Aug 23 16:20:55 Tower2 kernel: ata1.00: error: { UNC }
Aug 23 16:20:55 Tower2 kernel: ata1.00: configured for UDMA/133
Aug 23 16:20:55 Tower2 kernel: ata1: EH complete
Aug 23 16:20:55 Tower2 kernel: sd 1:0:0:0: [sda] 2930277168 512-byte hardware sectors (1500302 MB)
Aug 23 16:20:55 Tower2 kernel: sd 1:0:0:0: [sda] Write Protect is off
Aug 23 16:20:55 Tower2 kernel: sd 1:0:0:0: [sda] Mode Sense: 00 3a 00 00
Aug 23 16:20:55 Tower2 kernel: sd 1:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Aug 23 16:20:57 Tower2 kernel: ata1.00: exception Emask 0x0 SAct 0x7 SErr 0x0 action 0x0
Aug 23 16:20:57 Tower2 kernel: ata1.00: irq_stat 0x40000008
Aug 23 16:20:57 Tower2 kernel: ata1.00: cmd 60/00:08:18:fa:a1/02:00:62:00:00/40 tag 1 ncq 262144 in
Aug 23 16:20:57 Tower2 kernel: res 41/40:60:b8:fa:a1/85:01:62:00:00/40 Emask 0x409 (media error) 
Aug 23 16:20:57 Tower2 kernel: ata1.00: status: { DRDY ERR }
Aug 23 16:20:57 Tower2 kernel: ata1.00: error: { UNC }
Aug 23 16:20:57 Tower2 kernel: ata1.00: configured for UDMA/133
Aug 23 16:20:57 Tower2 kernel: ata1: EH complete
Aug 23 16:20:57 Tower2 kernel: sd 1:0:0:0: [sda] 2930277168 512-byte hardware sectors (1500302 MB)
Aug 23 16:20:57 Tower2 kernel: sd 1:0:0:0: [sda] Write Protect is off
Aug 23 16:20:57 Tower2 kernel: sd 1:0:0:0: [sda] Mode Sense: 00 3a 00 00
Aug 23 16:20:57 Tower2 kernel: sd 1:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Aug 23 16:21:00 Tower2 kernel: ata1.00: exception Emask 0x0 SAct 0x7 SErr 0x0 action 0x0
Aug 23 16:21:00 Tower2 kernel: ata1.00: irq_stat 0x40000008
Aug 23 16:21:00 Tower2 kernel: ata1.00: cmd 60/00:08:18:fa:a1/02:00:62:00:00/40 tag 1 ncq 262144 in
Aug 23 16:21:00 Tower2 kernel: res 41/40:60:b8:fa:a1/85:01:62:00:00/40 Emask 0x409 (media error) 
Aug 23 16:21:00 Tower2 kernel: ata1.00: status: { DRDY ERR }
Aug 23 16:21:00 Tower2 kernel: ata1.00: error: { UNC }
Aug 23 16:21:00 Tower2 kernel: ata1.00: configured for UDMA/133
Aug 23 16:21:00 Tower2 kernel: ata1: EH complete
Aug 23 16:21:00 Tower2 kernel: sd 1:0:0:0: [sda] 2930277168 512-byte hardware sectors (1500302 MB)
Aug 23 16:21:00 Tower2 kernel: sd 1:0:0:0: [sda] Write Protect is off
Aug 23 16:21:00 Tower2 kernel: sd 1:0:0:0: [sda] Mode Sense: 00 3a 00 00
Aug 23 16:21:00 Tower2 kernel: sd 1:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Aug 23 16:21:03 Tower2 kernel: ata1.00: exception Emask 0x0 SAct 0x7 SErr 0x0 action 0x0
Aug 23 16:21:03 Tower2 kernel: ata1.00: irq_stat 0x40000008
Aug 23 16:21:03 Tower2 kernel: ata1.00: cmd 60/00:08:18:fa:a1/02:00:62:00:00/40 tag 1 ncq 262144 in
Aug 23 16:21:03 Tower2 kernel: res 41/40:60:b8:fa:a1/85:01:62:00:00/40 Emask 0x409 (media error) 
Aug 23 16:21:03 Tower2 kernel: ata1.00: status: { DRDY ERR }
Aug 23 16:21:03 Tower2 kernel: ata1.00: error: { UNC }
Aug 23 16:21:03 Tower2 kernel: ata1.00: configured for UDMA/133
Aug 23 16:21:03 Tower2 kernel: sd 1:0:0:0: [sda] Result: hostbyte=0x00 driverbyte=0x08
Aug 23 16:21:03 Tower2 kernel: sd 1:0:0:0: [sda] Sense Key : 0x3 [current] [descriptor]
Aug 23 16:21:03 Tower2 kernel: Descriptor sense data with sense descriptors (in hex):
Aug 23 16:21:03 Tower2 kernel: 72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00 
Aug 23 16:21:03 Tower2 kernel: 62 a1 fa b8 
Aug 23 16:21:03 Tower2 kernel: sd 1:0:0:0: [sda] ASC=0x11 ASCQ=0x4
Aug 23 16:21:03 Tower2 kernel: end_request: I/O error, dev sda, sector 1654782648
Aug 23 16:21:03 Tower2 kernel: Buffer I/O error on device sda, logical block 206847831
Aug 23 16:21:03 Tower2 kernel: Buffer I/O error on device sda, logical block 206847832
Aug 23 16:21:03 Tower2 kernel: Buffer I/O error on device sda, logical block 206847833
Aug 23 16:21:03 Tower2 kernel: Buffer I/O error on device sda, logical block 206847834
Aug 23 16:21:03 Tower2 kernel: Buffer I/O error on device sda, logical block 206847835
Aug 23 16:21:03 Tower2 kernel: Buffer I/O error on device sda, logical block 206847836
Aug 23 16:21:03 Tower2 kernel: Buffer I/O error on device sda, logical block 206847837
Aug 23 16:21:03 Tower2 kernel: Buffer I/O error on device sda, logical block 206847838
Aug 23 16:21:03 Tower2 kernel: Buffer I/O error on device sda, logical block 206847839
Aug 23 16:21:03 Tower2 kernel: ata1: EH complete
Aug 23 16:21:03 Tower2 kernel: sd 1:0:0:0: [sda] 2930277168 512-byte hardware sectors (1500302 MB)
Aug 23 16:21:03 Tower2 kernel: sd 1:0:0:0: [sda] Write Protect is off
Aug 23 16:21:03 Tower2 kernel: sd 1:0:0:0: [sda] Mode Sense: 00 3a 00 00
Aug 23 16:21:03 Tower2 kernel: sd 1:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA

  Full syslog attached except for a bug chunk in the middle I had to cut out to make the attacment the right size.

 

It seems like there were a lot less errors the second time around.  Now is this still an RMA canidate or do you think this might be a MB error? (It's new too)

 

I'm running one more cycle

 

Thanks,

 

Jim

 

 

 

 

 

Share this post


Link to post

I still don't like what the disk is doing.  Far too many uncorrectable errors, and they seem to be continuing.

 

From what it appears, the pending-reallocation sectors were successfully written in their original locations and not re-allocated... interesting.

 

Joe L.

Share this post


Link to post

Can someone please tell me if my results are ok for my new drive?

Anyone know if this is ok. It looks ok, but I want to be sure because it will be my parity drive.

What is the thing I need to look at in the pre-clear results to determine if there were issues with the drive?

 

 

Aug 26 04:59:06 Tower preclear_disk-finish[22859]: smartctl version 5.38 [i486-slackware-linux-gnu] Copyright © 2002-8 Bruce Allen

Aug 26 04:59:06 Tower preclear_disk-finish[22859]: Home page is http://smartmontools.sourceforge.net/

Aug 26 04:59:06 Tower preclear_disk-finish[22859]:

Aug 26 04:59:06 Tower preclear_disk-finish[22859]: === START OF INFORMATION SECTION ===

Aug 26 04:59:06 Tower preclear_disk-finish[22859]: Device Model: WDC WD10EADS-00M2B0

Aug 26 04:59:06 Tower preclear_disk-finish[22859]: Serial Number: WD-WMAV50195436

Aug 26 04:59:06 Tower preclear_disk-finish[22859]: Firmware Version: 01.00A01

Aug 26 04:59:06 Tower preclear_disk-finish[22859]: User Capacity: 1,000,203,804,160 bytes

Aug 26 04:59:06 Tower preclear_disk-finish[22859]: Device is: Not in smartctl database [for details use: -P showall]

Aug 26 04:59:06 Tower preclear_disk-finish[22859]: ATA Version is: 8

Aug 26 04:59:06 Tower preclear_disk-finish[22859]: ATA Standard is: Exact ATA specification draft version not indicated

Aug 26 04:59:06 Tower preclear_disk-finish[22859]: Local Time is: Wed Aug 26 04:59:06 2009 GMT+4

Aug 26 04:59:06 Tower preclear_disk-finish[22859]: SMART support is: Available - device has SMART capability.

Aug 26 04:59:06 Tower preclear_disk-finish[22859]: SMART support is: Enabled

Aug 26 04:59:06 Tower preclear_disk-finish[22859]:

Aug 26 04:59:06 Tower preclear_disk-finish[22859]: === START OF READ SMART DATA SECTION ===

Aug 26 04:59:06 Tower preclear_disk-finish[22859]: SMART overall-health self-assessment test result: PASSED

Aug 26 04:59:06 Tower preclear_disk-finish[22859]:

Aug 26 04:59:06 Tower preclear_disk-finish[22859]: General SMART Values:

Aug 26 04:59:06 Tower preclear_disk-finish[22859]: Offline data collection status: (0x84)^IOffline data collection activity

Aug 26 04:59:06 Tower preclear_disk-finish[22859]: ^I^I^I^I^Iwas suspended by an interrupting command from host.

Aug 26 04:59:06 Tower preclear_disk-finish[22859]: ^I^I^I^I^IAuto Offline Data Collection: Enabled.

Aug 26 04:59:06 Tower preclear_disk-finish[22859]: Self-test execution status: ( 0)^IThe previous self-test routine completed

Aug 26 04:59:06 Tower preclear_disk-finish[22859]: ^I^I^I^I^Iwithout error or no self-test has ever

Aug 26 04:59:06 Tower preclear_disk-finish[22859]: ^I^I^I^I^Ibeen run.

Aug 26 04:59:06 Tower preclear_disk-finish[22859]: Total time to complete Offline

Aug 26 04:59:06 Tower preclear_disk-finish[22859]: data collection: ^I^I (19980) seconds.

Aug 26 04:59:06 Tower preclear_disk-finish[22859]: Offline data collection

Aug 26 04:59:06 Tower preclear_disk-finish[22859]: capabilities: ^I^I^I (0x7b) SMART execute Offline immediate.

Aug 26 04:59:06 Tower preclear_disk-finish[22859]: ^I^I^I^I^IAuto Offline data collection on/off support.

Aug 26 04:59:06 Tower preclear_disk-finish[22859]: ^I^I^I^I^ISuspend Offline collection upon new

Aug 26 04:59:06 Tower preclear_disk-finish[22859]: ^I^I^I^I^Icommand.

Aug 26 04:59:06 Tower preclear_disk-finish[22859]: ^I^I^I^I^IOffline surface scan supported.

Aug 26 04:59:06 Tower preclear_disk-finish[22859]: ^I^I^I^I^ISelf-test supported.

Aug 26 04:59:06 Tower preclear_disk-finish[22859]: ^I^I^I^I^IConveyance Self-test supported.

Aug 26 04:59:06 Tower preclear_disk-finish[22859]: ^I^I^I^I^ISelective Self-test supported.

Aug 26 04:59:06 Tower preclear_disk-finish[22859]: SMART capabilities: (0x0003)^ISaves SMART data before entering

Aug 26 04:59:06 Tower preclear_disk-finish[22859]: ^I^I^I^I^Ipower-saving mode.

Aug 26 04:59:06 Tower preclear_disk-finish[22859]: ^I^I^I^I^ISupports SMART auto save timer.

Aug 26 04:59:06 Tower preclear_disk-finish[22859]: Error logging capability: (0x01)^IError logging supported.

Aug 26 04:59:06 Tower preclear_disk-finish[22859]: ^I^I^I^I^IGeneral Purpose Logging supported.

Aug 26 04:59:06 Tower preclear_disk-finish[22859]: Short self-test routine

Aug 26 04:59:06 Tower preclear_disk-finish[22859]: recommended polling time: ^I ( 2) minutes.

Aug 26 04:59:06 Tower preclear_disk-finish[22859]: Extended self-test routine

Aug 26 04:59:06 Tower preclear_disk-finish[22859]: recommended polling time: ^I ( 230) minutes.

Aug 26 04:59:06 Tower preclear_disk-finish[22859]: Conveyance self-test routine

Aug 26 04:59:06 Tower preclear_disk-finish[22859]: recommended polling time: ^I ( 5) minutes.

Aug 26 04:59:06 Tower preclear_disk-finish[22859]: SCT capabilities: ^I (0x303f)^ISCT Status supported.

Aug 26 04:59:06 Tower preclear_disk-finish[22859]: ^I^I^I^I^ISCT Feature Control supported.

Aug 26 04:59:06 Tower preclear_disk-finish[22859]: ^I^I^I^I^ISCT Data Table supported.

Aug 26 04:59:06 Tower preclear_disk-finish[22859]:

Aug 26 04:59:06 Tower preclear_disk-finish[22859]: SMART Attributes Data Structure revision number: 16

Aug 26 04:59:06 Tower preclear_disk-finish[22859]: Vendor Specific SMART Attributes with Thresholds:

Aug 26 04:59:06 Tower preclear_disk-finish[22859]: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE

Aug 26 04:59:06 Tower preclear_disk-finish[22859]: 1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail Always - 0

Aug 26 04:59:06 Tower preclear_disk-finish[22859]: 3 Spin_Up_Time 0x0027 113 113 021 Pre-fail Always - 7308

Aug 26 04:59:06 Tower preclear_disk-finish[22859]: 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 18

Aug 26 04:59:06 Tower preclear_disk-finish[22859]: 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0

Aug 26 04:59:06 Tower preclear_disk-finish[22859]: 7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always - 0

Aug 26 04:59:06 Tower preclear_disk-finish[22859]: 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 15

Aug 26 04:59:06 Tower preclear_disk-finish[22859]: 10 Spin_Retry_Count 0x0032 100 253 000 Old_age Always - 0

Aug 26 04:59:06 Tower preclear_disk-finish[22859]: 11 Calibration_Retry_Count 0x0032 100 253 000 Old_age Always - 0

Aug 26 04:59:06 Tower preclear_disk-finish[22859]: 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 14

Aug 26 04:59:06 Tower preclear_disk-finish[22859]: 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 5

Aug 26 04:59:06 Tower preclear_disk-finish[22859]: 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 156

Aug 26 04:59:06 Tower preclear_disk-finish[22859]: 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0

Aug 26 04:59:06 Tower preclear_disk-finish[22859]: 197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 0

Aug 26 04:59:06 Tower preclear_disk-finish[22859]: 198 Offline_Uncorrectable 0x0030 100 253 000 Old_age Offline - 0

Aug 26 04:59:06 Tower preclear_disk-finish[22859]: 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0

Aug 26 04:59:06 Tower preclear_disk-finish[22859]: 200 Multi_Zone_Error_Rate 0x0008 100 253 000 Old_age Offline - 0

Aug 26 04:59:06 Tower preclear_disk-finish[22859]:

Aug 26 04:59:06 Tower preclear_disk-finish[22859]: SMART Error Log Version: 1

Aug 26 04:59:06 Tower preclear_disk-finish[22859]: No Errors Logged

Aug 26 04:59:06 Tower preclear_disk-finish[22859]:

Aug 26 04:59:06 Tower preclear_disk-finish[22859]: SMART Self-test log structure revision number 1

Aug 26 04:59:06 Tower preclear_disk-finish[22859]: No self-tests have been logged. [To run self-tests, use: smartctl -t]

Aug 26 04:59:06 Tower preclear_disk-finish[22859]:

Aug 26 04:59:06 Tower preclear_disk-finish[22859]:

Aug 26 04:59:06 Tower preclear_disk-finish[22859]: SMART Selective self-test log data structure revision number 1

Aug 26 04:59:06 Tower preclear_disk-finish[22859]: SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS

Aug 26 04:59:06 Tower preclear_disk-finish[22859]: 1 0 0 Not_testing

Aug 26 04:59:06 Tower preclear_disk-finish[22859]: 2 0 0 Not_testing

Aug 26 04:59:06 Tower preclear_disk-finish[22859]: 3 0 0 Not_testing

Aug 26 04:59:06 Tower preclear_disk-finish[22859]: 4 0 0 Not_testing

Aug 26 04:59:06 Tower preclear_disk-finish[22859]: 5 0 0 Not_testing

Aug 26 04:59:06 Tower preclear_disk-finish[22859]: Selective self-test flags (0x0):

Aug 26 04:59:06 Tower preclear_disk-finish[22859]: After scanning selected spans, do NOT read-scan remainder of disk.

Aug 26 04:59:06 Tower preclear_disk-finish[22859]: If Selective self-test is pending on power-up, resume after 0 minute delay.

Aug 26 04:59:06 Tower preclear_disk-finish[22859]:

 

Share this post


Link to post

If you didn't get any results when precear finished then your disk is good!  Also looking at the smart results you posted look great.

 

If you had issues you would have seen output along the lines of:

 

S.M.A.R.T. error count differences detected after pre-clear
note, some 'raw' values may change, but not be an indication of a problem
57c57
< 1 Raw_Read_Error_Rate 0x000f 099 099 051 Pre-fail Always - 5005
---
> 1 Raw_Read_Error_Rate 0x000f 099 099 051 Pre-fail Always - 5264
66c66
< 13 Read_Soft_Error_Rate 0x000e 099 099 000 Old_age Always - 4648
---
> 13 Read_Soft_Error_Rate 0x000e 099 099 000 Old_age Always - 4912
69c69
< 187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 4952
---
> 187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 9596
71c71
< 190 Airflow_Temperature_Cel 0x0022 071 067 000 Old_age Always - 29 (Lifetime Min/Max 29/33)
---
> 190 Airflow_Temperature_Cel 0x0022 068 067 000 Old_age Always - 32 (Lifetime Min/Max 29/33)
74c74
< 197 Current_Pending_Sector 0x0012 092 092 000 Old_age Always - 331
---
> 197 Current_Pending_Sector 0x0012 100 092 000 Old_age Always - 0
78c78
< 201 Soft_Read_Error_Rate 0x000a 097 097 000 Old_age Always - 228
---
> 201 Soft_Read_Error_Rate 0x000a 100 097 000 Old_age Always - 0

 

You probably got a "pre-clear was successful" or something like that..  Enjoy the new drive!

 

Share this post


Link to post

Can someone please tell me if my results are ok for my new drive?

Anyone know if this is ok. It looks ok, but I want to be sure because it will be my parity drive.

What is the thing I need to look at in the pre-clear results to determine if there were issues with the drive?

Look here for how to interpret your results:

http://en.wikipedia.org/wiki/Self-Monitoring,_Analysis,_and_Reporting_Technology#Known_ATA_S.M.A.R.T._attributes

 

As already described, your drive looks good.  it does not show uncorrectable errors.  But now you can verify for yourself.  ;D

Share this post


Link to post

Update

 

[sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA

 

Regarding the above, have enabled the write cache using "hdparm -W 1 /dev/sda" and able to get write speeds of 70-80 mb/s when preclearing. One 750Gb drive now preclears in 10 hours (the norm based on Joe's results) compared to 13 previously. However, I need to re-enable the write cache everytime I do a complete shutdown and bootup of the server. Would it be alright for me to add this line into the go script to be run each time at boot?

 

 

As for the squeaky hdd, have replaced it with a new one which doesn't squeaks. No point taking any chances.

 

Share this post


Link to post

Update

 

[sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA

 

Regarding the above, have enabled the write cache using "hdparm -W 1 /dev/sda" and able to get write speeds of 70-80 mb/s when preclearing. One 750Gb drive now preclears in 10 hours (the norm based on Joe's results) compared to 13 previously. However, I need to re-enable the write cache everytime I do a complete shutdown and bootup of the server. Would it be alright for me to add this line into the go script to be run each time at boot?

 

 

As for the squeaky hdd, have replaced it with a new one which doesn't squeaks. No point taking any chances.

 

It sounds as if your motherboard BIOS, (or disk controller) does not think there is any ability to use the hardware write-cache, but you know better.  ;D

I'd just add the line to the end of the "go" script, exactly as you said.

 

Glad you figured out how to enable the write-cache on your hardware. 

 

Also glad you got rid of the squeaky disk...  It can only indicate friction as parts rub on each other... and that is never good for a hard-disk.

 

Joe L.

Share this post


Link to post

Thanks Joe!  ;D

 

The drives were connected to a PCI Sata Raid card. I suspect that the raid bios turns off write cache by default to ensure data integrity in the event of power failure or something similar. Seems to be the most likely reason after googling around...

 

Share this post


Link to post

attached is my syslog with entries from running preclear.sh Version 0.9.3 on my new seagate 2tb ST32000542AS

 

I removed some mover entries for brevity

 

smartctl smartctl -a -d ata output before preclear.sh

 

=== START OF INFORMATION SECTION ===
Device Model:     ST32000542AS
Serial Number:    5XW05S2G
Firmware Version: CC34
User Capacity:    2,000,398,934,016 bytes
Device is:        Not in smartctl database [for details use: -P showall]
ATA Version is:   8
ATA Standard is:  ATA-8-ACS revision 4
Local Time is:    Wed Aug 26 20:13:17 2009 GMT+4
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: 		 ( 633) 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: 	 ( 255) minutes.
Conveyance self-test routine
recommended polling time: 	 (   2) minutes.
SCT capabilities: 	       (0x103f)	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   100   100   006    Pre-fail  Always       -       9991
  3 Spin_Up_Time            0x0003   100   100   000    Pre-fail  Always       -       0
  4 Start_Stop_Count        0x0032   100   100   020    Old_age   Always       -       3
  5 Reallocated_Sector_Ct   0x0033   100   100   036    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x000f   100   253   030    Pre-fail  Always       -       23
  9 Power_On_Hours          0x0032   100   100   000    Old_age   Always       -       0
10 Spin_Retry_Count        0x0013   100   100   097    Pre-fail  Always       -       0
12 Power_Cycle_Count       0x0032   100   100   020    Old_age   Always       -       3
183 Unknown_Attribute       0x0032   100   100   000    Old_age   Always       -       0
184 Unknown_Attribute       0x0032   100   100   099    Old_age   Always       -       0
187 Reported_Uncorrect      0x0032   100   100   000    Old_age   Always       -       0
188 Unknown_Attribute       0x0032   100   253   000    Old_age   Always       -       0
189 High_Fly_Writes         0x003a   100   100   000    Old_age   Always       -       0
190 Airflow_Temperature_Cel 0x0022   074   074   045    Old_age   Always       -       26 (Lifetime Min/Max 24/26)
194 Temperature_Celsius     0x0022   026   040   000    Old_age   Always       -       26 (0 24 0 0)
195 Hardware_ECC_Recovered  0x001a   100   100   000    Old_age   Always       -       9991
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   253   000    Old_age   Always       -       0
240 Head_Flying_Hours       0x0000   100   253   000    Old_age   Offline      -       194420284588039
241 Unknown_Attribute       0x0000   100   253   000    Old_age   Offline      -       0
242 Unknown_Attribute       0x0000   100   253   000    Old_age   Offline      -       1152

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.

 

smartctl -a -d ata ouput after preclear.sh

 

smartctl version 5.38 [i486-slackware-linux-gnu] Copyright (C) 2002-8 Bruce Allen
Home page is http://smartmontools.sourceforge.net/

=== START OF INFORMATION SECTION ===
Device Model:     ST32000542AS
Serial Number:    5XW05S2G
Firmware Version: CC34
User Capacity:    2,000,398,934,016 bytes
Device is:        Not in smartctl database [for details use: -P showall]
ATA Version is:   8
ATA Standard is:  ATA-8-ACS revision 4
Local Time is:    Fri Aug 28 11:45:36 2009 GMT+4
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: 		 ( 633) 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: 	 ( 255) minutes.
Conveyance self-test routine
recommended polling time: 	 (   2) minutes.
SCT capabilities: 	       (0x103f)	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   119   100   006    Pre-fail  Always       -       227959599
  3 Spin_Up_Time            0x0003   100   100   000    Pre-fail  Always       -       0
  4 Start_Stop_Count        0x0032   100   100   020    Old_age   Always       -       3
  5 Reallocated_Sector_Ct   0x0033   100   100   036    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x000f   100   253   030    Pre-fail  Always       -       122120
  9 Power_On_Hours          0x0032   100   100   000    Old_age   Always       -       39
10 Spin_Retry_Count        0x0013   100   100   097    Pre-fail  Always       -       0
12 Power_Cycle_Count       0x0032   100   100   020    Old_age   Always       -       3
183 Unknown_Attribute       0x0032   100   100   000    Old_age   Always       -       0
184 Unknown_Attribute       0x0032   100   100   099    Old_age   Always       -       0
187 Reported_Uncorrect      0x0032   100   100   000    Old_age   Always       -       0
188 Unknown_Attribute       0x0032   100   100   000    Old_age   Always       -       0
189 High_Fly_Writes         0x003a   100   100   000    Old_age   Always       -       0
190 Airflow_Temperature_Cel 0x0022   073   071   045    Old_age   Always       -       27 (Lifetime Min/Max 24/29)
194 Temperature_Celsius     0x0022   027   040   000    Old_age   Always       -       27 (0 24 0 0)
195 Hardware_ECC_Recovered  0x001a   051   051   000    Old_age   Always       -       227959599
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      -       27354646708252
241 Unknown_Attribute       0x0000   100   253   000    Old_age   Offline      -       3895294389
242 Unknown_Attribute       0x0000   100   253   000    Old_age   Offline      -       3703739875

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.

 

 

any comments appreciated

 

 

>   preclear_disk.sh - a new utility to burn-in and pre-clear disks for quick add

>   http://lime-technology.com/forum/index.php?topic=2817.0

>   ...

>   9. compares the SMART reports alerting you of differences.

 

I have been running preclear.sh directly from the console to avoid client telnet session disconnect ruining hours of a preclear attempt but presume a client telnet session is the only way to capture this output?

 

It would be nice if the SMART reports alert of differences was logged to syslog but I presume there's a reason why it isn't.

 

 

 

Share this post


Link to post

There is a program called screen.  It allows you to disconnect and reconnect to a particular session.

 

I have that setup and it works nicely.  there is a post somewhere that describes what you need..  You might be able to search the forums for it.

 

Also.. if you have mail setup..  you can use the mail parameters and it will e-mail you the differences as well..

 

Jim

Share this post


Link to post

It would be nice if the SMART reports alert of differences was logged to syslog but I presume there's a reason why it isn't.

New version of preclear_disk.sh does log the difference to the syslog.  There was no good reason not to, just did not think of it until you mentioned it.  Thanks for the suggestion. ;D

 

New 0.9.6 version has a few other improvements in reporting via e-mail (if you have a mail program configured on your server) and also reports drive temperature as the process is under way (in case the drive is overheating from lack of cooling air movement)

 

New version is attached to first post on original thread here

 

Joe L.

 

 

Share this post


Link to post

It would be nice if the SMART reports alert of differences was logged to syslog but I presume there's a reason why it isn't.

New version of preclear_disk.sh does log the difference to the syslog.  There was no good reason not to, just did not think of it until you mentioned it.   Thanks for the suggestion. ;D

 

New 0.9.6 version has a few other improvements in reporting via e-mail (if you have a mail program configured on your server) and also reports drive temperature as the process is under way (in case the drive is overheating from lack of cooling air movement)

 

New version is attached to first post on original thread here

 

Joe L.

 

 

 

Awesome, thanks very much!

Share this post


Link to post

I've just finished pre-clearing four drives; two seagate 1.5T's that were new, a Seagate 750G a few months old but hardly used and an older WD 500G drive.  Each and every one went through all ten steps, especially #7 where the pre-cleared flag is set on the drive, and all passed with no errors. 

 

Yes, when I review each of them with preclear_disk.sh -t, in every case it says the drive has NOT been pre-cleared!  This is with 0.9.3 of the script, and each were done separately (no concurrents).  There is also the statement that Partition 1 does not end on a cylinder boundary.

 

Any idea what might be going on?  Each of the processes ended with the diff display.  I do have the missing library for smartctl installed.

 

--Bill

Share this post


Link to post

I've just finished pre-clearing four drives; two seagate 1.5T's that were new, a Seagate 750G a few months old but hardly used and an older WD 500G drive.  Each and every one went through all ten steps, especially #7 where the pre-cleared flag is set on the drive, and all passed with no errors. 

 

Yes, when I review each of them with preclear_disk.sh -t, in every case it says the drive has NOT been pre-cleared!  This is with 0.9.3 of the script, and each were done separately (no concurrents).  There is also the statement that Partition 1 does not end on a cylinder boundary.

 

Any idea what might be going on?  Each of the processes ended with the diff display.  I do have the missing library for smartctl installed.

 

--Bill

To analyze what the script did, or did not do, please supply the output of the following two commands for each of the drives it says are not pre-cleared.

fdisk -l /dev/???

 

and

dd if=/dev/??? count=1 | od -x -A d

 

(substitute ? ? ? for your correct drive designation)

 

Joe L.

 

 

Share this post


Link to post

To analyze what the script did, or did not do, please supply the output of the following two commands for each of the drives it says are not pre-cleared.

fdisk -l /dev/???

 

and

dd if=/dev/??? count=1 | od -x -A d

 

(substitute ? ? ? for your correct drive designation)

 

Joe L.

Thanks Joe,  here it is:

 

Disk /dev/sde: 1500.3 GB, 1500301910016 bytes

1 heads, 63 sectors/track, 46512336 cylinders

Units = cylinders of 63 * 512 = 32256 bytes

Disk identifier: 0x00000000

 

  Device Boot      Start        End      Blocks  Id  System

/dev/sde1              2    46512336  1465138552+  83  Linux

Partition 1 does not end on cylinder boundary.

 

0000000 0000 0000 0000 0000 0000 0000 0000 0000

*

0000448 0000 0083 0000 003f 0000 7af1 aea8 0000

0000464 0000 0000 0000 0000 0000 0000 0000 0000

*

0000496 0000 0000 0000 0000 0000 0000 0000 aa55

0000512

 

 

Disk /dev/sdg: 1500.3 GB, 1500301910016 bytes

1 heads, 63 sectors/track, 46512336 cylinders

Units = cylinders of 63 * 512 = 32256 bytes

Disk identifier: 0x00000000

 

  Device Boot      Start        End      Blocks  Id  System

/dev/sdg1              2    46512336  1465138552+  83  Linux

Partition 1 does not end on cylinder boundary.

 

0000000 0000 0000 0000 0000 0000 0000 0000 0000

*

0000448 0000 0083 0000 003f 0000 7af1 aea8 0000

0000464 0000 0000 0000 0000 0000 0000 0000 0000

*

0000496 0000 0000 0000 0000 0000 0000 0000 aa55

0000512

 

 

Disk /dev/sdb: 750.1 GB, 750156374016 bytes

1 heads, 63 sectors/track, 23256336 cylinders

Units = cylinders of 63 * 512 = 32256 bytes

Disk identifier: 0x00000000

 

  Device Boot      Start        End      Blocks  Id  System

/dev/sdb1              2    23256336  732574552+  83  Linux

Partition 1 does not end on cylinder boundary.

 

0000000 0000 0000 0000 0000 0000 0000 0000 0000

*

0000448 0000 0083 0000 003f 0000 66b1 5754 0000

0000464 0000 0000 0000 0000 0000 0000 0000 0000

*

0000496 0000 0000 0000 0000 0000 0000 0000 aa55

0000512

 

 

--Bill

Share this post


Link to post

To analyze what the script did, or did not do, please supply the output of the following two commands for each of the drives it says are not pre-cleared.

fdisk -l /dev/???

 

and

dd if=/dev/??? count=1 | od -x -A d

 

(substitute ? ? ? for your correct drive designation)

 

Joe L.

Thanks Joe,  here it is:

 

Disk /dev/sde: 1500.3 GB, 1500301910016 bytes

1 heads, 63 sectors/track, 46512336 cylinders

Units = cylinders of 63 * 512 = 32256 bytes

Disk identifier: 0x00000000

 

   Device Boot      Start         End      Blocks   Id  System

/dev/sde1               2    46512336  1465138552+  83  Linux

Partition 1 does not end on cylinder boundary.

 

0000000 0000 0000 0000 0000 0000 0000 0000 0000

*

0000448 0000 0083 0000 003f 0000 7af1 aea8 0000

0000464 0000 0000 0000 0000 0000 0000 0000 0000

*

0000496 0000 0000 0000 0000 0000 0000 0000 aa55

0000512

 

 

Disk /dev/sdg: 1500.3 GB, 1500301910016 bytes

1 heads, 63 sectors/track, 46512336 cylinders

Units = cylinders of 63 * 512 = 32256 bytes

Disk identifier: 0x00000000

 

   Device Boot      Start         End      Blocks   Id  System

/dev/sdg1               2    46512336  1465138552+  83  Linux

Partition 1 does not end on cylinder boundary.

 

0000000 0000 0000 0000 0000 0000 0000 0000 0000

*

0000448 0000 0083 0000 003f 0000 7af1 aea8 0000

0000464 0000 0000 0000 0000 0000 0000 0000 0000

*

0000496 0000 0000 0000 0000 0000 0000 0000 aa55

0000512

 

 

Disk /dev/sdb: 750.1 GB, 750156374016 bytes

1 heads, 63 sectors/track, 23256336 cylinders

Units = cylinders of 63 * 512 = 32256 bytes

Disk identifier: 0x00000000

 

   Device Boot      Start         End      Blocks   Id  System

/dev/sdb1               2    23256336   732574552+  83  Linux

Partition 1 does not end on cylinder boundary.

 

0000000 0000 0000 0000 0000 0000 0000 0000 0000

*

0000448 0000 0083 0000 003f 0000 66b1 5754 0000

0000464 0000 0000 0000 0000 0000 0000 0000 0000

*

0000496 0000 0000 0000 0000 0000 0000 0000 aa55

0000512

 

 

--Bill

I'm not sure how you managed it, but all three have the file-system type set to "83" (linux) at offset 450.  This is not the normal value for a pre-cleared disk, but is what you would expect to find after a linux file system was created on the first partition.  With that value unRAID would be very likely to assume a reiserfs exists and not do anything to the drive as the remaining bytes all seem to match what would exist AFTER a formatting step had occurred and a reiserfs file-system created on the drives.

 

What did you do to the disks after you pre-cleared them?  Did you format them?  Did you attempt to mount them?  Did you use "fdisk" on them? Something put the "83" file system type byte in there for the first partition... and it was not the pre-clear script. 

 

Joe L.

Share this post


Link to post

I'm not sure how you managed it, but all three have the file-system type set to "83" (linux) at offset 450.  This is not the normal value for a pre-cleared disk, but is what you would expect to find after a linux file system was created on the first partition.   With that value unRAID would be very likely to assume a reiserfs exists and not do anything to the drive as the remaining bytes all seem to match what would exist AFTER a formatting step had occurred and a reiserfs file-system created on the drives.

 

What did you do to the disks after you pre-cleared them?  Did you format them?  Did you attempt to mount them?  Did you use "fdisk" on them? Something put the "83" file system type byte in there for the first partition... and it was not the pre-clear script.   

 

Joe L.

No, no fdisk.  I put them into their current device order, assigned them to their RAID role (disk1, disk3 and disk4 respectively) and started unRAID without a parity drive.  I did not format any drive or do any writing.  Shouldn't they have come up as unformatted in the Main menu?  None of them did.  Is the act of formatting in unRAID the only way the fs would get created (setting offset 83 to 83)?

 

I just finished pre-clearing another drive and this one does show pre-cleared with the -t option, and fdisk -l shows an ID of 0, and System=empty so as you said it would appear that preclear_disk.sh is not the culprit.  fdisk does indicate the error about partition 1 not ending on a cylinder boundary, though.  Is that normal? 

 

--Bill

 

Share this post


Link to post

Should I be concern with these Per-Fail #?

 

1st run:

Sep  2 08:22:57 Tower preclear_disk-start[29551]: Vendor Specific SMART Attributes with Thresholds:
Sep  2 08:22:57 Tower preclear_disk-start[29551]: ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
Sep  2 08:22:57 Tower preclear_disk-start[29551]:   1 Raw_Read_Error_Rate     0x002f   200   200   051    Pre-fail  Always       -       0
Sep  2 08:22:57 Tower preclear_disk-start[29551]:   3 Spin_Up_Time            0x0027   100   253   021    Pre-fail  Always       -       0
Sep  2 08:22:57 Tower preclear_disk-start[29551]:   4 Start_Stop_Count        0x0032   100   100   000    Old_age   Always       -       4
Sep  2 08:22:57 Tower preclear_disk-start[29551]:   5 Reallocated_Sector_Ct   0x0033   200   200   140    Pre-fail  Always       -       0
Sep  2 08:22:57 Tower preclear_disk-start[29551]:   7 Seek_Error_Rate         0x002e   200   200   000    Old_age   Always       -       0
Sep  2 08:22:57 Tower preclear_disk-start[29551]:   9 Power_On_Hours          0x0032   100   100   000    Old_age   Always       -       9
Sep  2 08:22:57 Tower preclear_disk-start[29551]:  10 Spin_Retry_Count        0x0033   100   253   051    Pre-fail  Always       -       0
Sep  2 08:22:57 Tower preclear_disk-start[29551]:  11 Calibration_Retry_Count 0x0032   100   253   000    Old_age   Always       -       0
Sep  2 08:22:57 Tower preclear_disk-start[29551]:  12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       3
Sep  2 08:22:57 Tower preclear_disk-start[29551]: 192 Power-Off_Retract_Count 0x0032   200   200   000    Old_age   Always       -       1
Sep  2 08:22:57 Tower preclear_disk-start[29551]: 193 Load_Cycle_Count        0x0032   200   200   000    Old_age   Always       -       13
Sep  2 08:22:57 Tower preclear_disk-start[29551]: 196 Reallocated_Event_Count 0x0032   200   200   000    Old_age   Always       -       0
Sep  2 08:22:57 Tower preclear_disk-start[29551]: 197 Current_Pending_Sector  0x0032   200   200   000    Old_age   Always       -       0
Sep  2 08:22:57 Tower preclear_disk-start[29551]: 198 Offline_Uncorrectable   0x0030   100   253   000    Old_age   Offline      -       0
Sep  2 08:22:57 Tower preclear_disk-start[29551]: 199 UDMA_CRC_Error_Count    0x0032   200   200   000    Old_age   Always       -       0
Sep  2 08:22:57 Tower preclear_disk-start[29551]: 200 Multi_Zone_Error_Rate   0x0009   100   253   051    Pre-fail  Offline      -       0

 

 

2nd run:

Sep  2 16:11:56 Tower preclear_disk-finish[24063]: SMART Attributes Data Structure revision number: 16
Sep  2 16:11:56 Tower preclear_disk-finish[24063]: Vendor Specific SMART Attributes with Thresholds:
Sep  2 16:11:56 Tower preclear_disk-finish[24063]: ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
Sep  2 16:11:56 Tower preclear_disk-finish[24063]:   1 Raw_Read_Error_Rate     0x002f   200   200   051    Pre-fail  Always       -       0
Sep  2 16:11:56 Tower preclear_disk-finish[24063]:   3 Spin_Up_Time            0x0027   100   253   021    Pre-fail  Always       -       0
Sep  2 16:11:56 Tower preclear_disk-finish[24063]:   4 Start_Stop_Count        0x0032   100   100   000    Old_age   Always       -       4
Sep  2 16:11:56 Tower preclear_disk-finish[24063]:   5 Reallocated_Sector_Ct   0x0033   200   200   140    Pre-fail  Always       -       0
Sep  2 16:11:56 Tower preclear_disk-finish[24063]:   7 Seek_Error_Rate         0x002e   200   200   000    Old_age   Always       -       0
Sep  2 16:11:56 Tower preclear_disk-finish[24063]:   9 Power_On_Hours          0x0032   100   100   000    Old_age   Always       -       17
Sep  2 16:11:56 Tower preclear_disk-finish[24063]:  10 Spin_Retry_Count        0x0033   100   253   051    Pre-fail  Always       -       0
Sep  2 16:11:56 Tower preclear_disk-finish[24063]:  11 Calibration_Retry_Count 0x0032   100   253   000    Old_age   Always       -       0
Sep  2 16:11:56 Tower preclear_disk-finish[24063]:  12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       3
Sep  2 16:11:56 Tower preclear_disk-finish[24063]: 192 Power-Off_Retract_Count 0x0032   200   200   000    Old_age   Always       -       1
Sep  2 16:11:56 Tower preclear_disk-finish[24063]: 193 Load_Cycle_Count        0x0032   200   200   000    Old_age   Always       -       18
Sep  2 16:11:56 Tower preclear_disk-finish[24063]: 196 Reallocated_Event_Count 0x0032   200   200   000    Old_age   Always       -       0
Sep  2 16:11:56 Tower preclear_disk-finish[24063]: 197 Current_Pending_Sector  0x0032   200   200   000    Old_age   Always       -       0
Sep  2 16:11:56 Tower preclear_disk-finish[24063]: 198 Offline_Uncorrectable   0x0030   100   253   000    Old_age   Offline      -       0
Sep  2 16:11:56 Tower preclear_disk-finish[24063]: 199 UDMA_CRC_Error_Count    0x0032   200   200   000    Old_age   Always       -       0
Sep  2 16:11:56 Tower preclear_disk-finish[24063]: 200 Multi_Zone_Error_Rate   0x0009   100   253   051    Pre-fail  Offline      -       0

 

thanks in advance,

~joy

Share this post


Link to post

Drive looks perfect, brand new with less than one day of service!

Share this post


Link to post

No, no fdisk.  I put them into their current device order, assigned them to their RAID role (disk1, disk3 and disk4 respectively) and started unRAID without a parity drive.  I did not format any drive or do any writing.  Shouldn't they have come up as unformatted in the Main menu?  None of them did.  Is the act of formatting in unRAID the only way the fs would get created (setting offset 83 to 83)?

It certainly sounds as if you've already created file-systems on the disks.  If you have them assigned to your array, can you store files on them?  (They would have shown as "Un-formatted" if unable to be mounted, and if they are mounted, they have a file-system.)  I somehow think you pressed the "Format" button... at least once.  I have never heard of unRAID doing it on its own, but then again, most of the time it is not presented with a pre-cleared disk before parity is established.

 

Edit: I've since figured out that the act of assigning the drives to the array will write the MBR's partition table in preparation for the creation of a file-system on it.

 

 fdisk does indicate the error about partition 1 not ending on a cylinder boundary, though.  Is that normal?  

 

--Bill

 

As far as the "warning" from fdisk about the partition not ending on a cylinder boundary.   Yes, very normal.

The Cylinder/Heads/Sectors notation is not used by modern disks.  It is "faked" and reported so very-old BIOS can still interact with the disk.

see here: http://www.pcguide.com/ref/hdd/geom/geomPhysical-c.html

and

here: http://www.pcguide.com/ref/hdd/geom/geomLogical-c.html

 

Modern disks use a linear addressing scheme... Their bit density on the platters guarantees more than 63 sectors per cylinder, but that is as many as the field in the MBR would allow...  The number of heads can be as high as 255, but again, no modern disk has that many.... typically they have 2 per platter, one on top and one on the bottom.   Many disks will therefore report 1 head, 63 sectors per cylinder, and a much higher number of "cylinders" than actually present.    The number of "sectors" per cylinder is not constant on modern disks...  There are more on the outer tracks than on the inner ones to keep the bit density equal. (otherwise, the bits on the inner tracks would be much closer together, and harder to read accurately)

 

Your disk "reported" 46,512,336 cylinders.  If true, the arm holding the disk head would have to be able to be positioned to 46 million different positions... accurately...   It reported 1 head... difficult to read the top AND bottom of the platter with only 1 head.  In fact, most 1.5TB drives have either 3 or 4 platters...  Impossible to read 6 (or 8 ) surfaces with 1 disk head.

Don't worry about the "partition not ending on cylinder boundary" warning... it has no meaning on current drives.

 

Joe L.

Share this post


Link to post

It certainly sounds as if you've already created file-systems on the disks.  If you have them assigned to your array, can you store files on them?  (They would have shown as "Un-formatted" if unable to be mounted, and if they are mounted, they have a file-system.)  I somehow think you pressed the "Format" button... at least once.  I have never heard of unRAID doing it on its own, but then again, most of the time it is not presented with a pre-cleared disk before parity is established.

Hmmm.  It seems obvious that I must have done something wrong in the sequence, but I'm quite sure I didn't format any drives.  In fact I recall being surprised that the supposedly pre-cleared ones didn't show up needing to be formatted, since with all zeros just written there can't be a filesystem structure there.

 

I'm ready to believe I could have gotten confused over the two 1.5T drives, but the 750G is an oddball size in this array and I know I did not format it - ever.  Is there any mode in unRAID that upon seeing a pre-cleared drive will put a filesystem on without requesting you to format it?  Puzzling.

 

I wonder, is there a byte in that first sector (or somewhere) where a pre-cleared flag could be placed and remain after the filesystem is added?  It seems like an indication that a given drive, now in operation, was ever pre-cleared.  It might be useful to know later, if you popped in a replacement drive in a hurry without time for the lengthy pre-clear process, so you could pre-clear it later when files could be moved around and there was more time available.

 

Thanks for the geometry lesson!  I knew things had changed considerably in the newer and larger drives but never had really paid much attention to it as long as they just worked!

 

--Bill

 

 

 

Share this post


Link to post

It certainly sounds as if you've already created file-systems on the disks.  If you have them assigned to your array, can you store files on them?  (They would have shown as "Un-formatted" if unable to be mounted, and if they are mounted, they have a file-system.)  I somehow think you pressed the "Format" button... at least once.  I have never heard of unRAID doing it on its own, but then again, most of the time it is not presented with a pre-cleared disk before parity is established.

Hmmm.  It seems obvious that I must have done something wrong in the sequence, but I'm quite sure I didn't format any drives.  In fact I recall being surprised that the supposedly pre-cleared ones didn't show up needing to be formatted, since with all zeros just written there can't be a filesystem structure there.

Do the disks show as available in the management interface?  (with a size, and free space?)

I'm ready to believe I could have gotten confused over the two 1.5T drives, but the 750G is an oddball size in this array and I know I did not format it - ever.  Is there any mode in unRAID that upon seeing a pre-cleared drive will put a filesystem on without requesting you to format it?  Puzzling.

Not that I'm aware of, but then most people have a parity drive assigned... I don't know what happens if a pre-cleared set of disks is present with no parity drive assigned.  I would have expected the "Format" button, but who knows.

 

the "Format" button would format all disks that were assigned and unable to be mounted.... It is not necessary to do it for each disk in turn.

I wonder, is there a byte in that first sector (or somewhere) where a pre-cleared flag could be placed and remain after the filesystem is added?  It seems like an indication that a given drive, now in operation, was ever pre-cleared.  It might be useful to know later, if you popped in a replacement drive in a hurry without time for the lengthy pre-clear process, so you could pre-clear it later when files could be moved around and there was more time available.

No, all of the bytes in the MBR (the first 512) are significant, and are tested by unRAID.  Interestingly, the remainder of the first cylinder (up to sector 62) are currently not used at all... for historical reasons that allow the disk to be recognized as partitioned in older BIOS and in Windows)  So, you could write something there... as a "note."  I'd just write something down on paper... If you accidentally made a drive look like it was pre-cleared, and it had anything other than zeros on the remainder of the disk, you would completely break all the parity calculations and be unable to restore from a disk failure unless you did a full parity check and fixed all the parity ... prior to the failure ...

Thanks for the geometry lesson!  I knew things had changed considerably in the newer and larger drives but never had really paid much attention to it as long as they just worked!

--Bill

It has been a long time since the old C/H/S geometry worked as originally defined.... In fact, it could not handle disks > 8 Gig.  (At that time, 8 Gig was a dream... disk sizes were measures in Megabytes, not Terabytes. and a (tiny by today's standards) 20 Megabyte drive was nearly $1000.  See here: http://www.mattscomputertrends.com/harddiskdata.html)

 

Joe L.

Share this post


Link to post
Not that I'm aware of, but then most people have a parity drive assigned... I don't know what happens if a pre-cleared set of disks is present with no parity drive assigned.  I would have expected the "Format" button, but who knows.

 

I can confirm that with a set of pre-cleared disks with no parity assigned, the "Format"button will still show up.

I added one pre-cleared disk first. Formatted it. Filled it up with data.

Then added a second one. Formatted it. Filled it up before adding a third parity drive.

The "Format" button shows up both times I added a pre-cleared disk.

 

Share this post


Link to post

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.