My new Unraid server never auto-starts - comes up 'Array stopped - stale configuration' each time.  After starting the array  manually, it runs perfectly.  So why doesn't the array doesn't auto-start ??

 

If I start the GUI while booting, 1-5 disks are missing ...

But all disks are found when the GUI is refreshed. Weird ...

 

syslog (diagnostics attached) shows all disks are commanded to spin-up and I hear them spooling in 4 groups.
8x drives are 7200rpm SAS 4TB Seagate Constellations, 2x drives are SATA 5400rpm/Intellipower, which always spin up in time.
Seagate quote startup current as 2.16A max at 12V and 0.52A max at 5V
HBA is 1x SAS 9220-8i flashed to IT mode.
PSU is Seasonic S620-12 II, giving 2x 24A at 12V at 24A and 24A at 5V.
Onboard disk write-caching in enabled.
Motherboard is GA-Z68AP-D3 V2.0

 

The drives not ready in time have 'later' drive letters (sdh sdi sdj sdk). They're not on the end of the PSU cables.
I use 2 SATA PSU cables and 1 peripheral PSU cable - max 3 drives per cable.
I can't see SMART errors on the Constellations and have 1x CRC error on a SATA drive.

 

Has anyone else had this slow start spin-up and not auto-starting?
Do SAS drives or Constellations take longer to spin up?
Do I have a PSU/HBA/HDD problem that needs fixing?
Is there a workaround to get the array to auto-start a bit later?
Or am I overlooking something else?

 

Super grateful for any suggestions !

 

Thanks, Judy
 

tower-diagnostics-20191114-2335.zip

What happens if you go to Settings -> Display Settings and change the setting of the "Display world-wide-name in devce ID" item?

HBA BIOS quite out date.

 

Nov 14 15:32:53 Tower kernel: mpt2sas_cm0: LSISAS2008: FWVersion(15.00.00.00), ChipRevision(0x03), BiosVersion(00.00.00.00)

 

5 hours ago, JudyZ said:

Do SAS drives or Constellations take longer to spin up?

You have eight 4TB Seagate Constellations, does problem fixed at some disks only or random ?

Edited November 16, 20196 yr by Benson