topic Re: MSA1000 problem in MSA Storage

MSA1000 problem

CA1096861 — Wed, 15 Mar 2006 04:10:54 GMT

HI
On our MSA1000 have I just created a new unit to use with our vmware ESX 2.5 server, but the ESX server can see the unit, the ACL ok.
The only thing that is difference from my other units is that this unit has a “Parity Init Status: waiting for first write” and I believe that is the problem.

Can any one help me?

Re: MSA1000 problem

Uwe Zessin — Wed, 15 Mar 2006 04:54:53 GMT

It's a "feature" :-(

For some reason I cannot understand, the MSA1000 does not start the parity initialization/ initial mirroring as soon as you create a logical disk. It rather waits until the host does the first write to the disk.

It should start working when you put a partition table and a VMFS on it.

Re: MSA1000 problem

CA1096861 — Wed, 15 Mar 2006 05:59:19 GMT

yes, but how can put a partition table and a VMFS on it, when my esx server can't see it.

Re: MSA1000 problem

Uwe Zessin — Wed, 15 Mar 2006 06:05:09 GMT

You need to scan for it. Assuming V2.5.2: e.g. in the MUI press the |_Options_| tab, then (Storage Management...) in the right column, then "Rescan SAN" (at the top of the new window).

Re: MSA1000 problem

CA1096861 — Wed, 15 Mar 2006 06:09:39 GMT

Yes I now, but it dose not find the disk, that is my problem

Re: MSA1000 problem

Uwe Zessin — Wed, 15 Mar 2006 06:15:21 GMT

If you write "new unit", I assume that the VMware ESX server already uses storage on the MSA1000?

It is sometimes necessary to scan a second time or even reboot the system :-(
Another potential problem is when the LUN address is too high. By default, the ESX server only scans LUNs 0..7.

In the MUI it is |_Options_|, (Advanced Settings...). The parameter name is "Disk.MaxLUN". Don't set it too high unless you really need it, because this slows down the boot time.