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-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 


Messages In This Thread
RE: [Iscsi, sanboot] Could not open San device: error 0x3f122003 (IET and ipxe issue) - nvcd7026 - 2017-03-19 18:25



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