We help IT Professionals succeed at work.

NAS issue

linuxperson
linuxperson asked
on
~ # esxcli storage nfs list
Volume Name  Host          Share       Accessible  Mounted  Read-Only  Hardware Acceleration
-----------  ------------  ----------  ----------  -------  ---------  ---------------------
NAS          192.168.1.10  /mnt/HD_a2       false     true      false  Unknown

I am trying to restart the service associated with NAS on ESXi 5.5
Comment
Watch Question

Andrew Hancock (VMware vExpert / EE Fellow)VMware and Virtualization Consultant
Fellow 2018
Expert of the Year 2017

Commented:
Remove the data store.

Author

Commented:
/var/log # esxcli storage nfs remove -v NAS
Sysinfo error on operation returned status : Busy. Please see the VMkernel log for detailed error information


2015-02-27T15:52:14.964Z cpu1:1145457 opID=5efc6c60)World: 14299: VC opID hostd-9d3b maps to vmkernel opID 5efc6c60
2015-02-27T15:52:14.973Z cpu4:1145689 opID=4f78f26d)World: 14299: VC opID hostd-aadb maps to vmkernel opID 4f78f26d
2015-02-27T15:52:14.973Z cpu4:1145689 opID=4f78f26d)WARNING: NFS: 1921: NAS has open files, cannot be unmounted
2015-02-27T15:52:14.978Z cpu1:1145461)<3>ata1.00: bad CDB len=16, scsi_op=0x9e, max=12
2015-02-27T15:52:14.984Z cpu1:1145461)<3>ata1.00: bad CDB len=16, scsi_op=0x9e, max=12
2015-02-27T15:52:14.993Z cpu0:1145461)<3>ata1.00: bad CDB len=16, scsi_op=0x9e, max=12
2015-02-27T15:52:14.997Z cpu3:1145461)<3>ata1.00: bad CDB len=16, scsi_op=0x9e, max=12
2015-02-27T15:52:15.000Z cpu3:1145461)<3>ata1.00: bad CDB len=16, scsi_op=0x9e, max=12
2015-02-27T15:52:15.004Z cpu3:1145461)<3>ata1.00: bad CDB len=16, scsi_op=0x9e, max=12
2015-02-27T15:52:15.007Z cpu3:1145461)<3>ata1.00: bad CDB len=16, scsi_op=0x9e, max=12
2015-02-27T15:52:15.010Z cpu3:1145461)<3>ata1.00: bad CDB len=16, scsi_op=0x9e, max=12
2015-02-27T15:52:15.016Z cpu3:1145461)FSS: 5091: No FS driver claimed device 'mpx.vmhba0:C0:T0:L0': Not supported
2015-02-27T15:52:15.018Z cpu3:1145461)Vol3: 716: Couldn't read volume header from control: Not supported
2015-02-27T15:52:15.018Z cpu3:1145461)Vol3: 716: Couldn't read volume header fro
2015-02-27T15:52:15.018Z cpu3:1145461)FSS: 5091: No FS driver claimed device 'co
2015-02-27T15:52:15.042Z cpu3:1145461)FSS: 5091: No FS driver claimed device 'mp
2015-02-27T15:52:15.048Z cpu3:1145461)VC: 2059: Device rescan time 18 msec (tota
2015-02-27T15:52:15.048Z cpu3:1145461)VC: 2062: Filesystem probe time 54 msec (d
2015-02-27T15:52:15.048Z cpu3:1145461)VC: 2064: Refresh open volume time 0 msec
2015-02-27T15:52:15.048Z cpu7:1145446)World: 14299: VC opID hostd-9d3b maps to v
2015-02-27T15:52:15.052Z cpu3:1145461)<3>ata1.00: bad CDB len=16, scsi_op=0x9e,
2015-02-27T15:52:15.061Z cpu3:1145461)<3>ata1.00: bad CDB len=16, scsi_op=0x9e,
2015-02-27T15:52:15.069Z cpu3:1145461)Vol3: 716: Couldn't read volume header fro
2015-02-27T15:52:15.069Z cpu3:1145461)Vol3: 716: Couldn't read volume header fro
2015-02-27T15:52:15.069Z cpu3:1145461)FSS: 5091: No FS driver claimed device 'co
2015-02-27T15:52:15.093Z cpu3:1145461)FSS: 5091: No FS driver claimed device 'mp
2015-02-27T15:52:15.095Z cpu3:1145461)<3>ata1.00: bad CDB len=16, scsi_op=0x9e,
2015-02-27T15:52:15.098Z cpu3:1145461)<3>ata1.00: bad CDB len=16, scsi_op=0x9e,
2015-02-27T15:52:15.101Z cpu3:1145461)<3>ata1.00: bad CDB len=16, scsi_op=0x9e,
2015-02-27T15:52:15.104Z cpu3:1145461)<3>ata1.00: bad CDB len=16, scsi_op=0x9e,
2015-02-27T15:52:15.107Z cpu3:1145461)<3>ata1.00: bad CDB len=16, scsi_op=0x9e,
2015-02-27T15:52:15.110Z cpu3:1145461)<3>ata1.00: bad CDB len=16, scsi_op=0x9e,
2015-02-27T15:52:15.116Z cpu3:1145461)FSS: 5091: No FS driver claimed device 'mp
2015-02-27T15:52:15.117Z cpu3:1145461)VC: 2059: Device rescan time 15 msec (tota
2015-02-27T15:52:15.117Z cpu3:1145461)VC: 2062: Filesystem probe time 51 msec (d
2015-02-27T15:52:15.117Z cpu3:1145461)VC: 2064: Refresh open volume time 0 msec
Andrew Hancock (VMware vExpert / EE Fellow)VMware and Virtualization Consultant
Fellow 2018
Expert of the Year 2017

Commented:
Check there are no files in use or reboot the ESXi host server.

Also check your NAS is on the HCL.

Author

Commented:
HCL is fine other hosts are able to access.

I had this issue on two host. when I did reboot the other server, it came back.

I wonder is there any way to fix without rebooting.

/var/log # nc -z 192.168.1.10 2049
Connection to 192.168.1.10 2049 port [tcp/nfs] succeeded!
VMware and Virtualization Consultant
Fellow 2018
Expert of the Year 2017
Commented:
Check what is using the data store.

If files are in use it will not allow dismount.

Check via GUI will check and tell you what is in use.

Author

Commented:
thanks it works now.

some cd/dvd rom connected in few VMs.