https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=276522
--- Comment #7 from [email protected] --- (In reply to Alan Somers from comment #4) If you look at #276524, you will see an extensive discussion on this. It seems likely that ESXi has misinterpreted the disks, perhaps because of mismatched info in outdated iSCSI pages. I don't know how this would have affected the Windows initiator, but it seems it has affected it somehow. If ESXi has never touched the target, Windows seems to have no issues with it. If ESXi has touched the target, Windows also fails. Perhaps the incorrect info ESXi derives is stored in MBR/GPT and used by Windows. In either case, it seems there is not much else to do here apart from what was already done in #276524. -- You are receiving this mail because: You are the assignee for the bug.
