I'm doing a new installation of RedHat 9, I have two hard drivers on this system.

hda is 850 MB: /usr
hdb is 541 MB: /boot, /, swap

When the installation is done, following is the screen message shown for my first boot. After the last time of kernel panic, the system just hang there:

:
:
hda: task_no_data_intr: status=0x51 { DriveReady SeekComplete Error }
hda: task_no_data_intr: error=0x40 { DriveStatusError }
hda: 1660176 sectors (850 MB) w/96KiB Cache, CHS=823/32/63, DMA
hdb: task_no_data_intr: status=0x51 { DriveReady SeekComplete Error }
hdb: task_no_data_intr: error=0x40 { DriveStatusError }
hdb: 1057392 sectors (541 MB) w/98KiB Cache, CHS=1049/16/63, DMA
ide-floppy driver 0.099.newide
Partition check:
hda: hda1
hdb:<4>hdb: dma_timer_expiry: dma status == 0x61
:
:
:
Loading ext3.o module
Mounting /proc filesystem
Creating block devices
Creating root devices
mkrootdev: lable / not found
Mounting root filesystem
mount: error 2 mounting ext3
pivotroot: pivot_root(/sysroot,/sysroot/initrd) failed: 2
umount /initrd/proc failed: 2
Freeing unused kernel memory: 116k freed
Kernel panic: No init found. Try passing init= option to kernel.

It looks like you are getting a lot of I/O errors trying to read your disks. Perhaps your new kernel does not have the proper IDE driver installed.

I don't know how RedHat detects hardware during an install but if possible see if the IDE chipset on your motherboard is what RedHat thinks it is.

How do I determine which chipset my motherboard has?

Even with the I/O errors, I was able to boot from floppy and make installation over HTTP.

I can boot from hard drive, but just couldn't finish the entire booting process.

Any way to fix this? Or should I add some special boot parameter?

--------------------------------------------------------------
How do I determine which chipset my motherboard has?

Open up your computer and read the number on the IDE chipset.
--------------------------------------------------------------
Or should I add some special boot parameter?

It is possible that the file system for / is ext2 and you have
told the boot loader (grub or lilo) that it is ext3, or vice versa.
It is also possible that you have told your bootloader to look for / on the wrong drive or partition.
--------------------------------------------------------------

I had simillar error messages. UDMA between controller and hard drive didn't play nicely. Try switching to PIO mode and see if you still get the error messages. research teh wen for status=0x51 and error=0x40.

I just figured out that by adding the boot parameter ide=nodma would solve the problem of dma_timer_expiry: dma status == 0x61 and boot successfully.

Thanks for all the comments

i have a similar error

hda: task_no_data_intr: status=0x51 { DriveReady SeekComplete Error }
hda: task_no_data_intr: error=0x04 { DriveStatusError }
hda: 6354432 sectors (3253 MB), CHS=788/128/63, UDMA(33)
ide-floppy driver 0.99.newide
Partiton check:
hda:

and it never leaves that screen
any help would be appreciated