I have a 21 disk + parity array, everything checks out fine with no errors, no smart problems, running unraid 5.0.5.

 

Suddenly and spontaneously this morning, disk15 has been completely erased.

 

There is nothing in the log that relates to this. Here is a snippet:

 

Dec 11 10:00:32 Stash last message repeated 10 times

Dec 11 10:10:43 Stash last message repeated 10 times

Dec 11 10:11:46 Stash last message repeated 26 times

Dec 11 10:17:45 Stash last message repeated 2 times

Dec 11 10:18:59 Stash last message repeated 7 times

Dec 11 10:20:54 Stash last message repeated 11 times

Dec 11 10:21:07 Stash last message repeated 9 times

Dec 11 13:53:23 Stash emhttp: shcmd (94): /usr/local/sbin/emhttp_event stopping_svcs

Dec 11 13:53:23 Stash kernel: mdcmd (394): nocheck

Dec 11 13:53:23 Stash kernel: md: nocheck_array: check not active

Dec 11 13:53:23 Stash emhttp_event: stopping_svcs

Dec 11 13:53:23 Stash emhttp: Stop AVAHI...

Dec 11 13:53:23 Stash emhttp: shcmd (95): /etc/rc.d/rc.avahidaemon stop |& logger

Dec 11 13:53:23 Stash logger: Stopping Avahi mDNS/DNS-SD Daemon: stopped

Dec 11 13:53:23 Stash avahi-daemon[2735]: Got SIGTERM, quitting.

Dec 11 13:53:23 Stash avahi-dnsconfd[2744]: read(): EOF

Dec 11 13:53:23 Stash avahi-daemon[2735]: Leaving mDNS multicast group on interface eth0.IPv4 with address 172.16.20.31.

Dec 11 13:53:23 Stash avahi-daemon[2735]: avahi-daemon 0.6.31 exiting.

Dec 11 13:53:23 Stash emhttp: shcmd (96): /etc/rc.d/rc.avahidnsconfd stop |& logger

Dec 11 13:53:23 Stash logger: Stopping Avahi mDNS/DNS-SD DNS Server Configuration Daemon: stopped

Dec 11 13:53:23 Stash emhttp: shcmd (97): ps axc | grep -q rpc.mountd

Dec 11 13:53:23 Stash emhttp: _shcmd: shcmd (97): exit status: 1

Dec 11 13:53:23 Stash emhttp: Stop SMB...

Dec 11 13:53:23 Stash emhttp: shcmd (98): /etc/rc.d/rc.samba stop |& logger

Dec 11 13:53:23 Stash emhttp: shcmd (99): rm /etc/avahi/services/smb.service &> /dev/null

Dec 11 13:53:23 Stash emhttp: Spinning up all drives...

 

the wiping happened some time between 10:21 and 13:53 (when I stopped and started the array to try and bring it back).

 

The only other piece of information I can think that would be of note is that this disk more than any was approaching being full - it had about 70GB free at the time of the incident.

 

I can't even rebuild with parity since it seems to unraid that everything is as it should be.

 

Any suggestions would be very gratefully received indeed.

First and most important, we need the complete syslog, zipped if necessary (please see this), and attached here.

 

I can reassure you that it is extremely unlikely that your data is gone.  I suspect a file system problem, so once the syslog has been saved, please see Check Disk File systems.

Is the disk still spinning ... would be my question.

Is the disk still spinning ... would be my question.

 

Even if dead, his parity protection would still provide access (slower) to the files and folders, plus he would see a red ball for the drive.