2 Bronze

Expand Migrated MetaLUN

Jump to solution
Hi All,

I recently migrated a 6TB MetaLUN from FC disks to SATA II disks, with the view to expanding the LUN by another 5TB... The migration was successful however the metaLUN still shows as FC and won't allow me to select LUNS created from SATA II disks when I try to expand (concatenate).

This is on a CX3-80 running flarecode 26.

Thanks.
Labels (1)
0 Kudos
1 Solution

Accepted Solutions
6 Indium

Re: Expand Migrated MetaLUN

Jump to solution
You could try to restart the management server (http://<ip of SPA or B>/setup. Wait until the service is back up an restart the one on the other SP. This might help, but I'm not sure. It doesn't hurt anyway, since restarting the mgmt server can be done online.

View solution in original post

0 Kudos
4 Replies
4 Ruthenium

Re: Expand Migrated MetaLUN

Jump to solution
If you are using the same Navisphere session that was used to perform the migration, it could be that the session is not updating properly. Try closing the browser and starting a new Navisphere session. Also have you checked the metaLUN properties in the CLI?

naviseccli -h [array ip address] getlun [lun number]
0 Kudos
2 Bronze

Re: Expand Migrated MetaLUN

Jump to solution
Restarting the browser does not change the behaviour.
naviseccli does not provide particularly useful information for the metalun.
using the CLI to perform the expand I get the error...

Error: metalun -expand command failed.
The drive type (SATA/FC) of all LUNs must be same within a metaLUN.


despite the fact that all existing disks in the meta are SATA II and those that I am trying to add are also SATA II... only the metaLUN show that it is FC (not the components)
0 Kudos
5 Rhenium

Re: Expand Migrated MetaLUN

Jump to solution
I would suggest that you open a call with EMC - when you migrate a LUN, some of the LUN identities are kept so that the host still sees the LUN as the same - even if you change the raid type, the original will still be seen by the host.

glen
6 Indium

Re: Expand Migrated MetaLUN

Jump to solution
You could try to restart the management server (http://<ip of SPA or B>/setup. Wait until the service is back up an restart the one on the other SP. This might help, but I'm not sure. It doesn't hurt anyway, since restarting the mgmt server can be done online.

View solution in original post

0 Kudos