April 29, 20242 yr Author 1 minute ago, emrepolat7 said: Yes it works now. Thank you very much. I would recommend that you fully uninstall the plugin once, reboot your server and after that install the plugin again from the CA App, I have maybe found another bug which should be fixed with that.
August 15, 20241 yr Plugin works great - but after a kernel panic and forced reboot I am getting a log full of the following every 5 seconds: Aug 15 14:53:21 Trinity kernel: iSCSI Login negotiation failed. Aug 15 14:53:26 Trinity kernel: Unable to locate Target IQN: iqn.2003-01.org.linux-iscsi.tower.x8664:sn.74c2161ab370 in Storage Node Aug 15 14:53:26 Trinity kernel: iSCSI Login negotiation failed. Aug 15 14:53:31 Trinity kernel: Unable to locate Target IQN: iqn.2003-01.org.linux-iscsi.tower.x8664:sn.74c2161ab370 in Storage Node Aug 15 14:53:31 Trinity kernel: iSCSI Login negotiation failed. Aug 15 14:53:36 Trinity kernel: Unable to locate Target IQN: iqn.2003-01.org.linux-iscsi.tower.x8664:sn.74c2161ab370 in Storage Node Aug 15 14:53:36 Trinity kernel: iSCSI Login negotiation failed. Aug 15 14:53:41 Trinity kernel: Unable to locate Target IQN: iqn.2003-01.org.linux-iscsi.tower.x8664:sn.74c2161ab370 in Storage Node Aug 15 14:53:41 Trinity kernel: iSCSI Login negotiation failed. Aug 15 14:53:46 Trinity kernel: Unable to locate Target IQN: iqn.2003 I have one connection up and running with no issues as follows: o- / ......................................................................................................................... [...] o- backstores .............................................................................................................. [...] | o- block .................................................................................................. [Storage Objects: 0] | o- fileio ................................................................................................. [Storage Objects: 1] | | o- fileIO ...................................................... [/mnt/user/BlueIris/fileIO.img (7.8TiB) write-back activated] | | o- alua ................................................................................................... [ALUA Groups: 1] | | o- default_tg_pt_gp ....................................................................... [ALUA state: Active/optimized] | o- pscsi .................................................................................................. [Storage Objects: 0] | o- ramdisk ................................................................................................ [Storage Objects: 0] o- iscsi ............................................................................................................ [Targets: 1] | o- iqn.2003-01.org.linux-iscsi.trinity.x8664:sn.ee7b28ed45fa ......................................................... [TPGs: 1] | o- tpg1 ............................................................................................... [no-gen-acls, no-auth] | o- acls .......................................................................................................... [ACLs: 1] | | o- iqn.1991-05.com.microsoft:aeonflux ................................................................... [Mapped LUNs: 1] | | o- mapped_lun0 ............................................................................... [lun0 fileio/fileIO (rw)] | o- luns .......................................................................................................... [LUNs: 1] | | o- lun0 ............................................... [fileio/fileIO (/mnt/user/BlueIris/fileIO.img) (default_tg_pt_gp)] | o- portals .................................................................................................... [Portals: 1] | o- 0.0.0.0:3260 ..................................................................................................... [OK] o- loopback ......................................................................................................... [Targets: 0] o- vhost ............................................................................................................ [Targets: 0] o- xen-pvscsi ....................................................................................................... [Targets: 0] There is no mention of IQN (ending in ab370) in the plugin interface. Is there a file/place that could have a dangling IQN that needs to be removed that is causing the errors? Uninstalling/reinstalling would work but am hoping for a simpler fix. Thanks!
August 15, 20241 yr 2 hours ago, pvonnur said: Plugin works great - but after a kernel panic and forced reboot I am getting a log full of the following every 5 seconds: Aug 15 14:53:21 Trinity kernel: iSCSI Login negotiation failed. Aug 15 14:53:26 Trinity kernel: Unable to locate Target IQN: iqn.2003-01.org.linux-iscsi.tower.x8664:sn.74c2161ab370 in Storage Node Aug 15 14:53:26 Trinity kernel: iSCSI Login negotiation failed. Aug 15 14:53:31 Trinity kernel: Unable to locate Target IQN: iqn.2003-01.org.linux-iscsi.tower.x8664:sn.74c2161ab370 in Storage Node Aug 15 14:53:31 Trinity kernel: iSCSI Login negotiation failed. Aug 15 14:53:36 Trinity kernel: Unable to locate Target IQN: iqn.2003-01.org.linux-iscsi.tower.x8664:sn.74c2161ab370 in Storage Node Aug 15 14:53:36 Trinity kernel: iSCSI Login negotiation failed. Aug 15 14:53:41 Trinity kernel: Unable to locate Target IQN: iqn.2003-01.org.linux-iscsi.tower.x8664:sn.74c2161ab370 in Storage Node Aug 15 14:53:41 Trinity kernel: iSCSI Login negotiation failed. Aug 15 14:53:46 Trinity kernel: Unable to locate Target IQN: iqn.2003 I have one connection up and running with no issues as follows: o- / ......................................................................................................................... [...] o- backstores .............................................................................................................. [...] | o- block .................................................................................................. [Storage Objects: 0] | o- fileio ................................................................................................. [Storage Objects: 1] | | o- fileIO ...................................................... [/mnt/user/BlueIris/fileIO.img (7.8TiB) write-back activated] | | o- alua ................................................................................................... [ALUA Groups: 1] | | o- default_tg_pt_gp ....................................................................... [ALUA state: Active/optimized] | o- pscsi .................................................................................................. [Storage Objects: 0] | o- ramdisk ................................................................................................ [Storage Objects: 0] o- iscsi ............................................................................................................ [Targets: 1] | o- iqn.2003-01.org.linux-iscsi.trinity.x8664:sn.ee7b28ed45fa ......................................................... [TPGs: 1] | o- tpg1 ............................................................................................... [no-gen-acls, no-auth] | o- acls .......................................................................................................... [ACLs: 1] | | o- iqn.1991-05.com.microsoft:aeonflux ................................................................... [Mapped LUNs: 1] | | o- mapped_lun0 ............................................................................... [lun0 fileio/fileIO (rw)] | o- luns .......................................................................................................... [LUNs: 1] | | o- lun0 ............................................... [fileio/fileIO (/mnt/user/BlueIris/fileIO.img) (default_tg_pt_gp)] | o- portals .................................................................................................... [Portals: 1] | o- 0.0.0.0:3260 ..................................................................................................... [OK] o- loopback ......................................................................................................... [Targets: 0] o- vhost ............................................................................................................ [Targets: 0] o- xen-pvscsi ....................................................................................................... [Targets: 0] There is no mention of IQN (ending in ab370) in the plugin interface. Is there a file/place that could have a dangling IQN that needs to be removed that is causing the errors? Uninstalling/reinstalling would work but am hoping for a simpler fix. Thanks! Looks like a remote host is trying to connect with the unraid ip but has the wrong target name.
September 17, 20241 yr Is it possible to do "zfs over ISCSI with proxmox , with this plugin? been struggling with it now for most of the day...lol
September 18, 20241 yr Author 8 hours ago, bar1 said: Is it possible to do "zfs over ISCSI with proxmox , with this plugin? been struggling with it now for most of the day...lol I have to research what this is. I assume this is a Proxmox exclusive feature...? I'm sure they'll have some documentation around that. Sorry but I don't use Proxmox but I will look into that. EDIT: Can you maybe link to some documentation or explain what you plan to do with that exactly?
September 18, 20241 yr Thanks for the reply, unfortunately this is not very well documented. This is the best guide I found but needs translation : https://deepdoc-at.translate.goog/dokuwiki/doku.php?id=virtualisierung:proxmox_kvm_und_lxc:proxmox_debian_als_zfs-over-iscsi_server_verwenden&_x_tr_sl=auto&_x_tr_tl=en&_x_tr_hl=en-GB official document : https://pve.proxmox.com/wiki/Storage:_ZFS_over_ISCSI I am using unriad as a vm and would like to use the storage in proxmox. maybe the first question should be which which g iSCSI target implementations is being used? LIO (Linux) IET (Linux) ISTGT (FreeBSD) Comstar (Solaris) I assume LIO.
September 18, 20241 yr Author 31 minutes ago, bar1 said: This is the best guide I found but needs translation Not for me… 31 minutes ago, bar1 said: I assume LIO. Yes I use the default LIO implementation. From what I understand you can basically follow the tutorial and set up Unraid as it is a node, all commands should be accesible from the command line on Unraid as usual.
September 18, 20241 yr Author 1 hour ago, bar1 said: Is targetclid.service enabled ? 1 hour ago, bar1 said: and the target group is tpg1? Wait, you are in the Initiator support thread... targetcli is part from iSCSI Target not Initiator. I thought you run the Target on Proxmox and use the Initiator from your Unraid VM to access the Target on Proxmox to utilize the storage from Proxmox on Unraid. In the tutorial that you've linked targetcli-fb and the service is installed/enabled on Proxmox and not the other way around.
October 19, 20241 yr I have the iscsi initiator plugin, is there a way to connect to an iscsi target and mount the partition via a user script? I’m trying to make a backup script that once a month will send a WOL packet to the backup server, connect to an iscsi target on the backup server, mount the partition located on the iscsi target, backup the data, unmount the partition on the iscsi target, then send an ssh command to shutdown the backup server. Thank you for the hard work and I look forward to your reply!
October 19, 20241 yr Author 1 hour ago, MetaCerberus said: is there a way to connect to an iscsi target and mount the partition via a user script? Yes: iscsiadm -m node -T <IQN> -p <IP>:<PORT> --login However I really don‘t understand why you want to do that through iSCSI, SMB or NFS would be the more obvious choice. I for example have a backup server that turns on automatically on a schedule, waits a few minutes until it‘s fully startet and then pulls the Data from my Main server through SSH which is in my opinion way more convenient. I use luckyBackup for that on my Backup server which is just a fancy GUI for rsync.
October 19, 20241 yr 12 minutes ago, ich777 said: Yes: iscsiadm -m node -T <IQN> -p <IP>:<PORT> --login However I really don‘t understand why you want to do that through iSCSI, SMB or NFS would be the more obvious choice. I for example have a backup server that turns on automatically on a schedule, waits a few minutes until it‘s fully startet and then pulls the Data from my Main server through SSH which is in my opinion way more convenient. I use luckyBackup for that on my Backup server which is just a fancy GUI for rsync. Its mainly because I've been running into issues with backing up huge amounts of data and files with SMB and NFS. Meanwhile, my testing using iSCSI has been essentially flawless. Since its a full backup of 40+TB of data that runs once a month, iSCSI has been the only solution that works at the speeds I expect. edit: also im glad to know its just a normal iscsi command. Edited October 19, 20241 yr by MetaCerberus
October 19, 20241 yr Author 2 minutes ago, MetaCerberus said: SMB and NFS Have you yet tried it over ssh? It works really well, just look at luckyBackup. iSCSI seems a bit over engineered.
October 19, 20241 yr 1 hour ago, ich777 said: Have you yet tried it over ssh? It works really well, just look at luckyBackup. iSCSI seems a bit over engineered. I'm assuming youre running luckyBackup through a docker container or a vm? if thats the case, this approach likely wont work since I am backing up my entire unraid server. Ive tried rsync over ssh but the overhead was quite heavy. it took me about 2 days to copy everything over rsync to an iscsi target vs almost a week to copy stuff over ssh. Not quite sure why since it should theoretically be very close in speeds. 32 minutes ago, Kilrah said: Why copy 40TB across entirely every month instead of using rsync/rsnapshot? a bit off topic for the thread, but this is because I am keeping 2 separate full copies of the data alternating every other month. This is a local backup. If it were a remote backup, I would be using a less heavy approach.
October 19, 20241 yr Author 36 minutes ago, MetaCerberus said: I'm assuming youre running luckyBackup through a docker container or a vm? if thats the case, this approach likely wont work since I am backing up my entire unraid server. Ive tried rsync over ssh but the overhead was quite heavy. it took me about 2 days to copy everything over rsync to an iscsi target vs almost a week to copy stuff over ssh. Not quite sure why since it should theoretically be very close in speeds. On the Backup server yes but not on the main server... Noting would prevent you like I do it to sync the whole server, as said above, the Backup server pulls the data in. Speeds are slightly slower with SSH usually but keep in mind that after the first sync finished rsync pulls only in the new data and the sync will be way quicker and it is way more efficient and pretty much the same since the data will then be also the same as on your Main server.
October 19, 20241 yr 3 hours ago, MetaCerberus said: a bit off topic for the thread, but this is because I am keeping 2 separate full copies of the data alternating every other month. This is a local backup. If it were a remote backup, I would be using a less heavy approach. Sure, but still seems like looking for a solution to a problem that shouldn't exist in the first place. Why be with an incomplete/inconsistent backup for a few days every month when an rsync would probably take a couple of hours to update things, and with rsnapshot would even let you keep a rotating versioned backup... 2 separate copies doesn't matter, same can be run towards both.
March 4, 20251 yr hey, i am using your iscsi plugin on unraid 7. I can see the target, but when i try to connect to it i get authorization failure. I have set the username root and its (unraid-)password in my client config, but it still wont let me connect. could you help me troubleshoot it or tell me where i can find logs regarding the iscsi plugin? Thanks. Server: Unraid 7.0.0, iscsi plugin version: 2023.03.25a Im trying to connect to the iscsi lun on unraid: iscsi config: o- / ......................................................................................................................... [...] o- backstores .............................................................................................................. [...] | o- block .................................................................................................. [Storage Objects: 0] | o- fileio ................................................................................................. [Storage Objects: 1] | | o- steam ......................................................... [/mnt/user/iscsi/steam.img (400.0GiB) write-back activated] | | o- alua ................................................................................................... [ALUA Groups: 1] | | o- default_tg_pt_gp ....................................................................... [ALUA state: Active/optimized] | o- pscsi .................................................................................................. [Storage Objects: 0] | o- ramdisk ................................................................................................ [Storage Objects: 0] o- iscsi ............................................................................................................ [Targets: 1] | o- iqn.2003-01.org.linux-iscsi.unraid.x8664:sn.05106e39d566 .......................................................... [TPGs: 1] | o- tpg1 ............................................................................................... [no-gen-acls, no-auth] | o- acls .......................................................................................................... [ACLs: 0] | o- luns .......................................................................................................... [LUNs: 1] | | o- lun0 .................................................... [fileio/steam (/mnt/user/iscsi/steam.img) (default_tg_pt_gp)] | o- portals .................................................................................................... [Portals: 1] | o- 0.0.0.0:3260 ..................................................................................................... [OK] o- loopback ......................................................................................................... [Targets: 0] o- vhost ............................................................................................................ [Targets: 0] o- xen-pvscsi ....................................................................................................... [Targets: 0] Im trying to login with this command on my client (Fedora Linux): iscsiadm --mode discovery --type sendtargets --portal 192.168.1.100 --login 192.168.1.100:3260,1 iqn.2003-01.org.linux-iscsi.unraid.x8664:sn.05106e39d566 I then receive auth failure: Logging in to [iface: default, target: iqn.2003-01.org.linux-iscsi.unraid.x8664:sn.05106e39d566, portal: 192.168.1.100,3260] iscsiadm: Could not login to [iface: default, target: iqn.2003-01.org.linux-iscsi.unraid.x8664:sn.05106e39d566, portal: 192.168.1.100,3260]. iscsiadm: initiator reported error (24 - iSCSI login failed due to authorization failure) on my client i adjusted this file to set the username and passowrd: /var/lib/iscsi/nodes/iqn.2003-01.org.linux-iscsi.unraid.x8664:sn.05106e39d566/192.168.1.100,3260,1/default node.session.auth.authmethod = CHAP node.session.auth.username = root node.session.auth.password = "password for root user on unraid" I guess i would need to set the crendentials on the server in some config? But I couldnt find where. Even better would be if I could just disable CHAP completely so my LUN doesnt require credentials. thanks! Edited March 4, 20251 yr by I_am_Mraio5436
March 4, 20251 yr Author 10 minutes ago, I_am_Mraio5436 said: iscsiadm: initiator reported error (24 - iSCSI login failed due to authorization failure) Try to use first: iscsiadm -m discovery -t sendtargets -p 192.168.1.100:3260 after that issue: iscsiadm -m node -T iqn.2003-01.org.linux-iscsi.unraid.x8664:sn.05106e39d566 -p 192.168.1.100:3260 --login I assume this is: 192.168.1.100 = Target IP (so to speak Unraid server) 3260 = Target Port (so to speak Unraid port) iqn.2003-01.org.linux-iscsi.unraid.x8664:sn.05106e39d566 = Target IQN (so to speak Unraid IQN) 14 minutes ago, I_am_Mraio5436 said: on my client i adjusted this file to set the username and passowrd: Please don't use credentials at all, the plugin doesn't support that, only the TPG and ACLs with the correct IQNs are needed.
March 4, 20251 yr 13 minutes ago, ich777 said: Try to use first: iscsiadm -m discovery -t sendtargets -p 192.168.1.100:3260 That gives me the correct target: 192.168.1.100:3260,1 iqn.2003-01.org.linux-iscsi.unraid.x8664:sn.05106e39d566 after that issue: iscsiadm -m node -T iqn.2003-01.org.linux-iscsi.unraid.x8664:sn.05106e39d566 -p 192.168.1.100:3260 --login that gives me: Logging in to [iface: default, target: iqn.2003-01.org.linux-iscsi.unraid.x8664:sn.05106e39d566, portal: 192.168.1.100,3260] iscsiadm: Could not login to [iface: default, target: iqn.2003-01.org.linux-iscsi.unraid.x8664:sn.05106e39d566, portal: 192.168.1.100,3260]. iscsiadm: initiator reported error (24 - iSCSI login failed due to authorization failure) iscsiadm: Could not log into all portals I assume this is: 192.168.1.100 = Target IP (so to speak Unraid server) 3260 = Target Port (so to speak Unraid port) iqn.2003-01.org.linux-iscsi.unraid.x8664:sn.05106e39d566 = Target IQN (so to speak Unraid IQN) Yes, thats correct. 13 minutes ago, ich777 said: Please don't use credentials at all, the plugin doesn't support that, only the TPG and ACLs with the correct IQNs are needed. I dont want to use credentials, thats why im confused about the errormessage. I didnt set any credentials in unraid. I ran these commands with sudo on my client. Edited March 4, 20251 yr by I_am_Mraio5436
March 4, 20251 yr Author 3 hours ago, I_am_Mraio5436 said: I dont want to use credentials, thats why im confused about the errormessage. I think you are missing the ACL, please look at this post at the second photo, you have to authorize the IQN from the Initiator (so to speak from the client) on the Target (so to speak Unraid) :
March 4, 20251 yr 3 hours ago, ich777 said: I think you are missing the ACL, please look at this post at the second photo, you have to authorize the IQN from the Initiator (so to speak from the client) on the Target (so to speak Unraid) : Im not sure what you are trying to say. The Link you are sending has Unraid as the Client and not the Host, its for the other plugin, which I dont need? I need to connect to the LUN on Unraid. How can i enable ACLs in the LUN in Unraid? I dont know where the config file for the iscsi connections / LUN are located. The second picture doesnt look at all what I am seeing in the plugin. I have now also tested, if I can connect from a different Client (Linux Mint), but I am getting the exact same Authorization failure error there, so it has to be some setting in unraid, but idk where to look (configfile) for that. Edited March 4, 20251 yr by I_am_Mraio5436
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.