Read Only

Completely free iSCSI initiator software for Mac OS X.
Post Reply
Rusty
Posts: 4
Joined: Tue Aug 30, 2016 12:33 am

Read Only

Post by Rusty » Tue Aug 30, 2016 12:36 am

I have connected to an iSCSI target but I only have read access. Does anyone know why this happens?

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

Re: Read Only

Post by Olivia (staff) » Wed Aug 31, 2016 11:11 pm

Which brand of target are you using? Please check permissions.
KernSafe Support Team
iSCSI SAN, iSCSI Target, iSCSI initiator and related technological support.
[email protected]

Rusty
Posts: 4
Joined: Tue Aug 30, 2016 12:33 am

Re: Read Only

Post by Rusty » Wed Aug 31, 2016 11:20 pm

Hi Olivia,

The Target is on a WDMyCloudEX4 NAS. It has CHAP authentication enabled, the permissions are pretty basic there is no way of configuring read on only access for the target.

I can connect to the target using the built in initiator on a Windows 10 machine using the same credentials and I can read/write to the target.

Thanks Olivia

genoso
Posts: 6
Joined: Thu Nov 03, 2016 2:10 pm

Re: Read Only

Post by genoso » Thu Nov 03, 2016 2:23 pm

Hi Olivia,

Same issue here with a WD EX2 NAS as target. I am using CHAP authentication and in Windows 10 I get full access but on my Mac, using KernSafe iSCSI Initiator X, I get just read only access.

I am using 2.20 version on Mac OS Sierra 10.12.1

BR

genoso
Posts: 6
Joined: Thu Nov 03, 2016 2:10 pm

Re: Read Only

Post by genoso » Fri Nov 04, 2016 3:10 pm

Hi,

I just realized, in my case, and probably in rest of people suffering this issue, was not related to KernSafe SW but due to Mac OS NTFS file system read only limitation.

I have confirmed if system has other file system it will get full write access!

BR

Rusty
Posts: 4
Joined: Tue Aug 30, 2016 12:33 am

Re: Read Only

Post by Rusty » Tue Nov 08, 2016 12:53 am

I am pretty sure the WD NAS Devices use a proprietary file system :?:

genoso
Posts: 6
Joined: Thu Nov 03, 2016 2:10 pm

Re: Read Only

Post by genoso » Tue Nov 08, 2016 7:55 am

Hi Rusty,

iSCSI target provides a Disk pseudo "physical" Connection towards initiator though IP network, andit is up to host running initiator to format and partition that hard disk.

In my case, I created a iSCSI unit on WD EX2 NAS and afterwards initiated it on a Windows system, from which I formatted it as NTFS. Later on, I mounted it into Mac OS Sierra and I showed already mentioned behavior.

If you want to get write/read access to the HD, use Disk Utility native application from Mac to format iSCSI unit once initiated, in the same way as you would do with an external USB HD pre-formatted in NTFS file system.

BR

Rusty
Posts: 4
Joined: Tue Aug 30, 2016 12:33 am

Re: Read Only

Post by Rusty » Wed Nov 09, 2016 12:51 am

Thanks BR, that makes perfect sense...
genoso wrote:use Disk Utility native application from Mac to format iSCSI unit once initiated
So if I understand correctly an iSCSI target cannot provide read/write access to MAC and Windows initiators, you have to choose a format?

That being the case, just out of curiosity, how do MAC computers handle using data on Shared folders on a Windows server? Does the same read only rule apply?

Cheers!

genoso
Posts: 6
Joined: Thu Nov 03, 2016 2:10 pm

Re: Read Only

Post by genoso » Wed Nov 09, 2016 11:09 am

Rusty wrote:Thanks BR, that makes perfect sense...

That being the case, just out of curiosity, how do MAC computers handle using data on Shared folders on a Windows server? Does the same read only rule apply?

Cheers!
Windows shared folders are supported by SAMBA protocol, which has nothing to do with iSCSI one.

SAMBA access control is handled by the server, being a layer over the file system underneath which is completely hidden to client host. It is equivalent to NFS for unix/linux systems or AFS (being deprecated ) for mac systems.

Hope this clarifies, if you want to dig into this subjects, you have plenty of information in the internet.

Post Reply