Hello All,

Let me start by saying thank you in advance. I have read a lot of posts on these forums looking for answers and appreciate everyone's contributions. So again thank you to the community.

In reference to my issue, I have seen similar issues and tried to solve accordingly but to no avail. I will elaborate to all things I remember doing (*unfortunately I have not documented the steps taken like I always intend to do).

I am currently on unraid 7.1.4

I had my disk 3 fail.

I have tried:

• Restart. No Luck.

• I physically replaced the bad drive with a fresh equal size drive. No drive showed up below as unnasigned and allowed me to assign the drive to the array.

• I tried rearranging the cables from my HBA to make sure the cable was not bad. I then replaced the cable from the HBA and still got same results.

• I updated the BIOS and Firmware on the HBA through the CLI in the GUI of unraid. I am not able to get into the BIOS of the card during boot up by hitting CTRL+C. I attempted multiple "solutions" from GROK and ChatGPT to return that option to no avail.

• Updated the motherboard BIOS. No luck

• Added app Unassigned Devices and the replacement drive now shows but I am unable to do anything with it.

  

I have an extra HBA but am worried about if I switch it out will it destroy my array and I lose my data (* I have it backed up but would prefer not having to rebuild)

I wondered if running New Config would possibly help but have the same worry of losing my data.

I have uploaded my Diags as well as some screenshots. I hope this is helpful. Please let me know what else you would be looking for to help me get this issue resolved.

I also included a screenshot of my shares and would take an criticism of the setup and recommended changes.

Hardware is:
Asus Pro-Art Z690 Creator Motherboard

Intel Core i9-12900K Desktop Processor 16 (8P+8E) Cores up to 5.2 GHz Unlocked LGA1700 600 Series Chipset 125W

4x CORSAIR Vengeance DDR5 32GB (2x16GB) DDR5 5600 (PC5-44800) C36 1.25V - Black

LSI 9305-24i x8 lane, PCIe 3.0 Full Height SAS SAS 9305 12 Gb/s SAS Host Bus Adapter

2-14TB Parity drives

14-14TB Array drives utilizing XFS

3-NVME & 1-M.2 2TB drives for Cache Pool using ZFS

Corsair HX Series, HX1200, 1200 Watt, Fully Modular Power Supply, 80+ Platinum

Nvidia RTX 3060Ti Video Card

diags.zip

A lot of disks. How are they powered?

1 hour ago, oshns11 said:

wondered if running New Config would possibly help

The only thing you can rebuild after New Config is parity.

3 hours ago, trurl said:

A lot of disks. How are they powered?

Corsair HX Series, HX1200, 1200 Watt, Fully Modular Power Supply, 80+ Platinum Certified, Model Number: CP-9020140-NA

3 hours ago, trurl said:

The only thing you can rebuild after New Config is parity.

OK. So I am understanding this correctly, are you saying all other disks would lose their data in the Array or that I can use one of my parity disks to rebuild the new drive once it's found?

You can swap both cables from the new disk3 with another disk and see where the issue follows

7 hours ago, oshns11 said:

OK. So I am understanding this correctly, are you saying all other disks would lose their data in the Array

I am saying that if you New Config, it will want to rebuild parity based on all the assigned disks. New Config will rebuild parity, and won't affect any other disks. The main point being, you can't rebuild a data disk when you New Config.

7 hours ago, oshns11 said:

use one of my parity disks to rebuild the new drive once it's found?

Parity plus all other disks are read to provide the data to rebuild to a new drive. Parity doesn't contain any of your data, and parity by itself can rebuild nothing.

On 1/18/2026 at 7:44 AM, trurl said:

I am saying that if you New Config, it will want to rebuild parity based on all the assigned disks. New Config will rebuild parity, and won't affect any other disks. The main point being, you can't rebuild a data disk when you New Config.

Parity plus all other disks are read to provide the data to rebuild to a new drive. Parity doesn't contain any of your data, and parity by itself can rebuild nothing.

OK Makes sense.

On 1/18/2026 at 3:37 AM, JorgeB said:

You can swap both cables from the new disk3 with another disk and see where the issue follows

No changes. Still shows the same disk missing. All S/Ns are still the same in the disk and parity locations. There are some differences that I found from when I started this and that would be that the linux drive assignments have changed. Example: Parity 1 was labeled as (sdc) but is now labeled as (sdh) and so on. The S/Ns all stayed in the same number slot (disk 1, disk 2, etc.)

5 minutes ago, oshns11 said:

There are some differences that I found from when I started this and that would be that the linux drive assignments have changed. Example: Parity 1 was labeled as (sdc) but is now labeled as (sdh) and so on

This is normal. Can happen when disks are added, removed, or disconnected, or just on reboot. That is why we usually don't talk about sdX except in very specific situations. Unraid identifies disks by Serial #

2 minutes ago, trurl said:

This is normal. Can happen when disks are added, removed, or disconnected, or just on reboot. That is why we usually don't talk about sdX except in very specific situations. Unraid identifies disks by Serial #

Makes sense. Any other suggestions to try?

On 1/18/2026 at 4:37 AM, JorgeB said:

see where the issue follows

14 minutes ago, oshns11 said:

shows the same disk missing

Seems like the disk is the problem then. Maybe original died, and replacement has some problem as well.

Can you see either disk in another system?

Like mentioned by trurl, if the issue follows the disk, that is likely the problem

2 hours ago, trurl said:

Seems like the disk is the problem then. Maybe original died, and replacement has some problem as well.

Can you see either disk in another system?

9 hours ago, JorgeB said:

Like mentioned by trurl, if the issue follows the disk, that is likely the problem

So I checked both devices on Windows and Linux using a USB adapter. Was able to find it both times and format. Then thought I would test it back in unraid using the same usb adatper and it showed up and was able to format to xfs. So that make me believe it is a bad HBA card because the switching of cables from one drive to another and from old to new had no effect. I have an extra card that I will swap in. I just am wondering if doing so would normally no affect the array?

32 minutes ago, oshns11 said:

So that make me believe it is a bad HBA card because the switching of cables from one drive to another and from old to new had no effect.

That doesn't make much sense, if the previous disk that was there was working, that one should also work.

6 hours ago, JorgeB said:

That doesn't make much sense, if the previous disk that was there was working, that one should also work.

My apologies. I meant to say that the new drive worked on both Windows and Linux. The old drive is unavailable on both.

On 1/18/2026 at 4:37 AM, JorgeB said:

swap both cables

Data and power?

2 hours ago, trurl said:

Data and power?

Yes, both were swapped. I swapped cards and it still did not see the new hard drive, not even in the bios utility for the card. Pretty sure you're right about the drive being the issue. Don't know why it can't be seen through the card but can be seen through USB. I ordered another drive of the same brand and model. We shall see what happens with that. Won't be here until Jan. 29th, so I will update when it arrives.

Make sure it's not the 3.3v SATA issue, try using a molex to SATA adapter with the drive.

16 hours ago, JorgeB said:

Make sure it's not the 3.3v SATA issue, try using a molex to SATA adapter with the drive.

I tried a SATA adapter just now and that didn't work. Thanks for the suggestion. Did not know about that issue.

I was at work today and managed to snag a brand new 24TB drive to borrow. That showed up right away. So now I will have to wait until the new 14TB shows up. Thank you all for your help. I will mark as solved.