G'day All,

I rebooted a RackShack Raq4i today and after about 9 minutes of no ping responses I had a chat online to RackShack support. They said it was still rebooting and explained that a Raq usually takes between 10 and 20 minutes to come back up. After talking (typing) to them for a while it was up in about 1 minute from the conversation ended. The total offline time was about 16 minutes.

We run quite a number of Linux and NT servers locally and we have nothing that takes that long to boot from a controlled shutdown.

Does anyone know if this is normal for a Cobalt device, or was someone pulling my leg and maybe something else was actually going on?

Thanks for your advice.

A reboot on my RaQ4 usually takes less than a minute, same for my RaQ3.

I don't kow if this depents on the number of hosted sites!?

1-2 minutes depending on the configuration

1-2 minutes is correct unless it has to run an fsck for whatever reason then 16 minutes can happen depending on how much data is there.

Steve

Linux reboots can be very fast or very slow depending on how the machine was shut down.

Take a peak in the /var/messages or /var/kernel logs to see what happened during the reboot.

If the machine was shutdown cleanly, then linux boot on my Raq4i in about 2 minutes. However, if it has been a long time since a reboot or the machine did not shutdown cleanly, fsck will run on startup. If there are errors, then fsck will try to fix these and reboot.

Since Raq4s have relative slow disk drives, fsck can take a long time to run, especially if there was corruption of the /home partition and there was a lot of data on it.

10-20 minutes to reboot would not be unusual in this case. To test this, reboot the server again.

Most of the time, my RaQ4 takes about 1-2 minutes to reboot back to full operation. My advice is to activate telnet on your RaQ (only on one or two domains). I have noticed that on some RaQ4 and RaQ3 configurations, when the RaQ is rebooted, it starts back up BUT, does not reactivate HTTPD. In this case, you can restart the HTTPD manually in telnet.