iPXE discussion forum

Hi all,

I'm in need of some help Dodgy

Over the last few days I've been trying to get iPXE connect to my Synology iSCSI target with little success. I want to do this so I can boot from SAN ESX in my lab.

So far I've configured the following...

Added DHCP options for undionly.kpxe to boot from tftp.
Embedded a script in undionly.pkxe to load a script from http.
The script contains the following

#!ipxe
sanboot -k iscsi:172.16.10.229::::iqn.test.com || chain http://172.16.10.230/pxelinux.0

Created pxelinux.cfg/default to point at a menu for the ESXi installation via http if sanboot fails.

When I attempt to boot a diskless host(VM in workstation at the moment) I see iPXE load and then the ESX installation starts. Which is all good but I dont get presented with an iSCSI lun to install into... Sad

I've looked at the iSCSI logs on the target I see Login, which is then followed by Close about 15 seconds later...

So at this point I'm not sure if the issue is with iPXE or the target. So I built a freenas iscsi target and I was seeing the same issue.

I've tried to make it was simple as possible by booting onto the ipxe.iso and running the following

dhcp
sanhook iscsi:172.16.10.230::::iqn.test.com

which responds with

Registered SAN device 0x80

but I still see the disconnect on the iSCSI Synology server about 5 - 15 seconds after.

I even tried a Freenas iscsi target and in the logs it gives me this
freenas WARNING: 172.16.10.127 (iqn.initiator.com): no ping reply (NOP-Out) after 5 seconds; dropping connection

Anyone got any ideas? Should what I'm trying to do work?

Thanks

James

The same happens here. I use RS815+. The wierd thing is I could boot WinPE but after installation I can't boot Win7.

For me the two things solved the problem:
- turn on the multiple I/O
- on the server give read and write rights for the booting client to the iSCSI target

Quote: Your code

Code:

#!ipxe sanboot -k iscsi:172.16.10.229::::iqn.test.com || chain http://172.16.10.230/pxelinux.0

Couple of (Possible) problems here I can see - my example doesn't use pxelinux.0:

Code:

#!ipxe

:defaultboot

sanboot --drive 0x80 iscsi:172.16.10.229::::iqn.test.com ||

:forinstallation

sanhook --drive 0x80 iscsi:172.16.10.229::::iqn.test.com ||

sanboot --drive 0x81 --no-describe http://172.16.10.230/$esxi5orlater.iso ||

ukjamesh

birotokmag

birotokmag

MultimediaMan