1.13: command not found

root@Unraid:/boot# ==  ST2000DL003-9VT166    6YD0GA61

-bash: ==: command not found

root@Unraid:/boot# == Disk /dev/sdf has been successfully precleared

-bash: ==: command not found

root@Unraid:/boot# == with a starting sector of 64

-bash: ==: command not found

root@Unraid:/boot# ============================================================================

-bash: ============================================================================: command not found

root@Unraid:/boot# ** Changed attributes in files: /tmp/smart_start_sdf  /tmp/smart_finish_sdf

-bash: ./bzimage: cannot execute binary file

root@Unraid:/boot#                ATTRIBUTE  NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS      RAW_VALUE

-bash: ATTRIBUTE: command not found

root@Unraid:/boot#      Raw_Read_Error_Rate =  116    100            6        ok          112515056

-bash: Raw_Read_Error_Rate: command not found

root@Unraid:/boot#          Spin_Retry_Count =  100    100          97        near_thresh 0

-bash: Spin_Retry_Count: command not found

root@Unraid:/boot#          End-to-End_Error =  100    100          99        near_thresh 0

-bash: End-to-End_Error: command not found

root@Unraid:/boot#  Airflow_Temperature_Cel =    66      68          45        near_thresh 34

-bash: Airflow_Temperature_Cel: command not found

root@Unraid:/boot#      Temperature_Celsius =    34      32            0        ok          34

-bash: Temperature_Celsius: command not found

root@Unraid:/boot#    Hardware_ECC_Recovered =    37    100            0        ok          112515056

-bash: Hardware_ECC_Recovered: command not found

root@Unraid:/boot#  No SMART attributes are FAILING_NOW

 

 

_________________

 

so it looks to me like this drive is a-OK.  The only reason i ask is because its an RMA from seagate.  Why do some always say Near Thresh if the drive is new?

It is because some brain-damaged engineer put the affiliated failure threshold within a few counts of the starting value and they were apparently too lazy to perform a proper "normalization"

 

unMENU will let you know if a normalized value is nearing its affiliated failure threshold. 

Unfortunately, as you've discovered, some disks start out that way, so the warning may be ignored for those specific parameters.