On Fri, Apr 08, 2011 at 07:26:55PM -0500, Gilbert Sebenste wrote:

...

Remember, you could have been at the limit of reboots before it does a automatic fsck. Been there, done that.

...or time, if the filesystem has a force-fsck-after-N-days feature.

Yes, it could have, but it's been 2 hours now, and the hard drive is only 40 gigs ssd. Since it was a pre-prod not yet in use server, it'll wait till monday.

On 04/09/2011 03:03 AM, Digimer wrote:

On 04/08/2011 10:00 PM, Nicolas Ross wrote:

...

...

On Fri, Apr 08, 2011 at 07:26:55PM -0500, Gilbert Sebenste wrote:

...

Remember, you could have been at the limit of reboots before it does a automatic fsck. Been there, done that.

...or time, if the filesystem has a force-fsck-after-N-days feature.

Yes, it could have, but it's been 2 hours now, and the hard drive is only 40 gigs ssd. Since it was a pre-prod not yet in use server, it'll wait till monday.

Please post a follow-up, I'm curious what went wrong. :)

Maybe your server is hanging at fsck recovery shell waiting for root password (or user interaction).

Do you have a option to reboot you system into rescue mode or better a KVM over IP ?

HTH

...

...

On Fri, Apr 08, 2011 at 07:26:55PM -0500, Gilbert Sebenste wrote:

...

Remember, you could have been at the limit of reboots before it does a automatic fsck. Been there, done that.

...or time, if the filesystem has a force-fsck-after-N-days feature.

Yes, it could have, but it's been 2 hours now, and the hard drive is only 40 gigs ssd. Since it was a pre-prod not yet in use server, it'll wait till monday.

Please post a follow-up, I'm curious what went wrong. :)

To follow-up on my own storry, I got there this morning, expecting to find the server stuck at fsck or somthing similar, only to find it with only the sord "GRUB" on the screen, and beeping like crazy. I didn't have any iso nor centos cd with me, so I'll get back there this after-noon with a portable cd-drive and centos cd.

To be continued...

...

To follow-up on my own storry, I got there this morning, expecting to find the server stuck at fsck or somthing similar, only to find it with only the sord "GRUB" on the screen, and beeping like crazy. I didn't have any iso nor centos cd with me, so I'll get back there this after-noon with a portable cd-drive and centos cd.

To be continued...

Ouch, that hurts. Do please follow up. :)

Indeed... I really don't know what went wrong... I booted in rescue mode, I did uninstalled the unsed old kernel, did grub-install /dev/sda, and rebooted. The server now boots normally...

Lessons of the storry: if you don't have a remote kvm, be at te console when upgrading !

Le 09/04/2011 08:23, Paul Daggett a écrit :

----- Original Message ---- From: Nicolas Rossrossnick-lists@cybercat.ca To: centos@centos.org Sent: Fri, April 8, 2011 8:24:39 PM Subject: [CentOS] 5.6 is out, great my first upgrade didn't work...

5.6 is out. That is good news.

I did a yum update on one of my non-critical server, and the server stoped responding to ping after the reboot, and never answered back. It's now been 10 minutes, so I'll have to take a ride to the colo...

Nice work dev team, keep up the good work. Let's hope that C6 will come soon ! I'm eager to upgrade. _______________________________________________

So what do you have at the console? All the more reason to have multiple levels of remote capability. -Paul

Hi,

I just updated remotely an old server (Dell PE 1850, Perc 4/i), and it rebooted fine : # cat /etc/redhat-release CentOS release 5.6 (Final)

So, for me , no problem...

Alain