jay_busacca

So I fixed mine and it ended up being very simple. I stopped my container, deleted my log.db file, restarted, that was it. The log file was corrupted.

We're you able to fix this? I have the same error since switching repositories.

7 is the first half, 7 cpu and 23 HT, but your point stands. I'm going to isolate 23 as well and see if that solves the issue. Thanks for the idea!

I searched the forums and it seems this may be a known issue, apologies if I missed a fix. i have cores 7, 8-31 pinned to a VM and isolated as well, but my docker containers, mostly Plex, stil hit core 7 all the time. I don't understand what I'm doing wrong. Any help is appreciated.

I'm really treading into "don't know what i'm doing" territory, but i rebooted and my shares came back. Now both cache disked have been disabled by Unraid and emulated, presumably because I interrupted the mover process. Now i have an issue with disabled disks, but i'll read the forums for a solution.

Hi All, I desparately need help as I really think I screwed up: I followed the steps to upgrade my cache pool from two 128gb drives to 2 1tb drives. Set the shares to 'yes', invoked mover, swapped drives, set share preference, mover again. Here's where I f*cked up. I set one share to "prefer" cache when I don't think I should have, as it's a ton of media files. I went to the share and changed the preference, but I didn't stop the mover. Now *all* my shares have disappeared. Currently panicking, not sure how I can fix this. Any help is appreciated.

This would be a great addition to the dashboard!