Nas_checkup fails with "Checking if Symapi data is present"

Hello!

I've created volumes with Disk provisioning wizard for file, then I tried to create file system. This process failed with error. No file system was in Unisphere, but nas_fs showed existance of it. I tried to create other fs, but it failed too. Then I deleted fs and ran checkup. It said:

-------------------------------------Errors------------------------------------- Control Station: Check if Symapi data is present Error HC_CS_14505082907: CKM00121900434 d8, no storage API data          available Action :          1. If the symptom above specifies a Storage System, the issue is             probably one of connectivity.             a. Run command "/nas/sbin/setup_clariion ".             b. Run command "/nas/bin/nas_storage -check -all" to verify that                the problem has been resolved.             c. If the problem persists, escalate this issue through your                support organization. Provide this output and any errors                received from the above procedure in the escalation.          2. If the symptom above specifies an individual disk, you may have an             orphaned disk volume -- a disk volume that is in the NASDB, but             does not actually exist on the storage system.             a. Determine which LUN this disk corresponds to:                 - Run command"/nas/bin/nas_disk -l"                 - Find the devID for that disk in the output. For example, if                   this line is the output for d41: "41 n 2047 F60005200268-0038                   CLSTD d41 1,2" then d41 has a devID of 0038)                 - Convert the devID which is in hex, to decimal. For example,                   0x38 = (3 * 16) + 8 = 56             b. Check the /nas/log/symapi.log for a message similar to:                "c_clar_dev_show: - : ".             c. If you find such a message, verify that the LUN exists on the                Storage System. To do this, you can either use Navisphere, or                run command "/nas/sbin/navicli -h getlun                ". If the LUN exists, navicli will return information. If                it does not exist, it will return a message similar to: "Error:                getlun command failed Invalid LUN number LUN does not exist"             d. Check for the LUN on both SPA and SPB. If the LUN doesn't exist                on either SP, you have an orphaned disk volume.             e. Confirm that you found the right disk by running command                "/nas/bin/nas_disk -info -o all" (note that                "all" does not have a hyphen in front of it). If you get a                message like "Error 3501: Storage API code=7:                SYMAPI_C_DEVICE_NOT_FOUND", then you have found the                orphaned disk.             f. Verify from the "/nas/bin/nas_disk -list" output that the disk                is not in use. If the disk is in use, escalate this issue                through your support organization. Provide this output and any                output from commands done during this procedure in the                escalation.             g. If this is the correct disk, and it is not in use, delete it                with command "/nas/bin/nas_disk -delete".             h. Run command "/nas/bin/nas_storage -check -all" to verify that                the problem has been resolved.             i. If the problem persists, escalate this issue through your                support organization. Provide this output and any output from                commands done during the above procedure in the escalation. --------------------------------------------------------------------------------

It is solution, but the problem is that disk d8 is used by v111 volume (meta), which is used by clarata_r6 (system) pool. And we know, that we cannot delete system pools.

I'm stuck.

Please, help! Thanks.

PS.

nas_version  7.1.55-3, upgraded from 7.0...