The server booted itself up as normal this morning, only to show everying as NEW.

 

I've attached a syslog before I try a reboot..  I assume I haven't lost anything, but the array is unprotected until parity is rebuilt?

 

The only other thiing i saw in last nights syslog was some sort of error shutting the array down.  Could this be connected?

 

Apr 27 23:00:00 Tower logger: Powerdown initiated
Apr 27 23:00:00 Tower logger: Shutting down Samba
Apr 27 23:00:00 Tower logger: Syncing the drives
Apr 27 23:00:09 Tower shfs(1): duplicate object: /mnt/disk4/./ehthumbs_vista.db
Apr 27 23:00:50 Tower last message repeated 3 times
Apr 27 23:01:17 Tower last message repeated 2 times
Apr 27 23:01:28 Tower logger: Killing active pids on the array drives
Apr 27 23:01:28 Tower logger: Umounting the drives
Apr 27 23:01:31 Tower logger: Stopping the Array
Apr 27 23:01:31 Tower kernel: mdcmd (11): stop
Apr 27 23:01:31 Tower kernel: md: 2 devices still in use.
Apr 27 23:01:32 Tower logger: cmdOper=stop
Apr 27 23:01:32 Tower logger: cmdResult=failed
Apr 27 23:01:32 Tower logger: 
Apr 27 23:01:33 Tower logger: Saving current syslog to /boot/logs/syslog.txt

Everything looks fine, except for a bad checksum on the superblock, probably related to the errors you saw on the previous shutdown.  To get back to normal, just do the Trust My Array procedure, follow the instructions carefully.

Thanks, I followed that and now a parity check is in progress.