dreamsy Posted November 23, 2021 Share Posted November 23, 2021 (edited) Hi, I've replaced a parity drive in my unraid machine and rebuild was all going smoothly but then the gui became unresponsive. The last status I saw was 99.9% and I believe it completed. The shares, Dockers, Vms are all responsive. I need some help in what I should do, I do not want to restart in case it still doing something in the background. I'd post the diagnostics but unfortunately don't know how without the gui (will search if there is another way). Thanks. nasbox2-diagnostics-20211123-1105.zip Edited November 23, 2021 by dreamsy Quote Link to comment
dreamsy Posted November 23, 2021 Author Share Posted November 23, 2021 So I restarted nginx and that has restored the webgui. I did run a few commands to restart earlier but when I checked the status it was 'not running' state. /etc/rc.d/rc.nginx start Quote Link to comment
dreamsy Posted November 23, 2021 Author Share Posted November 23, 2021 Gui has become unresponsive again. Please can someone look at the diagnostics for me. Thanks. Quote Link to comment
trurl Posted November 23, 2021 Share Posted November 23, 2021 Did the parity rebuild complete? For some reason system/df.txt is empty in those diagnostics, can you post new ones. Quote Link to comment
dreamsy Posted November 23, 2021 Author Share Posted November 23, 2021 Yes, I believe it all completed but then I started getting the gui responsiveness issues. I had to do a shutdown the server, it's all come up fine so far. Posting latest diagnostics. Thanks. nasbox2-diagnostics-20211123-1452.zip Quote Link to comment
trurl Posted November 23, 2021 Share Posted November 23, 2021 Just some things I notice in your diagnostics, unlikely to be the cause of your issue. ssd_pool is nearly full, but has no Minimum Free set. appdata and domains are set to prefer ssd_pool, but have some files on cache. Maybe that's intentional since ssd_pool is nearly full. system share is on the array instead of on a pool. This share has your docker.img (container executables) and libvirt.img. These files are always open when Docker or VM Manager is enabled in Settings. You want system share on pool so dockers/VMs performance won't be impacted by slower array, and so these open files will not keep array disks spinning. These latest diagnostics don't have any remote mounts. Couldn't see if there were any in the earlier diagnostics since df was empty. Did you have anything mounted remote in Unassigned Devices then? Quote Link to comment
dreamsy Posted November 23, 2021 Author Share Posted November 23, 2021 Thanks for the tips. There was some junk on ssd_pool that I could delete so that will free up some space. I've started to move the systems folder to one of the ssd_pool. I've got nothing mounted remote on unassigned devices. I have the Array and Pool devices, with only the flash drive in the unassgned devices (except for he old parity drive which will soon go into the pool). Hopefully this answers your question. Quote Link to comment
trurl Posted November 23, 2021 Share Posted November 23, 2021 16 minutes ago, dreamsy said: only the flash drive in the unassgned devices The boot flash shouldn't appear in Unassigned Devices. Looks like there is also another one listed in SMART. Is that the one you mean? Quote Link to comment
dreamsy Posted November 23, 2021 Author Share Posted November 23, 2021 I see two USBs in the main screen in the GUI. Might be the same physical USB drive. Quote Link to comment
dreamsy Posted November 24, 2021 Author Share Posted November 24, 2021 System is running fine now. The old parity drive has been added to the pool and I've made some changes suggested here. Thanks for the help. Quote Link to comment
itimpi Posted November 24, 2021 Share Posted November 24, 2021 18 hours ago, dreamsy said: I see two USBs in the main screen in the GUI. Might be the same physical USB drive. If you see the Unraid boot drive appear under Unassigned Devices, then that means that it has dropped offline and then re-connected with a different device Id. Quote Link to comment
JonathanM Posted November 24, 2021 Share Posted November 24, 2021 6 hours ago, dreamsy said: System is running fine now. The old parity drive has been added to the pool and I've made some changes suggested here. Thanks for the help. Since you have a previous parity drive in a data slot, be sure to delete all flash drive backups that referenced that drive as parity, and create new flash drive backups. If you were to accidentally restore one of the previous backups you would lose data when the system tried to build parity on your data drive. Quote Link to comment
dreamsy Posted November 24, 2021 Author Share Posted November 24, 2021 21 minutes ago, JonathanM said: Since you have a previous parity drive in a data slot, be sure to delete all flash drive backups that referenced that drive as parity, and create new flash drive backups. If you were to accidentally restore one of the previous backups you would lose data when the system tried to build parity on your data drive. Thanks for the advice, I really appreciate it. I wouldn't have done another backup - not realising that I had to. Also, on the USB issue - I have 2 physical usbs plugged in (one was hiding behind the other so did not spot it). Quote Link to comment
trurl Posted November 24, 2021 Share Posted November 24, 2021 21 hours ago, dreamsy said: I see two USBs in the main screen in the GUI. But your boot flash is appearing under Boot Device as it should, not under Unassigned Devices. What UD is listing under Dev2 is all the partitions (only one) on that UD. 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.