Lost Datastore After Hard Drive Replacement (RAID 5). Ahhhh...

[phyberport]

I've got an ESXi 5.0.0 box with 4 drives hooked up to an LSI MegaRAID 9260-4i. A few weeks back I had a bad disk in the RAID, so I pulled it out and replaced it with a slower drive I had kicking around. I recieved a new replacement and decided to replace the old one with the new one. I unplugged the old drive, plugged in the new one, fired up the system, initialized it and made it online, the array looked good from LSI's MegaRAID WebBIOS utility.

I booted up ESX and found I could not see the datastore. If I go to add storage, the LUN shows up, but ESX wants to create a new datastore with the free space on it. I also noticed in there that the datastore does not have a VMFS label.

Another weird thing is, if I refresh the storage, sometimes the datastore will show up, but the size and free space are all messed up, then it will go away again. I believe all my VMs are there, I just need to get access to them some how.

Thank you in advance for any suggestions you might have.

[Sreec]

Hello,

        Can you send the output of this command? fdisk -l ,also do a HBA rescan and post the kernel messages.

[nive1103]

Hi,

I think you need to resignature the datastore you are referring.

Check the log file /var/log/vmkernel for any entries corresponding to datastore.

[phyberport]

~ # fdisk -l

Found valid GPT with protective MBR; using GPT

fdisk: Sorry, can't handle GPT partitions, use partedUtil

Here is the output after a rescan from /var/log/vmkernel.log. I hope this is what you are after. All you help is greatly appreciated.

2013-02-14T15:48:11.619Z cpu7:2915)Vol3: 647: Couldn't read volume header from control: Invalid handle

2013-02-14T15:48:11.619Z cpu7:2915)FSS: 4333: No FS driver claimed device 'control': Not supported

2013-02-14T15:48:11.621Z cpu7:2915)FSS: 4333: No FS driver claimed device 't10.ATA_____WDC_WD20EADS2D00S2B0__________________________WD2DWCAVY1001503:1': Not supported

2013-02-14T15:48:11.641Z cpu7:2915)VC: 1449: Device rescan time 22 msec (total number of devices 5)

2013-02-14T15:48:11.641Z cpu7:2915)VC: 1452: Filesystem probe time 76 msec (devices probed 5 of 5)

2013-02-14T15:48:11.717Z cpu7:2915)Vol3: 647: Couldn't read volume header from control: Invalid handle

2013-02-14T15:48:11.718Z cpu7:2915)FSS: 4333: No FS driver claimed device 'control': Not supported

2013-02-14T15:48:11.720Z cpu7:2915)FSS: 4333: No FS driver claimed device 't10.ATA_____WDC_WD20EADS2D00S2B0__________________________WD2DWCAVY1001503:1': Not supported

2013-02-14T15:48:11.795Z cpu7:2915)VC: 1449: Device rescan time 22 msec (total number of devices 5)

2013-02-14T15:48:11.795Z cpu7:2915)VC: 1452: Filesystem probe time 76 msec (devices probed 5 of 5)

2013-02-14T15:48:11.842Z cpu7:2915)ScsiScan: 1098: Path 'vmhba2:C0:T4:L0': Vendor: 'ATA     '  Model: 'Hitachi HDS72302'  Rev: 'A180'

2013-02-14T15:48:11.842Z cpu7:2915)ScsiScan: 1101: Path 'vmhba2:C0:T4:L0': Type: 0x0, ANSI rev: 5, TPGS: 0 (none)

2013-02-14T15:48:11.845Z cpu7:2915)megasas_slave_configure: do not export physical disk devices to upper layer.

2013-02-14T15:48:11.845Z cpu7:2915)WARNING: ScsiScan: 1485: Failed to add path vmhba2:C0:T4:L0 : Not found

2013-02-14T15:48:11.846Z cpu0:2915)ScsiScan: 1098: Path 'vmhba2:C0:T5:L0': Vendor: 'ATA     '  Model: 'Hitachi HDS72302'  Rev: 'AA10'

2013-02-14T15:48:11.846Z cpu0:2915)ScsiScan: 1101: Path 'vmhba2:C0:T5:L0': Type: 0x0, ANSI rev: 5, TPGS: 0 (none)

2013-02-14T15:48:11.849Z cpu0:2915)megasas_slave_configure: do not export physical disk devices to upper layer.

2013-02-14T15:48:11.849Z cpu0:2915)WARNING: ScsiScan: 1485: Failed to add path vmhba2:C0:T5:L0 : Not found

2013-02-14T15:48:11.850Z cpu7:2915)ScsiScan: 1098: Path 'vmhba2:C0:T6:L0': Vendor: 'ATA     '  Model: 'Hitachi HDS72302'  Rev: 'A180'

2013-02-14T15:48:11.850Z cpu7:2915)ScsiScan: 1101: Path 'vmhba2:C0:T6:L0': Type: 0x0, ANSI rev: 5, TPGS: 0 (none)

2013-02-14T15:48:11.853Z cpu7:2915)megasas_slave_configure: do not export physical disk devices to upper layer.

2013-02-14T15:48:11.853Z cpu7:2915)WARNING: ScsiScan: 1485: Failed to add path vmhba2:C0:T6:L0 : Not found

2013-02-14T15:48:11.854Z cpu4:2915)ScsiScan: 1098: Path 'vmhba2:C0:T7:L0': Vendor: 'ATA     '  Model: 'Hitachi HDS72302'  Rev: 'A180'

2013-02-14T15:48:11.854Z cpu4:2915)ScsiScan: 1101: Path 'vmhba2:C0:T7:L0': Type: 0x0, ANSI rev: 5, TPGS: 0 (none)

2013-02-14T15:48:11.857Z cpu4:2915)megasas_slave_configure: do not export physical disk devices to upper layer.

2013-02-14T15:48:11.857Z cpu4:2915)WARNING: ScsiScan: 1485: Failed to add path vmhba2:C0:T7:L0 : Not found

2013-02-14T15:48:11.968Z cpu6:2915)Vol3: 647: Couldn't read volume header from control: Invalid handle

2013-02-14T15:48:11.968Z cpu6:2915)FSS: 4333: No FS driver claimed device 'control': Not supported

2013-02-14T15:48:11.971Z cpu6:2915)FSS: 4333: No FS driver claimed device 't10.ATA_____WDC_WD20EADS2D00S2B0__________________________WD2DWCAVY1001503:1': Not supported

2013-02-14T15:48:11.972Z cpu6:2915)VC: 1449: Device rescan time 22 msec (total number of devices 5)

2013-02-14T15:48:11.972Z cpu6:2915)VC: 1452: Filesystem probe time 76 msec (devices probed 5 of 5)

2013-02-14T15:48:12.016Z cpu1:2667)usb-storage: detected SCSI revision number 2 on vmhba32

2013-02-14T15:48:12.016Z cpu2:2172)ScsiUid: 273: Path 'vmhba32:C0:T0:L0' does not support VPD Device Id page.

2013-02-14T15:48:12.016Z cpu1:2172)VMWARE SCSI Id: Could not get disk id for vmhba32:C0:T0:L0

2013-02-14T15:48:12.059Z cpu6:2915)FSS: 4333: No FS driver claimed device 't10.ATA_____WDC_WD20EADS2D00S2B0__________________________WD2DWCAVY1001503:1': Not supported

2013-02-14T15:48:12.059Z cpu6:2915)Vol3: 647: Couldn't read volume header from control: Invalid handle

2013-02-14T15:48:12.059Z cpu6:2915)FSS: 4333: No FS driver claimed device 'control': Not supported

2013-02-14T15:48:12.115Z cpu6:2915)VC: 1449: Device rescan time 21 msec (total number of devices 5)

2013-02-14T15:48:12.115Z cpu6:2915)VC: 1452: Filesystem probe time 75 msec (devices probed 5 of 5)

2013-02-14T15:48:12.231Z cpu6:2915)Vol3: 647: Couldn't read volume header from control: Invalid handle

2013-02-14T15:48:12.231Z cpu6:2915)FSS: 4333: No FS driver claimed device 'control': Not supported

2013-02-14T15:48:12.234Z cpu6:2915)FSS: 4333: No FS driver claimed device 't10.ATA_____WDC_WD20EADS2D00S2B0__________________________WD2DWCAVY1001503:1': Not supported

2013-02-14T15:48:12.261Z cpu6:2915)VC: 1449: Device rescan time 22 msec (total number of devices 5)

2013-02-14T15:48:12.261Z cpu6:2915)VC: 1452: Filesystem probe time 75 msec (devices probed 5 of 5)

2013-02-14T15:48:12.379Z cpu4:2915)FSS: 4333: No FS driver claimed device 't10.ATA_____WDC_WD20EADS2D00S2B0__________________________WD2DWCAVY1001503:1': Not supported

2013-02-14T15:48:12.379Z cpu4:2915)Vol3: 647: Couldn't read volume header from control: Invalid handle

2013-02-14T15:48:12.379Z cpu4:2915)FSS: 4333: No FS driver claimed device 'control': Not supported

2013-02-14T15:48:12.407Z cpu4:2915)VC: 1449: Device rescan time 22 msec (total number of devices 5)

2013-02-14T15:48:12.407Z cpu4:2915)VC: 1452: Filesystem probe time 74 msec (devices probed 5 of 5)

2013-02-14T15:48:13.049Z cpu6:3388)Vol3: 647: Couldn't read volume header from control: Invalid handle

2013-02-14T15:48:13.049Z cpu6:3388)FSS: 4333: No FS driver claimed device 'control': Not supported

2013-02-14T15:48:13.052Z cpu6:3388)FSS: 4333: No FS driver claimed device 't10.ATA_____WDC_WD20EADS2D00S2B0__________________________WD2DWCAVY1001503:1': Not supported

2013-02-14T15:48:13.070Z cpu6:3388)VC: 1449: Device rescan time 22 msec (total number of devices 5)

2013-02-14T15:48:13.070Z cpu6:3388)VC: 1452: Filesystem probe time 74 msec (devices probed 5 of 5)

End of log reached.