August 19, 20214 yr 1 hour ago, iDJMic said: Just wanted to add a drive on the iSCSI under unassigned devices. That's not possible with this plugin because it's the iSCSI Target (Server) not the Initiator (Client). That would be a question for the UnassignedDevices thread.
August 23, 20214 yr I'm at a loss on how to set this up. I muddled my way through the other UI setup you all had. The new one is less straightforward. Got everything done except for the Add Map step on the Initiators page. What actually goes into the fields? Why are these not pre-populated or drop downs from the data that exists elsewhere in the plugins? I have no idea what format the Lun or Backstore name should be to enter into this form? Is there a set of screenshots where someone shows what those entries should look like?
August 23, 20214 yr Actually I dug into the code and found the issue. The command to add a mapping is populated incorrectly from the UI. The command that is generated during the Mapping process when using the UI has the word "typename" where it should contain the Lun ID (ie "lun0"). Hence the command will fail every time. No wonder I was confused.
August 23, 20214 yr Author 7 minutes ago, gingerdude said: Actually I dug into the code and found the issue. The command to add a mapping is populated incorrectly from the UI. The command that is generated during the Mapping process when using the UI has the word "typename" where it should contain the Lun ID (ie "lun0"). Hence the command will fail every time. No wonder I was confused. Had you created the LUN?
August 23, 20214 yr Everything was created beforehand. I now realize it's because the formatting for that Lun Id field is "fileio:test3". I was trying everything like "lun0" "backstores/fileio/test3" etc. I just needed to see the fields completed in an example to understand what to do.
August 27, 20214 yr I created initiator and LUN from fileIO, but client on macOS asks for CHAP details, when I enter username and password from unRAID, I get a message that the password must be 12 to 16 characters. And it is impossible to disable it. client: DAEMON tools macOS: 11.5.2 (20G95) unRAID: 6.9.2 When I create such an initiator on the Synology NAS, everything works without any problems. Edited August 27, 20214 yr by XiMA4
August 27, 20214 yr Author you need to create the acl and mapping also. Quote o- iqn.2003-01.org.linux-iscsi.computenode.x8664:sn.0e9010727885 ..................................................... [TPGs: 1] | o- tpg1 ............................................................................................... [no-gen-acls, no-auth] | o- acls .......................................................................................................... [ACLs: 1] | | o- iqn.1991-05.com.microsoft:desktop-jur4c32 ............................................................ [Mapped LUNs: 0] | o- luns .......................................................................................................... [LUNs: 2] | | o- lun0 ...................................................... [fileio/test (/mnt/user/iscsi/test.img) (default_tg_pt_gp)] | | o- lun1 .................................................... [fileio/test3 (/mnt/user/iscsi/test3.img) (default_tg_pt_gp)] | o- portals .................................................................................................... [Portals: 1] | o- 0.0.0.0:3260 ..................................................................................................... [OK]
August 27, 20214 yr 3 minutes ago, SimonF said: you need to create the acl and mapping also. Thanks for the answer, how to do this? Or where can I find information about this?
August 27, 20214 yr Author 26 minutes ago, XiMA4 said: Thanks for the answer, how to do this? Or where can I find information about this? On the Initiators tab add the IGN for your MAC and add the mapping.
August 27, 20214 yr 32 minutes ago, SimonF said: On the Initiators tab add the IGN for your MAC ... Wow! Works! Many thanks, didn’t know it needed to add the name of the initiator. This is not required at Synology. Edited August 27, 20214 yr by XiMA4
August 27, 20214 yr 1 hour ago, XiMA4 said: Wow! Works! Disastrously low write speed is it ok for iSCSI Target on unRAID? I am using FileIO 300GB in Array. Edited August 27, 20214 yr by XiMA4
August 27, 20214 yr 33 minutes ago, XiMA4 said: I am using FileIO 300GB in Array. Do you have Write Back enabled? If not make sure it's enabled. This is a really common thing with iSCSI and has nothing to do with unRAID. I run my NVME with a 10Gbit NIC and have no problem reaching 1GB/s, of course I use the whole disk as a initiator and not a FileIO volume.
August 27, 20214 yr 39 minutes ago, ich777 said: Do you have Write Back enabled? If not make sure it's enabled. Exactly! It was turned off. Now I am satisfied. Great plugin! Thanks for the help.
September 13, 20214 yr is there a way to use a share with this plugin or does it allow unassigned devices only? I am using zfs plugin and would like to use a zfs share. Thanks
September 13, 20214 yr 16 minutes ago, Xxharry said: is there a way to use a share with this plugin or does it allow unassigned devices only? iSCSI allows you to share a disk or a image file. A share is not possible since this is not SAMBA, iSCSI was created to share disks over the network (as the name implies), what you can do is that you create a FileIO image on a disk/share with the size that you want and then you can share this image as a disk via iSCSI. Be also sure to turn on "Write Back" for the FileIO image otherwise the transfer rates can be pretty slow.
September 13, 20214 yr Are there any plans to add ACL configuration to the plugin's web interface? In my case, iPXE doesn't play nice with LinuxIO/LIO, so I have to manually disable the ACL attribute `nopin_timeout` for every client, like so: echo 0 > /sys/kernel/config/target/iscsi/<target_iqn>/tpgt_1/acls/<client_iqn>/attrib/nopin_timeout
September 13, 20214 yr Author 11 hours ago, Didstopia said: web interface? Will look to see if easy to add.
September 14, 20214 yr Author @Didstopia Would you be able to provide extract from the Config on the status tab? o- iscsi ............................................................................................................. [Targets: 1] | o- iqn.2003-01.org.linux-iscsi.xxxxxx ................................................................................ [TPGs: 1] | o- tpg1 ............................................................................................... [no-gen-acls, no-auth] | o- acls .......................................................................................................... [ACLs: 1] | | o- iqn.1991-05.com.microsoft:xxxxxx ..................................................................... [Mapped LUNs: 1] | | o- mapped_lun1 ................................................................................ [lun1 fileio/test3 (rw)]
October 7, 20214 yr Hi, First of all, thank you for providing such a great tool! I successfully setted up an image target with this plugin and got my windows initiator conneted and run! However unraid server side syslog keep spaming this message every 3secs once connected: xxx kernel: iSCSI/iqn.1991-05.com.microsoft:xxx: Unsupported SCSI Opcode 0xa1, sending CHECK_CONDITION. I did some research and find out this seems harmless but just a windows thing, but it's anoying and fiiling up my syslog fast. Is there anything I can do?
October 8, 20214 yr Author On 10/7/2021 at 7:09 AM, ZZY said: Is there anything I can do? Not that I know of, I think its the client probing for info.
October 8, 20214 yr Author On 10/7/2021 at 7:09 AM, ZZY said: Is there anything I can do? Hi ich777 has suggested you can try the following: echo ":msg,contains,\"Unsupported SCSI Opcode 0xa1\" stop" >> /etc/rsyslog.d/01-blocklist.conf /etc/rc.d/rc.rsyslogd restart Also you will need to add to your go file to make persistent Edited October 8, 20214 yr by SimonF
October 9, 20214 yr 13 hours ago, SimonF said: Hi ich777 has suggested you can try the following: echo ":msg,contains,\"Unsupported SCSI Opcode 0xa1\" stop" >> /etc/rsyslog.d/01-blocklist.conf /etc/rc.d/rc.rsyslogd restart Also you will need to add to your go file to make persistent Yeah! I was trying to figure out how to filter such logs and this works perfectly! Thank you so much SimonF and ich777!
November 28, 20214 yr Hi, Is there a guild I can follow or instructions to get this working? I have tried to create a target by putting in a name and clicking the add target button but nothing happens. Clearly I don't know what I am doing. In the Diags window it says this for the last Targetcli output. targetcli shell version 2.1.54 Copyright 2011-2013 by Datera, Inc and others. For help on commands, type 'help'. /> WWN not valid as: iqn, naa, eui /> Global pref auto_save_on_exit=true Last 10 configs saved in /etc/target/backup/. Configuration saved to /etc/target/saveconfig.json Thanks Edited November 28, 20214 yr by Asus750
November 28, 20214 yr Author 34 minutes ago, Asus750 said: Hi, Is there a guild I can follow or instructions to get this working? I have tried to create a target by putting in a name and clicking the add target button but nothing happens. Clearly I don't know what I am doing. In the Diags window it says this for the last Targetcli output. targetcli shell version 2.1.54 Copyright 2011-2013 by Datera, Inc and others. For help on commands, type 'help'. /> WWN not valid as: iqn, naa, eui /> Global pref auto_save_on_exit=true Last 10 configs saved in /etc/target/backup/. Configuration saved to /etc/target/saveconfig.json Thanks What are you trying to connect? Can you provide some screen prints? You need to create the target, iqn luns, map the luns. Luns will need either a drive mapped or fileio
November 29, 20214 yr 4 hours ago, SimonF said: What are you trying to connect? Can you provide some screen prints? You need to create the target, iqn luns, map the luns. Luns will need either a drive mapped or fileio It looks like it started working. I rebooted the server after messing with it for a while and I have an option to choose a target now under create IQN. I have an sata SSD that I will be using to test it, and it picked that up on the devices tab. I will keep playing with it but looks to be working. Thanks for the quick reply.
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.