@olivierlambert I do.
I have also noticed something extremely weird.
I have 3 HDDs attached to one host.
2x2TB raid 1 (software raid done on the XCP-ng host)
1x4TB
lsblk
shows:
... SNIP ...
sda 8:0 0 1.8T 0 disk
├─sda2 8:2 0 1.8T 0 part
└─sda1 8:1 0 2G 0 part
...
sdb 8:16 0 1.8T 0 disk
├─sdb2 8:18 0 1.8T 0 part
└─sdb1 8:17 0 2G 0 part
└─md127 9:127 0 2G 0 raid1
...
sde 8:64 0 3.7T 0 disk
├─sde2 8:66 0 3.7T 0 part
└─sde1 8:65 0 2G 0 part
└─md127 9:127 0 2G 0 raid1
All 3 disks are passed through to a TrueNAS VM on the host, and all the data is properly stored, but I have no idea why mdadm shows that the 4TB disk is part of the raid, instead of the other one?
/dev/md127:
Version : 1.2
Creation Time : Sun Aug 27 14:32:08 2023
Raid Level : raid1
Array Size : 2094080 (2045.00 MiB 2144.34 MB)
Used Dev Size : 2094080 (2045.00 MiB 2144.34 MB)
Raid Devices : 2
Total Devices : 2
Persistence : Superblock is persistent
Update Time : Sun Oct 8 12:07:28 2023
State : clean
Active Devices : 2
Working Devices : 2
Failed Devices : 0
Spare Devices : 0
Consistency Policy : resync
Name : november:swap0
UUID : ae045fa0:74b00896:3134ede5:c837bec3
Events : 27
Number Major Minor RaidDevice State
0 8 65 0 active sync /dev/sde1
1 8 17 1 active sync /dev/sdb1
Anyways, this doesn't seem to be the issue, since the other host which has no HDDs attached, only m.2 VM SR's, and it also took exactly 10 minutes for the toolstack to go up.
Now XO can't reach any of the hosts, even though all the VMs are up.