In Part 1, we saw how to connect raspberry pi to synology nas using iSCSI. The previous post had a few hiccups.

Server startup was really slow.
Restart of open-iscsi service was slow.
Multiple errors in Synology NAS regarding Max Connections

In this post, we are going to streamline the configuration.

1. Stop initiators to attempt multiple sessions.

Prestep: Check for active sessions and logout of these sessions Find active sessions:

sudo iscsiadm -m session -o show

Logout of all the sessions

sudo iscsiadm --mode node --logoutall=all

Refer to the previous post for using the go code to delete hanging sessions if you encounter that situation.

Remove the discoveryDB

sudo iscsiadm -m discoverydb -P 1 -p portalip,3260 -t sendtargets -o delete

Rediscovery targets

sudo iscsiadm -m discovery -t sendtargets -p portalip

Remove unwanted targets from /etc/iscsi/nodes/ directory and interfaces from the iqn-target/* directory.

Edit the default file to add the CHAP settings

node.session.auth.authmethod = CHAP
node.session.auth.username = username
node.session.auth.password = password
node.session.auth.username_in = username_in
node.session.auth.password_in = password_in

Make the node startup automatic
```
node.startup = automatic
```
With the CHAP settings configured correctly, you can now login to the target by using
```
sudo iscsiadm -m node -T iqn.target -p portalip:portalport --login
```

Sometimes the iscsi_tcp module might not be loaded in the kernel. Looks like we need to run

sudo apt-get install linux-modules-extra-$(uname -r)

to install the module.

After these steps, iSCSI connections should get established really quickly. You can verify the impact of iscsi on system startup through sudo systemd-analyze blame command.

1. Stop initiators to attempt multiple sessions.#

1. Stop initiators to attempt multiple sessions.