Login to iSCSI target succeeds, but it is not mounted

Completely free iSCSI initiator software for Mac OS X.
Post Reply
Windfisch
Posts: 1
Joined: Sun Nov 25, 2018 4:45 am

Login to iSCSI target succeeds, but it is not mounted

Post by Windfisch » Sun Nov 25, 2018 4:48 am

I just installed KernSafe iSCSI Initiator on my MacBook Pro which runs macOS Mojave. The install worked fine, I had to manually allow the extension to be installed but it seemed to work. I can login to my iSCSI target, but no message pops up asking me to format the new disk, and when doing sudo diskutil list, no disk shows up.

What am I missing? Or is it currently not compatible with macOS Mojave?

Olivia (staff)
Posts: 205
Joined: Thu Nov 05, 2009 5:52 pm
Contact:

Re: Login to iSCSI target succeeds, but it is not mounted

Post by Olivia (staff) » Sun Jan 06, 2019 7:10 pm

We have resolved the issue in the new version 3.00, if anyone still have the issue, please report to us.
KernSafe Support Team
iSCSI SAN, iSCSI Target, iSCSI initiator and related technological support.
[email protected]

christancho
Posts: 1
Joined: Tue Jan 15, 2019 5:16 pm

Re: Login to iSCSI target succeeds, but it is not mounted

Post by christancho » Tue Jan 15, 2019 5:20 pm

Hi,
I'm having the same issue. I'm running iSCSI Initiator X 3.00 (1600) with macOS Mojave (10.14.2).
I have the target on "Logged On" status, but the disk utility does not recognize/view the new drive.

Am I missing something?
Thanks
Chris.

Olivia (staff)
Posts: 205
Joined: Thu Nov 05, 2009 5:52 pm
Contact:

Re: Login to iSCSI target succeeds, but it is not mounted

Post by Olivia (staff) » Thu Jan 17, 2019 12:46 am

Please follow these steps to ensure the previous version kernel module has been removed:
1. Launch terminal and run the command sudo rm -rf /System/Library/Extensions/KScsiPrt.kext
2. Reboot your machine.

Reinstall 3.0 again and try.
KernSafe Support Team
iSCSI SAN, iSCSI Target, iSCSI initiator and related technological support.
[email protected]

venanx
Posts: 1
Joined: Mon Jan 28, 2019 5:28 pm

Re: Login to iSCSI target succeeds, but it is not mounted

Post by venanx » Mon Jan 28, 2019 5:30 pm

Same problem here...MacOs Mojave - 10.14.2

demonzh
Posts: 2
Joined: Fri Oct 05, 2018 10:34 pm

Re: Login to iSCSI target succeeds, but it is not mounted

Post by demonzh » Mon Jan 28, 2019 11:07 pm

problem is still

mojave 10.14.3
kernsafe 3.0


I have tried the solution, but does't work

Olivia (staff)
Posts: 205
Joined: Thu Nov 05, 2009 5:52 pm
Contact:

Re: Login to iSCSI target succeeds, but it is not mounted

Post by Olivia (staff) » Wed Jan 30, 2019 5:41 am

KernSafe Support Team
iSCSI SAN, iSCSI Target, iSCSI initiator and related technological support.
[email protected]

tommasodangelo
Posts: 2
Joined: Sat Nov 23, 2019 9:13 am

Re: Login to iSCSI target succeeds, but it is not mounted

Post by tommasodangelo » Sat Nov 23, 2019 9:16 am

Hi, I have the same problem too. I have properly configured the iSCSI Initiator X and logged on. I created the target in the NAS and mapped the LUN. In the disk utility of the iMac I see the volume but I can't activate it. My nas is QNAP TS-832X with QTS 4.4.1.1101 operating system. My computer is the 2017 iMac 5k with High Sierra operating system. I tried the suggestions described above but they didn't work for me.

agtoever
Posts: 1
Joined: Mon Mar 30, 2020 12:33 am

Re: Login to iSCSI target succeeds, but it is not mounted

Post by agtoever » Mon Mar 30, 2020 1:26 am

I have the same problem.

- Target: Debian 10.3 with tgt 1.0.74-1
- Client: OSX Catalina (10.15.4)
- KernSafe iSCSI Initiator 3.20

Confirmed total uninstall of Kernsafe application and kext. Clean install of version 3.20. Confirmed kext version.

Target is discovered in the Initiator and logon is successfull. Logon confirmed on iSCSI Initiator and on the target:

Code: Select all

>> sudo tgtadm --mode conn --op show --tid 2
Session: 4
    Connection: 1
        Initiator: iqn.2006-03.com.kernsafe:mac-initiator
        IP Address: 192.168.67.35
But the target is not visible in DiskUtil (not in the GUI, nor in the Terminal).
I can successfully connect to the target from Win 10.

Please advise and thanks for your time.

Post Reply