targetcli fails on Pi Raspbian Jessie, as target.service cannot start. The problem lies with target_core_mod which cannot be loaded. Moreover, CONFIG_TARGET_CORE is not set, according to the kernel .config. Shoud I conclude that the Raspbian distro kernel has not properly configured the target_core_mod so that targetcli can work? Any help appreciated, Al. On install: targetcli (3.0+git0.7e32595e-2) ... Job for target.service failed. See 'systemctl status target.service' and 'journalctl -xn' for details. invoke-rc.d: initscript target, action "start" failed. systemctl status target.service: * target.service - LSB: Start service at boot time Loaded: loaded (/etc/init.d/target) Active: failed (Result: exit-code) since sat. 2016-03-26 10:02:55 CET; 6h ago Process: 732 ExecStart=/etc/init.d/target start (code=exited, status=1/FAILURE) systemctl start target.service: The Linux SCSI Target looks properly installed. The configfs filesystem is already mounted. Failed to load core module target_core_mod ... failed! Could not start The Linux SCSI Target ... failed! target.service: control process exited, code=exited status=1 raspberrypi systemd[1]: Failed to start LSB: The Linux SCSI Target service. with (failing) lio-utils, journalctl showed: Loading target_core_mod/ConfigFS core: [FAILED]: 1 Moreover kernel .config shows: # SCSI Transports # CONFIG_TARGET_CORE is not set system: Linux raspberrypi 4.1.13+ #826 PREEMPT Fri Nov 13 20:13:22 GMT 2015 armv6l GNU/Linux -- To unsubscribe from this list: send the line "unsubscribe target-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
