Troubleshooting
Problem
Kernel trap with Red Hat Linux v6.1 with RAID for Servers.
Resolving The Problem
Source
RETAIN tip H17609
Symptom
Red Hat Linux 6.1 will report a kernel trap if you install Linux to the onboard Adaptec SCSI controller and then add RAID drives later.
This behavior occurs when a ServeRAID card is in the system but not connected to a hard drive:
- if the card is removed, the install and subsequent booting go fine.
- if the card is connected to a hard drive (using the instructions below) the system installs and runs fine.
- If the card is in the system but, not connected to a hard drive, and remains unconnected it installs and boots fine.
- If the system has a ServeRAID card that is not connected to a hard-drive, has Red Hat Linux 6.1 installed via the on board Adaptec SCSI controller, is rebooted and subsequently has a hard-drive connected to the ServeRAID, then it will lock up on reboot.
Affected configurations
The system is any of the following IBM eServer xSeries servers:
- IBM eServer xSeries 340
- IBM eServer xSeries 240
- IBM eServer xSeries 230
The system is any of the following IBM Netfinity servers:
- a Netfinity 8500R server, type 8681, any model
- a Netfinity 7600 server, type 8665, any model
- a Netfinity 7100 server, type 8666, any model
- a Netfinity 7000-M10 server, type 8680, any model
- a Netfinity 7000 server, type 8651, any model
- a Netfinity 6000R server, type 8682, any model
- a Netfinity 5600 server, type 8664, any model
- a Netfinity 5500-M20 server, type 8662, any model
- a Netfinity 5500-M10 server, type 8661, any model
- a Netfinity 5500 server, type 8660, any model
- a Netfinity 5100 server, type 8658, any model
- a Netfinity 5000 server, type 8659, any model
- a Netfinity 4500R server, type 8656, any model
- a Netfinity 3500-M20 server, type 8657, any model
- a Netfinity 3500-M10 server, type 8655, any model
- a Netfinity 3500 server, type 8644, any model
- a Netfinity 3000 server, type 8476, any model
- a Netfinity 1000 server, type 8477, any model
The system is configured with the following option(s):
- a ServeRAID II Ultra SCSI Adapter, Option part number 76H3584, replacement part number (FRU) 76H3587
- a Netfinity ServeRAID 3H Ultra2 SCSI Adapter, Option part number 01K7207, replacement part number (FRU) 01K7396
- a Netfinity ServeRAID-3L Ultra2 SCSI Adapter, Option part number 01K7364, replacement part number (FRU) 01K7352
- a Netfinity ServeRAID 3HB Ultra2 SCSI Adapter, Option part number 37L6086, replacement part number (FRU) 01K7396 (adapter)
The following network operating system (NOS) is affected: Linux version 6.1 with any patch level applied.
The system has the symptom described above.
Solution
This behavior is solved by performing the installation of Red Hat 6.1, including the workaround instructions. Then, before connecting the ServeRAID adapter, boot to Red Hat 6.1 and install the following RPMs:
rpm -ivh --force sash-3.4-2.i386.rpm
rpm -ivh --force mkinitrd-2.4.1-2.i386.rpm
The RPMs are available from the Red Hat 6.2 CD.
sash-3.4-2.i386.rpm and mkinitrd-2.4.1-2.i386.rpm can also be found at:
ftp://ftp.redhat.com/pub/redhat/redhat-6.2-en/os/i386/RedHat/RPMS/
Then re-make the init ramdisks for the system:
mkinitrd -f /boot/initrd-2.2.12-20.img 2.2.12-20
mkinitrd -f /boot/initrd-2.2.12-20smp.img 2.2.12-20smp
Then run lilo:
lilo
Shut down the system:
init 0
and connect the ServeRAID adapter. When you reboot, the ServeRAID adapter will be detected by kudzu and the driver will be installed. You may still need to make partitions on the ServeRAID.
Workaround
For both text and GUI installs:
1. At the "Congratulations, installation is complete" screen, press the Ctrl, Alt and F2 keys simultaneously.
2. At the "bash#" prompt, type: cd /mnt/sysimage
3. Type the following (to set a system variable named LC_ALL): LC_ALL=C
4. Type the following: usr/sbin/chroot
This changes "root" from "/" to "/mnt/sysimage" makes subsequent accesses to "/whatever" tantamount to accesses to
"/mnt/sysimage/whatever".
5. Type the following: less /etc/lilo.conf
Look for the init* strings, and substitute what you find there for the init* strings below:
/sbin/mkinitrd -f /boot/initrd-2.2.12-20.img 2.2.12-20
This line reads the *.o files from /lib/modules/2.2.12-20 using the file "/etc/conf.modules" as a menu and builds the initial ram-disk from these files.
6. If you have an smp kernel use the following:
/sbin/mkinitrd -f /boot/initrd-2.2.12-20smp.img 2.2.12-20smp
NOTE: For each kernel you find in "/etc/lilo.conf", you will have a corresponding initial ram-disk, and will need to rebuild that ram-disk.
7. Type the following: /sbin/lilo -v
This forces the lilo executable to read the file "/etc/lilo.conf", and to find the physical location of each of the files described (including initial ram-disks).
8. Return to the install screen:
If using the text install, press the Ctrl, Alt, and F1 keys simultaneously.
If using the GUI install, press the Ctrl, Alt, and F7 keys simultaneously.
9. Conclude installation by pressing OK in the Text install or Exit in the GUI install.
NOTE: If you boot, and Red Hat begins to load, but later locks up with a kernel panic, then you have probably not made the initrd for that kernel, and will need to boot to a working system and run mkinitrd for that kernel, or reinstall (step 1 above).
Document Location
Worldwide
Was this topic helpful?
Document Information
Modified date:
28 January 2019
UID
ibm1MIGR-4JWSMK