[Plugin] iSCSI Initiator

[ich777]

11 hours ago, watevriwanabi said:

Thanks

As far as I can tell you are connected to the Target:

Feb 17 16:37:30 Server kernel: scsi host8: iSCSI Initiator over TCP/IP
Feb 17 16:37:30 Server root: Logging in to [iface: default, target: iqn.2004-04.com.qnap:ts-433:iscsi.backup.634ac9, portal: 192.168.0.7,3260]
Feb 17 16:37:30 Server root: Login to [iface: default, target: iqn.2004-04.com.qnap:ts-433:iscsi.backup.634ac9, portal: 192.168.0.7,3260] successful.
Feb 17 16:37:30 Server  iscsid: Connection1:0 to [target: iqn.2004-04.com.qnap:ts-433:iscsi.backup.634ac9, portal: 192.168.0.7,3260] through [iface: default] is operational now

 

Are you sure that you've assigned a disk on the Target to the LUN and configured everything properly on the Target? At least the connection seems to be working fine.

 

However I would recommend that you install the plugin Unassigned Devices and check if you see the the disk afterwards there.

[watevriwanabi]

22 hours ago, ich777 said:

Are you sure that you've assigned a disk on the Target to the LUN and configured everything properly on the Target?

I'm not completely sure I have the target configured correctly, but I think I do. I attached of screenshot if that helps.

 

 

22 hours ago, ich777 said:

I would recommend that you install the plugin Unassigned Devices and check if you see the the disk afterwards there.

I installed the plugin, "No Unassigned Disks available"

[ich777]

5 hours ago, watevriwanabi said:

I'm not completely sure I have the target configured correctly, but I think I do. I attached of screenshot if that helps.

I think there is something missing on your Target but I even don't know what software that is from where you posted a screenshot.

 

Are you sure that the Initiator name is in the ACL from the Target? From my perspective it can be only a little miss configuration since even the Target shows that your Initiator (Unraid) is connected.

[syq7970]

Hi, thanks for this great plugin.

Can I do some retry/reconnet config after ISCSI Server is down or reboot?

Now I have to recreate connection everytime, otherwise it will show "no active session".

Any suggestions?

Edited March 25, 2023 by syq7970

[ich777]

2 hours ago, syq7970 said:

Can I do some retry/reconnet config after ISCSI Server is down or reboot?

Currently not because that‘s not how iSCSI should be used but I will take a look at it and report back to implent a Reconnect button.

Please give me a few days.

[ich777]

On 3/25/2023 at 3:32 PM, syq7970 said:

Can I do some retry/reconnet config after ISCSI Server is down or reboot?

Can you give me a bit more context on that? No matter what I try, even if my target is now offline for a day it still reconnects to it when it becomes available again.

[syq7970]

On 3/28/2023 at 4:14 PM, ich777 said:

Can you give me a bit more context on that? No matter what I try, even if my target is now offline for a day it still reconnects to it when it becomes available again.

May be you can try use ISCSI plugin and ISCSI initiator plugin on the same unraid server.

Create a ISCSI target by ISCSI plugin, then use ISCSI initiator connect to localhost target, after this, reboot unraid server, ISCSI initiator always show "no active session" untill I recreate connection manually.

 

[ich777]

33 minutes ago, syq7970 said:

ISCSI initiator always show "no active session" untill I recreate connection manually.

Ah okay, now I get it, the issue is that the target is not available at boot.

I can maybe change the plugin with a extra setting to take that into account but this is very problematic and a niche use case.

 

Anyways I've updated the plugin and you have now a reconnect button.

[GGGXXXVVV]

Hello, I just tried to mount iscsi on window11 but I'm having some problems, when I mount it I get an authorization failure message, I've compared the correct settings but I can't find the problem.

[ich777]

10 hours ago, GGGXXXVVV said:

I can't find the problem

Could this be the issue:

 

 

The name doesn't match.

[rezo]

I was successfully using this in the past, few months ago I turned off my Unraid and now it doesnt want to reconnect the LUN. Though the iSCSI session seems to be active

 

 

 

 

 

 

Also the target (QNAP) shows the initiator is connected:

 

 

What could be the problem?

[ich777]

2 hours ago, rezo said:

I was successfully using this in the past, few months ago I turned off my Unraid and now it doesnt want to reconnect the LUN. Though the iSCSI session seems to be active

What did you do exactly? Did you upgrade to a newer Unraid version?

 

Do no devices appear in Unraid itself?

[rezo]

So I booted it up and it was not appearing then I did upgrade (both Unraid and the plug-in) in hope that it will resolve the problem. But at the end it didn’t, the LUN doesn’t appear under array at all. The weird thing is that I cannot even see the block device in dmesg

[ich777]

4 minutes ago, rezo said:

The weird thing is that I cannot even see the block device in dmesg

What happens when you select your target and click reconnect?

[rezo]

4 minutes ago, ich777 said:

What happens when you select your target and click reconnect?

Nothing 

 

 

 

 

root@rezo-unraid:~# dmesg
....
[   74.947923] NFSD: Using UMH upcall client tracking operations.
[   74.947927] NFSD: starting 90-second grace period (net f0000000)
[  128.354302] scsi host13: iSCSI Initiator over TCP/IP
root@rezo-unraid:~#

[ich777]

5 minutes ago, rezo said:

Nothing

It seems that the connection is established successfully. I will try that ASAP on my system.

 

Did maybe change anything on the QNAP site? Have you yet tried to connect from another machine to the Target?

[ich777]

@rezo I've now tried it and I can see the block device on the Initiator side:

 

I'm also on rc18 to compare apples to apples (also the Initiator side):

 

 

And this is on the Target side:

 

 

There must have changes something on the QNAP side, maybe try to recreate the Target and also everything on the Initiator side.

[rezo]

Indeed, I created a brand new LUN and Im able to attach.... Shit, I need to do a recovery somehow, crappy QNAP

 

3 hours ago, ich777 said:

 

@rezo I've now tried it and I can see the block device on the Initiator side:

 

I'm also on rc18 to compare apples to apples (also the Initiator side):

 

 

And this is on the Target side:

 

 

There must have changes something on the QNAP side, maybe try to recreate the Target and also

everything on the Initiator side.

 

 

[emrepolat7]

I can't find what I'm doing wrong?

[ich777]

58 minutes ago, emrepolat7 said:

I can't find what I'm doing wrong?

A bit more information would be nice please.

 

Did you map the LUN properly to the Initiator name?

It seems that Unraid is not able to connect to your Target, are you sure that your Target is running on port 3260?

 

Can you ping your Target from Unraid?

The plugin first tries to discover the Target with the specified IP and port, if that fails you see this message.

 

You can also try this by issuing (from a Unraid Terminal) :

iscsiadm -m discovery -t sendtargets -p 192.168.1.2:3260

 

[emrepolat7]

When I checked all the settings, I didn't find any mistakes. When I tried manually, I get the error below. Do you think this could be the problem?

 

root@polser:/usr/local/emhttp/plugins/iscsi-initiator/include# iscsiadm -m discovery -t sendtargets -p 192.168.1.2

iscsiadm: error while loading shared libraries: libcrypto.so.1.1: cannot open shared object file: No such file or directory

Edited yesterday at 12:05 PM by emrepolat7

[ich777]

13 minutes ago, emrepolat7 said:

Do you think this could be the problem?

On what Unraid version are you?

[emrepolat7]

6.13.0-beta.1

[ich777]

31 minutes ago, emrepolat7 said:

6.13.0-beta.1

Thank you, I will look into that and report back.

That's maybe caused because you are on the private test branch.

 

Please update the plugin to version 2024.04.29 and see if it is now working for you.

[emrepolat7]

56 minutes ago, ich777 said:

Thank you, I will look into that and report back.

That's maybe caused because you are on the private test branch.

 

Please update the plugin to version 2024.04.29 and see if it is now working for you.

 

Yes it works now. Thank you very much.