Jaster Posted May 30, 2021 Share Posted May 30, 2021 Hi Guys, I just started a new Server - my first Ryzen try - after assigning some disks I tried installing Krusader. It took very long (talking minutes). Any Container operation I try, basicly takes "forever" - it does complete however. I attached my diags, maybe I need to set something up differntly for ryzen? ferrum-diagnostics-20210530-1612.zip Quote Link to comment
Squid Posted May 30, 2021 Share Posted May 30, 2021 May 30 16:09:09 Ferrum kernel: mdcmd (36): check correct May 30 16:09:09 Ferrum kernel: md: recovery thread: recon P ... May 30 16:09:05 Ferrum emhttpd: shcmd (53): /usr/local/sbin/mount_image '/mnt/user/system/docker/docker.img' /var/lib/docker 10 # Share exists on disk1 Perfect storm. The system share (which is holding the docker image) only exists on the array (parity protected), and you're currently running a parity check. Ideally, you want the docker.img file to be on the cache drive. The share is set to be cache prefer, but the system can't move any file that's in use, and additionally you have the share set to use "cache" pool, but the drive is part of the "nvme" pool. Set the cache pool it's using to be "nvme". Disable the docker service (Settings, Docker), then run mover. When it's done re-enable. Alternatively instead of running mover, just delete the image and reinstall via Apps - Previous apps. Quote Link to comment
Jaster Posted May 30, 2021 Author Share Posted May 30, 2021 lol. That was easy. Thanks Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.