Device: /dev/ada3, ATA error count increased from 0 to 12

willtruenas111 · Aug 16, 2022

Hi

I got this critical error on my TrueNAS:

* Pool RAID state is ONLINE: One or more devices has experienced an unrecoverable error. An attempt was made to correct the error. Applications are unaffected.
* Device: /dev/ada3, ATA error count increased from 0 to 12.

Does anyone have any insight as to what I should do about this or what significance it has?

I ran smartctl -a /dev/ada3 and this is the output:

Code:

root@truenas[~]# smartctl -a /dev/ada3
smartctl 7.2 2021-09-14 r5236 [FreeBSD 13.1-RELEASE amd64] (local build)
Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Seagate Barracuda 7200.11
Device Model:     ST31000333AS
Serial Number:    6TE08VNS
LU WWN Device Id: 5 000c50 00e3c550f
Firmware Version: SD35
User Capacity:    1,000,204,886,016 bytes [1.00 TB]
Sector Size:      512 bytes logical/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 2.6, 3.0 Gb/s
Local Time is:    Tue Aug 16 09:58:18 2022 BST

==> WARNING: There are known problems with these drives,
see the following Seagate web pages:
http://knowledge.seagate.com/articles/en_US/FAQ/207931en
http://knowledge.seagate.com/articles/en_US/FAQ/207951en
http://knowledge.seagate.com/articles/en_US/FAQ/207957en

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
See vendor-specific Attribute list for marginal Attributes.

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:      (   0) The previous self-test routine completed
                                        without error or no self-test has ever
                                        been run.
Total time to complete Offline
data collection:                (  617) 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:        (   1) minutes.
Extended self-test routine
recommended polling time:        ( 212) minutes.
Conveyance self-test routine
recommended polling time:        (   2) minutes.
SCT capabilities:              (0x103b) SCT Status supported.
                                        SCT Error Recovery Control 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   099   099   006    Pre-fail  Always       -       28959177
  3 Spin_Up_Time            0x0003   093   091   000    Pre-fail  Always       -       0
  4 Start_Stop_Count        0x0032   097   097   020    Old_age   Always       -       3587
  5 Reallocated_Sector_Ct   0x0033   100   100   036    Pre-fail  Always       -       40
  7 Seek_Error_Rate         0x000f   072   060   030    Pre-fail  Always       -       20467954
  9 Power_On_Hours          0x0032   019   019   000    Old_age   Always       -       71259
 10 Spin_Retry_Count        0x0013   100   100   097    Pre-fail  Always       -       34
 12 Power_Cycle_Count       0x0032   100   100   020    Old_age   Always       -       205
184 End-to-End_Error        0x0032   100   100   099    Old_age   Always       -       0
187 Reported_Uncorrect      0x0032   088   088   000    Old_age   Always       -       12
188 Command_Timeout         0x0032   100   087   000    Old_age   Always       -       124556607584
189 High_Fly_Writes         0x003a   001   001   000    Old_age   Always       -       292
190 Airflow_Temperature_Cel 0x0022   059   033   045    Old_age   Always   In_the_past 41 (Min/Max 38/42 #1079)
194 Temperature_Celsius     0x0022   041   067   000    Old_age   Always       -       41 (0 16 0 0 0)
195 Hardware_ECC_Recovered  0x001a   046   024   000    Old_age   Always       -       28959177
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

SMART Error Log Version: 1
ATA Error Count: 12 (device log contains only the most recent five errors)
        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 12 occurred at disk power-on lifetime: 5717 hours (238 days + 5 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: WP 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
  -- -- -- -- -- -- -- --  ----------------  --------------------
  61 00 10 ff ff ff 4f 00  26d+05:48:32.532  WRITE FPDMA QUEUED
  60 00 08 ff ff ff 4f 00  26d+05:48:32.532  READ FPDMA QUEUED
  2f 00 01 10 00 00 00 00  26d+05:48:32.452  READ LOG EXT
  61 00 10 ff ff ff 4f 00  26d+05:48:29.346  WRITE FPDMA QUEUED
  60 00 08 ff ff ff 4f 00  26d+05:48:29.346  READ FPDMA QUEUED

Error 11 occurred at disk power-on lifetime: 5717 hours (238 days + 5 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: WP 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
  -- -- -- -- -- -- -- --  ----------------  --------------------
  61 00 10 ff ff ff 4f 00  26d+05:48:29.346  WRITE FPDMA QUEUED
  60 00 08 ff ff ff 4f 00  26d+05:48:29.346  READ FPDMA QUEUED
  2f 00 01 10 00 00 00 00  26d+05:48:29.345  READ LOG EXT
  61 00 10 ff ff ff 4f 00  26d+05:48:25.559  WRITE FPDMA QUEUED
  60 00 08 ff ff ff 4f 00  26d+05:48:25.557  READ FPDMA QUEUED

Error 10 occurred at disk power-on lifetime: 5717 hours (238 days + 5 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: WP 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
  -- -- -- -- -- -- -- --  ----------------  --------------------
  61 00 10 ff ff ff 4f 00  26d+05:48:25.559  WRITE FPDMA QUEUED
  60 00 08 ff ff ff 4f 00  26d+05:48:25.557  READ FPDMA QUEUED
  2f 00 01 10 00 00 00 00  26d+05:48:25.307  READ LOG EXT
  61 00 10 ff ff ff 4f 00  26d+05:48:21.332  WRITE FPDMA QUEUED
  61 00 18 ff ff ff 4f 00  26d+05:48:21.331  WRITE FPDMA QUEUED

Error 9 occurred at disk power-on lifetime: 5717 hours (238 days + 5 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: WP 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
  -- -- -- -- -- -- -- --  ----------------  --------------------
  61 00 10 ff ff ff 4f 00  26d+05:48:21.332  WRITE FPDMA QUEUED
  61 00 18 ff ff ff 4f 00  26d+05:48:21.331  WRITE FPDMA QUEUED
  61 00 58 ff ff ff 4f 00  26d+05:48:21.330  WRITE FPDMA QUEUED
  61 00 d0 ff ff ff 4f 00  26d+05:48:21.329  WRITE FPDMA QUEUED
  61 00 40 ff ff ff 4f 00  26d+05:48:21.327  WRITE FPDMA QUEUED

Error 8 occurred at disk power-on lifetime: 5717 hours (238 days + 5 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 08 ff ff ff 4f 00  26d+05:48:17.538  READ FPDMA QUEUED
  60 00 08 ff ff ff 4f 00  26d+05:48:17.538  READ FPDMA QUEUED
  60 00 08 ff ff ff 4f 00  26d+05:48:17.536  READ FPDMA QUEUED
  60 00 08 ff ff ff 4f 00  26d+05:48:17.535  READ FPDMA QUEUED
  60 00 08 ff ff ff 4f 00  26d+05:48:17.534  READ FPDMA QUEUED

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

I also ran the same command on a disk that didn't have any errors: smartctl -a /dev/ada3:

Code:

smartctl 7.2 2021-09-14 r5236 [FreeBSD 13.1-RELEASE amd64] (local build)
Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Seagate Barracuda 7200.14 (AF)
Device Model:     ST1000DM003-1SB102
Serial Number:    Z9AX6NK2
LU WWN Device Id: 5 000c50 0b29f19ab
Firmware Version: HPH4
User Capacity:    1,000,204,886,016 bytes [1.00 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    7200 rpm
Form Factor:      3.5 inches
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   ACS-3 T13/2161-D revision 3b
SATA Version is:  SATA 3.1, 6.0 Gb/s (current: 3.0 Gb/s)
Local Time is:    Tue Aug 16 09:59:53 2022 BST
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:  (0x82) Offline data collection activity
                                        was completed without error.
                                        Auto Offline Data Collection: Enabled.
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:                (  575) seconds.
Offline data collection
capabilities:                    (0x5b) SMART execute Offline immediate.
                                        Auto Offline data collection on/off support.
                                        Suspend Offline collection upon new
                                        command.
                                        Offline surface scan supported.
                                        Self-test supported.
                                        No 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:        ( 105) minutes.
SCT capabilities:              (0x10bd) SCT Status supported.
                                        SCT Error Recovery Control supported.
                                        SCT Feature Control supported.
                                        SCT Data Table supported.

SMART Attributes Data Structure revision number: 32
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x002f   075   063   006    Pre-fail  Always       -       37534792
  3 Spin_Up_Time            0x0023   097   097   000    Pre-fail  Always       -       0
  4 Start_Stop_Count        0x0032   100   100   000    Old_age   Always       -       83
  5 Reallocated_Sector_Ct   0x0033   100   100   010    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x002f   081   060   030    Pre-fail  Always       -       132729781
  9 Power_On_Hours          0x0032   090   090   000    Old_age   Always       -       9491
 10 Spin_Retry_Count        0x0033   100   100   097    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       83
180 Unknown_HDD_Attribute   0x002a   100   100   000    Old_age   Always       -       1684849827
183 Runtime_Bad_Block       0x0032   100   100   000    Old_age   Always       -       0
184 End-to-End_Error        0x0033   100   100   097    Pre-fail  Always       -       0
187 Reported_Uncorrect      0x0032   100   100   000    Old_age   Always       -       0
188 Command_Timeout         0x0032   100   100   000    Old_age   Always       -       0 0 0
189 High_Fly_Writes         0x003a   100   100   000    Old_age   Always       -       0
190 Airflow_Temperature_Cel 0x0022   064   060   040    Old_age   Always       -       36 (Min/Max 33/38)
193 Load_Cycle_Count        0x0032   100   100   000    Old_age   Always       -       474
194 Temperature_Celsius     0x0022   036   018   000    Old_age   Always       -       36 (0 18 0 0 0)
195 Hardware_ECC_Recovered  0x003a   029   012   000    Old_age   Always       -       37534792
196 Reallocated_Event_Count 0x0032   100   100   000    Old_age   Always       -       0
197 Current_Pending_Sector  0x0032   100   100   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0030   100   100   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x0032   200   200   000    Old_age   Always       -       0

SMART Error Log Version: 1
No Errors Logged

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%         1         -

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

willtruenas111 · Aug 16, 2022

Sorry, slight typo, the 2nd code block was performed on /dev/ada2 (a seemingly healthy disk) not ada3 (the erroring disk)

Heracles · Aug 16, 2022

Hi,

This may be a drive that is about to fail but it can also be something else. I would first check the cable and port. For that, I would power off the server, unplug the cable from both drive and port, and try to plug it back in another port if you have one available.

Also, to be sure you are safe, what kind of redundancy do you have in that pool ?
And how good are your backups ?

Always better to ensure your backups are good before incidents like this materializes...

Redcoat · Aug 16, 2022

Welcome to the forums!

In addition to @Heracles excellent advice, notice that you don't have routine smart testing set up on your drives and suggest that's also worthy of your consideration. See https://www.truenas.com/docs/core/coretutorials/services/configuringsmart/

willtruenas111 · Aug 16, 2022

Redcoat said:
Welcome to the forums!

In addition to @Heracles excellent advice, notice that you don't have routine smart testing set up on your drives and suggest that's also worthy of your consideration. See https://www.truenas.com/docs/core/coretutorials/services/configuringsmart/

Thank you for the welcome!

I have the following set up already, but perhaps not configured correctly?

willtruenas111 · Aug 16, 2022

Heracles said:
Hi,

This may be a drive that is about to fail but it can also be something else. I would first check the cable and port. For that, I would power off the server, unplug the cable from both drive and port, and try to plug it back in another port if you have one available.

Also, to be sure you are safe, what kind of redundancy do you have in that pool ?
And how good are your backups ?

Always better to ensure your backups are good before incidents like this materializes...

Thanks

I'm not sure I have any other ports available, I have four disks occupying all the slots in a HP ge8 proliant microserver.

Re backup, the RAID pool is setup so I can lose a disk, so I'm safe if one goes, hoping that doesn't happen of course from a financial perspective!

joeschmuck · Aug 16, 2022

willtruenas111 said:
Serial Number: 6TE08VNS

willtruenas111 said:
5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 40

willtruenas111 said:
9 Power_On_Hours 0x0032 019 019 000 Old_age Always - 71259

willtruenas111 said:
187 Reported_Uncorrect 0x0032 088 088 000 Old_age Always - 12

willtruenas111 said:
SMART Self-test log structure revision number 1 No self-tests have been logged. [To run self-tests, use: smartctl -t]

My advice: Replace your drive before it dies.
So lets take a closer look: at the above data I pulled from your post. I specified the serial number (always use the serial number when tracking a drive issue).

The Reallocated sectors is 40, that is very high. This means you have a physical defect, likely the rotating platers and the medium is flaking off.
The power on hours is OVER 8 years of power on time, that is impressive! your drive deserves to take a rest.
The Reported Uncorrected is how many times the drive could not recover data.
And the last one you were already told about, absolutely no SMART tests were run.

Replace your drive ASAP ! I have no idea what kind of pool you are running but if the drive dies, will your pool die? Are you running a RAIDZ2 or a Stripe?

Regardless, the drive will need to be replaced.

joeschmuck · Aug 16, 2022

Also, to ensure data integrity you might run a Scrub on your pool.

willtruenas111 · Aug 16, 2022

joeschmuck said:
My advice: Replace your drive before it dies.
So lets take a closer look: at the above data I pulled from your post. I specified the serial number (always use the serial number when tracking a drive issue).

The Reallocated sectors is 40, that is very high. This means you have a physical defect, likely the rotating platers and the medium is flaking off.
The power on hours is OVER 8 years of power on time, that is impressive! your drive deserves to take a rest.
The Reported Uncorrected is how many times the drive could not recover data.
And the last one you were already told about, absolutely no SMART tests were run.

Replace your drive ASAP ! I have no idea what kind of pool you are running but if the drive dies, will your pool die? Are you running a RAIDZ2 or a Stripe?

Regardless, the drive will need to be replaced.

Thanks for the reply.

It has indeed had quite the life, that drive, and certainly deserves a rest..

I checked the other drives who have much shorter power-on lifespans.

Fun fact: I ran a short background smart self-test just now and 'LifeTime(hours)' must be stored as a 16 bit integer. The disk has been on for so long that the number has rolled over to 5730 hours (71259 - 65535)!

I'm running a raidz1, with 4 1tb disks. That data stored isn't sentimental, but would be annoying to lose.

I checked and I have scrubs running every month, next one in 4 days.

joeschmuck · Aug 16, 2022

Thankfully you have 1TB drives, they should resilver fast.

Redcoat · Aug 16, 2022

willtruenas111 said:
Thank you for the welcome!

I have the following set up already, but perhaps not configured correctly?

View attachment 57726

Well, that's the screen in Services where you can enter HDD temperature trigger information in order to receive email alerts if things are getting toasty. You will have to decide your own tolerance to flirting with drive isues - for the three fields where you have 0, I have 10, 35 and 37, reading downwards, respectively.

But, more important, IMHO, is what you find from the link at the bottom of the page I indicated:

which takes you to a page with :

where you can configure the schedule of the testing to your liking. Standard advice has been to avoid simultaneous long and short tests and observe the scub/resilver warniong shown above; run short tests more frequently than long tests.

Here, for example, is my short schedule: Custom (0 03 05,12,19,26 * sun,mon,tue,wed,thu,fri,sat) - run on the hour at 3AM on the 5th, 12th, 19th, and 26th of any month, on whatrever day of the week those dates fall.

And my long: Custom (0 04 08,22 * sun,mon,tue,wed,thu,fri,sat) - (I'll leave you to figure that one out ...

)

Hopefully that will get you started.

Heracles · Aug 16, 2022

willtruenas111 said:
Re backup, the RAID pool is setup so I can lose a disk, so I'm safe if one goes, hoping that doesn't happen of course from a financial perspective!

Unfortunately, not really... A single physical incident like water or fire will destroy the server and all its drives. The same logical error or incident will destroy the data no matter how many drives are in the server.

See my signature about backups and what is needed to protect against every single incident. The more valuable the data, the more important it is to have proper backups.

Jailer · Aug 16, 2022

Your one of the lucky ones to have a Seagate 7200.11 drive last as long as it has. Get it replaced ASAP, they are known to be a terrible terrible drive.

danb35 · Aug 16, 2022

Was it not of that model that @DrKK said, "the optimal configuration is buried as deep as possible in the nearest landfill"?

joeschmuck · Aug 16, 2022

Some people are lucky I guess.

As for one drive safe from a failure, that is all good but if you are resilvering your drive and another one dies, well we have seen it before.

Jailer · Aug 16, 2022

danb35 said:
Was it not of that model that @DrKK said, "the optimal configuration is buried as deep as possible in the nearest landfill"?

If he didn't I will confirm it.

willtruenas111 · Aug 17, 2022

Redcoat said:
Well, that's the screen in Services where you can enter HDD temperature trigger information in order to receive email alerts if things are getting toasty. You will have to decide your own tolerance to flirting with drive isues - for the three fields where you have 0, I have 10, 35 and 37, reading downwards, respectively.

But, more important, IMHO, is what you find from the link at the bottom of the page I indicated:

View attachment 57733

which takes you to a page with :

View attachment 57734

where you can configure the schedule of the testing to your liking. Standard advice has been to avoid simultaneous long and short tests and observe the scub/resilver warniong shown above; run short tests more frequently than long tests.

Here, for example, is my short schedule: Custom (0 03 05,12,19,26 * sun,mon,tue,wed,thu,fri,sat) - run on the hour at 3AM on the 5th, 12th, 19th, and 26th of any month, on whatrever day of the week those dates fall.

And my long: Custom (0 04 08,22 * sun,mon,tue,wed,thu,fri,sat) - (I'll leave you to figure that one out ...)

Hopefully that will get you started.

Appreciate the help and explanation.

I've now got long and short smart test tasks set up, and scrubs, at alternating times (I've also backed up my truenas config just in case..)

willtruenas111 · Aug 17, 2022

Wow looks like I've gotten lucky with that drive.. to the bottom of the landfill it goes!

willtruenas111 · Aug 17, 2022

Jailer said:
If he didn't I will confirm it.

Do you have any recommendations for a 'budget' 1TB drive to replace it?

Jailer · Aug 17, 2022

Brand is strictly up to you but make sure you research and ensure that it is NOT an SMR drive. You want a CMR drive.

Important Announcement for the TrueNAS Community.

Device: /dev/ada3, ATA error count increased from 0 to 12

Dabbler

Dabbler

Wizard

MVP

Dabbler

Dabbler

Old Man

Old Man

Dabbler

Old Man

MVP

Wizard

Not strong, but bad

Hall of Famer

Old Man

Not strong, but bad

Dabbler

Dabbler

Dabbler

Not strong, but bad

Important Announcement for the TrueNAS Community.

Related topics on forums.truenas.com for thread: "Device: /dev/ada3, ATA error count increased from 0 to 12"

Similar threads