"Incorrect Function" when Initializing a iSCSI Target

I had it connecting to the wrong controller.

Thanks!

Hi, i don't know if is correct to expand this question, but it's quite a bit related with my problem.

My Disk array is a MD3620f (fiber).

I'm with the same problem of the incorrect function when initializing a disk on Windows Disk Management. I've changed the connection to the right controller and the initialization error disappeared, but when i try to create an partition on the initialized disk i shows a popup that says: "The parameter is incorrect".

The same disk mapped to a linux machine works fine, no errors.

The intention was to connect the windows machine on a fiber switch in witch happens to be connect the md3620f and a tape library TL4000. For test purpose i've connected the machine directly to the controller port and the result was the same.

By the way, sorry for my bad english.

Thanks for any attention.

Brosig

Hello Brosig,

When you are trying to partition the virtual disk from the windows host has the virtual disk finished initializing in MDSM? Also does the host have access to both controllers on the MD3620f or does it only have access to a single controller?

You also stated that the same virtual disk is mapped to a linux machine & it works, are you trying to have both the linux host & the windows host have access to the same virtual disk at the same time? Here is a link to the administrator guide for your MD3620f & if you look on page 90 it explains storage partitioning. ftp://ftp.dell.com/Manuals/Common/powervault-md3200_Administrator%20Guide_en-us.pdf

Please let us know if you have any other questions.

Hi Sam,
Thanks for your time.
When i've tried to partition the disk it was already initialized be de MDSM.
On this moment the Host has access to both controllers, but i've tried in several forms. Host directly connected to controller 0, Host directly connected to controller 1, host connected to fiber switch and both controllers connected to the fiber switch, and so on.

On this moment the configuration is this:

About the mapping: the idea with one of the virtual disks is to make it available to one HostGroup, so i can use it with different servers and with the machine responsible for backup on tape. Reading the Administrator Guide i've seen no reference of limitations based on different Operating Systems on the same group, i'm right?

As my configuration was not working, i've tried to map two Virtual Disks to different machines. The one on Windows host have the problem that avoid me to partition/format it, the one on linux host has no problems.

For tests purposes, i've switched the mapping. The virtual disk partitioned on the linux host became visible on the windows host (after a reboot of the host) but i'm still not able to format it.

Another thing that is happening is that with both controllers connected on the fiber switch the virtual disks becomes visible twice, although the MDSM displays an alert warning that the Virtual Disk Not on Preferred Path:

It appears to me that some configuration is missing on the windows host, but i'm not able to find any reference of it on the Manuals.

Again, thanks for your time

Brosig

Sorry, a just found the reference of Hosts Operating Systems:

"All hosts in a host group must have the same host type (operating system). In addition, all hosts in the host group must

have special software, such as clustering software, to manage virtual disk sharing and accessibility." pg. 57

But still, on a single Windows host i don't figure out how to make it work.