sanboot iscsi fails. Any idea why?

[mcb30]

(2014-06-17 18:22)ingestre Wrote:  The hardware being booted is identical - In fact it's the same machine! I booted it into Clonezilla to image its local drive to the iscsi target.

OK; that should work.

Quote:I'm using a Mikrotik routerboard (brilliant router!) as the router between initiator and target so I guess I could use the packet sniffing capabilites in that to ascertain iSCSI activity on port 3260?. How do I interpret any packets captured?

Mainly you just want to see if there is any activity, which would indicate that the initiator is still alive and doing something.

What is the last thing that you see on the screen?

If you add a Windows boot menu (i.e. a second entry in C:\boot.ini), does the menu show up? That would indicate that NTLDR is able to start up and access the disk, at least.

Michael