[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: Kernel panic f7t3 and f7t4



I'll assume that you already know that /dev/hdX drives now appear as /dev/sdX devices. Based on your post, your boot is failing before any of this would even matter.

I believe your problem is that the md raid driver is not being loaded by initrd during boot initialization. I had the same problem (see my posts, and bug entitled Kernel panic: LVM not working in kernel since 2.6.20-1.3069 on this list) with Logical Volume Manager.

My problem was that all of my /etc/fstab entries were using LABEL= or UUID= to describe disk partitions. When installing the kernel, the mkinitrd script builds the initrd in /boot for the kernel. It is full of conditional code (it's a bash script that writes a nash script). I suspect that the mkinitrd script can't determine that you are running meta disks, and the appropriate initialization isn't occurring.

I debugged my problem by:

cd /tmp
cp /boot/initrd-<kernel release version>.img /tmp/initrd-<kernel release version>.img.gz
gunzip initrd-<kernel release version>.gz
mkdir initrd
cd initrd
cpio -cid -I ../initrd-<kernel release version>.img

now examine the init nash script against a working script (from CentOS).

My bug is https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=237415

The module to file against is most likely mkinitrd, if the problem I had is causing your problem.

I hope that this points you in the right direction.

Andy


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]