Search found 4 matches

by bigjme
Thu Jan 15, 2026 10:49 am
Forum: StarWind NVMe-oF Initiator [+Free], Deduplication Analyzer, RDMA Performance Benchmark
Topic: Unable to discover targets using TCP using nvme-of initiator
Replies: 55
Views: 232540

Re: Unable to discover targets using TCP using nvme-of initiator

yaroslav (staff) wrote:
Thu Jan 15, 2026 10:44 am
Confirmed to be a driver problem. The new driver should work.
Are we expecting to get a new driver any time soon as i know one was being worked on earlier in this topic anyway?
by bigjme
Sun Jan 11, 2026 1:19 pm
Forum: StarWind NVMe-oF Initiator [+Free], Deduplication Analyzer, RDMA Performance Benchmark
Topic: Unable to discover targets using TCP using nvme-of initiator
Replies: 55
Views: 232540

Re: Unable to discover targets using TCP using nvme-of initiator

Under the windows Iscsi Initiator with the old version installed: Discovery -> Discovery Portal -> Advanced -> Local adaptor: Starwind -> Initiator ip: Which ever is right -> Set the ip for the Truenas server -> Port set to usually 4420 to match Truenas You should see entries like this show up after...
by bigjme
Sun Jan 11, 2026 12:23 pm
Forum: StarWind NVMe-oF Initiator [+Free], Deduplication Analyzer, RDMA Performance Benchmark
Topic: Unable to discover targets using TCP using nvme-of initiator
Replies: 55
Views: 232540

Re: Unable to discover targets using TCP using nvme-of initiator

Ok let me just post a bit of information here and just point out a few things to prevent people going around in circles and arguing over the same things Truenas Only TCP is available or discoverable on consumer hardware regardless of what you have in the server or initiator unless you have an enterp...
by bigjme
Mon Dec 01, 2025 12:02 pm
Forum: StarWind NVMe-oF Initiator [+Free], Deduplication Analyzer, RDMA Performance Benchmark
Topic: Unable to discover targets using TCP using nvme-of initiator
Replies: 55
Views: 232540

Re: Unable to discover targets using TCP using nvme-of initiator

I had to completely blow away the share on truenas and i updated the nqn to not have the uuid (which truenas wanted to put by default). After i recreated the share the discovery address which was previously "tcp:nqn.2014-08.org.nvmexpress.discovery" connected directly to the correct one i...