A fixed vxvm-startup2 script was first provided in the following versions of VxVM

SPARC: 5.0MP3RP1HF12 (also included in 5.0MP3RP2 and later)
x86_64: 5.0MP3RP3HF2

Note the following entry in the patch README files:

(e1589881) Dump device was changed to none (dumps disabled) after encapsulating a boot disk.

With the revised startup script in place the following messages are seen during boot disk encapsulation and subsequent boot:

During encapsulation:

Hostname: utslabmro6
VxVM vxvm-startup2 INFO V-5-2-503 VxVM general startup...
 VxVM vxvm-reconfig INFO V-5-2-324 The Volume Manager is now reconfiguring (partition phase)...
 VxVM vxvm-reconfig INFO V-5-2-499 Volume Manager: Partitioning c1t0d0 as an encapsulated disk.
/dev/dsk/c1t0d0s1 was dump device --
invoking dumpadm(1M) -d swap to select new dump device
 VxVM vxvm-reconfig INFO V-5-2-323 The Volume Manager is now reconfiguring (initialization phase)...
 VxVM vxvm-reconfig INFO V-5-2-497 Volume Manager: Adding rootdg01 (c1t0d0) as an encapsulated disk.
VxVM vxcap-vol INFO V-5-2-89 Adding volumes for c1t0d0...
Starting new volumes...
VxVM vxcap-vol INFO V-5-2-444 Updating /etc/vfstab...
Remove encapsulated partitions...

VxVM vxroot INFO V-5-2-328 The Volume Manager will now set up your Boot Disk as a managed disk.
VxVM vxroot INFO V-5-2-290 Saving original configuration...
16 blocks
 VxVM vxvm-reconfig NOTICE V-5-2-393 The system will now be rebooted.
syncing file systems... done
rebooting...

During boot:

VxVM vxvm-startup2 INFO V-5-2-503 VxVM general startup...
VxVM vxvm-startup2 INFO V-5-2-3619 Setting partition /dev/dsk/c1t0d0s1 as the dump device.

Now, on logging back into the system we can see that the dump device has been configured correctly:

utslabmro6:ksh# dumpadm
     Dump content: kernel pages
      Dump device: /dev/dsk/c1t0d0s1 (swap)
Savecore directory: /var/crash/utslabmro6
 Savecore enabled: yes

Note that if a customer has already encapsulated their boot disk whilst using the defective vxvm-startup2 they should ensure that the dump device has  been set to a valid slice manually using the dumpadm command:

root@pnd1# dumpadm -d /dev/dsk/c0t0d0s1
     Dump content: kernel pages
      Dump device: /dev/dsk/c0t0d0s1 (swap)
Savecore directory: /var/crash/pnd1
 Savecore enabled: yes

For further information see etrack incident e1589881
 

Volume Manager 5.0MP3 ships with a defective vxvm-startup2 script (/lib/svc/method/vxvm-startup2 on Solaris 10, /etc/init.d/vxvm-startup2 on Solaris  8/9) which is unable to configure a valid dump device during and after encapsulation of a boot disk.

If the defective script is in use during encapsulation the following messages will be seen during boot disk encapsulation and when the script is run  during subsequent boots:

Encapsulation:

VxVM vxroot INFO V-5-2-328 The Volume Manager will now set up your Boot Disk as a managed disk.
VxVM vxroot INFO V-5-2-290 Saving original configuration...
16 blocks
 VxVM vxvm-reconfig NOTICE V-5-2-393 The system will now be rebooted.
syncing file systems... done
rebooting...

During boot:

savecore: no dump device configured  
savecore: no dump device configured
Jun  9 12:13:04 utslabmro6 savecore: no dump device configured
dumpadm: no swap devices could be configured as the dump device

On logging back into the system dumpadm shows that no dump device has been configured, and as such system dumps are disabled. This means that a crash  dump will NOT be collected in the event of system panic:

utslabmro6:ksh# dumpadm
     Dump content: kernel pages
      Dump device: none (dumps disabled)  <-- No dump device configured.
Savecore directory: /var/crash/utslabmro6
 Savecore enabled: yes
utslabmro6:ksh#