syslog attached.

 

Happened while I was copying files from one disk to another. What to do next?

syslog.zip

SMART test on the disk (sdb) failed saying "No such device" so I guess it must be an unseated SATA or so, right?

 

Can get to fixing that once the copying gets done.

After the copy got done, I stopped the array. When I did this, the parity disk showed a blue ball - new parity disk installed. I just restarted the array and now its rebuilding parity. Strange! I haven't even opened the cabinet to check cables or anything.

Did the parity rebuild work okay?  Hopefully all's well now, but you should take some steps to protect against a repeat.

 

As I suspect you know, your syslog shows a TON of read errors, write errors, and rejected commands to "offline device" with regard to the parity drive.

 

I suspect you've got a marginally seated SATA cable.    The vibration of constant access can cause a marginal connection to have issues -- which is likely what happened.

 

Did you use latching cables for all of your SATA connections?    If not, I'd replace them all.    In any event, I'd reseat your SATA cables -- especially on the parity drive.

 

 

Thank you. I will look this up since the same problem has happened again today.

 

I am using latching type connectors. But will still check the connections.