[SOLVED] Boot not working with ZFS virtual volume
|
2017-03-18, 17:33
(This post was last modified: 2017-03-20 17:56 by ventura57.)
Post: #1
|
|||
|
|||
[SOLVED] Boot not working with ZFS virtual volume
I am trying to boot a ZFS virtual volume but for a reason that I don't understand it's not working. I can mount using the iscsiadm but not using iPXE.
# iscsiadm -m node -T iqn.2017-03.localdomain.localhost:zd0 -p 192.168.251.4 --login Logging in to [iface: default, target: iqn.2017-03.localdomain.localhost:zd0,portal: 192.168.251.4,3260] (multiple) Login to [iface: default, target: iqn.2017-03.localdomain.localhost:zd0,portal: 192.168.251.4,3260] successful. Below is the log result when I try to use iPXE. I am using GRUB with the following configuration: -------------------------------------------------------------------------------------------------------------------- menuentry 'Netboot iPXE-iscsi' { insmod gzio insmod part_msdos insmod btrfs set root='hd0,msdos1' linux16 /@/boot/ipxe.lkrn initrd16 /@/boot/myscript.ipxe } -------------------------------------------------------------------------------------------------------------------- The script is: -------------------------------------------------------------------------------------------------------------------- #!ipxe set syslog 192.168.251.4 dhcp net1 prompt --key 0x02 --timeout 2000 Press Ctrl-B for the iPXE command line... && shell || set initiator-iqn iqn.2005-03.org.open-iscsi:e0b5b56adf72 sanboot iscsi:192.168.251.4::3260:0:iqn.2017-03.localdomain.localhost:zd0 -------------------------------------------------------------------------------------------------------------------- The syslog result. -------------------------------------------------------------------------------------------------------------------- ipxe: Configuring (net1 00:1b:24:fe:07:0a)..... ok ipxe: Press Ctrl-B for the iPXE command line... ipxe: iSCSI 0xe99f4 initiator iqn.2005-03.org.open-iscsi:e0b5b56adf72 ipxe: iSCSI 0xe99f4 target 192.168.251.4 iqn.2017-03.localdomain.localhost:zd0 ipxe: iSCSI 0xe99f4 entering security negotiation ipxe: SCSI 0xe9b44 created for LUN 0000-0000-0000-0000 ipxe: iSCSI 0xe99f4 ignoring TargetPortalGroupTag=1 ipxe: iSCSI 0xe99f4 handling AuthMethod=None ipxe: iSCSI 0xe99f4 entering operational negotiation ipxe: iSCSI 0xe99f4 ignoring HeaderDigest=None ipxe: iSCSI 0xe99f4 ignoring DataDigest=None ipxe: iSCSI 0xe99f4 ignoring MaxConnections=1 ipxe: iSCSI 0xe99f4 ignoring InitialR2T=Yes ipxe: iSCSI 0xe99f4 ignoring ImmediateData=No ipxe: iSCSI 0xe99f4 ignoring MaxBurstLength=262144 ipxe: iSCSI 0xe99f4 ignoring DefaultTime2Wait=2 ipxe: iSCSI 0xe99f4 ignoring DefaultTime2Retain=0 ipxe: iSCSI 0xe99f4 ignoring MaxOutstandingR2T=1 ipxe: iSCSI 0xe99f4 ignoring DataPDUInOrder=Yes ipxe: iSCSI 0xe99f4 ignoring DataSequenceInOrder=Yes ipxe: iSCSI 0xe99f4 ignoring ErrorRecoveryLevel=0 ipxe: iSCSI 0xe99f4 entering full feature phase ipxe: SCSI 0xe9b44 waiting for unit to become ready ipxe: SCSI 0xe9b44 tag 18ae0002 status 02 sense 70 key 00 additional 2900 ipxe: SCSI 0xe9b44 tag 18ae0002 closed: Input/output error (http://ipxe.org/1d704039) ipxe: SCSI 0xe9b44 not ready: Input/output error (http://ipxe.org/1d704039) ipxe: iSCSI 0xe99f4 closed: Input/output error (http://ipxe.org/1d704039) ipxe: SCSI 0xe9b44 tag 18ae0002 closed: Input/output error (http://ipxe.org/1d704039) ipxe: assert(((&scsicmd->list))->next->prev == ((&scsicmd->list))) failed at drivers/block/scsi.c line 399 ipxe: assert(((&scsicmd->list))->prev->next == ((&scsicmd->list))) failed at drivers/block/scsi.c line 399 ipxe: Could not open SAN device: Error 0x3f122003 (http://ipxe.org/3f122003) ipxe: Execution of "<INITRD>" failed: Error 0x3f122003 (http://ipxe.org/3f122003) -------------------------------------------------------------------------------------------------------------------- Any help or suggestion is welcome, Ventura |
|||
2017-03-20, 17:54
(This post was last modified: 2017-03-20 17:55 by ventura57.)
Post: #2
|
|||
|
|||
RE: [SOLVED] Boot not working with ZFS virtual volume
I was using TGT iSCSI Target framework that I didn't find in the iSCSI iPXE target list then I decided to replace for LIO on Linux and that fix the problem.
Another thing I learned is that using tcpdump/Wireshark can help a lot. Tcpdump decode iSCSI protocol in a way that is really helpful. Ventura |
|||
« Next Oldest | Next Newest »
|
User(s) browsing this thread: 1 Guest(s)