[gPXE] iSCSI Booting

[Andrew Bobulsky]

No sooner did I send that email that I realize you appear to have mounted
your image file to a loopback device :-P

It might be worth trying to cut the middleman and point your iscsi target
directly at the image file.  Otherwise, all I can suggest here is that you
break out the trusty debug modes.

Sorry about that!

-Andrew Bobulsky

On Mon, Dec 20, 2010 at 11:24 AM, Andrew Bobulsky <rulerof at gmail.com> wrote:

> Hello Chad,
>
> We've all had one issue or another with a grumpy iSCSI target, so I can
> sympathize ;)
>
> I don't know a whole ton about diagnosing a misbehaving MBR, so this is
> only a guess:
>
> In you iSCSI target config, you've set the IO mode to blockio.  However, it
> appears that your target points to an image file...  Whenever I've used IET
> (I think that's what you're using here, could be wrong) and pointed a target
> at an image file, I've configured it for "fileio" instead of "blockio."  You
> may want to try that instead.
>
> It's really a shot in the dark, but it might be worth a shot!
>
> Best of luck to you!
>
> Cheers,
> Andrew Bobulsky
>
>
> On Sun, Dec 19, 2010 at 9:22 PM, Chad Voelker <chad.voelker at gmail.com>wrote:
>
>> Hello,
>>
>> I'm trying to boot a Ubuntu Lucid PC (2.6.32-26 - GRUB2) using a chained
>> gPXE boot, it halts at "Booting from BIOS drive 0x80". I've tried
>> various machines, so I'm assuming it is a problem with the iSCSI image's
>> boot sectors or some other boot-related setup on the image. I can mount
>> the iSCSI drive without a problem. I followed the directions here:
>> http://www.etherboot.org/wiki/sanboot/ubuntu_iscsi2
>>
>> I was hoping to see some logging showing the iSCSI connection, but I've
>> searched through /var/log on the iscsitarget and don't see any relevant
>> iSCSI activity. I also looked to see if there was any evidence of a
>> partial boot by looking at the log files on the iSCSI image (after
>> mounting on another machine), but nothing has been touched for days.
>>
>> Various data is below. Any thoughts? Thanks in advance.
>>
>> -Chad
>>
>> I created a .kpxe formatted rom using rom-o-matic.net following all of
>> the defaults except using the undionly NIC.
>>
>> DHCP Server::dhcpd.conf:
>> host y {
>>         hardware ethernet 00:1b:21:12:41:ff;
>>         fixed-address 192.168.1.90;
>>         option host-name "y";
>>         if exists user-class and option user-class = "gPXE" {
>>                 option root-path
>> "iscsi:192.168.1.170::::iqn.2010-10.net.xxxx:mc-y.lun1";
>>         } else {
>>                 option root-path "192.168.1.170:/nfsroot/mythfrontends";
>>                 filename "mythfrontends/gpxe-1.0.1-undionly-trim.kpxe";
>>         }
>> }
>>
>> iSCSI Target::/etc/ietd.conf:
>> Target iqn.2010-10.net.xxxx:mc-y.lun1
>>         Lun 0 Path=/dev/loop0,IOMode=wb,Type=blockio
>>         Alias LUN0
>>
>> iSCSI Target::$ losetup -a
>> /dev/loop0: [0811]:8388611 (/clients/iscsi/mc-y-lun1.img)
>>
>> iSCSI Image::$ cat /etc/default/grub
>> GRUB_CMDLINE_LINUX_DEFAULT="ip=dhcp ISCSI_INITIATOR=y
>> ISCSI_TARGET_NAME=iqn.2010-10.net.voelkers:y.lun1
>> ISCSI_TARGET_IP=192.168.1.170 ISCSI_TARGET_PORT=3260 quiet splash"
>> _______________________________________________
>> gPXE mailing list
>> gPXE at etherboot.org
>> http://etherboot.org/mailman/listinfo/gpxe
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://etherboot.org/pipermail/gpxe/attachments/20101220/8ce5d50b/attachment.html