We are in the process of migrating this forum. A new space will be available soon. We are sorry for the inconvenience.

Unable to boot from Network kernel


sandygws
06-11-2013, 23:12
Okay, it seems the problem might be something more fundamental, as I can't get access either by HD or using a Network boot.

Dear Customer,

Your ticket 1553xxx is going to be taken by one of our operators (Mehdi).

We'll do our best to resolve this incident as soon as possible.

sandygws
06-11-2013, 22:49
Thank you Felix, I have changed the netboot to "root=/dev/md2" and performed a hard reboot in the manager.

Fingers crossed it works

I have no idea why fsck failed: I haven't modified fstab since the day I first got the server. I'll take a look when it comes back up!

grrrr ... I guess that fsck problem is going to mean any reboots are going to take 30 mins+ ?

Felix
06-11-2013, 22:44
sandygws wrote:
>
> I should add that the server is now also failing to reboot from the HD -
> either when I use 'sudo reboot' or do a 'hard reboot' in the OVH
> Manager.
>
> On the two occasions I have had to reboot the server today, I receive
> the following a few minutes later: 'Dear Customer, Our monitoring
> system, has just detected a defect on your server'.
>
> Then roughly 30 mins later, the server is back up ...
>
> Sigh.
>
>

The last outage is due to:

Filesystem manual check
Here are the details of the performed operation:
The server has completed a file system check (fsck)
The server was blocked when checking files with the message:

(fsck.ext3:no such file or directory while trying to open /dev/md127
possibly non existant device ?
fsck died with exit status 8 )

Actions:
"ctrl+d" done

Result:
Login to server. Ping OK, services started.

Maybe check your initrd or fstab for invalid entries.

I see your netboot is set like this: "root=/dev/md1".
But it should be "root=/dev/md2" in your case.

Felix

sandygws
06-11-2013, 22:32
I should add that the server is now also failing to reboot from the HD - either when I use 'sudo reboot' or do a 'hard reboot' in the OVH Manager.

On the two occasions I have had to reboot the server today, I receive the following a few minutes later: 'Dear Customer, Our monitoring system, has just detected a defect on your server'.

Then roughly 30 mins later, the server is back up ...

Sigh.

sandygws
06-11-2013, 21:51
Thank you Felix

Number: 372225

The server will not boot from the network kernel regardless of which option(s) I choose.

Moreover, every single time I reboot the server, it fails to come up and I receive the 'Our monitoring system, has just detected a defect on your server' email.

Then, usually 30 mins - 1 hour later, the server is back up.

How can I check why this is happening? It never happened before I attempted to boot from the network kernel ...

Felix@OVH
05-11-2013, 16:28
on an FS-8T it should be /dev/md2.
You could post the "server number" here, it's visible in the Managerv3 overview, and only OVH staff can find the correlating server with it.

Felix

sandygws
04-11-2013, 18:21
As the server is currently down, I can't check the /etc/fstab

Which is the default 'root partition' for an FS-8T: IDE, SCSI or RAID-SOFT?

sandygws
04-11-2013, 18:08
Felix, I have sent you a 'friendship request' .. I guess that would allow me to PM you?

Felix@OVH
04-11-2013, 17:59
I don't know which server it is, so can't have a look...

But usually the problem is that no "root=" parameter is specified in the advanced netboot settings. You have to set your /-partition there - you can find it in your /etc/fstab.
(it mostly is "/dev/sda1" or "/dev/md1", but if you have a different partitioning and/or GPT partitioning, it shifts by 1 or 2)

Felix

sandygws
04-11-2013, 15:57
For some reason Netboot simply doesn't work for my server.

I have tried both 3.10.9 x86_64 & SMP & IPV6 & 3.10.9 x86_64 & SMP & IPV6 & NZ_1000, but after rebooting the server always fails to respond and I receive the 'Our monitoring system, has just detected a defect on your server' email.

Can someone at OVH please take a look at this.

Thank you.