iserver2 Downtime

After another power failure, iserver2 again failed to boot. The server was loading the kernel and initrd, but then kernel panicking. After booting using a rescue disk, the kernel and initrd from bc247 were scp’ed across and added to the grub menu. This did not help, and the same error occurred. After rebooting the rescue disk and looking over the grub arguments, I noticed that the name of the volume group was different to the name of the volume group defined as the rootfs in the grub menu. After changing the old VG name in grub to the new VG name, the server finally booted again. Once init started, the boot again halted, this time while trying to mount / with fstab. One more rescue disk boot, and fstab was also updated with the proper VG names….. Lesson learned:

DO NOT CHANGE THE NAME OF A LOGICAL VOLUME OR VOLUME GROUP WITHOUT UPDATING:

1) grub

2) fstab

I hope anyone else who stumbles on unknown kernel panics on boot finds this post. I had wasted hours trying to figure out this problem, and ended up only finding the solution by accident.

Advertisements
Posted in Downtime
One comment on “iserver2 Downtime
  1. […] with drivers for some new NIC’s being tested, and the old kernel source was deleted in the Logical Volume Mishap. New scripts have been written to automatically increment the version numbers and to archive the […]

    Like

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: