Thanks for the welcome, much appreciated buddy! In response, yes, that's exactly my problem... I've installed CentOS to the SAN, but it boots to PXE and asks for TFTP service instead of booting to ISCSI. Here's an article which I think shows where I'm going wrong:
The theory in a nutshell
So, what do we need for booting iSCSI on a computer that doesn't support iSCSI boot? There's a quite crazy, repeating bootstrapping process:
- The BIOS or NIC send a DHCP request to set-up the IP network settings and find a network bootable server, using the PXE-UNDI mechanisms
- gPXE image is found, and downloaded using TFTP. gPXE sends yet another DHCP request and should now find the iSCSI address of the remote boot disk
- gPXE starts as an iSCSI initiator that logs in to the iSCSI target, reads the remote boot disk's MBR and starts its boot loader (grub)
- grub loads the kernel and initrd
- initrd sends yet another DHCP request, sets up the IP network, and uses the iscsistart script, which sets up the iscsi initiator and logins (yes, again) to the iscsi target.
- iscsistart script then mounts this disk and uses pivot_root (as usual) to make it the new root
- boot process starts from the real root now, running /sbin/init
What do you think? Does this sound correct to you? It say it should boot to TFTP to find a gPXE image... But how do create or find this image? Ugh, this is why I'm the intern! Again thanks for your help!!
