I took my drives off line to replace my parity drive.  I spun them all back up and ran preclear on my new drive.  All my drives came up with the exception of my SSD cache drive.  It had worked perfectly until I took it off line...this wasn’t the first time I’d taken it off line.  It shows it as unmountable no file system 32.

Edited October 1, 20178 yr by bprohs
Solved

Post your diagnostics:

Tools - > Diagnostics

I’m sorry, but I’m not sure how to go about doing that.  I ‘ll try and figure it out and get back to you...thanks

 

2 minutes ago, bprohs said:

I’m sorry, but I’m not sure how to go about doing that.  I ‘ll try and figure it out and get back to you...thanks

7 hours ago, johnnie.black said:

Post your diagnostics:

Tools - > Diagnostics

Follow Jonnie's instructions...

Got it...I missed the thing at the bottom...I guess at 70 my eyesight isn’t what it used to be...haha

tower-diagnostics-20170930-0908.zip

Hopefully I did this right...Thanks for any help

One of your cache devices (cache1) dropped offline a couple of days ago:

 

Sep 28 04:18:39 Tower kernel: ata7: hard resetting link
Sep 28 04:18:39 Tower kernel: ata7: SATA link up 3.0 Gbps (SStatus 123 SControl 310)
Sep 28 04:19:09 Tower kernel: ata7.00: qc timeout (cmd 0xec)
Sep 28 04:19:09 Tower kernel: ata7.00: failed to IDENTIFY (I/O error, err_mask=0x4)
Sep 28 04:19:09 Tower kernel: ata7.00: revalidation failed (errno=-5)
Sep 28 04:19:09 Tower kernel: ata7.00: disabled

Can't see when it went unmountable since there are some hours missing from the logs, you should power down, check cables on cache1, power back up, start the array, grab and post new diagnostics.

Thanks Johnnie!  I'm sure glad you know what this says, because I have no idea what I'm looking at.  I'll check the cables and grab the diagnostics like you recommend.

I really appreciate your help!

 

Johnnie, I took my server down to check my cables and when I powered it up, both of my cache drives came up..so all is good.  I guess I should have rebooted it after I ran preclear on my new parity drive.   Live and learn...Again thanks for the help!  I did learn a lot from the experience.

 

Edited October 1, 20178 yr by bprohs

Those are the same diags, wrong file?

How do I go about saying my problem is solved?

If the cache mounted after rebooting you want to run a correcting scrub and make sure all errors are corrected, also check SMART for the disk that dropped offline.

 

 

I’ll do both of those...thanks.