question

JohnLenz-5880 avatar image
0 Votes"
JohnLenz-5880 asked JohnLenz-5880 answered

Black scrreen

This is a new one on me...

Host - server2012R2 Datacenter, Hyper-V
Hyper-V system that was working: Server2012R2 Standard

I get the following screen on the start of the Hyper-V machine (won't upload)
It is a black screen with either Hyper-V text or all black and a single "dot" for the cursor.

Hyper-V manager shows as running. I do not get the login screen in the Hyper-V system..

This Hyper-V machine has been booting for years and has disk space available.
It also is coming up with blue "trouble shooting" startup screen. If I restart it comes back to the same blue screen.

The physical disk drive did have problems and I had ChkDsk repair them.

Since this is a virtual sever, how do I repair it.

Hyper-V manager is the only way I can turn off the machine. If I could upload images I would show the other in Hyper-V session error message when I try to restart it or turn it off. It doesn't like it from the Hyper-V session, only Hyper-V manager.

How do I get it back and running?



windows-server-hyper-v
5 |1600 characters needed characters left characters exceeded
Toggle Comment visibility. Current Visibility: Visible to all users

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

4 Answers

JohnLenz-5880 avatar image
0 Votes"
JohnLenz-5880 answered

Update...

The physical drive the VM was on was corrupted. Had to await delivery of replacement drive.
Replacement drive installed and stable.

I use NovaStor Server software... I restored a VM image backup and the VM is now operational.

5 |1600 characters needed characters left characters exceeded
Toggle Comment visibility. Current Visibility: Visible to all users

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

DSPatrick avatar image
0 Votes"
DSPatrick answered

The physical disk drive did have problems and I had ChkDsk repair them.

You can also try chkdsk on the virtual machine but I wouldn't hold much hope. Time may be better spent standing up a new one, patch fully, migrate roles over to it and move on.

--please don't forget to Accept as answer if the reply is helpful--









5 |1600 characters needed characters left characters exceeded
Toggle Comment visibility. Current Visibility: Visible to all users

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

JohnLenz-5880 avatar image
0 Votes"
JohnLenz-5880 answered

That is what afraid of!

5 |1600 characters needed characters left characters exceeded
Toggle Comment visibility. Current Visibility: Visible to all users

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

XiaoweiHe-MSFT avatar image
0 Votes"
XiaoweiHe-MSFT answered

Hi,

As far as I'm concerned, if you would like to keep the original VM, it's recommended to open a case with MS directly, so that they can analyze the dump or use other methods to find the issue, since your issue looks complex that not easy to fix through forum. If you want to get a quick fix, then, create a new one and migrate the roles to the new VM.

Below is the link to open a case with MS:

https://support.microsoft.com/en-us/gp/customer-service-phone-numbers

Thanks for your time!
Best Regards,
Anne

If the Answer is helpful, please click "Accept Answer" and upvote it.

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.


5 |1600 characters needed characters left characters exceeded
Toggle Comment visibility. Current Visibility: Visible to all users

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.