HGTX Posted May 17, 2023 Share Posted May 17, 2023 (edited) Hi all. I wasn't sure whether to post in the Docker or VM forums, so I'm starting here. I'm having an issue where Docker and VM manager don't start automatically. They behave as follows: If they are enabled when I restart my server, one of the drives in my cache pool drops into my unassigned devices list and the array won't start. If they are disabled when I restart the server, the array starts normally. Then I can go into settings and enable Docker and VM manager manually. In this case, my VMs work normally. Most Docker applications work too, except for a few Binhex applications which won't start at all. When this problem started, I assumed I had a bad connection on one of the NVME cache drives because the problem was intermittent and hard to predict. I re-seated a loose drive, and although the problem didn't go away, the behavior is very predictable now. I've attached my diagnostics. Is there anything I'm overlooking? Any tips or directions to an existing thread would be greatly appreciated. aviario-diagnostics-20230517-1057.zip Edited May 17, 2023 by HGTX Add more details Quote Link to comment
Solution JorgeB Posted May 17, 2023 Solution Share Posted May 17, 2023 That NVMe device is being passed-through to the pfsense VM, so when it starts you lose the device, adjust the VM config. Quote Link to comment
HGTX Posted May 17, 2023 Author Share Posted May 17, 2023 2 hours ago, JorgeB said: That NVMe device is being passed-through to the pfsense VM, so when it starts you lose the device, adjust the VM config. Thanks JorgeB. That seems to have solved the problem. I no longer use that pfsense VM so I just went ahead a nuked it. There's till one Docker application that won't start up, but I'll sort that out later. 1 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.