For this to work, caa, poolfs and solid db has to be accessable.
Using rmdbsp command for SSP: Example: $ lsmap -all SVSA Physloc Client Partition ID --------------- -------------------------------------------- ------------------ vhost0 U7778.23X.06BC7DA-V1-C11 0x00000002 VTD vtscsi0 Status Defined LUN 0x8100000000000000 Backing device client_rtvg_vht0.626a8d2721a1c82ea6f249db71d2aa76 Physloc Mirrored N/A VTD vtscsi1 Status Available LUN 0x8200000000000000 Backing device rajtest_lu.b60808789896ce984d8de79768781c63 Physloc Mirrored N/A Commands: $ rmbdsp -vtd vtscsi0 -f $ rmbdsp -vtd vtscsi1 -f //////////////////////////////////////////// Below if accidently rmdev has been used //////////////////////////////////////////// For SSP so do not use any rmdev command available for vhost adapter. For SSP use the SSP commands to make sure they take care of the problem. ( Type rmbdsp for help ) Correct Sequence is Only: $ rmbdsp -sp-bd -f If rmdev -dev vhost has been used by accident then to cvorrect this: $ oem_setup_env # rm /var/vio/storagepools/fb_client_pool/aixsnd2_hdisk0 # rm /var/vio/storagepools/fb_client_pool/.aixsnd2_hdisk0