Replacement Disk not Initializing

Hello,

A few weeks ago I had a disk just up and go missing from my main pool. Since then, I have been attempting to replace it and am running into an issue where 2 disks in a row just don’t show up in Truenas for me to use.

System setup:
TrueNAS - 25.04.2.4
Motherboard - Asrock X370 Killer SLI/ac
CPU - AMD Ryzen 5 1600
Ram - Corsair Vengeance LPX 32GB (2 x 16GB) DDR4 DRAM 3200MHz C16
PSU - Corsair CX 750M
LSI HBA (dmsg output below)

mpt2sas_cm0: LSISAS2308: FWVersion(20.00.07.00), ChipRevision(0x05)

Original disk layout was 4x Exos X16 14TB SATA (ST14000NM005G) in Z2

Attempting to replace the supposedly dead one with an Exos X14 14TB SATA (ST14000NM0258). [Yes, these are all used disks. This is for personal use and new costs are insane just to store my media and personal computer backups.]

I’ve been using sata power pigtails to solve for the 3.3v concern but these just won’t show up no matter what I try.

Here’s my lsblk output

NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop1 7:1 0 365.3M 1 loop
sda 8:0 0 12.7T 0 disk
└─sda1 8:1 0 12.7T 0 part
sdb 8:16 0 12.7T 0 disk
└─sdb1 8:17 0 12.7T 0 part
sdc 8:32 0 29.8G 0 disk
├─sdc1 8:33 0 1M 0 part
├─sdc2 8:34 0 512M 0 part
└─sdc3 8:35 0 29.3G 0 part
sdd 8:48 0 12.7T 0 disk
└─sdd1 8:49 0 12.7T 0 part
sde 8:64 0 238.5G 0 disk
└─sde1 8:65 0 238.5G 0 part
sdf 8:80 0 238.5G 0 disk
└─sdf1 8:81 0 238.5G 0 part
sdg 8:96 0 29.8G 0 disk
├─sdg1 8:97 0 1M 0 part
├─sdg2 8:98 0 512M 0 part
└─sdg3 8:99 0 29.3G 0 part

The original three 14TB drives show up just fine, but I cannot get the one that (apparently) died or either of the replacements to be recognized when going through the HBA.

Things I’ve tried:
-Using a different cable from the LSI card
-Using a different port on the LSI card
-Excluding the sata power pigtail
-Using a separate sata cable from the PSU
-Unplugging 4 other disks from power in case for some reason my PSU didn’t like the total draw
-Using a SATA data cable directly from the motherboard

When I plug the new disk into a SATA port directly on the motherboard instead, the original doesn’t show up at all. The newest one does show up (see lsblk below - shows up as ‘sbc’) but it cannot be used. When I try to replace and when I try to wipe it, I get ERRNO 5 input/output error - also below.

NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop1 7:1 0 365.3M 1 loop
sda 8:0 0 12.7T 0 disk
└─sda1 8:1 0 12.7T 0 part
sdb 8:16 0 12.7T 0 disk
└─sdb1 8:17 0 12.7T 0 part
sdc 8:32 0 12.7T 0 disk
sdd 8:48 0 12.7T 0 disk
└─sdd1 8:49 0 12.7T 0 part
sde 8:64 0 29.8G 0 disk
├─sde1 8:65 0 1M 0 part
├─sde2 8:66 0 512M 0 part
└─sde3 8:67 0 29.3G 0 part
sdf 8:80 0 238.5G 0 disk
└─sdf1 8:81 0 238.5G 0 part
sdg 8:96 0 238.5G 0 disk
└─sdg1 8:97 0 238.5G 0 part
sdh 8:112 0 29.8G 0 disk
├─sdh1 8:113 0 1M 0 part
├─sdh2 8:114 0 512M 0 part
└─sdh3 8:115 0 29.3G 0 part

Error when try to replace and when try to wipe:

Traceback (most recent call last):
File “/usr/lib/python3/dist-packages/middlewared/job.py”, line 515, in run
await self.future
File “/usr/lib/python3/dist-packages/middlewared/job.py”, line 560, in _run_body
rv = await self.method(*args)
^^^^^^^^^^^^^^^^^^^^^^^^
File “/usr/lib/python3/dist-packages/middlewared/schema/processor.py”, line 174, in nf
return await func(*args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^
File “/usr/lib/python3/dist-packages/middlewared/schema/processor.py”, line 48, in nf
res = await f(*args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3/dist-packages/middlewared/plugins/disk
/wipe.py", line 143, in wipe
await self.middleware.run_in_thread(self.wipe_impl, job, dev, mode, event)
File “/usr/lib/python3/dist-packages/middlewared/main.py”, line 627, in run_in_thread
return await self.run_in_executor(io_thread_pool_executor, method, *args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File “/usr/lib/python3/dist-packages/middlewared/main.py”, line 624, in run_in_executor
return await loop.run_in_executor(pool, functools.partial(method, *args, **kwargs))
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File “/usr/lib/python3.11/concurrent/futures/thread.py”, line 58, in run
result = self.fn(*self.args, **self.kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3/dist-packages/middlewared/plugins/disk
/wipe.py", line 89, in _wipe_impl
os.fsync(f.fileno())
OSError: [Errno 5] Input/output error

smartctl -a on the disk that finally showed up

=== START OF INFORMATION SECTION ===
Device Model: ST14000NM0258
Serial Number: ZHZ69JQ1
LU WWN Device Id: 5 000c50 0c4df5f59
Firmware Version: SS02
User Capacity: 14,000,519,643,136 bytes [14.0 TB]
Sector Size: 512 bytes logical/physical
Rotation Rate: 7200 rpm
Device is: Not in smartctl database 7.3/6028
ATA Version is: ATA8-ACS T13/1699-D revision 4
SATA Version is: SATA 3.0, 6.0 Gb/s
Local Time is: Tue Jan 13 00:01:34 2026 CST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

Read SMART Data failed: scsi error device not ready

I’m still new to Truenas (and anything non-Windows), so assume I don’t automatically know how to do the specific thing you’re asking me to do.

Thank you for any help you can give me.

Nothing fundamentally wrong with used disks, but where did these came from and do they work somewhere (desktop, USB enclosure…)?
The concern is whether you might have ben scammed and got DOA drives.

ST14000NM005G is a SATA drive.
Your new drive is ST14000NM0258 which is a SAS drive.

These are different protocols and may be why you are having the problems.

I’m going to have to crack open my main desktop to try on another system.

The two new ones that don’t appear to work came from an ebay seller with solid ratings.

It’s definitely a SATA drive, Seagate’s spec sheet, the label on the drive itself, and the fact that I can easily attach SATA cables indicate that.

You are absolutely correct. I just used a Seagate link which said it was SAS, however now that I looked at the Spec sheet, itis a SATA drive. Sorry for the mis-information.