SOLVED Question regarding resilvering.

[ARKansans]

Hi there, yesterday I replaced a 4tb drive with a 10tb drive, resilvering finished this morning.
Replacement was made just to enlarge the pool, nothing wrong with the 4tb drive.
Now i'm getting errors and server is resilvering again.
It started just about when I started to make a new jail, no idea if that's related.

Got this email

New alerts:
* Pool Geymsla state is ONLINE: One or more devices has experienced an unrecoverable error. An attempt was made to correct the error. Applications are unaffected.

Then few min laters I got another one.

New alert:
* Pool Geymsla state is ONLINE: One or more devices is currently being resilvered. The pool will continue to function, possibly in a degraded state.

The following alert has been cleared:
* Pool Geymsla state is ONLINE: One or more devices has experienced an unrecoverable error. An attempt was made to correct the error. Applications are unaffected.

And another one

The following alert has been cleared:
* Pool Geymsla state is ONLINE: One or more devices is currently being resilvered. The pool will continue to function, possibly in a degraded state.

Then I checked the pool

Code:

root@freenas[~]# zpool status
  pool: Geymsla
 state: ONLINE
  scan: resilvered 246M in 00:01:13 with 0 errors on Sun Jun  5 15:55:05 2022
config:

        NAME                                            STATE     READ WRITE CKS                                                                                      UM
        Geymsla                                         ONLINE       0     0                                                                                           0
          raidz2-0                                      ONLINE       0     0                                                                                           0
            gptid/55f18eb0-0700-11ea-b671-001e67b6be28  ONLINE       0     0                                                                                           0
            gptid/578d774b-0700-11ea-b671-001e67b6be28  ONLINE       0     0                                                                                           0
            gptid/5958c7a3-0700-11ea-b671-001e67b6be28  ONLINE       0     0                                                                                           0
            gptid/5b67112d-0700-11ea-b671-001e67b6be28  ONLINE       0     0                                                                                           0
          raidz2-1                                      ONLINE       0     0                                                                                           0
            gptid/c32349aa-e437-11ec-b872-001e67b6be28  ONLINE       0     0                                                                                           0
            gptid/e367f52b-0bb3-11ea-81da-001e67b6be28  ONLINE       0     0                                                                                           0
            gptid/e5c76fa6-0bb3-11ea-81da-001e67b6be28  ONLINE       0     0                                                                                           0
            gptid/e7ed145d-0bb3-11ea-81da-001e67b6be28  ONLINE       0     0                                                                                           0

errors: No known data errors

Then again few min later I got another email.

New alerts:
* Pool Geymsla state is ONLINE: One or more devices has experienced an unrecoverable error. An attempt was made to correct the error. Applications are unaffected.

And a follow up email a minute later

The following alert has been cleared:
* Pool Geymsla state is ONLINE: One or more devices has experienced an unrecoverable error. An attempt was made to correct the error. Applications are unaffected.

And I checked the pool again.

Code:

root@freenas[~]# zpool status
  pool: Geymsla
 state: ONLINE
  scan: resilvered 10.6M in 00:00:04 with 0 errors on Sun Jun  5 16:08:18 2022
config:

        NAME                                            STATE     READ WRITE CKSUM
        Geymsla                                         ONLINE       0     0     0
          raidz2-0                                      ONLINE       0     0     0
            gptid/55f18eb0-0700-11ea-b671-001e67b6be28  ONLINE       0     0     0
            gptid/578d774b-0700-11ea-b671-001e67b6be28  ONLINE       0     0     0
            gptid/5958c7a3-0700-11ea-b671-001e67b6be28  ONLINE       0     0     0
            gptid/5b67112d-0700-11ea-b671-001e67b6be28  ONLINE       0     0     0
          raidz2-1                                      ONLINE       0     0     0
            gptid/c32349aa-e437-11ec-b872-001e67b6be28  ONLINE       0     0     0
            gptid/e367f52b-0bb3-11ea-81da-001e67b6be28  ONLINE       0     0     0
            gptid/e5c76fa6-0bb3-11ea-81da-001e67b6be28  ONLINE       0     0     0
            gptid/e7ed145d-0bb3-11ea-81da-001e67b6be28  ONLINE       0     0     0

errors: No known data errors

Is this normal behaviour or is something wrong?

 

[Dice]

Is this normal behaviour or is something wrong?

This is not to be expected, with healthy drives.

I THINK what happened - during the resilver process problems of data corruption was found, but solved 'thnx to ZFS'.
Once the resilvers were complete, the errors were gone.
On the other hand, I THINK it is expected the errors on individual drives remain in the log output you showed - where no errors are found.
I'd expect one to manually clear such errors before they "dissappear".
Something is up here.

I'd have a look at all smart values of the drives to get clues about their health.
smartctl -a /dev/adaX

 

[ARKansans]

The emails are up to 20 that I've received now, the latest is.

New alert:
* Pool Geymsla state is DEGRADED: One or more devices are faulted in response to persistent errors. Sufficient replicas exist for the pool to continue functioning in a degraded state.
The following devices are not healthy:

• Disk ST10000VN0004-1ZD101 ZA2BE0K6 is FAULTED

The output I get is.

Code:

root@freenas[~]# smartctl -a /dev/ada2
smartctl 7.2 2020-12-30 r5155 [FreeBSD 12.2-RELEASE-p14 amd64] (local build)
Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Seagate IronWolf
Device Model:     ST10000VN0004-1ZD101
Serial Number:    ZA2BE0K6
LU WWN Device Id: 5 000c50 0b6573589
Firmware Version: SC60
User Capacity:    10,000,831,348,736 bytes [10.0 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 5
SATA Version is:  SATA 3.1, 6.0 Gb/s (current: 3.0 Gb/s)
Local Time is:    Sun Jun  5 18:06:28 2022 GMT
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:                    (0x7b) SMART execute Offline immediate.
                                        Auto Offline data collection on/off supp                                             ort.
                                        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:        ( 858) minutes.
Conveyance self-test routine
recommended polling time:        (   2) minutes.
SCT capabilities:              (0x50bd) 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   084   064   044    Pre-fail  Always       -                                                    231206793
  3 Spin_Up_Time            0x0003   097   087   000    Pre-fail  Always       -                                                    0
  4 Start_Stop_Count        0x0032   100   100   020    Old_age   Always       -                                                    72
  5 Reallocated_Sector_Ct   0x0033   100   100   010    Pre-fail  Always       -                                                    56
  7 Seek_Error_Rate         0x000f   090   060   045    Pre-fail  Always       -                                                    925619879
  9 Power_On_Hours          0x0032   075   075   000    Old_age   Always       -                                                    22550 (164 123 0)
 10 Spin_Retry_Count        0x0013   100   100   097    Pre-fail  Always       -                                                    0
 12 Power_Cycle_Count       0x0032   100   100   020    Old_age   Always       -                                                    72
184 End-to-End_Error        0x0032   100   100   099    Old_age   Always       -                                                    0
187 Reported_Uncorrect      0x0032   100   100   000    Old_age   Always       -                                                    0
188 Command_Timeout         0x0032   100   100   000    Old_age   Always       -                                                    0
189 High_Fly_Writes         0x003a   001   001   000    Old_age   Always       -                                                    108
190 Airflow_Temperature_Cel 0x0022   071   060   040    Old_age   Always       -                                                    29 (Min/Max 29/30)
191 G-Sense_Error_Rate      0x0032   082   082   000    Old_age   Always       -                                                    37966
192 Power-Off_Retract_Count 0x0032   100   100   000    Old_age   Always       -                                                    75
193 Load_Cycle_Count        0x0032   100   100   000    Old_age   Always       -                                                    1664
194 Temperature_Celsius     0x0022   029   040   000    Old_age   Always       -                                                    29 (0 21 0 0 0)
195 Hardware_ECC_Recovered  0x001a   003   001   000    Old_age   Always       -                                                    231206793
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
200 Pressure_Limit          0x0023   100   100   001    Pre-fail  Always       -                                                    0
240 Head_Flying_Hours       0x0000   100   253   000    Old_age   Offline      -                                                    22475 (178 121 0)
241 Total_LBAs_Written      0x0000   100   253   000    Old_age   Offline      -                                                    168982407682
242 Total_LBAs_Read         0x0000   100   253   000    Old_age   Offline      -                                                    1194372393630

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%     22535         -
# 2  Short offline       Completed without error       00%     22296         -
# 3  Extended offline    Completed without error       00%     22224         -
# 4  Short offline       Completed without error       00%     22128         -
# 5  Short offline       Completed without error       00%     21959         -
# 6  Extended offline    Completed without error       00%     21898         -
# 7  Short offline       Completed without error       00%     21799         -
# 8  Short offline       Completed without error       00%     21583         -
# 9  Extended offline    Completed without error       00%     21511         -
#10  Short offline       Completed without error       00%     21415         -
#11  Short offline       Completed without error       00%     21247         -
#12  Extended offline    Completed without error       00%     21174         -
#13  Short offline       Completed without error       00%     21079         -
#14  Short offline       Completed without error       00%     20839         -
#15  Extended offline    Completed without error       00%     20764         -
#16  Short offline       Completed without error       00%     20671         -
#17  Short offline       Completed without error       00%     20503         -
#18  Extended offline    Completed without error       00%     20428         -
#19  Short offline       Completed without error       00%     20335         -
#20  Short offline       Completed without error       00%     20167         -
#21  Extended offline    Completed without error       00%     20090         -

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.

root@freenas[~]#

EDIT:
I just just noticed this in the messages.
I attached longer output below.

Jun 5 17:39:34 freenas ada2 at ahcich3 bus 0 scbus5 target 0 lun 0
Jun 5 17:39:34 freenas ada2: <ST10000VN0004-1ZD101 SC60> ACS-3 ATA SATA 3.x device
Jun 5 17:39:34 freenas ada2: Serial Number ZA2BE0K6
Jun 5 17:39:34 freenas ada2: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes)
Jun 5 17:39:34 freenas ada2: Command Queueing enabled
Jun 5 17:39:34 freenas ada2: 9537536MB (19532873728 512 byte sectors)
Jun 5 17:39:34 freenas ses0: ada2,pass10 in 'Slot 03', SATA Slot: scbus5 target 0
Jun 5 17:40:41 freenas ada2 at ahcich3 bus 0 scbus5 target 0 lun 0
Jun 5 17:40:41 freenas ada2: <ST10000VN0004-1ZD101 SC60> s/n ZA2BE0K6 detached
Jun 5 17:40:41 freenas (ada2:ahcich3:0:0:0): Periph destroyed

 

[Dice]

=== START OF INFORMATION SECTION === Model Family: Seagate IronWolf

Unfortunately reading SMART values from Seagate is a mess for proprietary reasons.

Are all the emails pointing to the same drive?
It might be a issue with a cable/connector.

If it is on various drives, that would point to a mishap with the controller.

 

[ARKansans]

Unfortunately reading SMART values from Seagate is a mess for proprietary reasons.

Are all the emails pointing to the same drive?
It might be a issue with a cable/connector.

If it is on various drives, that would point to a mishap with the controller.

Yes all the emails are pointing to the same drive.
I noticed that you posted just after I made a edit to the post, did you see the messages output?

I'll turn the server off later tonight and reseat all the cables.

 

[Dice]

I'll turn the server off later tonight and reseat all the cables.

Cool.

I'd expect a cable issue causing the drive to glitch, would make it look faulty to TN.
Which In turn, probably would better explain why there are no "errors" on the pool, once the drive is found again, and in particular - after you've scrubbed the pool again.

 

[ARKansans]

So I should force scrub on that pool after I've started the server again?

 

[Dice]

I believe that is a good idea.
At least that will verify your data is in better shape than TN indicates your drive health is at.
I'd also have a look at chaning that particular cable to that drive, or even changing SATA port.

 

[ARKansans]

I finally managed to shutdown, reseat and power back up, and it started right away resilvering, although at
considerably slower pace then my last 10tb resilvering @ 350M/s instead of 1.4G/s.
Maybe it's just slow at the beginning and then will rev up?
--------------------------------------------------------------------------------------------
Just as I was about to post this reply, I received another e-mail

TrueNAS @ freenas.Workgroup

New alert:
* Pool Geymsla state is ONLINE: One or more devices is currently being resilvered. The pool will continue to function, possibly in a degraded state.

The following alert has been cleared:
* Pool Geymsla state is DEGRADED: One or more devices are faulted in response to persistent errors. Sufficient replicas exist for the pool to continue functioning in a degraded state.
The following devices are not healthy:

• Disk ST10000VN0004-1ZD101 ZA2BE0K6 is FAULTED

then 12 min later

TrueNAS @ freenas.Workgroup

New alert:
* Pool Geymsla state is ONLINE: One or more devices has experienced an unrecoverable error. An attempt was made to correct the error. Applications are unaffected.

The following alert has been cleared:
* Pool Geymsla state is ONLINE: One or more devices is currently being resilvered. The pool will continue to function, possibly in a degraded state.

zpool status now gives me

Code:

root@freenas[~]# zpool status
  pool: Geymsla
 state: ONLINE
status: One or more devices has experienced an unrecoverable error.  An
        attempt was made to correct the error.  Applications are unaffected.
action: Determine if the device needs to be replaced, and clear the errors
        using 'zpool clear' or replace the device with 'zpool replace'.
   see: https://openzfs.github.io/openzfs-docs/msg/ZFS-8000-9P
  scan: resilvered 34.0G in 00:12:30 with 0 errors on Mon Jun  6 11:22:46 2022
config:

        NAME                                            STATE     READ WRITE CKSUM
        Geymsla                                         ONLINE       0     0     0
          raidz2-0                                      ONLINE       0     0     0
            gptid/55f18eb0-0700-11ea-b671-001e67b6be28  ONLINE       0     0     0
            gptid/578d774b-0700-11ea-b671-001e67b6be28  ONLINE       0     0     1
            gptid/5958c7a3-0700-11ea-b671-001e67b6be28  ONLINE       0     0     0
            gptid/5b67112d-0700-11ea-b671-001e67b6be28  ONLINE       0     0     0
          raidz2-1                                      ONLINE       0     0     0
            gptid/c32349aa-e437-11ec-b872-001e67b6be28  ONLINE       0     0     0
            gptid/e367f52b-0bb3-11ea-81da-001e67b6be28  ONLINE       0     0     0
            gptid/e5c76fa6-0bb3-11ea-81da-001e67b6be28  ONLINE       0     0     0
            gptid/e7ed145d-0bb3-11ea-81da-001e67b6be28  ONLINE       0     0     0

errors: No known data errors

All disks show as online under status in the pool and pool shows as ONLINE (Unhealthy)

 

[Samuel Tai]

You have one disk with checksum errors. Wait until the resilver is done, and then scrub your pool. This should repair the block with the invalid checksum using redundant data and/or metadata from the other pool members.

 

[ARKansans]

You have one disk with checksum errors. Wait until the resilver is done, and then scrub your pool. This should repair the block with the invalid checksum using redundant data and/or metadata from the other pool members.

The resilvering finished 11:10 (33 min ago), so I guess it's safe now to scrub it?

 

[Samuel Tai]

The resilvering finished 11:10 (33 min ago), so I guess it's safe now to scrub it?

Yes, go for it.

 

[ARKansans]

The scrubbing just finished now, still having problem, unless I have to do 'zpool clear' ?
Critical alert is still up since 11:23 last morning.
Would this be the right command if I need to clear it?

Code:

zpool clear Geymsla gptid/578d774b-0700-11ea-b671-001e67b6be28

I did perform long S.M.A.R.T. test on it now, say's it'll finish in 14 hours or so.

Code:

root@freenas[~]# zpool status
  pool: Geymsla
 state: ONLINE
status: One or more devices has experienced an unrecoverable error.  An
        attempt was made to correct the error.  Applications are unaffected.
action: Determine if the device needs to be replaced, and clear the errors
        using 'zpool clear' or replace the device with 'zpool replace'.
   see: https://openzfs.github.io/openzfs-docs/msg/ZFS-8000-9P
  scan: scrub repaired 0B in 21:33:39 with 0 errors on Tue Jun  7 09:19:37 2022
config:

        NAME                                            STATE     READ WRITE CKS                                                              UM
        Geymsla                                         ONLINE       0     0                                                                   0
          raidz2-0                                      ONLINE       0     0                                                                   0
            gptid/55f18eb0-0700-11ea-b671-001e67b6be28  ONLINE       0     0                                                                   0
            gptid/578d774b-0700-11ea-b671-001e67b6be28  ONLINE       0     0                                                                   1
            gptid/5958c7a3-0700-11ea-b671-001e67b6be28  ONLINE       0     0                                                                   0
            gptid/5b67112d-0700-11ea-b671-001e67b6be28  ONLINE       0     0                                                                   0
          raidz2-1                                      ONLINE       0     0                                                                   0
            gptid/c32349aa-e437-11ec-b872-001e67b6be28  ONLINE       0     0                                                                   0
            gptid/e367f52b-0bb3-11ea-81da-001e67b6be28  ONLINE       0     0                                                                   0
            gptid/e5c76fa6-0bb3-11ea-81da-001e67b6be28  ONLINE       0     0                                                                   0
            gptid/e7ed145d-0bb3-11ea-81da-001e67b6be28  ONLINE       0     0                                                                   0

errors: No known data errors

The CKSUM row somehow seems to get broken when I paste it here in code, and kinda hides
far right off the sheet.

 

[Samuel Tai]

If the scrub was clean, then you can try the zpool clear.

 

[ARKansans]

If the scrub was clean, then you can try the zpool clear.

Where can I see if the scrub was clean?
Is the zpool clear command correct I posted above? As according to the manual the device name is only 6 characters, unless
it's talking about the ada1p2/ada2p2/ada3p2 etc.

 

[Samuel Tai]

zpool status will show the status of the scrub. You don't need the device in the zpool clear, just the pool name.

 

[ARKansans]

I just cleared the pool and nothing has shown up yet, keeping fingers crossed!
And thank you very much guys for the help! It's greatly appreciated!

 

[ARKansans]

I totally forgot to ask, is there any need to scrub the pool each time I replace an HDD if I'm just doing an upgrade
and everything is ok?

 

[Dice]

I totally forgot to ask, is there any need to scrub the pool each time I replace an HDD if I'm just doing an upgrade
and everything is ok?

A few years back this was the regular recommendation on the forums.
I've applied it such as "whenever uncomfortable events happen - I run a scrub to feel safe all is well".

I believe there was a change a few versions back where the replacement/resilvering of drives also included a scrub functionality, rendering "old advice" redundant.
*checking the documentation*

Disk Replacement

Describes how to replace a disk and restore the hot spare in TrueNAS CORE.

www.truenas.com

...would you look at that:

"TrueNAS resilvers the pool during the replacement process.

I'll still run a scrub whenever I find something worrisome.

 

[ARKansans]

The manual only say's it'll resilver the pool, no mentioning about scrubbing, so I wasn't sure, but after a little more
searching I found a manual from Oracle that states that resilvering is a form of disk scrubbing, sorry
for these questions but when working with a live system you don't want to take any chances :)
Thanks again!