Running 7.3.1 and it appears that while stopping and then starting the array manually, the array does not come up. Seems fine on a complete reboot.

I see this in the log. Thoughts on what might be going on here?

emhttpd: cmdStart: already starting

clarabell-diagnostics-20260603-1136.zip

Maybe this go be the culprit?

I also see a stale reference to vm directory, not sure how to remove this reference, is it in the img file?

2026-06-03 15:26:54.398+0000: 14020: info : libvirt version: 12.2.0

2026-06-03 15:26:54.398+0000: 14020: info : hostname: clarabell

2026-06-03 15:26:54.398+0000: 14020: error : virDirOpenInternal:3163 : cannot open directory '/mnt/user/kvm/domains/windows7': No such file or directory

2026-06-03 15:26:54.398+0000: 14020: error : storageDriverAutostartCallback:213 : internal error: Failed to autostart storage pool 'windows7': cannot open directory '/mnt/user/kvm/domains/windows7': No such file or directory

2026-06-03 15:26:56.705+0000: 14020: warning : qemuDomainObjTaintMsg:5727 : Domain id=1 name='windows10' uuid=589b80db-794f-9069-8df3-49347dab4887 is tainted: high-privileges

Edited June 3Jun 3 by joelones

Try booting in safe mode.

20 hours ago, JorgeB said:

Try booting in safe mode.

I will try but what would booting in safe mode confirm?

Does it have something to do with this error?

No internal boot setup detected. Launch Internal Boot to configure one.

Would this prevent the array from starting once I stop the array ? If so why is this happening? And why would the array come up fine on reboot?

Edited June 4Jun 4 by joelones

You've set the array to autostart and it's supposedly doing that, so why would you try to also start it manually? What's the actual problem if any?

Edited June 4Jun 4 by Kilrah

1 minute ago, Kilrah said:

You've set the array to autostart and it's supposedly doing that, so why would you try to also start it manually? What's the actual problem if any?

Sorry by what is your question?

I'd like to stop the array manually to test something and then bring it up manually. The problem is that it doesn't come up. That's the problem.

There's no indication in the log why the array could not come up. It's terrible from a user experience perspective that there's no warning or visible error.

I'm spinning in circles with this now.

Edited June 4Jun 4 by joelones

it appeared to be the usb_manager plugin causing the array not starting, closing.