Quantcast
Channel: VMware Communities : Discussion List - VMware ESXi 5
Viewing all articles
Browse latest Browse all 20614

ESXi5 datastore not mount

$
0
0

Hi All,

 

 

I cannot get my datastore mount after ESX server restart, below is the error msg from kernel log.

 

 

2013-03-20T19:00:42.646Z cpu0:2651)<3>ata3.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x0
2013-03-20T19:00:42.646Z cpu0:2651)<3>ata3.00: irq_stat 0x40000008
2013-03-20T19:00:42.646Z cpu0:2651)<3>ata3.00: cmd 60/08:00:60:a9:00/00:00:00:00:00/40 tag 0 ncq 4096 in
         res 41/40:00:60:a9:00/89:00:00:00:00/40 Emask 0x409 (media error) <F>
2013-03-20T19:00:42.646Z cpu0:2651)<3>ata3.00: status: { DRDY ERR }
2013-03-20T19:00:42.646Z cpu0:2651)<3>ata3.00: error: { UNC }
2013-03-20T19:00:42.652Z cpu0:2651)<6>ata3.00: configured for UDMA/133
2013-03-20T19:00:42.652Z cpu0:2651)<6>ata3: EH complete
2013-03-20T19:00:42.652Z cpu1:2049)ScsiDeviceIO: 2316: Cmd(0x4124007c98c0) 0x28, CmdSN 0x17 to dev "t10.ATA_____WDC_WD10EARS2D00MVWB0_________________________WD2DWMAZA0512584" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x3 0x11 0x4.
2013-03-20T19:00:42.652Z cpu0:2860)FS3Misc: 1440: Long VMFS3 rsv time on 'WD0' (held for 2907 msecs). # R: 0, # W: 0 bytesXfer: 0 sectors
2013-03-20T19:00:42.653Z cpu0:2860)WARNING: HBX: 1889: Failed to initialize VMFS3 distributed locking on volume 4f48a73b-19854499-46ae-14dae9991e03: I/O error
2013-03-20T19:00:42.773Z cpu1:2860)FSS: 4333: No FS driver claimed device '4f48a72e-1a0cba3b-1667-14dae9991e03': Not supported
2013-03-20T19:00:42.773Z cpu1:2860)LVM: 12007: Failed to mount 4f48a72e-1a0cba3b-1667-14dae9991e03 (now umounting): Not supported

 

 

Anyone can help!


Viewing all articles
Browse latest Browse all 20614

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>