"HostDatastoreSystem.CreateVmfsDatastore" for object "ha-datastoresystem" when adding drive to datas

B

balance101

Limp Gawd
Joined
Jan 31, 2008
Messages
411
I'm getting the following error when I try to add a wd 250 gb drive to datastores. I had a power issues today. System lost power for a second because someone accidentally pull the plug. After reboot, my wd 250gb was drop out of my datastores while my ssd m4 64gb was fine and running. I try putting it back but no success. So I ended up removing the drive and formatting it on another machine. When I try to added it it the error.



I deleted all reference to the datastore (vm that was pointing to datastore / cd iso to datastore) the datastore name seems to be gone. I try adding another ssd to datastore and no problem, haven't found another mechanical drive to try yet. I'm just wondering if this is a logic error, I didnt unmount/detach the drive properly and its causing error?



thanks



Call "HostDatastoreSystem.CreateVmfsDatastore" for object "ha-datastoresystem" on ESXi "xxxxxx" failed.

Operation failed, diagnostics report: Unable to create Filesystem, please see VMkernel log for more details: Failed to check for existing file system on device '/vmfs/devices/disks/t10.ATA_____WDC_WD2500BEVS2D75UST0________________________WD2DWXE708ET7359:1'.
 
from vmkernel.log

2016-03-05T00:05:46.287Z cpu1:33354)<3>ata5.00: exception Emask 0x0 SAct 0x3 SErr 0x0 action 0x0

2016-03-05T00:05:46.287Z cpu1:33354)<3>ata5.00: irq_stat 0x40000008

2016-03-05T00:05:46.287Z cpu1:33354)<3>ata5.00: cmd 60/08:00:78:ab:00/00:00:00:00:00/40 tag 0 ncq 4096 in

res 41/40:00:78:ab:00/50:00:00:00:00/40 Emask 0x409 (media error) <F>

2016-03-05T00:05:46.287Z cpu1:33354)<3>ata5.00: status: { DRDY ERR }

2016-03-05T00:05:46.287Z cpu1:33354)<3>ata5.00: error: { UNC }

2016-03-05T00:05:46.288Z cpu1:33354)<6>ata5.00: configured for UDMA/133

2016-03-05T00:05:46.288Z cpu1:33354)<6>ata5: EH complete

2016-03-05T00:05:46.288Z cpu17:32824)ScsiDeviceIO: 2651: Cmd(0x43a5ca1fa380) 0x28, CmdSN 0x17 from world 34819 to dev "t10.ATA_____WDC_WD2500BEVS2D75UST0________________________WD2DWXE708ET7359" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x3 0x11 0x4.

2016-03-05T00:05:46.288Z cpu17:32824)NMP: nmp_ThrottleLogForDevice:3286: Cmd 0x28 (0x43a5ca2ad040, 0) to dev "t10.ATA_____WDC_WD2500BEVS2D75UST0________________________WD2DWXE708ET7359" on path "vmhba36:C0:T0:L0" Failed: H:0x3 D:0x0 P:0x0 Possible sense$

2016-03-05T00:05:46.288Z cpu17:32824)WARNING: NMP: nmp_DeviceRequestFastDeviceProbe:237: NMP device "t10.ATA_____WDC_WD2500BEVS2D75UST0________________________WD2DWXE708ET7359" state in doubt; requested fast path state update...

2016-03-05T00:05:46.288Z cpu17:32824)ScsiDeviceIO: 2651: Cmd(0x43a5ca2ad040) 0x28, CmdSN 0x28b4 from world 0 to dev "t10.ATA_____WDC_WD2500BEVS2D75UST0________________________WD2DWXE708ET7359" failed H:0x3 D:0x0 P:0x0 Possible sense data: 0x0 0x0 0x0.

2016-03-05T00:05:46.289Z cpu20:34819)FS3Misc: 1759: Long VMFS rsv time on 'WD_250GB' (held for 4262 msecs). # R: 0, # W: 0 bytesXfer: 0 sectors

2016-03-05T00:05:46.289Z cpu12:37581)Partition: 426: Failed read for "t10.ATA_____WDC_WD2500BEVS2D75UST0________________________WD2DWXE708ET7359": I/O error

2016-03-05T00:05:46.289Z cpu12:37581)Partition: 1006: Failed to read protective mbr on "t10.ATA_____WDC_WD2500BEVS2D75UST0________________________WD2DWXE708ET7359" : I/O error

2016-03-05T00:05:46.289Z cpu12:37581)WARNING: Partition: 1157: Partition table read from device t10.ATA_____WDC_WD2500BEVS2D75UST0________________________WD2DWXE708ET7359 failed: I/O error

2016-03-05T00:05:46.289Z cpu20:34819)WARNING: HBX: 2240: Failed to initialize VMFS distributed locking on volume 567b68b9-9a4ca454-ad94-0025902d81ba: I/O error

2016-03-05T00:05:46.289Z cpu20:34819)Vol3: 3147: Failed to get object 28 type 1 uuid 567b68b9-9a4ca454-ad94-0025902d81ba FD 0 gen 0 :I/O error

2016-03-05T00:05:46.289Z cpu20:34819)WARNING: Fil3: 2469: Failed to reserve volume f530 28 1 567b68b9 9a4ca454 2500ad94 ba812d90 0 0 0 0 0 0 0

2016-03-05T00:05:46.289Z cpu20:34819)Vol3: 3147: Failed to get object 28 type 2 uuid 567b68b9-9a4ca454-ad94-0025902d81ba FD 4 gen 1 :I/O error

2016-03-05T00:05:50.559Z cpu1:33354)<3>ata5.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x0

2016-03-05T00:05:50.559Z cpu1:33354)<3>ata5.00: irq_stat 0x40000008

2016-03-05T00:05:50.559Z cpu1:33354)<3>ata5.00: cmd 60/08:00:78:ab:00/00:00:00:00:00/40 tag 0 ncq 4096 in

res 41/40:00:78:ab:00/50:00:00:00:00/40 Emask 0x409 (media error) <F>

2016-03-05T00:05:50.559Z cpu1:33354)<3>ata5.00: status: { DRDY ERR }

2016-03-05T00:05:50.559Z cpu1:33354)<3>ata5.00: error: { UNC }

2016-03-05T00:05:50.561Z cpu1:33354)<6>ata5.00: configured for UDMA/133

2016-03-05T00:05:50.561Z cpu1:33354)<6>ata5: EH complete

2016-03-05T00:05:50.561Z cpu13:32820)NMP: nmp_ThrottleLogForDevice:3286: Cmd 0x28 (0x43a5ca49b880, 34819) to dev "t10.ATA_____WDC_WD2500BEVS2D75UST0________________________WD2DWXE708ET7359" on path "vmhba36:C0:T0:L0" Failed: H:0x0 D:0x2 P:0x0 Valid sens$

2016-03-05T00:05:50.561Z cpu13:32820)ScsiDeviceIO: 2651: Cmd(0x43a5ca49b880) 0x28, CmdSN 0x17 from world 34819 to dev "t10.ATA_____WDC_WD2500BEVS2D75UST0________________________WD2DWXE708ET7359" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x3 0x11 0x4.

2016-03-05T00:05:50.562Z cpu20:34819)FS3Misc: 1759: Long VMFS rsv time on 'WD_250GB' (held for 3962 msecs). # R: 0, # W: 0 bytesXfer: 0 sectors

2016-03-05T00:05:50.562Z cpu20:34819)WARNING: HBX: 2240: Failed to initialize VMFS distributed locking on volume 567b68b9-9a4ca454-ad94-0025902d81ba: I/O error

2016-03-05T00:05:50.562Z cpu20:34819)Vol3: 3147: Failed to get object 28 type 1 uuid 567b68b9-9a4ca454-ad94-0025902d81ba FD 0 gen 0 :I/O error

2016-03-05T00:05:50.562Z cpu20:34819)WARNING: Fil3: 2469: Failed to reserve volume f530 28 1 567b68b9 9a4ca454 2500ad94 ba812d90 0 0 0 0 0 0 0

2016-03-05T00:05:50.562Z cpu20:34819)Vol3: 3147: Failed to get object 28 type 2 uuid 567b68b9-9a4ca454-ad94-0025902d81ba FD 4 gen 1 :I/O error

2016-03-05T00:05:54.854Z cpu1:33354)<3>ata5.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x0

2016-03-05T00:05:54.854Z cpu1:33354)<3>ata5.00: irq_stat 0x40000008

2016-03-05T00:05:54.854Z cpu1:33354)<3>ata5.00: cmd 60/08:00:78:ab:00/00:00:00:00:00/40 tag 0 ncq 4096 in

res 41/40:00:78:ab:00/50:00:00:00:00/40 Emask 0x409 (media error) <F>

2016-03-05T00:05:54.854Z cpu1:33354)<3>ata5.00: status: { DRDY ERR }

2016-03-05T00:05:54.854Z cpu1:33354)<3>ata5.00: error: { UNC }

2016-03-05T00:05:54.856Z cpu1:33354)<6>ata5.00: configured for UDMA/133

2016-03-05T00:05:54.856Z cpu1:33354)<6>ata5: EH complete

2016-03-05T00:05:54.856Z cpu14:32821)ScsiDeviceIO: 2651: Cmd(0x43a5c08c4300) 0x28, CmdSN 0x17 from world 34819 to dev "t10.ATA_____WDC_WD2500BEVS2D75UST0________________________WD2DWXE708ET7359" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x3 0x11 0x4.

2016-03-05T00:05:54.857Z cpu20:34819)FS3Misc: 1759: Long VMFS rsv time on 'WD_250GB' (held for 4118 msecs). # R: 0, # W: 0 bytesXfer: 0 sectors

2016-03-05T00:05:54.857Z cpu20:34819)WARNING: HBX: 2240: Failed to initialize VMFS distributed locking on volume 567b68b9-9a4ca454-ad94-0025902d81ba: I/O error

2016-03-05T00:05:54.857Z cpu20:34819)Vol3: 3147: Failed to get object 28 type 1 uuid 567b68b9-9a4ca454-ad94-0025902d81ba FD 0 gen 0 :I/O error

2016-03-05T00:05:54.857Z cpu20:34819)WARNING: Fil3: 2469: Failed to reserve volume f530 28 1 567b68b9 9a4ca454 2500ad94 ba812d90 0 0 0 0 0 0 0

2016-03-05T00:05:54.857Z cpu20:34819)Vol3: 3147: Failed to get object 28 type 2 uuid 567b68b9-9a4ca454-ad94-0025902d81ba FD 4 gen 1 :I/O error

2016-03-05T00:06:02.610Z cpu16:33293)NMP: nmp_ResetDeviceLogThrottling:3349: last error status from device mpx.vmhba32:C0:T0:L0 repeated 32 times

2016-03-05T00:06:32.609Z cpu16:33293)NMP: nmp_ResetDeviceLogThrottling:3349: last error status from device t10.ATA_____WDC_WD2500BEVS2D75UST0________________________WD2DWXE708ET7359 repeated 1 times

2016-03-05T00:09:05.840Z cpu19:32826)NMP: nmp_ThrottleLogForDevice:3286: Cmd 0x9e (0x43a5ca49af80, 0) to dev "mpx.vmhba32:C0:T0:L0" on path "vmhba32:C0:T0:L0" Failed: H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0. Act:NONE

2016-03-05T00:09:06.180Z cpu19:32826)NMP: nmp_ThrottleLogForDevice:3219: last error status from device mpx.vmhba32:C0:T0:L0 repeated 10 times

2016-03-05T00:09:06.350Z cpu22:35542 opID=8456ea0b)World: 15514: VC opID 1B96E2AA-00000250-f691 maps to vmkernel opID 8456ea0b

2016-03-05T00:09:06.350Z cpu22:35542 opID=8456ea0b)VC: 3551: Device rescan time 329 msec (total number of devices 5)

2016-03-05T00:09:06.350Z cpu22:35542 opID=8456ea0b)VC: 3554: Filesystem probe time 180 msec (devices probed 4 of 5)

2016-03-05T00:09:06.350Z cpu22:35542 opID=8456ea0b)VC: 3556: Refresh open volume time 1 msec

2016-03-05T00:09:06.473Z cpu22:35542 opID=8456ea0b)LVM: 3684: [t10.ATA_____WDC_WD2500BEVS2D75UST0________________________WD2DWXE708ET7359:1] Device expanded (actual size 488394752 blocks, stored size 488390017 blocks)

2016-03-05T00:09:06.485Z cpu22:35542 opID=8456ea0b)LVM: 3684: [t10.ATA_____WDC_WD2500BEVS2D75UST0________________________WD2DWXE708ET7359:1] Device expanded (actual size 488394752 blocks, stored size 488390017 blocks)

2016-03-05T00:09:06.486Z cpu22:35542 opID=8456ea0b)LVM: 3684: [t10.ATA_____WDC_WD2500BEVS2D75UST0________________________WD2DWXE708ET7359:1] Device expanded (actual size 488394752 blocks, stored size 488390017 blocks)

2016-03-05T00:09:06.496Z cpu22:35542 opID=8456ea0b)LVM: 3684: [t10.ATA_____WDC_WD2500BEVS2D75UST0________________________WD2DWXE708ET7359:1] Device expanded (actual size 488394752 blocks, stored size 488390017 blocks)

2016-03-05T00:09:06.497Z cpu22:35542 opID=8456ea0b)LVM: 3684: [t10.ATA_____WDC_WD2500BEVS2D75UST0________________________WD2DWXE708ET7359:1] Device expanded (actual size 488394752 blocks, stored size 488390017 blocks)

2016-03-05T00:09:06.526Z cpu19:32826)NMP: nmp_ThrottleLogForDevice:3219: last error status from device mpx.vmhba32:C0:T0:L0 repeated 20 times

2016-03-05T00:09:06.609Z cpu22:35542 opID=8456ea0b)VC: 3551: Device rescan time 29 msec (total number of devices 5)

2016-03-05T00:09:06.609Z cpu22:35542 opID=8456ea0b)VC: 3554: Filesystem probe time 124 msec (devices probed 4 of 5)

2016-03-05T00:09:06.609Z cpu22:35542 opID=8456ea0b)VC: 3556: Refresh open volume time 1 msec

2016-03-05T00:09:06.613Z cpu22:35542 opID=8456ea0b)LVM: 3684: [t10.ATA_____WDC_WD2500BEVS2D75UST0________________________WD2DWXE708ET7359:1] Device expanded (actual size 488394752 blocks, stored size 488390017 blocks)

2016-03-05T00:09:06.624Z cpu22:35542 opID=8456ea0b)LVM: 3684: [t10.ATA_____WDC_WD2500BEVS2D75UST0________________________WD2DWXE708ET7359:1] Device expanded (actual size 488394752 blocks, stored size 488390017 blocks)

2016-03-05T00:09:10.769Z cpu1:33354)<3>ata5.00: exception Emask 0x0 SAct 0x3 SErr 0x0 action 0x0

2016-03-05T00:09:10.769Z cpu1:33354)<3>ata5.00: irq_stat 0x40000008

2016-03-05T00:09:10.769Z cpu1:33354)<3>ata5.00: cmd 60/40:00:00:a8:00/05:00:00:00:00/40 tag 0 ncq 688128 in

res 41/40:00:78:ab:00/50:00:00:00:00/40 Emask 0x409 (media error) <F>

2016-03-05T00:09:10.769Z cpu1:33354)<3>ata5.00: status: { DRDY ERR }

2016-03-05T00:09:10.769Z cpu1:33354)<3>ata5.00: error: { UNC }

2016-03-05T00:09:10.771Z cpu1:33354)<6>ata5.00: configured for UDMA/133

2016-03-05T00:09:10.771Z cpu1:33354)<6>ata5: EH complete

2016-03-05T00:09:10.771Z cpu15:32822)NMP: nmp_ThrottleLogForDevice:3286: Cmd 0x28 (0x43a5c9b72040, 35542) to dev "t10.ATA_____WDC_WD2500BEVS2D75UST0________________________WD2DWXE708ET7359" on path "vmhba36:C0:T0:L0" Failed: H:0x0 D:0x2 P:0x0 Valid sens$

2016-03-05T00:09:10.771Z cpu15:32822)ScsiDeviceIO: 2651: Cmd(0x43a5c9b72040) 0x28, CmdSN 0x2 from world 35542 to dev "t10.ATA_____WDC_WD2500BEVS2D75UST0________________________WD2DWXE708ET7359" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x3 0x11 0x4.

2016-03-05T00:10:02.611Z cpu12:33293)NMP: nmp_ResetDeviceLogThrottling:3349: last error status from device mpx.vmhba32:C0:T0:L0 repeated 10 times

2016-03-05T00:12:37.296Z cpu4:32811)NMP: nmp_ThrottleLogForDevice:3286: Cmd 0x9e (0x439dc0962f80, 0) to dev "mpx.vmhba32:C0:T0:L0" on path "vmhba32:C0:T0:L0" Failed: H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0. Act:NONE
 
How did you format it on the other machine?

I'd suggest doing a full wipe of the drive (not format) so that it has no data or filesystem when added to your ESXi host.
 
I did that, I even used ssh into exsi to format drive before adding the drive. Other drives I add, doesn't have problem. I think some how esxi still think it has this datastore or vcentre? I might just wipe the boot usb, when I have time... or dont use this drive on the system. thanks for the help.
 
You must log in or register to reply here.
Back
Top