- told this used to work with RHEL5.0.

Please attach the /tmp/anaconda.log (during installation) or /var/log/anaconda.log (after installation) to this bug report so we can see what's going on.  The syslog in the same location would be helpful too.

Oh I just also noticed you're referring to 5.2 RC 2.  Was this also an issue in RHEL5.2 GA?

Created attachment 319548 [details]
Anaconda log

Created attachment 319549 [details]
syslog

Was this an issue in the final GA release?

(In reply to comment #6)
> Was this an issue in the final GA release?
We can check it also in final GA release. We are stll downloading GA iso. I will update you tomorrow.

(In reply to comment #6)
> Was this an issue in the final GA release?

Denis, 
The ISO for RH5.2 RC2 and RH5.2 GA have the same MD5 sum, what makes me feel that they are the same. Could you please check for me that they are in fact different?
Thanks.

Per release engineering - RC2 was chosen as the GA release.
Denise

So RHEL5.2 RC2 and RHEL5.2 GA are the same.
Do you have any suggestion? Why system hangs at GRUB?

Martin and/or Krzysztof,

Can you please:
1) Boot the RHEL-5.2 install media into rescue mode on the system in question after trying todo a RHEL-5.2 install and then chroot to the root of the installed system and do:
mount proc /proc -t proc
mount sysfs /sys -t sysfs

And then run grub, and try to manually set grub up: When you run grub you get a "grub >" prompt, assuming your /boot partition (or / if you don't have a separate /boot) is the first partition on the disk you would then type:

root (hd0,0)
setup (hd0)

Note that if your /boot partition is for example the second partition of the raidset, then the first command would be root (hd0,1) etc.

If all goes well the output should look something like:

grub> root (hd0,0)
root (hd0,0)
 Filesystem type is ext2fs, partition type 0x83
grub> setup (hd0)
setup (hd0)
 Checking if "/boot/grub/stage1" exists... no
 Checking if "/grub/stage1" exists... yes
 Checking if "/grub/stage2" exists... yes
 Checking if "/grub/e2fs_stage1_5" exists... yes
 Running "embed /grub/e2fs_stage1_5 (hd0)"...  16 sectors are embedded.
succeeded
 Running "install /grub/stage1 (hd0) (hd0)1+16 p (hd0,0)/grub/stage2 /grub/grub.conf"... succeeded
Done.
grub>

If this works, then please check if the system will boot properly after this. If it doesn't please let us know where it fails and how exactly which as much detail as possible.

2) Confirm that this used to work with RHEL 5.0
3) Try installing RHEL 5.1 and see if that works (I want to narrow the range of
   releases to seardh for possible causes of this regression as much as possible)

Also can you please attach the output of lspci on this system?

Ok digging deeper, I've found some interesting info in the syslog:

ata1.00: ATA-7: WDC WD2500YS-01SHB1, 20.06C06, max UDMA/133
ata2.00: ATA-7: WDC WD2500YS-01SHB1, 20.06C06, max UDMA/133
scsi7 : pata_marvell
ata7.00: ATA-7: ST3160815A, 3.AAD, max UDMA/100

So this system has 2 sata disks on the ich9 and then a pata disk on a marvel controller which gets detected as the last disk, which might confuse things.

This probably means EDD is giving us the wrong answer for which disk is bootable, can you try to install RHEL-5.2 GA again on this system and then in the install bootloader screen make sure the right disk is selected on which to install the bootloader?

On the bootloader setup screen there will be a checkbox with behind that something like: "install boot loader on /dev/sdc" and then a Change Device button.

Click the Change Device button and make sure you have the disk / raid set selected, which is selected to boot from in the BIOS as the disk to boot from.

Also when the installation is done, and the installer presents a reboot button to press to reboot, can you please:
1) Not press that button!
2) Switch to the available bash shell at tty, using CTRL+ALT+F2
3) In that bash shell type: "cat /mnt/sysimage/boot/grub/device.map"
4) write down the output of the command given by 3) and post it here.

Hans,

According to Your procedure system in booting now, but there is other problem (look at attachment RH53.jpg). 

I will start from beginning:
1. Pata disk was removed
2. Bootloader configuration was changed according to Your information
3. Output from device.map - "(hd0) /dev/mapper/isw_bchhaaahhf_RAID0TEST" its raid 0 from 2 drives
4. After reboot bootloader is starting, but system its freezing (kernel panic). Bash shell is not available.

Created attachment 320671 [details]
Screenshot - RH52.jpg

(In reply to comment #13)
> Hans,
> 
> According to Your procedure system in booting now, but there is other problem
> (look at attachment RH53.jpg). 
> 
> I will start from beginning:
> 1. Pata disk was removed
> 2. Bootloader configuration was changed according to Your information
> 3. Output from device.map - "(hd0) /dev/mapper/isw_bchhaaahhf_RAID0TEST" its
> raid 0 from 2 drives
> 4. After reboot bootloader is starting, but system its freezing (kernel panic).
> Bash shell is not available.

Hmm,

This is a different problem then the initial problem reported in this bug, can you please file a new bug for this?

Also to expedite work on that new bug, please boot into rescue mode and get /boot/initrd-*.img from the installed system and attach that to the new bug, if its to big to attach please mail it to me directly.

The problem reported in this bugzilla does not exist when the correct disk is selected in the install bootloader screen.  So per Krzysztof, I am closing this BZ. The bug for the other problem is 467027- PC hangs after click on "Skip" button in "Installation Number" query.