Post Reply 
 
Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
[Iscsi, sanboot] Could not open San device: error 0x3f122003 (IET and ipxe issue)
2017-03-13, 22:56 (This post was last modified: 2017-03-19 19:55 by nvcd7026.)
Post: #1
[Iscsi, sanboot] Could not open San device: error 0x3f122003 (IET and ipxe issue)
Hi all,

I switched to the latest ipxe build (fdcdc) (git://git.ipxe.org/ipxe.git), but somehow I'm not able to sanboot with iscsi anymore. It gives an error, showing "Could not open San device: error 0x3f122003". Both UEFI and BIOS mode encounter the same error.

However if I switch back to the old build 30f9, the San device is correctly registered, no error occurs with booting.

(server: Ubuntu 16.04 with iscsitarget (iSCSI Enterprise Target))

Here is the menu entry:

:Win10-installer
dhcp net0
set net0/gateway 0.0.0.0
set keep-san 1
sanhook --drive 0x81 iscsi:${fog-ip}::::workgroup:install-test
set path /fog/win10-installer-1607
kernel http://${fog-ip}/fog/boot/winpe/wimboot
initrd http://${fog-ip}${path}/bootmgr BOOTMGR
#initrd http://${fog-ip}${path}/bootmgr.exe bootmgr.exe
initrd http://${fog-ip}${path}/bootmgr.efi bootmgr.efi
initrd http://${fog-ip}${path}/boot/bcd bcd
initrd http://${fog-ip}${path}/boot/boot.sdi boot.sdi
initrd http://${fog-ip}${path}/sources/boot.wim boot.wim
imgstat || echo "ERROR at IMGSTAT"; sleep 3
prompt || echo "ERROR at PROMPT"; sleep 3
boot || echo "ERROR AT BOOT"; sleep 3;goto MENU


The attachments are screenshots with debug mode on (iscsi), taken from hyper-v (UEFI mode). I appreciate any helps!

https://imgur.com/a/JT83O

------
Edit:

I tested with the package targetcli today, and the san device registered normally; so I think the problem might be about IET(iSCSI Enterprise Target) and ipxe.

3/20:

Here is the screenshot with scsi debug option enabled:

https://imgur.com/6YdOEyS

...
iSCSI 0xf6e503e8 ignoring ErrorRecoueryLeuel-0
iSCSI 0xf6e503e8 entering full feature phase
SCSI 0xf6e52448 waiting for unit to become ready
SCSI 0xf6e52448 tag 18ae0002 status 02 sense 70 key 00 additional 2900
SCSI 0xf6e52448 tag 18ae0002 closed: Input/output error (http://ipxe.org/1d704098)
SCSI 0xf6e52448 not ready: Input/output error (http://ipxe.org/1d704098)
iSCSI 0xf6e503e8 closed: Input/output error (http://ipxe.org/1d704098)
SCSI 0xf6e52448 tag 18ae0002 closed: Input/output error (http://ipxe.org/1d704098)
assert((($scsicmd->list))->next->prev == (($scsicmd->list))) failed at drivers/block/scsi.c line 399
assert((($scsicmd->list))->prev->next == (($scsicmd->list))) failed at drivers/block/scsi.c line 399
Could not open SAN device: Error 0x3f122083 (http://ipxe.org/3f122083)
Could not boot: Error 0x3f122083 (http://ipxe.org/3f122083)
Could not boot: Error 0x3f122083 (http://ipxe.org/3f122083)
Find all posts by this user
Quote this message in a reply
2017-03-18, 17:37
Post: #2
RE: [Iscsi, sanboot] Could not open San device: error 0x3f122003 (IET and ipxe issue)
(2017-03-13 22:56)nvcd7026 Wrote:  Hi all,

I switched to the latest ipxe build (fdcdc) (git://git.ipxe.org/ipxe.git), but somehow I'm not able to sanboot with iscsi anymore. It gives an error, showing "Could not open San device: error 0x3f122003". Both UEFI and BIOS mode encounter the same error.

However if I switch back to the old build 30f9, the San device is correctly registered, no error occurs with booting.

(server: Ubuntu 16.04 with iscsitarget (iSCSI Enterprise Target))

Here is the menu entry:

:Win10-installer
dhcp net0
set net0/gateway 0.0.0.0
set keep-san 1
sanhook --drive 0x81 iscsi:${fog-ip}::::workgroup:install-test
set path /fog/win10-installer-1607
kernel http://${fog-ip}/fog/boot/winpe/wimboot
initrd http://${fog-ip}${path}/bootmgr BOOTMGR
#initrd http://${fog-ip}${path}/bootmgr.exe bootmgr.exe
initrd http://${fog-ip}${path}/bootmgr.efi bootmgr.efi
initrd http://${fog-ip}${path}/boot/bcd bcd
initrd http://${fog-ip}${path}/boot/boot.sdi boot.sdi
initrd http://${fog-ip}${path}/sources/boot.wim boot.wim
imgstat || echo "ERROR at IMGSTAT"; sleep 3
prompt || echo "ERROR at PROMPT"; sleep 3
boot || echo "ERROR AT BOOT"; sleep 3;goto MENU


The attachments are screenshots with debug mode on (iscsi), taken from hyper-v (UEFI mode). I appreciate any helps!

https://imgur.com/a/JT83O

------
Edit:

I tested with the package targetcli today, and the san device registered normally; so I think the problem might be about IET(iSCSI Enterprise Target) and ipxe.

I am having a similar problem using BIOS. I suggest you to include also 'scsi' (not only iscsi) in your debug option, there is more error to be reported.

Ventura
Find all posts by this user
Quote this message in a reply
2017-03-19, 18:25
Post: #3
RE: [Iscsi, sanboot] Could not open San device: error 0x3f122003 (IET and ipxe issue)
Thanks; so I reinstalled IET to reproduce the issue, here is the screenshot with scsi debug option:

https://imgur.com/6YdOEyS

...
iSCSI 0xf6e503e8 ignoring ErrorRecoueryLeuel-0
iSCSI 0xf6e503e8 entering full feature phase
SCSI 0xf6e52448 waiting for unit to become ready
SCSI 0xf6e52448 tag 18ae0002 status 02 sense 70 key 00 additional 2900
SCSI 0xf6e52448 tag 18ae0002 closed: Input/output error (http://ipxe.org/1d704098)
SCSI 0xf6e52448 not ready: Input/output error (http://ipxe.org/1d704098)
iSCSI 0xf6e503e8 closed: Input/output error (http://ipxe.org/1d704098)
SCSI 0xf6e52448 tag 18ae0002 closed: Input/output error (http://ipxe.org/1d704098)
assert((($scsicmd->list))->next->prev == (($scsicmd->list))) failed at drivers/block/scsi.c line 399
assert((($scsicmd->list))->prev->next == (($scsicmd->list))) failed at drivers/block/scsi.c line 399
Could not open SAN device: Error 0x3f122083 (http://ipxe.org/3f122083)
Could not boot: Error 0x3f122083 (http://ipxe.org/3f122083)
Could not boot: Error 0x3f122083 (http://ipxe.org/3f122083)

@Ventura
Are you also using IET for the iscsi target? I switched to Targetcli and it worked fine with ipxe, no san device registering problems occur.
Find all posts by this user
Quote this message in a reply
Post Reply 




User(s) browsing this thread: 1 Guest(s)