Koi Posted August 28, 2020 Share Posted August 28, 2020 Been trying to get Macinabox working on and off since installing unraid. Took another swing at it this week and machine has been rebooting and starting parity checks since. Fix Common Problem reporting hardware errors. Diagnostics attached. I welcome and am grateful for any assistance. Thanks! deepthought-diagnostics-20200827-2152.zip Quote Link to comment
trurl Posted August 28, 2020 Share Posted August 28, 2020 Does it run stable if you disable VMs and Dockers? Why do you have 60G allocated to docker.img, have you had problems filling it? 20G should be more than enough, and making it larger won't fix anything, it will only make it take longer to fill. Quote Link to comment
Koi Posted August 28, 2020 Author Share Posted August 28, 2020 I'm not sure if it runs stable with VM's and Docker containers running; but I believe the last reboot/parity check occurred without VM's or containers running. To be clear I generally dont have any containers running and the only VM ive run lately was the Mac Vm created by macinbox. I allocated 60G as that's the most I could spare for the Mac VM; 20G is certainly not enough room, for me anyway. Not sure what you mean by problems filling it. However, I dont really care so much about getting the Mac Vm running, Ive removed it in fact. I only included the info on Mac Vm as the issue seems to have started since I recently installed it. Thanks! Quote Link to comment
trurl Posted August 28, 2020 Share Posted August 28, 2020 Not sure if you know it but you will always get a parity check after an "unclean shutdown". Is it actually rebooting, or is it just unresponsive and you are rebooting it yourself? Try disabling the docker service (Settings - Docker) and VM service (Settings - VM Manager), reboot in SAFE mode, and see if it will complete a parity check. Quote Link to comment
Koi Posted August 28, 2020 Author Share Posted August 28, 2020 I understand that is normal, included just in case. 😃 It's actually rebooting itself. Ill login and the array will be off or will be in parity check. Ive completed 2 parity checks in last cpl days without errors. I will try disabling both of those and see how it goes, thanks! Quote Link to comment
trurl Posted August 28, 2020 Share Posted August 28, 2020 Are there any symptoms while it is running? Are you sure there isn't a power issue? Quote Link to comment
Koi Posted August 28, 2020 Author Share Posted August 28, 2020 Im sure of nothing! 😃 Quote Link to comment
Koi Posted August 28, 2020 Author Share Posted August 28, 2020 Forgot to turn off Vm and Docker services before bed last night but everything is running as is, so yay. However, Im still getting the hardware warning, so boo. Thoughts? Thanks! Quote Link to comment
Squid Posted August 28, 2020 Share Posted August 28, 2020 14 minutes ago, Koi said: However, Im still getting the hardware warning, so boo. Certain combinations of motherboards / unraid versions / cpu's (or your kids finding the keys to your liquor cabinet, "borrowing" a few ounces and then refilling it with water) will issue an MCE when initializing the processor. This is what's happening with you, and is nothing to worry about and can be safely ignored. Quote Link to comment
Koi Posted August 28, 2020 Author Share Posted August 28, 2020 Lol, I knew it was the kids! Thank you kindly, I shall ignore 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.