1) PowerPath 3.0 is quote old now and you may need to run a "powercf -q" followed by "powermt config" to correctly integrate new devices.
2) Do you have a Celerra on your site? Has this "new" disk been previously used by the Celerra? If so, the Celerra signature may still be present on the disk and PowerPath will "hide" it from the host OS. To check whether this is the case, run "powerprotect format" and see if its visible then. If it is - you may need to have the volume VTOC'd (formatted) from the Symm to clear the Celerra signature which is at the end of the volume.
We're using a striped metadevice where the last three disks out of this metadevice used to be mapped to a Celerra.
I've created a new metadevice with the last three devices now being the first three and a couple of other volumes, which have always been FBA devices, attached to it.
After a reboot -- -rv, a powercf -i, powermt config and a powermt save the emcpower device is working fine.
So might this Celerra VTOC label on the end of the last volume on this metadevice been the problem.
Good to hear its sorted. It was almost certainly the Celerra label issue. If you have this again, refer the support lab to Knowledgebase article emc90082 for details on how to remove the Celerra signature.
Another option is to have your CE VTOC the affected volumes.
MarcT2
2 Intern
•
131 Posts
1
March 8th, 2007 07:00
Two things you could try.
1) PowerPath 3.0 is quote old now and you may need to run a "powercf -q" followed by "powermt config" to correctly integrate new devices.
2) Do you have a Celerra on your site? Has this "new" disk been previously used by the Celerra? If so, the Celerra signature may still be present on the disk and PowerPath will "hide" it from the host OS. To check whether this is the case, run "powerprotect format" and see if its visible then. If it is - you may need to have the volume VTOC'd (formatted) from the Symm to clear the Celerra signature which is at the end of the volume.
Best Regards,
Marc
Kiran3
410 Posts
0
March 8th, 2007 18:00
jgrinwis
1 Rookie
•
99 Posts
0
March 9th, 2007 05:00
I've created a new metadevice with the last three devices now being the first three and a couple of other volumes, which have always been FBA devices, attached to it.
After a reboot -- -rv, a powercf -i, powermt config and a powermt save the emcpower device is working fine.
So might this Celerra VTOC label on the end of the last volume on this metadevice been the problem.
MarcT2
2 Intern
•
131 Posts
0
March 9th, 2007 05:00
Good to hear its sorted. It was almost certainly the Celerra label issue.
If you have this again, refer the support lab to Knowledgebase article emc90082 for details on how to remove the Celerra signature.
Another option is to have your CE VTOC the affected volumes.
Best Regards,
Marc