[CentOS] New motherboard - kernel panic

[Bowie Bailey]

On 4/15/2013 5:09 PM, m.roth at 5-cent.us wrote:
> Bowie Bailey wrote:
>> On 4/15/2013 1:35 PM, m.roth at 5-cent.us wrote:
>>> Bowie Bailey wrote:
>>>> On 4/12/2013 5:33 PM, Bowie Bailey wrote:
>>>>> I had to replace the motherboard on one of my CentOS 4 systems and am
>>>>> now getting a kernel panic.
>>>>>
>>>>> When I try to boot up, I get this:
>>>>>
>>>>>           Volume group "VolGroup00" not found
>>>>>         ERROR: /bin/lvm exited abnormally! (pid 448)
>>>>>         mount: error 6 mounting ext3
>>>>>         mount: error 2 mounting none
>>>>>         switchroot: mount failed: 22
>>>>>         umount /initrd/dev failed: 2
>>>>>         Kernel panic - not syncing: Attempted to kill init!
>>>>>
>>>>> (I apologize for any typos, I don't have a way to copy/paste from that
>>>>> screen)
>>>>>
>>>>> I can boot up with the boot CD, go into rescue mode and browse the
>>>>> files, so I know the drives are ok.
>>>>>
>>>>> I found some stuff online saying that I should recreate my initrd from
>>>>> rescue mode if the motherboard changed.  I tried this, but am still
>>>>> getting the same results.
>>> Sorry, hit <send> and had another thought: I think you said you rebuilt
>>> the initrd... *could* you see the drives? *Did* the running system you
>>> rebuilt from have all the LVM drivers loaded when you rebuilt it?
>> I can see the drives from the rescue environment.  I don't know how to
>> check the LVM drivers.
> You need *both* the md drivers and lvm drivers. I haven't built a system
> using lvm in years, I'm afraid, but it shouldn't be too hard.
>
> Btw, this may be of some interest:
> <http://www.centos.org/docs/5/html/Cluster_Logical_Volume_Manager/device_mapper.html>

I got it figured out.  The problem was at the sata driver level. The 
instructions I found for rebuilding the initrd neglected to mention that 
I needed to edit modprobe.conf and add the appropriate driver 
information first.

I'm still not sure why it was able to get as far as loading the kernel 
before suddenly being unable to see the drives.  If it needs sata 
drivers to see the disks, why doesn't it need them to read the boot 
partition?  I didn't have to mess with grub or the boot sector after 
changing motherboards.

-- 
Bowie