Broken system after installing USB qube

[sigma]

It is HVM, everythings the same as sys-usb.

[apparatus]

Check the journalctl in dom0, maybe there are some related messages when you start sys-ssd.

@sigma

Checked the logs with nano like this:
nano var/log/xen/console/guest-sys-ssd.log

Did you check exactly like this in dom0 terminal without leading slash / in the path?

[sigma]

Yeah, I forgot to put a slash before var
guest-sys-ssd.log (1.1 MB)
guest-sys-ssd-dm.log (605.1 KB)

[apparatus]

Can you try to remove all attached PCI devices in sys-ssd and start it without them? Will it start?

[sigma]

Yes, it starts with no problems without PCI devices.

[apparatus]

That’s strange.
For some reason the qubes-iptables systemd service is hanging:

[2023-12-20 07:21:06] [.[0m.[0;31m*     .[0m] (1 of 2) Job qubes-iptables.service/start running (4s / no limit)
[2023-12-20 07:21:06] .M
.[K[.[0;1;31m*.[0m.[0;31m*    .[0m] (1 of 2) Job qubes-iptables.service/start running (5s / no limit)
[2023-12-20 07:21:07] .M
.[K[.[0;31m*.[0;1;31m*.[0m.[0;31m*   .[0m] (1 of 2) Job qubes-iptables.service/start running (5s / no limit)
[2023-12-20 07:21:08] .M
.[K[ .[0;31m*.[0;1;31m*.[0m.[0;31m*  .[0m] (2 of 2) Job unbound-anchor.service/start running (4s / no limit)

I’m not sure what’s wring with it.
Maybe it’s hanging on qubesdb-read for some reason and there is a problem with qubes-db service.

[sigma]

Ok, it’s not really necessary for me to access internal SSDs from within Qubes. It’s enough to isolate them from dom0 in my case.

[sigma]

Thank you guys for helping me get started with Qubes OS. It’s an awesome OS and it’s well worth it to learn how to use it.

[apparatus]

The same issue was reported here as well:

Sys-usb field start after attach pci sdd

sys-usb field start after attach pci sdd qvm-start sys-usb Cannot connect to qrexec agent for 60 seconds, see /var/log/xen/console/guest-sys-usb.log for details also I tried with no-strict-reset same error

[apparatus]

I’ve create sys-ssd based on fedora-39-xfce template and attached my second NVMe drive to it for a test and I can boot it just fine and it sees the NVMe disk.
Maybe try to attach your SSDs one at a time to check if it’s a problem with one specific disk.

[sigma]

Your suggestion actually worked!

But only for 1 SSD which is removable. The other one is non-removable SSD and it still doesn’t work. Doesn’t matter in what sequence you try.

I’m totally fine with this, as I’m not going to be using it anyway, but it’s nice that at least 1 of them is working and maybe I’ll need it future.

I appreciate your help brother! Thank you very much.

[secblocks]

@apparatus

problem with one specific disk

yes I have with one specific disk