Replacing RMA-ed drive, now encountering new errors

[Anarchia]

Hi Y’all, I had to RMA a drive (you can find my last post about it in the history). Finally got my new drive, installed it and booted up. 10 minutes later I got this warning email below! I tried reseating the cables and rebooting, but no change in error. I’m adding two photos, one from the VDEV tab and one from the DISK tab. Any command line tools I can use to aid in diagnosing? I’m not even sure where to start.

TrueNAS @ [system name

New alerts:

• Pool [poolName] state is DEGRADED: One or more devices could not be used because the label is missing or invalid. Sufficient replicas exist for the pool to continue functioning in a degraded state.
  The following devices are not healthy:

  • Disk WDC_WD40EZAX-00C8UB0 WD-WX32D83957EU is UNAVAIL

Current alerts:

• Pool [poolName] state is DEGRADED: One or more devices could not be used because the label is missing or invalid. Sufficient replicas exist for the pool to continue functioning in a degraded state.
  The following devices are not healthy:

  • Disk WDC_WD40EZAX-00C8UB0 WD-WX32D83957EU is UNAVAIL

[SmallBarky]

Did you follow the Documents for your version of TrueNAS on how to replace a disk?
Linked to version 25.10. change if you are on a different version.

Are the alerts pointing to your previous, removed disk SN?

Replacing Disks

[Johnny_Fartpants]

Select the UNAVAILABLE drive and click replace selecting your new drive. You can’t just take the old drive out and put the new one in your need to tell the system what to do.

[Anarchia]

Totally, makes sense. I don’t see anything in this drop down menu to select.

[SmallBarky]

Power the system off and check your cables to the new drive if you are not seeing it in the GUI. It should have showed on your disks screenshot, as long as that was after you put in the drive and attached power and SATA and then booted back up

If you can’t see your new disk in the BIOS / UEFI and TrueNAS, you may have got a DOA drive or something after checking power and SATA connections.

[joeschmuck]

What I see are:

1. You have one NVMe drive which is your boot-pool
2. You have one drive sda part of your freddieBoardPool, and the serial number is listed.

Questions:

1. What is the serial number of the new drive you installed? We only need the last 4 characters if they are different from K5K3.
2. Where did this “new” drive come from and is it really new/unused?
   3. Are the drive capacities the same or the new drive at least larger?

Actions:

1. If the drive is not new, you should wipe the drive first. Do it in a different computer if you can so you do not goof and wipe the only drive you have data on.

[Anarchia]

Hi, thanks for the reply.

I’ll get the serial number later but i can confirm its not K5K3, thats the serial number of a drive I bought a few months ago.

The new drive came as a replacement from an RMA request to western digital. Its a refurbished WD Blue. As its an RMA, it should be an identically sized drive to the original drive.

I will double check the cables are are all plugged in and seated correctly and then try again. A reboot of the machine did not detect the second drive.

[Fleshmauler]

@Anarchia

Its a refurbished WD Blue

I once had to push back onto WD for sending me an ‘equivalent space 8TB drive’; while burning it in I noticed that it performed about 75MBps slower than what I sent in. They took back the refurb & sent me a brand new identical model (as the original non-refurb’d drive) - performance on it was within +/- 5MBps & acceptable.

Also, unrelated, but a 4TB WD Blue might be SMR; double check if it is CMR or SMR. SMR eventually will have serious issues when used with ZFS.

Either way, it seems like the drive isn’t being detected. If you’ve confirmed & reseated power/data connections & it also isn’t showing up in bios, then the previous two points are useless as I’d guess the refurb is DOA.