During a parity check after rebuilding a drive that dropped out of my array during a previous parity check (the drive was fine unraid lost connectivity for unknow reason), a different drive just dropped out of my array and red-balled.

 

When I stopped the array, it showed the disk as not installed.  I powered down, checked the cables and they were connected and tight.  Re-seated the cables and booted back up.

Drive appears just fine in unraid after reboot, so I started the re-build

 

There is something wrong I think, if the server can re-build a drive just fine, but then fails out a different drive on a parity check run immediately afterwards, no system re-boot or changes made in-between.

 

Both disks that were dropped were connected to my 8-disk supermicro sas/sata pci-e card.

 

1. What could be causing these disk drops during parity check? 

2. I have attached my syslog for any assistance it may provide

3. I have attached my SMART report for the red-balled disk, please confirm the disk is OK

smartsdn.txt

syslogDec1.txt

Check BIOS settings . See my sig.

I will be home in a couple hours and will check my BIOS thank you.

Anything in the syslog or SMART report?

Is the drive good or ti I need to replace it?

SMART looks fine. Syslog shows some BIOS settings are not preferred.

Ok, I will go through the bios once the drive is done rebuilding in the morning, before I start the next parity check.

 

Can you tell which settings?

pnp should be disabled. There may be others.

I could not find anywhere to change pnp setting, I did disable the HD audio.

 

I have posted an updated syslog since making the change, please let me know if there are other bios settings I still need to change, thank you.

syslogDec2.txt

Parity check completed successfully.