Hello,
We had an IO issue it seems back on the 11th from our VM to our data partition on the OS disk. The disk was around 30 GB in size, or the normal provision size, but now seems to be the same size as a DVD and our data partition is missing from the VHD.
We have downloaded the VHD and looked into the logs which we will post below. We worked through some other forum posts which don't seem to work. On the 11th when the original problem occurred the disk IO went to 0 along with network out IO.
We have restarted, no good, shutdown and started, deleted and kept attached disk and recreated, same issue. The VM only exhibits very low CPU usage and no network IO out or disk IO. We can't SSH in or get a console so we don't know what the VM is doing or how to get the disk fixed to retrieve our data partition with company emails on them.
Here is the info from the logs that lead me to think there was a possible back end problem with the VHD/blob.
I found these messages in the logs of the VHD I downloaded which I looked for earlier on the forums but seemed to be related to a fix back in 2012(?) possibly:
(all times Central US; edited for brevity)
Sep 11 14:11:22 - hv_storvsc vmbus_0_2: cmd 0x28 scsi status 0x2 srb status 0x4
5 of these within one minute
Then they start again at 20:36 and repeat until:
Sep 11 20:40:51 - sd 1:0:1:0 [sdb] Result: hostbyte=DID_TARGET_FAILURE driverbyte=DRIVER_OK
Sep 11 20:40:51 - sd 1:0:1:0 [sdb] CDB: Read(10): 28 00 00 2e e6 00 00 01 00 00
Sep 11 20:40:51 - end_request: critical target error, dev sdb, sector 3073536
Then the vmbus_0_2 errors repeat for the next 3-4 minutes and then the log entries end.
sdb should have been my data partition on the VHD.
Any help on reviving this VM and recovering the VHD as it was would greatly be appreciated.