How to change access on target from Read Only

Windows iSCSI SAN, Linux iSCSI SAN, Mac OS X iSCSI SAN and Virtual Native SAN.
Post Reply
dean1952
Posts: 3
Joined: Thu Jul 29, 2010 1:51 pm

How to change access on target from Read Only

Post by dean1952 » Fri Jul 30, 2010 8:35 am

Using a share on WinServer 2003 as a target from another server. (Share is an empty disk)
Initiator (under "Targets") has Access setting "read only"

Receiving error message on vSphere console when attempting to add the share as new storage on ESXi 4 server:

Call "HostDatastoreSystem.CreateVmfsDatastore" for object "ha-datastoresystem" on ESXi "cma-xen" failed.

No other diagnostic data is displayed or logged. Is it possible that this is an authority issue? Under which user/authority are writes executed? (Do I need to have an Active Directory userid for the target server included in the iStorage user & group containers?)

I've verified the CHAP settings.

thanks for any help.

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

Re: How to change access on target from Read Only

Post by Olivia (staff) » Sun Aug 01, 2010 9:29 pm

Which version are you using?
1.x:
do you have add the log-on use to a group and select the group to "Read Write Groups" of your target? You can modify target settings by:
right click on the target node item in the left tree, and then select Edit Target.
2.x:
Just create a full-access group and add this use to the group the target should be inherit from global authorization mode; or add a group which hold the user to target's CHAP page, the target should not be inherit from global authorization mode.
KernSafe Support Team
iSCSI SAN, iSCSI Target, iSCSI initiator and related technological support.
[email protected]

dean1952
Posts: 3
Joined: Thu Jul 29, 2010 1:51 pm

Re: How to change access on target from Read Only

Post by dean1952 » Mon Aug 02, 2010 7:06 am

The r/w access problem was caused by an authentication error.
I added a local user account to the the server where the target disk array is attached and added this user to a group with read/write access to the array.
This eliminated the read/only problem.

Post Reply