RN104: ghost “NG-8TB-Seagate” volume (RAID unknown) Inactive/Unprotected

BrainzUK wrote:

NG-WDRED-3TB-1 (0 data, 0 free, RAID unknown)

This was the old 3 TB drive (which was primary).

[26/03/05 20:45:16 GMT] notice:volume:LOGMSG_HEALTH_VOLUME Volume NG-8TB-Seagate health changed from Unprotected to Inactive.
[26/03/05 20:45:20 GMT] info:volume:LOGMSG_DELETE_VOLUME Volume NG-WDRED-3TB-1 was deleted from the system.
[26/03/05 20:45:29 GMT] notice:volume:LOGMSG_HEALTH_VOLUME Volume NG-8TB-Seagate health changed from Inactive to Unprotected.
[26/03/05 20:45:32 GMT] notice:volume:LOGMSG_HEALTH_VOLUME Volume NG-8TB-Seagate health changed from Unprotected to Inactive.
[26/03/05 20:45:34 GMT] info:volume:LOGMSG_DELETE_VOLUME_NEW_HOME_FOLDER Home folders are newly created on volume NG-8TB-Seagate.
[26/03/05 20:45:47 GMT] notice:volume:LOGMSG_HEALTH_VOLUME Volume NG-8TB-Seagate health changed from Unprotected to Inactive.

This was deleted after the new Seagate was installed - I can't tell if you did that manually or if the system did it on its own.

As I mentioned in the PM, several logs are flooded with the 8 TB volume health toggling between inactive and unprotected.  I can't see the underlying errors that are causing that.

If the 3 TB drive you replaced was healthy, then I'd suggest switching back to that temporarily.  But it's not - over 20 thousand ATA errors, and 76 pending sectors.

I think the path forward is to replace the Seagate with an Ironwolf (though unfortunately you might be past the return window).  But I think testing the drive first would be useful.