I had a drive temporarily connected via a SATA->USB connector and it was assigned as to the array as disk12. I was using it as a temporary destination while migrating disks from Reiserfs to XFS. The drive was in the midst of having another drive copied to it when it got unplugged. I noticed that the copy was continuing in the PuTTY session when I got to my desktop. I've since stopped the copy.

 

My plan of action is:

• Stop the array
  
• Plug the drive back in
  
• Start the array
  
• Run a parity check
  
• Continue as if nothing else happened

 

Is there anything else I need to do? Anything else I should check? Fortunately, the drive itself didn't fall or get moved significantly, it was just the adapter that got pulled off the back of it.

 

I'm attaching diagnostics. I had to break it into 2 pieces because the file size limit was exceeded. Part 1 is everything but the logs, Part 2 (attached to the 1st reply) is the logs - I had to set 7Zip to maximum compression to get it under the 320k file size limit.

nas-diagnostics-20161127-1220_Pt_1.zip

Here are the logs

nas-diagnostics-20161127-1220_Pt_2.zip

I haven't looked at the logs, but theoretically if you have a parity drive, the disconnected drive would be seamlessly emulated by the rest of your drives, and it would be red balled. If that is the case, the drive needs to be rebuilt, using the procedure for a red balled drive outlined in the FAQ. You can't run a parity check with a red balled drive, it must be rebuilt first.

Like Jonathan guessed you have a disable disk, you'll need to rebuild it.

Thanks for the confirmation, guys.