Issue installing OS via kickstart - Red Screen of Death

[Matthew Sarro]

Hey everyone,
We have a DL360 G6 test system in the lab right now we're using as a sandbox for a future deployment. We just received the 'sanitized' kickstart file. However since I've tried using it, as soon as the system reboots post-install there is an 'illegal opcode' red screen of death.

The server configuration is as follows:
4x 146gb hdd SAS, in two raid 1+0 mirrors.

System partitions include:
100mb /boot
the rest of the first and second mirror is an LVM filesystem housing swap and /.

Now we've built this system before with no issue so I know its an issue with the kickstart file. I've narrowed it down to the following lines that aren't in our original kickstart file:

bootloader --location=mbr
(original read:bootloader --location=mbr --driveorder=cciss/c0d0,cciss/c0d1)

lang en_US
(original read:lang en_US.UTF-8)

langsupport --default en_US.iso885915 en_US.iso885915
(original read:NOT IN ORIGINAL)

mouse generic3ps/2 --device psaux --emulthree
(original read:NOT IN ORIGINAL)

clearpart --all --initlabel
(original read: clearpart --all)

zerombr yes
(original read: NOT IN ORIGINAL)

rmmod qla2xxx
rmmod qla2xxx_con
rmmod lpfc
(not in original, added for system stability according to deployment team)

Can anyone see an issue with any of these lines? This is with Red Hat Enterprise 5.4.

Thus far I've been able to eliminate the zerombr option as the cause, but I'm not sure if it could be interacting sourly with something else.

[Steven E. Protter]

Shalom Matthew,

Check and see if this kickstart file is using an image made from a G5 or earlier server. G6 has different disk drivers required and images from older servers may cause this condition.

To use kickstart with G6 servers, a new image will have to be created with a bare metal install.

SEP

[Jimmy Vance]

I've found the red screen of death to be firmware related. Normally updating all the firmware in the server will resolve the problem.