NOTICE: vxvm: unexpected status on close

Cause

Every time the system boots (or is shut down), the message is displayed on the
console. Sometimes the following message is also displayed on the console and in
the /var/adm/messages file:
WARNING:
/iommu@0,10000000/sbus@0,10001000/SUNW,soc@2,0/SUNW,pln@a0000000,74127a/ssd@4,2
(ssd22):
Error for Command: <undecoded cmd 0x35> Error Level: Fatal
Requested Block: 0 Error Block: 0
Vendor: CONNER Serial Number: 93081LPT
Sense Key: Aborted Command
ASC: 0xb3 (<vendor unique code 0xb3>), ASCQ: 0x0, FRU: 0x0
WARNING:
/iommu@0,10000000/sbus@0,10001000/SUNW,soc@2,0/SUNW,pln@a0000000,74127a/ssd@4,2
(ssd22): ssd_synchronize_cache failed (5)

Action
In a High Availability system with NVRAM, this error would be caused by
unprocessed data in a NVRAM cache of the active logical host that has been down
and started again later. Because of the possibility of error, NVRAM should not be
used in an HA system. The problem can be solved in this case by removing the
NVRAM on the HA system.
In a non-HA system, this error can also be caused by stale data in the NVRAM
cache. (The example commands that follow assume the controller for the array is c1.)
To fix for a non-HA system:
1. Turn off all fast writes on this array and sync any remaining pending writes:
# ssaadm fast_write -d c1
# ssaadm sync_cache c1
2. When you sync the fast writes to the array, all pending writes are physically made
to the disks. Anything that is left in the cache is stale; thus, it is safe to purge it.
Run this command:
# ssaadm purge c1

3. Turn on the fast writes for the disks. This command might be different on your
system, depending on the disks where you want fast writes enabled and the types
of fast writes you want:
# ssaadm fast_write -s -e c1