Server Booting But No Monitor or Network connection to access ssh

Asked by Jeff

I Currently had two servers, my previous one that crashed on the 9th of December and now a new Sever that crashed today. "15-1-15"
They have both had the same problem: Server will boot up fine, but with the VGA connected to a monitor nothing is displayed (even if VGA is unplugged), i cannot access the login or grub menu, server won't connect to router/network even though its hardwired with Ethernet... :/

     Can't see any Logs or Error(s) messages, due to no access to anything.

Any help or ideas?

Question information

Language:
English Edit question
Status:
Answered
For:
Ubuntu Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Manfred Hampl (m-hampl) said :
#1

If you connect a monitor and try booting, do you see anything on the screen, e.g. bios boot messages?
Do you see anything that confirms that the system is really starting, e.g. disk activity or network traffic indicators?
As an attempt to confirm that the system is correctly running: Can you try logging in "blind" with username and password and issue the command "sudo poweroff". Does that shut down the system?

Revision history for this message
Jeff (jefferysash) said :
#2

Nope nothing comes up on screen on boot. Just a black screen.
I've tried logging in blind but keyboard and mouse are inoperable also.
 Hdd is spinning fine, just no idea to why both systems that are totally
different are having the same issues.

On Friday, 16 January 2015, Manfred Hampl <
<email address hidden>> wrote:

> Your question #260771 on Ubuntu changed:
> https://answers.launchpad.net/ubuntu/+question/260771
>
> Status: Open => Needs information
>
> Manfred Hampl requested more information:
> If you connect a monitor and try booting, do you see anything on the
> screen, e.g. bios boot messages?
> Do you see anything that confirms that the system is really starting, e.g.
> disk activity or network traffic indicators?
> As an attempt to confirm that the system is correctly running: Can you try
> logging in "blind" with username and password and issue the command "sudo
> poweroff". Does that shut down the system?
>
> --
> To answer this request for more information, you can either reply to
> this email or enter your reply at the following page:
> https://answers.launchpad.net/ubuntu/+question/260771
>
> You received this question notification because you asked the question.
>

Revision history for this message
Manfred Hampl (m-hampl) said :
#3

Are you sure that your display hardware (monitor, cables, ...) is ok? I would expect that at least the BIOS boot messages should be shown.

Revision history for this message
Jeff (jefferysash) said :
#4

It always used to show the "Packard bell" bios boot up image, now it's just
a black screen.
 As far as I know it's fine, but I've tried a graphics card in both
machines as well as the internal one and they still don't respond, also
have tried an alternative VGA cable but still nothing comes up on screen.
 This Packard Bell had only been running for 2 days before this incident.

(My previous server was HP that had been running for 11months and this same
problem occurd to that one on the 9th of December.)

On Sunday, 18 January 2015, Manfred Hampl <
<email address hidden>> wrote:

> Your question #260771 on Ubuntu changed:
> https://answers.launchpad.net/ubuntu/+question/260771
>
> Status: Open => Needs information
>
> Manfred Hampl requested more information:
> Are you sure that your display hardware (monitor, cables, ...) is ok? I
> would expect that at least the BIOS boot messages should be shown.
>
> --
> To answer this request for more information, you can either reply to
> this email or enter your reply at the following page:
> https://answers.launchpad.net/ubuntu/+question/260771
>
> You received this question notification because you asked the question.
>

Revision history for this message
Manfred Hampl (m-hampl) said :
#5

If there was a Packard Bell logo visible earlier and it isn't any more, then your problem seems not to be related to the operating system, but to either hardware or BIOS.

Can you help with this problem?

Provide an answer of your own, or ask Jeff for more information if necessary.

To post a message you must log in.