- Software-Network Stack.png (166.14 KiB) Viewed 73 times
The Latest Gartner® Magic Quadrant™Hyperconverged Infrastructure Software
The Latest Gartner® Magic Quadrant™Hyperconverged Infrastructure Software
Search found 3 matches
- Wed Oct 07, 2026 9:06 pm
- Forum: StarWind NVMe-oF Initiator [+Free], Deduplication Analyzer, RDMA Performance Benchmark
- Topic: Second VAST volume missing after domain-joined reboot
- Replies: 3
- Views: 124
Re: Second VAST volume missing after domain-joined reboot
This is the topology - single cx6 - dedicated network to VAST
- Wed Oct 07, 2026 9:04 pm
- Forum: StarWind NVMe-oF Initiator [+Free], Deduplication Analyzer, RDMA Performance Benchmark
- Topic: Second VAST volume missing after domain-joined reboot
- Replies: 3
- Views: 124
Re: Second VAST volume missing after domain-joined reboot
When joined to WORKGROUP - i.e. no domain join everything works perfectly.
Join Domain, reboot - path goes phantom - every time
Leave Domain, reboot, path comes back - every time
Could it be a race condition introduced by the domain join on reboot?
Join Domain, reboot - path goes phantom - every time
Leave Domain, reboot, path comes back - every time
Could it be a race condition introduced by the domain join on reboot?
- Wed Oct 07, 2026 7:28 pm
- Forum: StarWind NVMe-oF Initiator [+Free], Deduplication Analyzer, RDMA Performance Benchmark
- Topic: Second VAST volume missing after domain-joined reboot
- Replies: 3
- Views: 124
Second VAST volume missing after domain-joined reboot
Validated with these versions as of 2026-10-06 (this lab only): Windows Server 2019 Datacenter Evaluation 1809 StarWind NVMe-oF Initiator: Controller / miniport 2.0.0.729 VAST: 5.5.1. - Lab cluster (block NVMe/TCP; two mapped volumes per host) Mellanox CX-6 Driver=2.42.22627.0 Summary On domain-join...