SOLVED SMART error - persistent email notifications after drive change

[Panik]

Hi,

I started receiving SMART error notifications for one of my drives. After changing the drive. I continue to get the notifications for the same drive S/N that was removed and replaced. All drive pass smart tests and smartctl shows not issues.

I'm not sure why I continue to get emails for a drive that is no longer in the system.

What simple thing am I missing?

Thanks for the help.

 

[joeschmuck]

Welcome to the Forums.

The first thing you need to do is read the Forum Rules listed above (in red letters). Then post your system specs and what version of TrueNAS you are using.

Additional information we will need for this problem is the output (in code brackets) of the following command:
zpool status

Include a screen shot of the TrueNAS GUI that shows the drive still listed.

 

[Panik]

OK, Sorry for not including. Thanks for the help.

The drive is no longer listed. It was in /dev/da1
I also included a snip of the email. As you can see, the serial number listed in the email is not in the pool any longer. Yet I keep getting these emails.

S/N: Z1Z1AWSG00009352M2P2 - Is the one I removed and no longer listed.


TrueNAS-13.0-U3

Running in Proxmox VM
Dell Precision T7910 server
CPU: 2X - Intel XEON E5-2640 - 40 CPU (6 Allocated to TrueNAS)
RAM: 94 GB (24GB Allocated to TrueNAS)
Hard Drives:
Boot: NVME 1TB (32GB Allocated to TrueNAS)
Pool: 4X - SEAGATE ST4000NM0023 – 4TB SAS Drives (Passed Through to TrueNAS)

Code:

truenas% zpool status
  pool: Main1
 state: ONLINE
  scan: scrub repaired 0B in 01:45:12 with 0 errors on Sun Nov 20 04:45:17 2022
config:

        NAME                                            STATE     READ WRITE CKSUM
        Main1                                           ONLINE       0     0     0
          raidz1-0                                      ONLINE       0     0     0
            gptid/0f9f2e79-6528-11ed-883e-11bc47dff592  ONLINE       0     0     0
            gptid/86d02564-ecfe-11ec-be00-ebe9c13d0985  ONLINE       0     0     0
            gptid/87a5fa51-ecfe-11ec-be00-ebe9c13d0985  ONLINE       0     0     0
            gptid/86a85155-ecfe-11ec-be00-ebe9c13d0985  ONLINE       0     0     0

errors: No known data errors

  pool: boot-pool
 state: ONLINE
  scan: scrub repaired 0B in 00:00:03 with 0 errors on Sun Nov 20 03:45:03 2022
config:

        NAME        STATE     READ WRITE CKSUM
        boot-pool   ONLINE       0     0     0
          da0p2     ONLINE       0     0     0

errors: No known data errors

 

[joeschmuck]

A few questions:
Did you hot swap the failed drive out of the system? If yes, have you completely powered off the system (cold steel) and then powered it back on?
If that did not help, IF your pool is not encrypted then I recommend you Export your pool and then Import your pool. This may clear the anomaly. If you pool is encrypted then read up on what you need to Import an encrypted pool. I don't know the answer on that because I do not use encrypted pools. All I know is it can be tricky and it's best to have all your data backed up if you attempt it. That is not the same for a non-encrypted pool, those work easily.

Let me know if this helps.

 

[Panik]

A few questions:
Did you hot swap the failed drive out of the system? If yes, have you completely powered off the system (cold steel) and then powered it back on?
If that did not help, IF your pool is not encrypted then I recommend you Export your pool and then Import your pool. This may clear the anomaly. If you pool is encrypted then read up on what you need to Import an encrypted pool. I don't know the answer on that because I do not use encrypted pools. All I know is it can be tricky and it's best to have all your data backed up if you attempt it. That is not the same for a non-encrypted pool, those work easily.

Let me know if this helps.

Thanks, I did hot swap the drive. I have not powered down. I will do that and report back. Thanks.

 

[Panik]

Thanks @joeschmuck . I guess it was a simple as a rebooting the server. I never thought to do the ole reboot...... duh!

 

[joeschmuck]

Glad to help.