so you ran the command above and the disk is still listed when you run nas_disk -l 

exactly.

Hi, thank you for your answer.

I forgot  to include some steps already realized, I ran this command but the message after press enter, was you can delete this disk because has a vol allocation, So I tried to delete the volume, and the message was the volume belongs to a storage group, but the storage goup ~fileserver does not allow me delete anything.

Any other suggestions?

Thank you in advance.

nas_disk -delete -perm -unbind

No, that´s is the case, I believe, because I dont have any file system created.

no, is listed with "y".

That means it’s still in use ..did you create any file systems ?

That disk is listed with an “n” in the inuse column ?

can you paste output from "nas_fs -l"

[nasadmin@vnxfsql ~]$ nas_fs -l

id      inuse type acl   volume    name                server

1         n    1   0     10        root_fs_1

2         y    1   0     40        root_fs_common      1,2

3         n    5   0     73        root_fs_ufslog

5         n    5   0     93        root_fs_d3

6         n    5   0     94        root_fs_d4

7         n    5   0     95        root_fs_d5

8         n    5   0     96        root_fs_d6

9         y    1   0     12        root_fs_2           1

13        y    1   0     14        root_fs_3           2

17        n    5   0     110       root_panic_reserve

run this, it should tell us what file system(s) reside on each dvol

/nas/tools/whereisfs -ld

this is odd ..can you paste output from "nas_disk -l"

[nasadmin@vnxfsql ~]$ /nas/tools/whereisfs -ld

No Symmetrixes on the backend

No user filesystems on Clariion APM00112000979

[nasadmin@vnxfsql ~]$ nas_disk -l

id   inuse  sizeMB    storageID-devID   type  name          servers

1     y      11260  APM00112000979-2007 CLSTD root_disk     1,2

2     y      11260  APM00112000979-2008 CLSTD root_ldisk    1,2

3     y       2038  APM00112000979-2009 CLSTD d3            1,2

4     y       2038  APM00112000979-200A CLSTD d4            1,2

5     y       2044  APM00112000979-200B CLSTD d5            1,2

6     y      65526  APM00112000979-200C CLSTD d6            1,2

7     n     257242  APM00112000979-0010 CLSAS d7            1,2

8     n     257242  APM00112000979-0011 CLSAS d8            1,2

9     y      10239  APM00112000979-0034 CLATA d9            1,2

10    y      10239  APM00112000979-005C CLATA d10           1,2

are these datamovers in production ? Any chance you could schedule a failover and failback ?