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.

pls help in interpreting preclear output

Featured Replies

I am not sure what to think of the preclear script output on a new 2TB drive.... Are these errors relatively benign, or should the drive be RMAed.  More in general, is there some sort of smart-for-dummies resource I should be looking at?

 

thanks

 

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

=                unRAID server Pre-Clear disk /dev/sdk

=                      cycle 1 of 1

= Disk Pre-Clear-Read completed                                DONE

= Step 1 of 10 - Copying zeros to first 2048k bytes            DONE

= Step 2 of 10 - Copying zeros to remainder of disk to clear it DONE

= Step 3 of 10 - Disk is now cleared from MBR onward.          DONE

= Step 4 of 10 - Clearing MBR bytes for partition 2,3 & 4      DONE

= Step 5 of 10 - Clearing MBR code area                        DONE

= Step 6 of 10 - Setting MBR signature bytes                    DONE

= Step 7 of 10 - Setting partition 1 to precleared state        DONE

= Step 8 of 10 - Notifying kernel we changed the partitioning  DONE

= Step 9 of 10 - Creating the /dev/disk/by* entries            DONE

= Step 10 of 10 - Testing if the clear has been successful.    DONE

= Disk Post-Clear-Read completed                                DONE

Disk Temperature: 28C, Elapsed Time:  28:55:58

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

==

== Disk /dev/sdk has been successfully precleared

==

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

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

54c54

<  1 Raw_Read_Error_Rate    0x000f  100  100  006    Pre-fail  Always      -      8858

---

>  1 Raw_Read_Error_Rate    0x000f  119  100  006    Pre-fail  Always      -      215132998

58c58

<  7 Seek_Error_Rate        0x000f  100  253  030    Pre-fail  Always      -      47

---

>  7 Seek_Error_Rate        0x000f  100  253  030    Pre-fail  Always      -      239267

64c64

< 188 Unknown_Attribute      0x0032  100  253  000    Old_age  Always      -      0

---

> 188 Unknown_Attribute      0x0032  100  100  000    Old_age  Always      -      0

66,67c66,67

< 190 Airflow_Temperature_Cel 0x0022  076  072  045    Old_age  Always      -      24 (Lifetime Min/Max 20/24)

< 195 Hardware_ECC_Recovered  0x001a  100  100  000    Old_age  Always     

---

> 190 Airflow_Temperature_Cel 0x0022  072  071  045    Old_age  Always      -      28 (Lifetime Min/Max 20/29)

> 195 Hardware_ECC_Recovered  0x001a  050  044  000    Old_age  Always     

70,73c70,73

< 199 UDMA_CRC_Error_Count    0x003e  200  253  000    Old_age  Always      -      0

< 240 Head_Flying_Hours      0x0000  100  253  000    Old_age  Offline      -      208859964637188

< 241 Unknown_Attribute      0x0000  100  253  000    Old_age  Offline      -      0

< 242 Unknown_Attribute      0x0000  100  253  000    Old_age  Offline      -      1632

---

> 199 UDMA_CRC_Error_Count    0x003e  200  200  000    Old_age  Always      -      0

> 240 Head_Flying_Hours      0x0000  100  253  000    Old_age  Offline      -      75217762254881

> 241 Unknown_Attribute      0x0000  100  253  000    Old_age  Offline      -      4195964891

> 242 Unknown_Attribute      0x0000  100  253  000    Old_age  Offline      -      3796633323

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

You have to be very careful about reading that output.  Not everything in that report is an error.  Basically, it is showing you some parameters before and after the preclear finished so you can compare the values and determine if there was any change.

 

The only items of interest really are the Error_rates, which started with 100 or higher and finished at 100 (first column of numbers).  The second column is the max lifetime and the third is the fail point.  Your drive looks fine, just a little more chatty with its condition than most.

 

If you're worried about that ECC_Recovered code, here is an excerpt from the Wikipedia entry on S.M.A.R.T. values:

 

ID Attribute name Description

195 Hardware ECC Recovered The raw value has different structure for different vendors and is often not meaningful as a decimal number.

 

I'll accompany this with my usual disclaimer of "I'm no expert" and let Joe or one of the other guys correct me if / where I'm wrong.  :P

The 253 values are those the manufacturer uses when a drive is from the factory.

The 100 values are those assigned when a drive is first put into use by you.

 

nothing looks abnormal at all.  This is a perfectly working drive.  As far as interpreting the output, look to the wiki:

http://en.wikipedia.org/wiki/S.M.A.R.T.

 

The numbers in the "RAW" column are typically only meaningful to the manufacturer...  The few exceptions are temperature, re-allocated sectors, and sectors pending re-allocation.

 

 

  • Author

Thanks a lot guys.  :)  Bookmarked that wikipedia page.

 

Luca

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.