My unRAID machine went from 17 TB to 11 TB used overnight and I have no idea why
EDIT: u/Araero called it: I had set (and forgot) a rule in Maintainerr that was set to delete shows in Sonarr AND to take action after 30 days. Honestly a hilarious turn of events. I'm glad I have a backup of the shows I cared most about. So if you've been playing around with maintainarr like me, be sure to check you haven't left a funny setting like this on.
# Original post:
I am very confused and I hope someone can point me in the right direction to figure out what happened.
First, here are the specs of my machine:
unRAID: 7.2.2 CPU: Intel i3-12100 RAM: 32 GB
1x 1TB NVME Cache (single NVME stick)
2x 16TB HDD (1x parity, 1x array) 1x 4TB HDD (array) 1x unassigned 1TB HDD (for cctv)
When I checked my unRAID machine earlier today, I suddenly noticed it said "11.3 TB used of 20TB". It had been \~17TB used for the past 6 months, so this was quite a shock.
I immediately ran QDirStat and started testing media. To my relief (and surprise), I couldn't find a single thing out of order. All plex media i tried, played. My Immich media loaded. Sonarr and Radarr don't report any missing media that I didn't already know about. There are no SMART errors and no unRAID warnings/errors.Yet QDirStat also showed me only 11.3 TB is being used. EDIT: it turns out data has been deleted. See the edit at the end of the post.
I opened Grafana to see when this happened this is what I saw:

So it started at 7 AM this morning. Both drives in the array just took a nosedive for \~10 minutes.
Looking through the syslog, I didn't see anything that seemed relevant, but this is an excerpt from around 7 AM.
Dec 9 06:56:21 Haven kernel: docker0: port 3(veth3ba523e) entered disabled state Dec 9 06:56:54 Haven kernel: docker0: port 3(vethc0ffae3) entered blocking state Dec 9 06:56:54 Haven kernel: docker0: port 3(vethc0ffae3) entered disabled state Dec 9 06:56:54 Haven kernel: vethc0ffae3: entered allmulticast mode Dec 9 06:56:54 Haven kernel: vethc0ffae3: entered promiscuous mode Dec 9 06:56:57 Haven kernel: eth0: renamed from veth8222c47 Dec 9 06:56:57 Haven kernel: docker0: port 3(vethc0ffae3) entered blocking state Dec 9 06:56:57 Haven kernel: docker0: port 3(vethc0ffae3) entered forwarding state Dec 9 07:07:37 Haven flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update Dec 9 07:46:51 Haven emhttpd: spinning down /dev/sdc Dec 9 08:10:25 Haven emhttpd: spinning down /dev/sde Dec 9 08:10:36 Haven emhttpd: spinning down /dev/sdbDec 9 06:56:21 Haven kernel: docker0: port 3(veth3ba523e) entered disabled state Dec 9 06:56:54 Haven kernel: docker0: port 3(vethc0ffae3) entered blocking state Dec 9 06:56:54 Haven kernel: docker0: port 3(vethc0ffae3) entered disabled state Dec 9 06:56:54 Haven kernel: vethc0ffae3: entered allmulticast mode Dec 9 06:56:54 Haven kernel: vethc0ffae3: entered promiscuous mode Dec 9 06:56:57 Haven kernel: eth0: renamed from veth8222c47 Dec 9 06:56:57 Haven kernel: docker0: port 3(vethc0ffae3) entered blocking state Dec 9 06:56:57 Haven kernel: docker0: port 3(vethc0ffae3) entered forwarding state Dec 9 07:07:37 Haven flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update Dec 9 07:46:51 Haven emhttpd: spinning down /dev/sdc Dec 9 08:10:25 Haven emhttpd: spinning down /dev/sde Dec 9 08:10:36 Haven emhttpd: spinning down /dev/sdb
Are there any other logs or places I can look to figure out what happened? Has anyone had something similar happen?
~~If I figure out what data was deleted, I'll be sure to update this post.~~
EDIT: Data has indeed been deleted. It seems extremely random. For example, a folder of "rare media" with some of my favorite shows contained 19 shows, but now just 3 remain in that folder. It is insane to me that kept anything. Why those 3 shows?
Now I'm worried random folder have been deleted all over the system. What could be causing this??