iSCSI service keeps stopping / will not start up

[Marty Lavender]

I apologize ahead of time if I ask more questions than the normal person. I want to make sure I understand exactly what responses I may get to my issue.

I have installed FreeNAS 8.0.2 running under VirtualBox 4.1.6.
I have configured 1 volume which holds 4 iSCSI targets configured
I have gone through all the steps to set these up

I realized the iSCSI service was not running
I went to the Services section and clicked on the switch to start the service
After about 5 seconds, I get a message stating the service failed to start

Is there a log that I can look at to see what may be causing the issue?\

Any guidance is very much appreciated.

 

[Marty Lavender]

This is what I saw this morning in the logs:

Nov 15 04:58:05 freenas kernel: GEOM: stripe/iSCSIstripe: the secondary GPT table is corrupt or invalid.
Nov 15 04:58:05 freenas kernel: GEOM: stripe/iSCSIstripe: using the primary only -- recovery suggested.
Nov 15 04:58:05 freenas kernel: GEOM: ufsid/4ec13cfcf449c443: the secondary GPT table is corrupt or invalid.
Nov 15 04:58:05 freenas kernel: GEOM: ufsid/4ec13cfcf449c443: using the primary only -- recovery suggested.
Nov 15 04:58:05 freenas kernel: GEOM: ufs/iSCSI: the secondary GPT table is corrupt or invalid.
Nov 15 04:58:05 freenas kernel: GEOM: ufs/iSCSI: using the primary only -- recovery suggested.
Nov 15 04:58:05 freenas kernel: Trying to mount root from ufs:/dev/ufs/FreeNASs1a
Nov 15 04:58:05 freenas kernel: GEOM: da0: the secondary GPT table is corrupt or invalid.
Nov 15 04:58:05 freenas kernel: GEOM: da0: using the primary only -- recovery suggested.
Nov 15 04:58:05 freenas kernel: GEOM: stripe/iSCSIstripe: the secondary GPT table is corrupt or invalid.
Nov 15 04:58:05 freenas kernel: GEOM: stripe/iSCSIstripe: using the primary only -- recovery suggested.
Nov 15 04:58:05 freenas kernel: GEOM: ufs/iSCSI: the secondary GPT table is corrupt or invalid.
Nov 15 04:58:05 freenas kernel: GEOM: ufs/iSCSI: using the primary only -- recovery suggested.
Nov 15 04:58:06 freenas root: /etc/rc: WARNING: failed precmd routine for vmware_guestd
Nov 15 04:58:11 freenas ntpd[1447]: ntpd 4.2.4p5-a (1)
Nov 15 04:58:13 freenas avahi-daemon[1676]: WARNING: No NSS support for mDNS detected, consider installing nss-mdns!
Nov 15 04:58:19 freenas ntpd[1448]: time reset +0.162642 s
Nov 15 04:58:20 freenas mountd[2040]: can't delete exports for /: Device busy
Nov 15 05:13:19 freenas ntpd[1448]: kernel time sync status change 2001
Nov 15 20:17:31 freenas freenas[1694]: Executing: /usr/sbin/service ix-istgt quietstart
Nov 15 20:17:32 freenas freenas[1694]: Executing: /usr/sbin/service istgt forcestop
Nov 15 20:17:32 freenas freenas: istgt not running? (check /var/run/istgt.pid).
Nov 15 20:17:32 freenas freenas[1694]: Executing: /usr/sbin/service istgt restart
Nov 15 20:17:32 freenas freenas: istgt not running? (check /var/run/istgt.pid).
Nov 15 20:17:32 freenas freenas: Starting istgt.
Nov 15 20:17:32 freenas freenas: istgt version 0.4 (20110928)
Nov 15 20:17:32 freenas istgt[61709]: istgt version 0.4 (20110928)
Nov 15 20:17:32 freenas freenas: normal mode
Nov 15 20:17:32 freenas istgt[61709]: normal mode
Nov 15 20:17:32 freenas freenas: istgt_lu.c:1329:istgt_lu_add_unit: ***ERROR*** LU1: InitiatorGroup2 not found
Nov 15 20:17:32 freenas istgt[61709]: istgt_lu.c:1329:istgt_lu_add_unit: ***ERROR*** LU1: InitiatorGroup2 not found
Nov 15 20:17:32 freenas freenas: istgt_lu.c:1954:istgt_lu_init: ***ERROR*** lu_add_unit() failed
Nov 15 20:17:32 freenas istgt[61709]: istgt_lu.c:1954:istgt_lu_init: ***ERROR*** lu_add_unit() failed
Nov 15 20:17:32 freenas freenas: istgt.c:1667:main: ***ERROR*** istgt_lu_init() failed
Nov 15 20:17:32 freenas istgt[61709]: istgt.c:1667:main: ***ERROR*** istgt_lu_init() failed
Nov 15 20:17:32 freenas root: /usr/local/etc/rc.d/istgt: WARNING: failed to start istgt
Nov 15 20:17:32 freenas freenas: /usr/local/etc/rc.d/istgt: WARNING: failed to start istgt
Nov 15 20:17:33 freenas freenas[1694]: Executing: /bin/pgrep -F /var/run/istgt.pid istgt

 

[jgreco]

It looks like something's wrong with the filesystem you have. I'd suggest you go use a shell to see if it's okay, and if so, COPY IT if you want to be able to save it, just to be safe. Once you do that, you can reinitialize or recover the filesystem without also worrying about your data's integrity.

 

[Marty Lavender]

I have no data at all on the volumes as of yet. This is all happening after a fresh install. I was simply trying to get the volumes setup so I could configure the iSCSI targets for a lab I was working on.

 

[srit]

I had a similar issue

I have a similar issue. I found that I need to have the initiator group set to ALL ALL otherwise the service wont start. additionally make sure your LUN/Volume names have no spaces.