VelcroBP Posted August 7, 2022 Share Posted August 7, 2022 I recently completed file system conversion on all my data disks following the guide from the wiki. All seemingly went well. However, the next scheduled mover task seemed to be hung up (kicked off @ 0130, still running @ 0730). I panicked and stopped mover via CLI. The server would not seem to reboot. I issued POWERDOWN via CLI and it eventually shut down, although uncleanly. After the resulting parity check (0 errors), the next scheduled mover task also seemed frozen. At this point, I launched MC and looked on each Data disk for any duplicates of something on the Cache disk. I found a couple of "***.partial" files that I don't think would be a problem, but deleted anyway because the downloads are not important. After verifying there is nothing on the Cache that's already on an array disk, I invoked mover again. According to the log, it seems to start on the first file and then just sits there. On the main UI page, there appears to be very slow write activity to an array disk, as well as reads on the cache. Below is the NetData for the array disk (which is shingled): Quote Link to comment
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.