Here is the problem I’m facing, maybe is better to explain this to see if recompiling a kernel with iSCSI support will fix the problem.
I’m trying to use my jetsnano in a Kubernetes cluster using k3s. As part of a kubernetes cluster (Kubernetes is a tool to handle many machines from a central place to deploy apps) I want to use Longhorn to manage storage.
Longhorn requires iSCSI on each machine with storage to share it in the cluster, my Jetsnano has a 500gb SSD.
I need to install open-iscsi and nfs-common.
open-iscsi works as a service, and when I check if the service is running in my Jestnano I see the following:
$ systemctl status iscsid.service
iscsid.service - iSCSI initiator daemon (iscsid)
Loaded: loaded (/lib/systemd/system/iscsid.service; enabled; vendor preset: enabled)
Active: activating (start) since Sun 2022-01-09 21:11:26 GMT; 6s ago
Docs: man:iscsid(8)
Process: 426 ExecStart=/sbin/iscsid (code=exited, status=0/SUCCESS)
Process: 407 ExecStartPre=/lib/open-iscsi/startup-checks.sh (code=exited, status=0/SUCCESS)
Tasks: 0 (limit: 4181)
CGroup: /system.slice/iscsid.service
Jan 09 21:11:26 quino systemd[1]: Starting iSCSI initiator daemon (iscsid)...
Jan 09 21:11:26 quino iscsid[426]: iSCSI logger with pid=431 started!
Jan 09 21:11:26 quino systemd[1]: iscsid.service: Failed to parse PID from file /run/iscsid.pid: Invalid argument
$ journalctl -e -f -u iscsid
-- Logs begin at Sun 2022-01-09 02:44:58 GMT. --
Jan 09 18:16:57 quino systemd[1]: iscsid.service: Failed to parse PID from file /run/iscsid.pid: Invalid argument
Jan 09 18:16:57 quino iscsid[21406]: iSCSI daemon with pid=21412 started!
Jan 09 18:16:57 quino iscsid[21406]: can not create NETLINK_ISCSI socket
Jan 09 18:18:27 quino systemd[1]: iscsid.service: Start operation timed out. Terminating.
Jan 09 18:18:27 quino systemd[1]: iscsid.service: Failed with result 'timeout'.
Jan 09 18:18:27 quino systemd[1]: Failed to start iSCSI initiator daemon (iscsid).
From this post open-iscsi installation failed on TX1/TX2 Jetpack3.0/3.1 -- ubuntu 16.04 - #8 by asnail I can see the last comment saying “issue resolved with kernel missed iscsi initiator configuration.”
Does that mean I need to recompile the kernel with iscsi support?
Checking your answer on that post, is a configuration issue, no need it to recompile the kernel