iSCSI service will not start after config of targets / extents

[Jared M.]

Hello!

So I am setting up iSCSI and am having the hardest time getting it to work. The iSCSI service will not turn on if I have an target / extent under associated targets tab configured. So I can turn the service on with everything but that configured but as soon as I configure that part it no longer responds and will not turn on. The error message I receive on the console is:
"istgt[2420]: istgt_lu_disk.c: 642 :istgt_lu_disk_init: ***ERROR*** LU1: LUN0: open error(errno=17)
istgt[2420: istgt_lu.c:2091:istgt_lu_init_unit: ***ERROR*** LU1: lu_disk_init() failed
istgt[2420: istgt_lu.c:2345:istgt_lu_reload_update: ***ERROR*** LU1: lu_init_unit() failed"

The guide I was following to set this up is located here:

http://www.erdmanor.com/blog/connec...i-5-5-hypervisor-performing-vm-guest-backups/

Looks like someone else had the same issue way earlier in releases, bug tracker here:
https://bugs.freenas.org/issues/255

Please help! :( I am getting really frustrated.

 

[dlavigne]

Which version of FreeNAS?

 

[Loren]

I believe I am experiencing the same problem. I have a SuperMicro server with 4 SATA 2TB drives. No RAID controller. Originally FreeNAS 9.1.1 x64. Upgraded to 9.2.1.2 x64. Problem occurred with both versions.

Since I have no RAID, I am creating 4 Extents (/dev/ada0 through /dev/ada3)

But I can only start the iSCSI service with extent1 (/dev/ada0). If try to configure any other extents (or even if I remove all associated targets and just try to work with something other than /dev/ada0), i get the similar error.

Mar 20 16:12:28 myserver notifier: istgt not running? (check /var/run/istgt.pid).
Mar 20 16:12:28 myserver notifier: istgt not running? (check /var/run/istgt.pid).
Mar 20 16:12:28 myserver notifier: Starting istgt.
Mar 20 16:12:28 myserver notifier: istgt version 0.5 (20121028)
Mar 20 16:12:28 myserver istgt[15607]: istgt version 0.5 (20121028)
Mar 20 16:12:28 myserver istgt[15607]: normal mode
Mar 20 16:12:28 myserver notifier: normal mode
Mar 20 16:12:28 myserver istgt[15607]: using kqueue
Mar 20 16:12:28 myserver notifier: using kqueue
Mar 20 16:12:28 myserver istgt[15607]: using host atomic
Mar 20 16:12:28 myserver notifier: using host atomic
Mar 20 16:12:28 myserver istgt[15607]: istgt_lu_disk.c: 642:istgt_lu_disk_init: ***ERROR*** LU1: LUN0: open error(errno=17)
Mar 20 16:12:28 myserver notifier: istgt_lu_disk.c: 642:istgt_lu_disk_init: ***ERROR*** LU1: LUN0: open error(errno=17)
Mar 20 16:12:28 myserver istgt[15607]: istgt_lu.c:2091:istgt_lu_init_unit: ***ERROR*** LU1: lu_disk_init() failed
Mar 20 16:12:28 myserver notifier: istgt_lu.c:2091:istgt_lu_init_unit: ***ERROR*** LU1: lu_disk_init() failed
Mar 20 16:12:28 myserver istgt[15607]: istgt_lu.c:2166:istgt_lu_init: ***ERROR*** LU1: lu_init_unit() failed
Mar 20 16:12:28 myserver notifier: istgt_lu.c:2166:istgt_lu_init: ***ERROR*** LU1: lu_init_unit() failed
Mar 20 16:12:28 myserver istgt[15607]: istgt.c:2799:main: ***ERROR*** istgt_lu_init() failed
Mar 20 16:12:28 myserver notifier: istgt.c:2799:main: ***ERROR*** istgt_lu_init() failed
Mar 20 16:12:28 myserver notifier: LU1 HDD UNIT
Mar 20 16:12:28 myserver notifier: LU1: LUN0 file=/dev/ada1, size=2000398934016
Mar 20 16:12:28 myserver notifier: LU1: LUN0 3907029168 blocks, 512 bytes/block
Mar 20 16:12:28 myserver root: /usr/local/etc/rc.d/istgt: WARNING: failed to start istgt
Mar 20 16:12:28 myserver notifier: /usr/local/etc/rc.d/istgt: WARNING: failed to start istgt

 

[dlavigne]

Please create a bug report at bugs.freenas.org and post the issue number here.

 

[Loren]

Possible solution found.
I booted my server using a WinPE rescue disk. I opened up Disk Management and found that the the first drive (which was the one that was working with iSCSI in FreeNAS (/dev/ada0) was un-initialized and had no partitions. The other 3 disks each had two partitions, one 2GB and one with the remainder of the 2TB drive. So I deleted all the partitions on the drives and restarted the system back into FreeNAS.

Now I am able to create Associated Targets and start the iSCSI service without any error.