alanb007

Hi there My setup was bare bones. No VM's, plugins or apps. Just file backup In the end i gave up and moved to OMV. I just could not get Unraid to close down correctly and on restart, it wanted to do a parity check. While i know the basics for Linux, solving this kind of problem is above my pay grade 🙂 Good luck in solving your problem all the best Alan

Does this help?? This is what is in the log straight away Oct 21 22:21:24 Tower emhttpd: error: get_key_info, 577: Invalid argument (22): get_message: /boot/config/BTRS.key (-3) Oct 21 22:21:25 Tower emhttpd: error: get_key_info, 577: Invalid argument (22): get_message: /boot/config/BTRS.key (-3) Oct 21 22:21:26 Tower emhttpd: error: get_key_info, 577: Invalid argument (22): get_message: /boot/config/BTRS.key (-3) Oct 21 22:21:27 Tower emhttpd: error: get_key_info, 577: Invalid argument (22): get_message: /boot/config/BTRS.key (-3) Oct 21 22:21:28 Tower emhttpd: error: get_key_info, 577: Invalid argument (22): get_message: /boot/config/BTRS.key (-3) Oct 21 22:21:29 Tower emhttpd: error: get_key_info, 577: Invalid argument (22): get_message: /boot/config/BTRS.key (-3) Oct 21 22:21:30 Tower emhttpd: error: get_key_info, 577: Invalid argument (22): get_message: /boot/config/BTRS.key (-3) Oct 21 22:21:31 Tower emhttpd: error: get_key_info, 577: Invalid argument (22): get_message: /boot/config/BTRS.key (-3) Oct 21 22:21:32 Tower emhttpd: error: get_key_info, 577: Invalid argument (22): get_message: /boot/config/BTRS.key (-3) Oct 21 22:21:33 Tower emhttpd: error: get_key_info, 577: Invalid argument (22): get_message: /boot/config/BTRS.key (-3) Oct 21 22:21:34 Tower emhttpd: error: get_key_info, 577: Invalid argument (22): get_message: /boot/config/BTRS.key (-3) Oct 21 22:21:35 Tower emhttpd: error: get_key_info, 577: Invalid argument (22): get_message: /boot/config/BTRS.key (-3) Oct 21 22:21:36 Tower emhttpd: error: get_key_info, 577: Invalid argument (22): get_message: /boot/config/BTRS.key (-3) Oct 21 22:21:37 Tower emhttpd: error: get_key_info, 577: Invalid argument (22): get_message: /boot/config/BTRS.key (-3) Oct 21 22:21:38 Tower emhttpd: error: get_key_info, 577: Invalid argument (22): get_message: /boot/config/BTRS.key (-3)

ok i just enabled it

tower-diagnostics-20221021-2143.zip Hi Everyone. I am not an expert with Unraid and have trawled as much as i can but i am getting nowhere. I suspect i am missing something simple... I have a very basic setup. No docker, no plugins, no apps, no VM's. Just file storage. The unit is not running all the time, its only on when i need it. This suits my requirements. It was working perfectly and then it suddenly stopped shutting down properly. Start up used take take less than a minute but now it takes about 5 or 6 mins. Then when i log in, it still takes a while for the array to start. On shutdown, the computer never fully turns off. There is a line on the screen that says umount: /dev: target is busy I do not know whether this is the problem but even if it is, i do not know how to get rid of it. Motherboard is Gigabyte Technology Co., Ltd. X58A-UD5 with 10 hard disks (includes 1 ssd for cache) Any wise guidance would be really appreciated. While i have learned a lot with Linux over the years, this kind of problem is above my pay grade 🙂 Thanks everyone Alan