2

I have a pyTarget iSCSI target. I'm able to use iPXE to connect to the target and install Ubuntu. After installation, I can't boot into the image, however.

pyTarget config.xml:

<root>
    <!-- configure target console -->
    <console ip="" port="3260" debug_level="6" />

    <!-- configure the first target -->
    <target name="iscsi" ip="192.168.1.10" port="3260" portal="1">
        <!-- the first iqn of this target configured for disk array -->
        <host name="iqn.2006-11.1" target_pwd="" initiator_pwd="">
            <lun id="0" type="0" path="E:\pyTarget\ubuntu16.ima" capacity="81943040" />
        </host>
    </target>
</root>

pyTarget console at start-up:

INFO:   pyTarget 1.5.7.1 2010-12-26
INFO:   start iSCSI Service ...
INFO:   start iSNS Service ...
INFO:   initialize virtual device, please wait...
INFO:   start Http Service ...
DEBUG:  create target iscsi 192.168.1.10 3260 1
DEBUG:  create host iqn.2006-11.1
DEBUG:  target iscsi add host iqn.2006-11.1
DEBUG:  Disk(E:\pyTarget\ubuntu16.ima) : initialize finish!
DEBUG:  host iqn.2006-11.1 add lun 0.
DEBUG:  configure target done
INFO:   initialize finish, start to run ...

As install begins:

DEBUG:  create connect
INFO:   initiator 192.168.1.15:38822 connect.
NEGOTIATION:    SessionType = Discovery
NEGOTIATION:    TargetName = iscsi
NEGOTIATION:    InitiatorName = iqn.2006-11.1
DEBUG:  create session 00023d000000-0001.
DEBUG:  host iqn.2006-11.1 add session 00023d000000-0001.
INFO:   SessionID: 00023d000000-0001
DEBUG:  session 00023d000000-0001 add connect 0.
INFO:   ConnectID: 0
NEGOTIATION:    TargetPortalGroupTag = 1
NEGOTIATION:    HeaderDigest = None
NEGOTIATION:    DataDigest = None
NEGOTIATION:    MaxRecvDataSegmentLength = 32768
NEGOTIATION:    TargetMaxRecvdataLength = 65536
NEGOTIATION:    ErrorRecoveryLevel = 0
NEGOTIATION:    DefaultTime2Retain = 0
NEGOTIATION:    DefaultTime2Wait = 2
NEGOTIATION:    OFMarker = No
NEGOTIATION:    IFMarker = No
DEBUG:  connect 0 login finish
COMMAND:        Text Request
DEBUG:  session 00023d000000-0001 add connect 0.
DEBUG:  host iqn.2006-11.1 remove session 00023d000000-0001.
DEBUG:  destroy session 00023d000000-0001.
DEBUG:  connect 0 finish.
DEBUG:  create connect
DEBUG:  destroy connect 0
INFO:   initiator 192.168.1.15:38824 connect.
NEGOTIATION:    SessionType = Discovery
NEGOTIATION:    TargetName = iscsi
NEGOTIATION:    InitiatorName = iqn.2006-11.1
DEBUG:  create session 00023d000000-0002.
DEBUG:  host iqn.2006-11.1 add session 00023d000000-0002.
INFO:   SessionID: 00023d000000-0002
DEBUG:  session 00023d000000-0002 add connect 0.
INFO:   ConnectID: 0
NEGOTIATION:    TargetPortalGroupTag = 1
NEGOTIATION:    HeaderDigest = None
NEGOTIATION:    DataDigest = None
NEGOTIATION:    MaxRecvDataSegmentLength = 32768
NEGOTIATION:    TargetMaxRecvdataLength = 65536
NEGOTIATION:    ErrorRecoveryLevel = 0
NEGOTIATION:    DefaultTime2Retain = 0
NEGOTIATION:    DefaultTime2Wait = 2
NEGOTIATION:    OFMarker = No
NEGOTIATION:    IFMarker = No
DEBUG:  connect 0 login finish
COMMAND:        Text Request
DEBUG:  session 00023d000000-0002 add connect 0.
DEBUG:  host iqn.2006-11.1 remove session 00023d000000-0002.
DEBUG:  destroy session 00023d000000-0002.
DEBUG:  connect 0 finish.
DEBUG:  create connect
DEBUG:  destroy connect 0
INFO:   initiator 192.168.1.15:38826 connect.
NEGOTIATION:    SessionType = Normal
NEGOTIATION:    TargetName = iscsi
NEGOTIATION:    InitiatorName = iqn.2006-11.1
DEBUG:  create session 00023d010000-0003.
DEBUG:  host iqn.2006-11.1 add session 00023d010000-0003.
INFO:   SessionID: 00023d010000-0003
DEBUG:  session 00023d010000-0003 add connect 0.
INFO:   ConnectID: 0
NEGOTIATION:    TargetPortalGroupTag = 1
NEGOTIATION:    TargetAlias = DESKTOP-54T1C9D
NEGOTIATION:    HeaderDigest = None
NEGOTIATION:    DataDigest = None
NEGOTIATION:    MaxRecvDataSegmentLength = 65536
NEGOTIATION:    TargetMaxRecvdataLength = 65536
NEGOTIATION:    ErrorRecoveryLevel = 0
NEGOTIATION:    DefaultTime2Retain = 0
NEGOTIATION:    DefaultTime2Wait = 2
NEGOTIATION:    OFMarker = No
NEGOTIATION:    IFMarker = No
NEGOTIATION:    MaxConnections = 1
NEGOTIATION:    InitialR2T = Yes
NEGOTIATION:    ImmediateData = Yes
NEGOTIATION:    DataPDUInOrder = Yes
NEGOTIATION:    DataSequenceInOrder = Yes
NEGOTIATION:    MaxOutstandingR2T = 1
NEGOTIATION:    MaxBurstLength = 262144
NEGOTIATION:    FirstBurstLength = 65536
DEBUG:  connect 0 login finish
COMMAND:        SCSI Request
COMMAND:        Inquiry LUN:0
COMMAND:        SCSI Request
COMMAND:        Inquiry LUN:0
COMMAND:        SCSI Request

As install completes & I attempt to boot into the image:

COMMAND:        SCSI Request
COMMAND:        Write(10)  LBA:0x1c40800 LEN:0x8 LUN:0
COMMAND:        SCSI Request
COMMAND:        Write(10)  LBA:0x1c40800 LEN:0x8 LUN:0
COMMAND:        SCSI Request
COMMAND:        Write(10)  LBA:0x1c40800 LEN:0x8 LUN:0
COMMAND:        SCSI Request
COMMAND:        Write(10)  LBA:0x1c40800 LEN:0x8 LUN:0
COMMAND:        SCSI Request
COMMAND:        Write(10)  LBA:0x800 LEN:0x8 LUN:0
COMMAND:        SCSI Request
COMMAND:        Test Unit Ready LUN:0
COMMAND:        SCSI Request
COMMAND:        Test Unit Ready LUN:0
# Install ends here
# Client restarts, attempts to boot to the new install:
DEBUG:  create connect
INFO:   initiator 192.168.1.15:30733 connect.
NEGOTIATION:    SessionType = Normal
WARNING:        initiator name or target name is INVAILD iqn.2006-11.1
DEBUG:  connect 0 finish.

Dropping to iPXE shell and attempting manual sanboot, it spits out additional information - this error:

(Error code 3c0d61)
This error originated from one of the following locations within the iPXE source code:
net/tcp/iscsi.c (line 1226)
This error indicates an unexpected status received from the iSCSI target.

Wireshark has the following:

Client sends an iSCSI LOGIN Command to host, notable content:

Key/Value Pairs
    KeyValue: InitiatorName=iqn.2006-11.1
    KeyValue: TargetName=iqn.2006-11.1
    KeyValue: SessionType=Normal
    KeyValue: AuthMethod=CHAP,None

Host returns iSCSI LOGIN response, notable content:

Status: Missing parameter (0x0207)

This error code is discussed briefly on this mailing list but I am not savvy enough to understand its significance.

I don't understand how the target or initiator name can suddenly be invalid? Nor what parameter is missing. The connection was literally just in use and there were no complaints during the installation... I can even replicate this - starting the installation again is not a problem, and completes just fine (again). And after the reinstall, same problem when I try to boot!

The one thing I can notice, is that there is something odd about empty passwords in either iSCSI or PXE. During ubuntu install, in order to complete the iSCSI volume login, I have to press spacebar once - it doesn't accept NULL length password, even though password is essentially NULL in config.

But, it's not possible to input SPACE as a password in iPXE - sole empty space seems to be regarded as NULL. Setting initiator_pwd to not NULL doesn't appear to help, however.

I've been stuck at this point for hours now. Where do I go from here for more troubleshooting?

EDIT: Forgot to add:

iPXE config:

#!ipxe
set iscsi-target iscsi:192.168.1.10::::iqn.2006-11.1
set gateway 0.0.0.0
set initiator-iqn iqn.2007-11.1
set keep-san 1
sanboot ${iscsi-target}
boot

New config.xml

<!-- configure the first target -->
<target name="iscsi" ip="192.168.1.10" port="3260" portal="1">
    <!-- the first iqn of this target configured for disk array -->
    <host name="iqn.2006-11.1" target_pwd="1" initiator_pwd="1"> # <-- Set passwords to avoid NULL problem, this comment was not part of the actual config
        <lun id="0" type="0" path="E:\pyTarget\ubuntu16.ima" capacity="81943040" />
    </host>
</target>

Dropped iPXE shell after the script failed:

1. dhcp
2. login
   username: iscsi
   password: 1
3. sanboot iscsi:192.168.1.10::::iqn.2006-11.1

New packet capture:

iSCSI (Login Command)
    Opcode: Login Command (0x03)
    1... .... = T: Transit to next login stage
    .0.. .... = C: Text is complete
    .... 00.. = CSG: Security negotiation (0x0)
    .... ..01 = NSG: Operational negotiation (0x1)
    VersionMax: 0x00
    VersionMin: 0x00
    TotalAHSLength: 0x00
    DataSegmentLength: 93 (0x0000005d)
    ISID: 40002723b2f3
    TSIH: 0x0000
    InitiatorTaskTag: 0x18ae0002
    CID: 0x0000
    CmdSN: 0x00000000
    ExpStatSN: 0x00000001
    Key/Value Pairs
        KeyValue: InitiatorName=iqn.2007-11.1
        KeyValue: TargetName=iqn.2006-11.1
        KeyValue: SessionType=Normal
        KeyValue: AuthMethod=CHAP,None
    Padding: 000000

iSCSI (Login Response)
    Opcode: Login Response (0x23)
    0... .... = T: Stay in current login stage
    .0.. .... = C: Text is complete
    .... 00.. = CSG: Security negotiation (0x0)
    VersionMax: 0x00
    VersionActive: 0x00
    TotalAHSLength: 0x00
    DataSegmentLength: 0 (0x00000000)
    ISID: 40002723b2f3
    TSIH: 0x0000
    InitiatorTaskTag: 0x18ae0002
    StatSN: 0x00000001
    ExpCmdSN: 0x00000000
    MaxCmdSN: 0x00000000
    Status: Missing parameter (0x0207)

sanboot iscsi:192.168.1.10::::iscsi returns Status: Authentication failed (0x0201) in wireshark and corresponding Operation not permitted 410d61 in client console.

pyTarget console:

DEBUG:  create connect
DEBUG:  destroy connect 0
INFO:   initiator 192.168.1.15:1552 connect.
NEGOTIATION:    SessionType = Normal
NEGOTIATION:    TargetName = iscsi
WARNING:        InitiatorName %s do not exist. iqn.2007-11.1
DEBUG:  connect 0 finish.
  • Did you submit LUN 0? – Zac67 Oct 7 '17 at 19:44
  • @Zac67 I am not sure I understand - what do you mean when you say "submit"? I have LUN 0 in config.xml and it appears in pytarget console as well. – Vegard Oct 7 '17 at 19:48
  • I'm not familiar with pyTarget but it seems the LUN 0 is not used in the PXE boot - can you see it in the capture? Another possibility is the intiator iqn.2007-11.1 that apparently wasn't used before. Is it assigned on the target? – Zac67 Oct 7 '17 at 20:04
  • @Zac67 I discovered my mistake. I thought backwards about which names go where - I used initiator name in place of target name, and vice versa. A mistake that cost many hours... but now I know. – Vegard Oct 7 '17 at 20:06
  • Good job! You should accept your answer to keep this question from popping up again and again. – Zac67 Oct 7 '17 at 20:08
2

The last error message flipped the lightswitch. Embarassingly, I had the names backwards:

In iPXE shell:

set initiator-iqn iqn.2006-11.1
sanboot iscsi:192.168.1.10::::iscsi

Now I have boot...

To clarify, iPXE config works when it looks like this:

#!ipxe
set iscsi-target iscsi:192.168.1.10::::iscsi
set gateway 0.0.0.0
set initiator-iqn iqn.2006-11.1
set keep-san 1
sanboot ${iscsi-target}
boot
  • If you are using pyTarget and don't need authentication, add the following to config.xml to avoid a world of CHAP-pain: <item key="AuthMethod" value="none" /> – Vegard Oct 7 '17 at 21:47
  • Where did you get the ipxe with iscsi enabled? – JdeHaan Apr 18 '18 at 17:51
  • @JdeHaan What do you mean? – Vegard Apr 18 '18 at 18:25
  • the default ipxe package of debian and ubuntu does not contain the code to run 'sanboot', in fact gives an explicit reference to the ipxe.org website which invites future supporters to fund an effort to include it. Iscsi/sanboot are extra's, like http support, built into ipxe, unlike the original syslinux version that only does tftp. You apparently used an ipxe version that does support sanboot. So, my question: where did you get it? – JdeHaan Apr 18 '18 at 18:51
  • my fault. You made me triple check my conditions. I'm using efi/uefi and on that platform it isn't implemented yet: lists.ipxe.org/pipermail/ipxe-devel/2014-November/003905.html – JdeHaan Apr 18 '18 at 19:12

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.