This error usually indicates that you are successfully connecting to your SAN target, but the SAN disk you are trying to access does not exist.

Things you can try:

  * Connect to the SAN target from another initiator (e.g. a Linux or Windows box), and check that you can access the SAN disk from there.

  * Check the ACL settings on your SAN target to ensure that the iPXE initiator will be granted access to the SAN disk.  Many SAN targets will allow you to restrict the visibility of individual SAN disks on the basis of the initiator's identity (e.g. the iSCSI initiator IQN).  If you are using an iSCSI target, see also [[:err:2c0d603b|error 0x2c0d603b]] for iSCSI-specific information relating to ACLs.

  * Check the LUN mappings on your SAN target, and make sure that iPXE is attempting to connect to the correct LUN.  If no LUN is explicitly specified, iPXE will connect to LUN 0, which may not be correct for your setup.  For example, if your iSCSI root path is <code>iscsi:iscsi.example.com::::iqn.1992-01.com.example.iscsi:target</code> then iPXE will connect to LUN 0, since no LUN is explicitly specified.  To instruct iPXE to connect to LUN 1, you would need to use an iSCSI root path such as <code>iscsi:iscsi.example.com:::1:iqn.1992-01.com.example.iscsi:target
                          ^
                           \_ LUN goes here</code>

   * Check to see that there is an associated disk or disk image file on the iSCSI Target. A Missing or invalid disk or disk image file will result in this error.

   * For Linux iSCSI Targets you can check the /etc/tgt/targets.conf file.

   * For Microsoft iSCSI Target you can check the target with the Get-IscsiServerTarget Powershell command.