I messed up, I saw that my motherboard was a year behind on the latest bios update and decided to update. I am on the latest Inraid 7.3.1

TUF GAMING Z790-PLUS WIFI now updated to Version 1836 Intel i5 14600k

After that Unraid was running fine , array on line docker containers and plugins are working . Multiple remote plex users streaming no issues . 1st of the month I had a Parity check scheduled it started everything started to read then certain CPU cores pinned at 100 and parity check stalled not progress past the 0.1% .

I did a check with google and made some power management changes to the bios settings but still no luck parity check stalled each time.

the last attempt to run parity check one of the drives gave errors and Unraid removed the drive . I stopped the array unselected that drive and started the array again . The drive is emulated I tried to run unbalance to move the files that are now emulated to a good drive but it too stalls out.

Here is what I did change in the bios

1. Performance Baseline to ASUS Advanced OC

2. Disable Aggressive SATA Link Power Management (ALPM)

3. Readjust RAM Stability (Disable XMP / AEMP II) set to Ai Overclock Tuner to auto

4. PCI Express Native Power Management to Disabled.

5. Change PEG - ASPM and PCH - ASPM states to Disabled.

Unconfirmed 114525.crdownload

Please post the complete diagnostics, and make sure you confirm the downaloed file in Chrome so that it gets renamed to zip

Here is the diagnostics file

tower-diagnostics-20260607-0822.zip

Looks like disk5 was disabled, but I don't see disk5 in the SMART reports.

Emulated disk5 is mounted but it appears to be empty. Is disk5 supposed to be empty?

emulated disk 5 has 559 gb of data and the files are still available in SMB share from windows machine. As well when I try to use Unbalanced it finds Disk 5 emulated files, goes through all checks and shows good to move to another disk, when I start a move it starts as usual but then stalls and remaining time continues to go up with nothing moving.

Edited June 7Jun 7 by chadsfake

I should have said nearly empty. Filesystem overhead can make it seem like a drive has a lot of used space even it if is empty. Disk5 has a lot less used than many of your other disks so I thought perhaps it should have more.

Diagnostics does show one user share with files on disk5

U--------S                        shareUseCache="yes"     # Share exists on cache, disk1, disk2, disk3, disk4, disk5, disk6, disk7, disk9

Why are you trying to move files from an emulated disk?

I don't have another disk to replace this failed drive right now and want to move the emulated files to another working disk.

Two things are not working as they should and I suspect they are related

1. I can't move these files from the failed disk emulated

2. I could not run a parity check previously before this disk failed.

Both of these tasks stall but shares, dockers etc still work.

Do you still have the original disk5? In what way did it "fail"? Connection problems are much more common than disk problems.

Yes it is in place still just disabled . I am not concerned with that disk right now and will pull it and test in a dock. My concern is why can't I run unbalanced to move the files from emulated to another disk and why I could not run parity check before this disk failed .

Do you think it is all related to this disk being close to failing when I was trying to do a parity check that it was locking up the system? If it is still in my server connected but disabled could this be causing unbalanced to now run?

I wanted to try to move the files before shutting down the server and removing this drive

6 hours ago, chadsfake said:

it is in place still just disabled

9 hours ago, trurl said:

I don't see disk5 in the SMART reports

Is it still plugged in to the controller? If not, plug it back in and post new diagnostics. It can be tested in place no need for a dock.

6 hours ago, chadsfake said:

related to this disk being close to failing

Not seen any evidence there is anything wrong with the disk.

7 hours ago, trurl said:

Connection problems are much more common than disk problems.

If the disk is OK it would be simpler and better to just rebuild it.

The disk is still connected , I have not shut down the server or removed any cables or disks .

Is the problem I have having not being able to run unbalanced now or the parity check before disk 5 was removed by Unraid being caused by this disk ?

The server should not crash just by dealing with an emulated disk. Diags show the disk dropping offline before; this is typically a power/connection issue. Check/replace cables for disk5 and post new diags after array start (the disk will still be disabled; this is expected)

I shut down , checked cables even moved the sata cable to an unused port and here is the diagnostics file after restart.

tower-diagnostics-20260608-1241.zip

Still not seeing any drive that might have been disk5. How is that disk plugged in to power?

I switched power leads with another drive and no change.

But lets put that aside I am fine to consider that drive dead and look at the bigger problem I am having.

That is the issue of my bios update and the impact it is having on trying to do two things.

1. I can't currently use unbalance to move files (which I would like to do before I try anything else)

2. Iwas not able to complete a parity check

You cannot run a parity check with a disabled disk and single parity, can run a read check. Enable the syslog server, start a read check (or a rebuild if you have a spare disk) and post that log if the server crashes.

OK I think I have this solved now. The bios updates looks to have made my two sata controllers stop working . I had a ASM1166 M.2 PCIE to SATA and another older PCIe to sata . I replaced those with one LSI 9300-8i mini sas to sata and all looks to be working fine now except disk5 that failed won't recognize in the Unraid server or using a dock on another machine that will be RMA'd. The controllers had been working fine for years previous to the upgrade.