shredswithpiks

Same issue on my end. Logs have the following errors over and over and over: Either a database problem or a mapping problem. I *think* they may have added in a /config path that didn't used to be defined or expected, so Sonarr can't find the config files. Maybe? edit: seems to be a database problem edit 2: decently easy fix in my case. sonarr creates periodic backups and drops them in /config/Backups (or from Unraid host - /path/to/appdata/sonarr/Backups... in most cases that's probably /mnt/user/appdata/sonarr/Backups by default). Moved /mnt/user/appdata/sonarr/sonarr.db to /mnt/user/appdata/sonarr/sonarr.db_old, unzipped the second-to-most-recent backup and moved it's sonarr.db to /mnt/user/appdata/sonarr/sonarr.db. Started right up after that.

I'm having similar issues. Every few days, sometimes after about a week, my unraid server will go very unresponsive. One thing I've noticed is that my memory utilization is going way up. I have Plex transcoding to memory and it doesn't seem to be cleaning up the transcode files after upgrading to 6.12.x. I'll have large files in there eating up almost all of the 32GB ram I have. I think the server is just choking on running out of memory. Frustratingly, this worked perfectly fine prior to 6.12.x (my unraid box has been chugging along for about six years now...). I'm wondering if others with the unresponsive server issue are also running plex and transcoding to memory. I grabbed an old nvme drive to transcode to instead, made the change this morning, and will see if that stablizes things for me.

I just updated and the array went straight into a parity check. I doubt your issue is result of a power outage/dip/whatever. But, docker and plex seem to be running without needing me to kick it with workarounds, so that's nice.

Hmm.... since upgrading, system has been crashing about once a day and I have to hard power cycle it. It comes back fine, and no errors until it crashes. But since it hard locks, I can't pull diag/logs to troubleshoot. Anyone else having a similar issue? I've switched docker to ipvlan, made sure I don't have any of the incompatible plugins running, and sanity checked all the settings I can think of. Probably going to have to roll back. System was solid as can be on previous versions and the only time I ever had to reboot was to upgrade

OK, that worked flawlessly! Thanks for the help!!!

Thanks I will give this a shot!

Yup, understood. It's not critical data or anything, just a place I've been throwing old disks I've upgraded to larger disks in the main array. Kind of a nice spot for crunching large sets of data I don't need to keep around very long. Really just looking to understand whether cache pools will try to import existing filesystems or if they create new filesystems every time - in case I can save myself a bit of time bouncing data around.

So, long story short... I had a 3 disk BTRFS RAID5 cache pool using disks sitting in a mediasonic probox USB 3.1 enclosure. I added a 4th drive to the probox, and that caused the probox to set new serial numbers for all the disks (kind of a wtf moment). I can still manually mount the btrfs array, but would like to put it back into a cache pool through the GUI. If I set up a "new" cache pool and add the disks back in the same order they were (just using the "new" serial numbers), will unraid just see the btrfs filesystem and import/adopt it? Or is it going to reformat everything and try to create a brand new filesystem?