poku

I've been thinking same; the unraid UI is definitely a bit outdated and uninformative at times. I would love to see refreshments like in the screenshot OP provided. Of course there are dockers, but it makes sense for all this information to exist in the UnRAID GUI.

I think I've been having similar problem. Started after the latest update here as well. The whole webUI goes unresponsive, iowait times go high as hell. Going to commandline to see some system details, most of the times the commands just hang and I can't even CTRL-C out. The system did that just a moment ago, had to force shutdown and I'm now doing parity check. I was thinking it could be a bottleneck from slow HDD's and things like finished downloads overloading the transfer capacity? I started to at the Docker containers, but could not find any clues if they are the root of this problem. What containers do you have enabled and are in use? Does anyone have any good tips where to look when trying to find the cause for high iowait? I found this discussion from Docker Github, could it be related to this one? They seem to have concluded it to be a kernel bug.

Thanks! I tried to move one docker there and it worked fine. I'll have to transfer the rest later. Just to be clear - you cannot map user shares to the unassigned device? I fear it could cause problems because the device isn't show in any menus and therefore it appears you can't assign user shares there or use new permissions tool? I managed to quite thoroughly fuck up the server by filling up the cache with file transfers, making all the Dockers and the system etc to hang up. A separate SSD for all the important stuff could maybe prevent this for happening again!

I was wondering the same thing as Kukielka. I didn't find an option to assign an user share like appdata or VM storage to a certain disk using Unassigned Devices plugin. I tried to google it, but didn't find how to do it. Do you have any good info about it or could you maybe provide the steps to do it? Thanks!

Oh man. I feel dumb now. I knew it should be something easy, but for some reason I missed that part of the wiki. Does not show faulty anymore, data rebuild in process. Thank you very much!

I think I'm in a bit of a similar situation! The disk appears faulty; file system status "-", and red cross besides the drive saying "Device disabled, contents emulated". The error appeared after starting up the server one day, worked just fine when shutting down. Possibly caused by sudden shutdown? I tried running xfs_repair with -v -L parameters, but it did not do anything. SMART details appear fine. Is it possible that a brand new drive just suddenly fails like this? What can I do next to fix it? Thank you very much in advance! EDIT: I am dumb. If anyone else happens to stumble upon the same question, see the post below for easy fix.