PDA

View Full Version : Adding an iSCSI drive to install fails


mr2147
2007-06-17, 04:03 AM CDT
Hi,

has anyone successfully installed Release 7 on an iSCSI drive?
I already filed a bug report (No: 243300) but that has not yet received any comments.

Short explanation:
Description of problem:

Version-Release number of selected component (if applicable):
Fedora Release 7

How reproducible:
Always reproducible

Steps to Reproduce:
1. Click on "Advanced storage configuration"
2. Add iSCSI target
3. Enter 192.168.0.131 as IP Address and
iqn.2007-03.net-layer-7.blackbird:storage.seagull as target

Actual results:
The iSCSI drive does not show up.

Expected results:
The drive shows up and can be selected to partition and install.

Additional info:

Here is the output on the different virtual consoles:

ALT-F3:

INFO iSCSI initiator name iqn.2007-03.net.layer-7.blackbird:storage.seagull
INFO ISCSID is /usr/sbin/iscsid
WARNING no record found!
WARNING isfsiadm failed to login to 192.168.0.131
INFO iSCSI shutdown

ALT-F4:

iscsid: iSCSI logger with pid=691 started!
iscsid: transport class version 2.0-724. iscsid version 2.0-754
iscsid: an InitiatorAlias= is required, but was not found in
+/etc/iscsi/initiatorname.iscsi
iscsid: iSCSI sync pid=693 started
iscsid: iSCSI daemin with pid=692 started!
scsi2: iSCSI Initiator over TCP/IP
iscsi: couldn't create a new connection for session 0
iscsid: iSCSI logger with pid=723 started!
iscsid: received iferror -12
iscsid: can't create connection (115)
iscsid: transport class version 2.0-724. iscsid version 2.0-754
iscsid: can not bind IPC socket

ALT-F5:

192.168.0.131:3260,1 iqn.2007-03.net.layer-7.blackbird:storage.seagull
iscsiadm: initiator reported error (9 - internal error)

-----------------------------------------------------------------------------------------

Starting an initiator on another machine leads to the following messages
in the syslog:

Loading iSCSI transport class v2.0-724.
iscsi: registered transport (tcp)
iscsi: registered transport (iser)
scsi9 : iSCSI Initiator over TCP/IP
scsi 9:0:0:0: Direct-Access IET VIRTUAL-DISK 0 PQ: 0 ANSI: 4
SCSI device sdg: 4194304 512-byte hdwr sectors (2147 MB)
sdg: Write Protect is off
sdg: Mode Sense: 77 00 00 08
SCSI device sdg: write cache: disabled, read cache: enabled, doesn't support DPO
+or FUA
SCSI device sdg: 4194304 512-byte hdwr sectors (2147 MB)
sdg: Write Protect is off
sdg: Mode Sense: 77 00 00 08
SCSI device sdg: write cache: disabled, read cache: enabled, doesn't support DPO
+or FUA
sdg: sdg1
sd 9:0:0:0: Attached scsi disk sdg
sd 9:0:0:0: Attached scsi generic sg6 type 0
scsi 9:0:0:1: Direct-Access IET VIRTUAL-DISK 0 PQ: 0 ANSI: 4
SCSI device sdh: 409600 512-byte hdwr sectors (210 MB)
sdh: Write Protect is off
sdh: Mode Sense: 77 00 00 08
SCSI device sdh: write cache: disabled, read cache: enabled, doesn't support DPO
+or FUA
SCSI device sdh: 409600 512-byte hdwr sectors (210 MB)
sdh: Write Protect is off
sdh: Mode Sense: 77 00 00 08
SCSI device sdh: write cache: disabled, read cache: enabled, doesn't support DPO
+or FUA
sdh: sdh1
sd 9:0:0:1: Attached scsi disk sdh
sd 9:0:0:1: Attached scsi generic sg7 type 0

It correctly reports both LUNs. Even if I comment out the second LUN it
doesent change anything. Does anyone have an idea?!

Thanks,
Michael.