HI,
You've stated that the storage team did the migration of IBM Storage to Nimble storage, I'm guessing that that is where the problem lies. Or there could be issues with the vpath software and Nimble storage, does the Solaris version support Nimble?
I would have tackled this a different way;
- Added the new disk to the running system as normal.
- Extended the metadevice into a four way mirror.
- Remove the original disk.
- Recreate the metadb.
I'm not sure why you would attempt to do this using SAN replication, the only exception I would make is where you can replicate the device at a block level ensuring tha the boot block and everything else would come over.
You may get away with installing the boot block and re-labeling the disks, but I'd rather adopt the add the disks and extend the mirror approach.
Given the current situation, you may want to try the metarecover options to recover the individual devices.
Regards
Gull04
--- Post updated at 03:15 PM ---
Hi,
Just out of curiosity, have you made any required changes to /etc/vfstab - you don't mention it.
Regards
Gull04