I am trying to set up Armbian as an iSCSI initiator using open-iscsi. The result is
Mar 15 03:07:13 matrix iscsid[2207]: iSCSI logger with pid=2208 started!
Mar 15 03:07:13 matrix systemd[1]: iscsid.service: Failed to parse PID from file /run/iscsid.pid: Invalid argument
Mar 15 03:07:13 matrix iscsid[2208]: iSCSI daemon with pid=2209 started!
Mar 15 03:07:13 matrix iscsid[2208]: can not create NETLINK_ISCSI socket
Mar 15 03:08:43 matrix systemd[1]: iscsid.service: Start operation timed out. Terminating.
Mar 15 03:08:43 matrix systemd[1]: iscsid.service: Failed with result 'timeout'.
with a timeout of around 90 seconds. I'm running the kernel
Linux matrix 4.14.171-s5p6818 #24 SMP Mon Feb 17 06:09:30 CET 2020 aarch64 GNU/Linux
in the Buster image. It would appear from /boot/config-4.14.171-s5p6818 that
# CONFIG_SCSI_ISCSI_ATTRS is not set
# CONFIG_SCSI_SAS_ATTRS is not set
# CONFIG_SCSI_SAS_LIBSAS is not set
# CONFIG_SCSI_SRP_ATTRS is not set
CONFIG_SCSI_LOWLEVEL=y
# CONFIG_ISCSI_TCP is not set
# CONFIG_ISCSI_BOOT_SYSFS is not set
That ISCSI_TCP is not set for ISCSI_ATTRS. On a Raspberry Pi (also based on Buster) with the default Raspbian kernel the modules
automatically load and all is well. However, I can't get Armbian to work. I think I might need to recompile the kernel, but am not very excited to do so. A web search also indicated that incorrectly configured selinux could cause the same problem, but I don't think selinux is running. Does anyone know what's wrong and how to fix it?
Question
ejolson
I am trying to set up Armbian as an iSCSI initiator using open-iscsi. The result is
with a timeout of around 90 seconds. I'm running the kernel
in the Buster image. It would appear from /boot/config-4.14.171-s5p6818 that
That ISCSI_TCP is not set for ISCSI_ATTRS. On a Raspberry Pi (also based on Buster) with the default Raspbian kernel the modules
automatically load and all is well. However, I can't get Armbian to work. I think I might need to recompile the kernel, but am not very excited to do so. A web search also indicated that incorrectly configured selinux could cause the same problem, but I don't think selinux is running. Does anyone know what's wrong and how to fix it?
Link to comment
Share on other sites
4 answers to this question
Recommended Posts