iscsiadm: initiator reported error (19 - encountered non-retryable iSCSI login failure) / Could not log into all portals
See original GitHub issueI am suddenly getting this new error message, seems similar to 112. I had not changed my democratic-csi config since mid-October and got this error starting a few days ago. I’m running democratic-csi chart 0.8.3 with freenas-api-iscsi driver.
MountVolume.MountDevice failed for volume "pvc-5a7349c4-b25e-45a6-9475-c18e4bc7cc6c" : rpc error: code = Internal desc = {"code":19,"stdout":"Logging in to [iface: default, target: iqn.2005-10.org.freenas.ctl:flux-nextcloud-nextcloud-db, portal: 10.2.1.1,3260] (multiple)\n","stderr":"iscsiadm: Could not login to [iface: default, target: iqn.2005-10.org.freenas.ctl:flux-nextcloud-nextcloud-db, portal: 10.2.1.1,3260].\niscsiadm: initiator reported error (19 - encountered non-retryable iSCSI login failure)\niscsiadm: Could not log into all portals\n"}
Per 112, I have tried running systemctl restart scst on SCALE, although I already had several targets available at the time when I started receiving the error. I also tried restarting SCALE, updating SCALE from TrueNAS-SCALE-22.02-RC.1 to TrueNAS-SCALE-22.02-RC.2, and restarting nodes, to no avail.
LMK if I can hunt down other logs or provide additional config files that might be of use.
Issue Analytics
- State:
- Created 2 years ago
- Comments:11 (6 by maintainers)
Top Results From Across the Web
Unable to connect to iSCSI Target - LinuxQuestions.org
iscsiadm : initiator reported error (19 - encountered non-retryable iSCSI login failure) iscsiadm: Could not log into all portals
Read more >iscsiadm login failed - Google Groups
I'm trying to connect my open-iscsi initiator to target, but failed to login with the command "sudo iscsiadm -m node --login".
Read more >2017715 – [RBD] ISCSI - Login failed and unable to discover ...
We see issue only with mutual chap as we do not see login successful. ... non-retryable iSCSI login failure) iscsiadm: Could not log...
Read more >[solved] Can't login to iSCSI target - Ubuntu Forums
I used this guide in the past to configure the iSCSI initiator. ... reported error (19 - encountered non-retryable iSCSI login failure).
Read more >iSCSI errors when logging in to target - CentOS forum
... iscsiadm: initiator reported error (19 - encountered non-retryable iSCSI login failure) iscsiadm: Could not log into all portals.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Just kubectl delete the pv. Retain doesn’t really do anything special other than prevent it from deleting when a bound pvc is deleted.
With a ‘retain’ policy, what is the appropriate way to remove?