From a cold boot, the array does not start (either automatically or manually).  OS boots, GUI works, all drives light up green.  No errors with the array or drives shown on GUI.

 

Troubleshooting steps so far:

removed the USB drive containing the OS and scanned it using a Windows system checking for errors, none found

Installed Fix Common Problems plugin, ran it, fixed issues concerning notifications and SS plugin for cache drives.  Scan did not run in detail because array was not started

ran SMART reports, all drives passed.

Reboots and Turn On/ Off and repeated scans have not worked.

 

I have attached the diagnosis zip 

diagnostics-20170721-1115.zip

Did you try and start the array during before grabbing the diagnostics?

 

If so its probably this line

Jul 21 11:00:15 Tower kernel: md: do_run: lock_bdev error: -2

of which I have no idea.

 

Side question:  Are you really running a 100Mbit/s  network?  Just so rare nowadays to see one still running.

I dont think I did, but perhaps without thinking I attempted to start it again.  Let me know if I need to provide another log

 

It better be 1000, but thats a different problem for me to investigate later once the array is back online.

Safe thing is to try and start, then post another diagnostics.

39 minutes ago, Squid said:

Safe thing is to try and start, then post another diagnostics.

Good Point

tower-diagnostics-20170721-1453.zip

I see the same thing  (I'd guess you tried to start ~2:43)

 

Jul 21 14:43:22 Tower emhttp: err: mdcmd: write: No such file or directory
Jul 21 14:43:22 Tower emhttp: shcmd (130): rmmod md-mod |& logger
Jul 21 14:43:22 Tower kernel: mdcmd (41): start STOPPED
Jul 21 14:43:22 Tower kernel: md: do_run: lock_bdev error: -2
Jul 21 14:43:22 Tower kernel: md: unRAID driver removed

Admittedly, I don't know everything, and that error is something I'm not familiar with and can't recall seeing around here.  Perhaps @limetech might have some better understanding.  Also might want to email [email protected] pointing them to this thread with an explanation.

Most likely related to this:

 

Jul 21 14:38:29 Tower kernel: ata13.00: qc timeout (cmd 0x27)
Jul 21 14:38:29 Tower kernel: ata13.00: failed to read native max address (err_mask=0x4)
Jul 21 14:38:29 Tower kernel: ata13.00: HPA support seems broken, skipping HPA handling
Jul 21 14:38:29 Tower kernel: check SRS 0 00000001.
Jul 21 14:38:29 Tower kernel: drivers/scsi/mvsas/mv_sas.c 1435:mvs_I_T_nexus_reset for device[6]:rc= 0
Jul 21 14:38:29 Tower kernel: mvsas 0000:01:00.0: Phy6 : No sig fis
Jul 21 14:38:29 Tower kernel: drivers/scsi/mvsas/mv_sas.c 1870:Release slot [0] tag[0], task [ffff880419976f00]:
Jul 21 14:38:29 Tower kernel: sas: sas_ata_task_done: SAS error 8a
Jul 21 14:38:29 Tower kernel: ata13.00: failed to IDENTIFY (I/O error, err_mask=0x11)
Jul 21 14:38:29 Tower kernel: random: crng init done
Jul 21 14:38:29 Tower kernel: ata13.00: qc timeout (cmd 0xec)
Jul 21 14:38:29 Tower kernel: ata13.00: failed to IDENTIFY (I/O error, err_mask=0x5)

 

Do you know what ata13 is? is any device missing? it doesn't appear to be an array device, if unsure reboot and post new diags.

There are no hardware changes, but I'll investigate ata13 in case something died.  

Thanks for the help

 

I unplugged the optical drive, and that allowed the array to start.  I will further troubleshoot the optical drive, but for now the immediate need of getting to my data has been addressed.