SOLVED iSCSI service fails to start

ocalvo

Cadet
Joined
May 26, 2021
Messages
5
I am trying to configure a new target, after running the wizard if I stop the service, it wont start again.

How can I run the service in interactive mode?

Here is the output of var/log/meesages:
May 27 19:52:33 truenas kernel: DLM installed
May 27 19:52:34 truenas kernel: [3751557]: scst: User interface thread started
May 27 19:52:34 truenas kernel: [3751407]: scst: Attached to scsi0, channel 0, id 0, lun 0, type 0
May 27 19:52:34 truenas kernel: [3751407]: scst: Attached to scsi1, channel 0, id 0, lun 0, type 0
May 27 19:52:34 truenas kernel: [3751407]: scst: Attached to scsi6, channel 0, id 0, lun 0, type 0
May 27 19:52:34 truenas kernel: [3751566]: scst: Init thread started
May 27 19:52:34 truenas kernel: [3751567]: scst: Task management thread started
May 27 19:52:34 truenas kernel: [3751568]: scst: Management thread started
May 27 19:52:34 truenas kernel: [3751407]: scst: Target template copy_manager registered successfully
May 27 19:52:34 truenas kernel: [3751407]: scst: Target copy_manager_tgt for template copy_manager registered successfully
May 27 19:52:34 truenas kernel: [3751407]: scst: Using security group "copy_manager_tgt" for initiator "copy_manager_sess" (target copy_manager_tgt)
May 27 19:52:34 truenas kernel: [3751407]: scst: SCST version 3.6.0-pre loaded successfully (global max mem for commands ignored, per device 1591MB)
May 27 19:52:34 truenas kernel: [3751407]: scst: Enabled features: TRACING
May 27 19:52:34 truenas kernel: [3751407]: iscsi-scst: iSCSI SCST Target - version 3.6.0-pre
May 27 19:52:34 truenas kernel: [3751407]: iscsi-scst: Registered iSCSI transport: iSCSI-TCP
May 27 19:52:34 truenas kernel: [3751407]: scst: Target template iscsi registered successfully
May 27 19:52:34 truenas kernel: [3751569]: iscsi-scst: Read thread for pool 0000000043714918 started
May 27 19:52:34 truenas kernel: [3751570]: iscsi-scst: Read thread for pool 0000000043714918 started
May 27 19:52:34 truenas kernel: [3751571]: iscsi-scst: Read thread for pool 0000000043714918 started
May 27 19:52:34 truenas kernel: [3751572]: iscsi-scst: Read thread for pool 0000000043714918 started
May 27 19:52:34 truenas kernel: [3751573]: iscsi-scst: Read thread for pool 0000000043714918 started
May 27 19:52:34 truenas kernel: [3751574]: iscsi-scst: Read thread for pool 0000000043714918 started
May 27 19:52:34 truenas kernel: [3751575]: iscsi-scst: Read thread for pool 0000000043714918 started
May 27 19:52:34 truenas kernel: [3751576]: iscsi-scst: Read thread for pool 0000000043714918 started
May 27 19:52:34 truenas kernel: [3751577]: iscsi-scst: Write thread for pool 0000000043714918 started
May 27 19:52:34 truenas kernel: [3751578]: iscsi-scst: Write thread for pool 0000000043714918 started
May 27 19:52:34 truenas kernel: [3751579]: iscsi-scst: Write thread for pool 0000000043714918 started
May 27 19:52:34 truenas kernel: [3751580]: iscsi-scst: Write thread for pool 0000000043714918 started
May 27 19:52:34 truenas kernel: [3751581]: iscsi-scst: Write thread for pool 0000000043714918 started
May 27 19:52:34 truenas kernel: [3751582]: iscsi-scst: Write thread for pool 0000000043714918 started
May 27 19:52:34 truenas kernel: [3751583]: iscsi-scst: Write thread for pool 0000000043714918 started
May 27 19:52:34 truenas kernel: [3751584]: iscsi-scst: Write thread for pool 0000000043714918 started
May 27 19:52:34 truenas kernel: [3751407]: iscsi-scst: Registered iSCSI transport: iSER
May 27 19:52:34 truenas kernel: [3751599]: scst: Virtual device handler vdisk_fileio for type 0 registered successfully
May 27 19:52:34 truenas kernel: [3751599]: scst: Virtual device handler vdisk_blockio for type 0 registered successfully
May 27 19:52:34 truenas kernel: [3751599]: scst: Virtual device handler vdisk_nullio for type 0 registered successfully
May 27 19:52:34 truenas kernel: [3751599]: scst: Virtual device handler vcdrom for type 5 registered successfully
May 27 19:52:34 truenas kernel: [3751605]: iscsi-scst: Created iser portal cm_id:000000006541b596
May 27 19:52:34 truenas kernel: [3751605]: iscsi-scst: iser portal cm_id:000000006541b596 listens on: 0.0.0.0:3260
May 27 19:52:34 truenas kernel: [3751605]: iscsi-scst: Created iser portal cm_id:000000003524dfc8
May 27 19:52:34 truenas kernel: [3751605]: iscsi-scst: iser portal cm_id:000000003524dfc8 listens on: 0000:0000:0000:0000:0000:0000:0000:0000 3260
May 27 19:52:34 truenas kernel: [3751557]: scst: Removed all devices from group copy_manager_tgt
May 27 19:52:34 truenas kernel: [3751557]: dev_vdisk: Registering virtual vdisk_blockio device server.systemdisk (BLOCKIO, ROTATIONAL)
May 27 19:52:34 truenas kernel: [3751605]: iscsi-scst: Releasing allocated resources
May 27 19:52:34 truenas kernel: [3751605]: iscsi-scst: iser portal cm_id:000000006541b596 releasing
May 27 19:52:34 truenas kernel: [3751605]: iscsi-scst: done releasing portal 000000004abb57c3
May 27 19:52:34 truenas kernel: [3751605]: iscsi-scst: iser portal cm_id:000000003524dfc8 releasing
May 27 19:52:34 truenas kernel: [3751605]: iscsi-scst: done releasing portal 0000000076074c63
May 27 19:52:34 truenas kernel: [3751649]: iscsi-scst: Unregistered iSCSI transport: iSER
May 27 19:52:34 truenas kernel: [3751569]: iscsi-scst: Read thread for pool 0000000043714918 finished
May 27 19:52:34 truenas kernel: [3751570]: iscsi-scst: Read thread for pool 0000000043714918 finished
May 27 19:52:34 truenas kernel: [3751571]: iscsi-scst: Read thread for pool 0000000043714918 finished
May 27 19:52:34 truenas kernel: [3751572]: iscsi-scst: Read thread for pool 0000000043714918 finished
May 27 19:52:34 truenas kernel: [3751573]: iscsi-scst: Read thread for pool 0000000043714918 finished
May 27 19:52:34 truenas kernel: [3751574]: iscsi-scst: Read thread for pool 0000000043714918 finished
May 27 19:52:34 truenas kernel: [3751575]: iscsi-scst: Read thread for pool 0000000043714918 finished
May 27 19:52:34 truenas kernel: [3751576]: iscsi-scst: Read thread for pool 0000000043714918 finished
May 27 19:52:34 truenas kernel: [3751577]: iscsi-scst: Write thread for pool 0000000043714918 finished
May 27 19:52:34 truenas kernel: [3751578]: iscsi-scst: Write thread for pool 0000000043714918 finished
May 27 19:52:34 truenas kernel: [3751579]: iscsi-scst: Write thread for pool 0000000043714918 finished
May 27 19:52:34 truenas kernel: [3751580]: iscsi-scst: Write thread for pool 0000000043714918 finished
May 27 19:52:34 truenas kernel: [3751581]: iscsi-scst: Write thread for pool 0000000043714918 finished
May 27 19:52:34 truenas kernel: [3751582]: iscsi-scst: Write thread for pool 0000000043714918 finished
May 27 19:52:34 truenas kernel: [3751583]: iscsi-scst: Write thread for pool 0000000043714918 finished
May 27 19:52:34 truenas kernel: [3751584]: iscsi-scst: Write thread for pool 0000000043714918 finished
May 27 19:52:34 truenas kernel: [3751649]: scst: Target template iscsi unregistered successfully
May 27 19:52:34 truenas kernel: [3751649]: iscsi-scst: Unregistered iSCSI transport: iSCSI-TCP
May 27 19:52:34 truenas kernel: [3751650]: scst: Device handler "vdisk_nullio" unloaded
May 27 19:52:34 truenas kernel: [3751650]: scst: Device handler "vdisk_blockio" unloaded
May 27 19:52:34 truenas kernel: [3751650]: scst: Device handler "vdisk_fileio" unloaded
May 27 19:52:34 truenas kernel: [3751650]: scst: Device handler "vcdrom" unloaded
May 27 19:52:34 truenas kernel: [3751650]: scst: Waiting for 1 active commands to complete...
May 27 19:52:34 truenas kernel: [3751650]: scst: All active commands completed
May 27 19:52:34 truenas kernel: [3751650]: scst: Target copy_manager_tgt for template copy_manager unregistered successfully
May 27 19:52:34 truenas kernel: [3751650]: scst: Target template copy_manager unregistered successfully
May 27 19:52:34 truenas kernel: [3751567]: scst: Task management thread finished
May 27 19:52:34 truenas kernel: [3751568]: scst: Management thread finished
May 27 19:52:34 truenas kernel: [3751566]: scst: Init thread finished
May 27 19:52:34 truenas kernel: [3751650]: scst: Detached from scsi0, channel 0, id 0, lun 0, type 0
May 27 19:52:34 truenas kernel: [3751650]: scst: Detached from scsi1, channel 0, id 0, lun 0, type 0
May 27 19:52:35 truenas kernel: [3751650]: scst: Detached from scsi6, channel 0, id 0, lun 0, type 0
May 27 19:52:35 truenas kernel: [3751650]: scst: Exiting SCST sysfs hierarchy...
May 27 19:52:38 truenas kernel: [3751557]: scst: User interface thread finished
May 27 19:52:38 truenas kernel: [3751650]: scst: Exiting SCST sysfs hierarchy done
May 27 19:52:38 truenas kernel: [3751650]: scst: SCST unloaded
 

morganL

Captain Morgan
Administrator
Moderator
iXsystems
Joined
Mar 10, 2018
Messages
2,694
which software version?

So the service was running after wizard,,, but after stopping it, it doesn't restart? Being very clear about what worked and what did not helps everyone
 

ocalvo

Cadet
Joined
May 26, 2021
Messages
5
which software version?

So the service was running after wizard,,, but after stopping it, it doesn't restart? Being very clear about what worked and what did not helps everyone
This is correct. I figured out what the problem was. I will post details here in a bit.
 

ocalvo

Cadet
Joined
May 26, 2021
Messages
5
Using 'TrueNAS-SCALE-21.04-ALPHA.1'

When running the wizrd it allow me to use dots "." in the name of the target, this generated a `/etc/scst.conf` that looks like:
```
HANDLER vdisk_blockio {
DEVICE iscsi.server.systemdisk {
filename /dev/zvol/SystemPool/VMs/Server/SystemDisk
blocksize 4096
read_only 0
usn d0f97c38380317a
naa_id 0x6589cfc000000558c5530253583ade57
prod_id "iSCSI Disk"
t10_vend_id TrueNAS
t10_dev_id d0f97c38380317a
}

}

TARGET_DRIVER iscsi {
enabled 1

TARGET iqn.2005-10.org.freenas.ctl:iscsi-server-systemdisk {
enabled 1
per_portal_acl 1

GROUP security_group {
INITIATOR *\#*

LUN 0 iscsi.server.systemdisk
}
}
}
```

Changing `iscsi.server.systemdisk` to `iscsi-server-systemdisk` resolved the issue.
Otherwise dmesg shows an error saying the a device has an invalid name with "dot"
 

morganL

Captain Morgan
Administrator
Moderator
iXsystems
Joined
Mar 10, 2018
Messages
2,694
Glad you solved..... there are so many ways that there can be misconfiguration... which is why we ask that these problem statements include all the detail.
 

ornias

Wizard
Joined
Mar 6, 2020
Messages
1,458
in addition to what @morganL said, this is definately something that needs a Jira ticket because the UI should allow things like these that break.
 

Arwen

MVP
Joined
May 17, 2014
Messages
3,611
Here, let me fix that for you :smile:
in addition to what @morganL said, this is definately something that needs a Jira ticket because the UI should NOT allow things like these that break.
 
Top