Hi,

I have an 8 disk unRAID array with 2 parity disks (plus 2 cache SSDs).

2 of my disks failed (1 parity and 1 data) and ive replaced them with new drives.

On boot everything seems fine, but when i try and start the array it just sits there and wont start.

I can open a second browser and shutdown or restart unRAID...but the same thing happens again.

Thanks,

Cameron

raid-diagnostics-20250329-1848.zip

Check/replace cables for disk3 and post new diags after array start.

Hi, Thanks for the fast response

 

I had already replaced all teh SATA cables with brand new ones, however after your email i checked and that drive had a different cable (different brand/design) to all the others. So i replaced it with another brand new one (brand new out of sealed packet again) but this time matching the other 7 cables in use.

 

New log attached.

 

Im suspecting a faulty drive - its late at night here and i can hear one of the drives 'resetting' over and over again.

 

I can see the same error repeating in the logs...how do i convert the ata mention in the logs "ata6.00: failed command: READ FPDMA QUEUED" to a disk number?

 

 

raid-diagnostics-20250330-0422.zip

I tried something else too (new log file attached):

 

All i did was swap the suspected faulty drives SATA cable with another drive - at the mainboard. (i.e. swap two SATA cables at the mainboard)

 

I can see in the logs now that instead of ata6.00 having errors over and over again it is now ata4.00 that is having errors over and over.

 

To my mind that rules our the SATA cable and the port on the mainboard...unless I'm missing/misunderstanding something.

 

Thanks again,

 

Cameron

raid-diagnostics-20250330-0515.zip

ATA4 is now disk3, so since the issue follows the disk, looks like it failed, do you still have the old disks that were replaced?

Yes, i have all the disks.

 

(I also have all my original RAID 6 disks that i copied the data from).

 

I have bought 5 new 20Tb disks now and will start from scratch with a fresh boot USB and fresh drives and recopy the data...hope for better luck this time!

 

So, ive installed 5x brand new 20TB drives.

I've installed an unRAID trial on a brand new USB.

And i cant even create an array.

Log file attached.

 

Is there an issue with unRAID and 14th Gen Core i9? (i cant find any report of it, i have the latest BIOS for my mainboard, and this mainabord, CPU, RAM has been running Windows Server HyperV for ages without issue).

raid-diagnostics-20250330-2115.zip

17 minutes ago, cjaffrey said:

Is there an issue with unRAID and 14th Gen Core i9?

Nope, but there have been multiple users with those and similar CPUs affected by the Intel 13/14 gen issue, and since the Unraid driver is crashing, and that is almost always a hardware problem, yours also may be defective, could also be a RAM problem if you like to run memtest first.

Ive run memtest and got a PASS -  ive also swapped out the RAM - having the same issue.

 

What is the 14th Gen issue ...would it affect unRAID but not Windows?  (I know about the power issues that are meant to be resolved by BIOS updates - which i have)

 

Edited March 30, 20251 yr by cjaffrey

Google "intel 13/14th gen issues", and it will also affect Windows, just will be more visible with Unraid during parity sync due to CPU load.

FYI, I switched out the CPU for a i9-12900K (everything else exactly the same) and the array is now building.