Aschenbach/Freeman updated me with this info offlist. He said I could forward the info to the list for future users hitting the problem:
<from Aschenbach/Freeman> Thanks for replying, You were right about this problem i have with a Dell AX4-5SCi iscsi storage unit. The problem was the storage devices needs to grant access to the machine that it needs to communicate with. I had to go to the web IP interface of the Storage Device to give access to the rhel linux machine. After i've done that, it was working for me. <end> On 12/15/2011 08:46 AM, [email protected] wrote: > The device you are trying to access is a LUNZ. > > Dec 13 09:54:08 arc2 kernel: Vendor: DGC Model: > **LUNZ** Rev: 0223 > Dec 13 09:54:08 arc2 kernel: Type: Direct- > Access ANSI SCSI revision: 04 > Dec 13 09:54:08 arc2 kernel: Vendor: DGC Model: > **LUNZ** Rev: 0223 > > This is a device that is used for in band communications with the array. You > need to add LUNs to the storage group assigned to your host then rescan the > SCSI bus to pick up the new LUN. After point you will have a device that you > can write to. > > Regards, > Wayne. > > -----Original Message----- > From: [email protected] [mailto:[email protected]] On > Behalf Of Mike Christie > Sent: Tuesday, December 13, 2011 5:03 PM > To: [email protected] > Cc: aschenbach > Subject: Re: Unable to read new detected iscsi device /dev/sdb > > On 12/13/2011 10:39 AM, aschenbach wrote: >> [root@arc2 ifaces]# uname -a >> Linux arc2.irss.unc.edu 2.6.18-238.12.1.el5 #1 SMP Sat May 7 20:18:50 >> EDT 2011 x86_64 x86_64 x86_64 GNU/Linux > >> Dec 13 09:54:08 arc2 kernel: Broadcom NetXtreme II iSCSI Driver bnx2i >> v2.1.3 (Aug 10, 2010) >> Dec 13 09:54:08 arc2 kernel: iscsi: registered transport (bnx2i) >> Dec 13 09:54:08 arc2 kernel: scsi89 : Broadcom Offload iSCSI Initiator >> Dec 13 09:54:08 arc2 kernel: bnx2i [16:00.00]: ISCSI_INIT passed >> Dec 13 09:54:08 arc2 kernel: scsi90 : Broadcom Offload iSCSI Initiator >> Dec 13 09:54:08 arc2 kernel: bnx2i [13:00.00]: ISCSI_INIT passed >> Dec 13 09:54:08 arc2 kernel: scsi91 : Broadcom Offload iSCSI Initiator >> Dec 13 09:54:08 arc2 kernel: scsi92 : Broadcom Offload iSCSI Initiator >> Dec 13 09:54:08 arc2 kernel: scsi93 : Broadcom Offload iSCSI Initiator >> Dec 13 09:54:08 arc2 kernel: scsi94 : Broadcom Offload iSCSI Initiator >> Dec 13 09:54:08 arc2 kernel: iscsi: registered transport (tcp) >> Dec 13 09:54:08 arc2 kernel: iscsi: registered transport (iser) >> Dec 13 09:54:08 arc2 kernel: iscsi: registered transport (be2iscsi) >> Dec 13 09:54:08 arc2 iscsid: iSCSI logger with pid=26230 started! >> Dec 13 09:54:08 arc2 kernel: scsi95 : iSCSI Initiator over TCP/IP >> Dec 13 09:54:08 arc2 kernel: scsi96 : iSCSI Initiator over TCP/IP >> Dec 13 09:54:08 arc2 kernel: Vendor: DGC Model: >> LUNZ Rev: 0223 >> Dec 13 09:54:08 arc2 kernel: Type: Direct- >> Access ANSI SCSI revision: 04 >> Dec 13 09:54:08 arc2 kernel: Vendor: DGC Model: >> LUNZ Rev: 0223 >> Dec 13 09:54:08 arc2 kernel: Type: Direct- >> Access ANSI SCSI revision: 04 >> Dec 13 09:54:08 arc2 kernel: sdb : READ CAPACITY failed. >> Dec 13 09:54:08 arc2 kernel: sdb : status=1, message=00, host=0, >> driver=08 >> Dec 13 09:54:08 arc2 kernel: sd: Current: sense key: Illegal Request >> Dec 13 09:54:08 arc2 kernel: Add. Sense: Logical unit not >> supported >> Dec 13 09:54:08 arc2 kernel: >> Dec 13 09:54:08 arc2 kernel: sdc : READ CAPACITY failed. >> Dec 13 09:54:08 arc2 kernel: sdc : status=1, message=00, host=0, >> driver=08 >> Dec 13 09:54:08 arc2 kernel: sd: Current: sense key: Illegal Request >> Dec 13 09:54:08 arc2 kernel: Add. Sense: Logical unit not >> supported >> Dec 13 09:54:08 arc2 kernel: >> Dec 13 09:54:08 arc2 kernel: sdb: test WP failed, assume Write Enabled >> Dec 13 09:54:08 arc2 kernel: sdb: asking for cache data failed >> Dec 13 09:54:08 arc2 kernel: sdb: assuming drive cache: write through >> Dec 13 09:54:08 arc2 kernel: sd 95:0:0:0: Attached scsi disk sdb >> Dec 13 09:54:08 arc2 kernel: sd 95:0:0:0: Attached scsi generic sg1 >> type 0 >> Dec 13 09:54:08 arc2 kernel: sdc: test WP failed, assume Write Enabled >> Dec 13 09:54:08 arc2 kernel: sdc: asking for cache data failed >> Dec 13 09:54:08 arc2 kernel: sdc: assuming drive cache: write through >> Dec 13 09:54:08 arc2 kernel: sd 96:0:0:0: Attached scsi disk sdc >> Dec 13 09:54:08 arc2 kernel: sd 96:0:0:0: Attached scsi generic sg2 >> type 0 >> Dec 13 09:54:09 arc2 iscsid: transport class version 2.0-871. iscsid >> version 2.0-872 >> Dec 13 09:54:09 arc2 iscsid: iSCSI daemon with pid=26231 started! >> Dec 13 09:54:09 arc2 iscsid: Connection1:0 to [target: iqn. >> 1992-04.com.emc:cx.apm00100800387.a1, portal: 152.2.32.187,3260] >> through [iface: bnx2i.00:10:18:41:53:f6] is operational now >> Dec 13 09:54:09 arc2 iscsid: Connection2:0 to [target: iqn. >> 1992-04.com.emc:cx.apm00100800387.a0, portal: 152.2.32.186,3260] >> through [iface: bnx2i.00:10:18:41:53:f6] is operational now >> >> [root@arc2 ifaces]# /sbin/fdisk /dev/sdb >> >> Unable to read /dev/sdb >> >> >> i don't understand why i can't seem to format this iscsi storage >> device ? please advise >> > > It looks like the target is not set up correctly or you trying to access > the wrong device. Is sdb's module listed as LUNZ? > > cat /sys/block/sdb/device/model > > If so then that is not a LUN that has storage backing it. It is some > sort of magic administration type of device. > > You might not have the target setup so the initiator can access the > storage correctly. Is there some sort of access list on the target? > > Does it work with software iscsi? > -- You received this message because you are subscribed to the Google Groups "open-iscsi" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/open-iscsi?hl=en.
