← Back to team overview

kernel-packages team mailing list archive

[Bug 1034015] Re: iSCSI target returns "Device type is not supported by server", discovery fails.


Pending results of

** Tags added: regression-potential

** Changed in: linux (Ubuntu)
       Status: Triaged => Incomplete

You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.

  iSCSI target returns "Device type is not supported by server",
  discovery fails.

Status in “linux” package in Ubuntu:
Status in “open-iscsi” package in Ubuntu:

Bug description:
  Connecting from an Ubuntu 12.04LTS server to a
  SANRAD (http://www.sanrad.com) switch offering iSCSI connectivity, fails.
  First, look for targets

  root@media2:~# iscsiadm -m discovery -t st -p,65535 bigmedia1,65535 bigmedia1,65535 bigmedia1,65535 media1target,65535 media1target,65535 media1target,65535 bigmedia2,65535 bigmedia2,65535 bigmedia2

  Lots of nice targets - now connect to one

  root@media2:~# iscsiadm -m node -T bigmedia1 -p -l
  Logging in to [iface: default, target: bigmedia1, portal:,3260]
  Login to [iface: default, target: bigmedia1, portal:,3260]: successful
  root@media2:~# echo $?

  Apparently connected - it says successful, and returns zero. Now,
  check partitions

  root@media2:~# cat /proc/partitions
  major minor  #blocks  name

    11        0    1048575 sr0
     8        0  731445248 sda
     8        1    1048576 sda1
     8        2  730395648 sda2
   252        0   20971520 dm-0
   252        1    8388608 dm-1

  Nothing new - sda is my root drive, the new one should be in there as
  sdb. Checking dmesg, it has two new lines

  [  358.391438] scsi6 : iSCSI Initiator over TCP/IP
  [  358.645490] scsi scan: INQUIRY result too short (5), using 36

  Please see http://karlsbakk.net/tmp/iscsi-debug.txt for a login
  attempt with -d 200 and http://karlsbakk.net/tmp/iscsi-fail.pcap for a
  traffic dump between the two machines during login attempt.

  Please note that with open-iscsi on a CentOS 5.8 machine of the same
  make, this works perfectly.


To manage notifications about this bug go to: