Member Avatar for anitha2324

i tried to install redhat linux enterprise edition WS version 5 on the my system with the following configuration


Pentium core 2 duo 2.13
Intel D945GCL motherboard
320gb Maxator hard disk (SATA)
Liton DVD/WR
LG CD WRITER
1024 mb RAM


BUT AM GETTING AN ERROR INDICATING THAT drivers not found

then i used the command "linux all-generic-ide"

it was installed sucessfully ,

but after the successful installation it shows me a message that u can reboot , i have rebooted the machine but i still got new message , the new messages says:


uncompressing linux..ok, booting the kernel.
PCI: Unable to handle 64-bit address space for
PCI: Unable to handle 64-bit address space for
PCI: Unable to handle 64-bit address space for
audit(1176073482.545:0): initialized
Red Hat nash version 4.1.18 starting
mkrootdev: label /1 not found
mount: errer 2 mounting ext3
mount: error 2 mounting none
switchroot: mount failed: 22
umount /initrd/dev failed: 2
kernel panic - not syncing: Attempted to kill init!


and it will not rebooting at all

i have selected RedHat title in GRUB Menu and added 'noacpi' ( and also 'noapm' in another time) at the end of kernel line and rebooted again but am still getting the same error

am a newbie to linux

  • 4 Contributors
  • 3 Replies
  • 363 Views
  • 1 Month Discussion Span
  • Latest Post Latest Post by pallipika

Dani AI

Generated

Short diagnosis and what matters most: the repeated
PCI: Unable to handle 64-bit address space for lines are a kernel probe message that commonly appears when a 32‑bit kernel sees PCI devices with 64‑bit BARs — it is usually informative and not the direct cause of a panic. (access.redhat.com)
The fatal sequence in the log is the mkrootdev: label /1 not found → mount: error 2 mounting ext3 → switchroot: mount failed lines: that indicates the initramfs/initrd could not find or access the installed root filesystem (wrong label/device or the driver needed to talk to the disk is missing from the initrd). (linuxquestions.org)

Practical, focused checks (ordered by likelihood):

  • Verify the GRUB kernel line and the exact initrd file referenced in GRUB and confirm /etc/fstab is using the same label/device name that really exists (check partition labels).
  • Inspect the initrd contents (list modules/files) to see whether the SATA/controller driver is present; on RHEL5-era systems lsinitrd (or unpacking the initrd) shows the modules inside. (simplylinuxfaq.com)
  • If the initrd lacks the driver the kernel needs, recreate it so the correct module is included (RHEL5 uses mkinitrd; supply the kernel version and force overwrite if needed). (docs.redhat.com)

Context tying the thread together: was right to point at disk/driver mismatch as the likely root cause, ’s irqpoll note is a useful kernel-parameter troubleshooting tip for controller IRQ races (rarely fixes an initrd that lacks a driver), and ’s rescue-mode / label suggestion is exactly the right diagnostic direction. The usual resolution is to boot rescue, mount the installed tree, confirm labels in /etc/fstab/GRUB, and rebuild the initrd to include the correct SATA module (or change BIOS SATA mode to match the installed driver) before rebooting. (docs.redhat.com)

Helpful items for deeper debugging: the exact GRUB entry (kernel + initrd lines), kernel version, /boot listing, output of lsinitrd (or the unpacked initrd), and the partition label(s) (e2label/blkid). These make the next troubleshooting steps deterministic rather than speculative.

Recommended Answers

All 3 Replies

Member Avatar for John A

It kind of sounds like you don't have SATA support in your kernel. The fact that the kernel cannot mount your root partition makes me almost certain that the kernel is incapable of handling SATA drives. I'm no Red Hat expert, but you might have to choose a special option in the installation process to install a kernel that does have support for SATA.

Member Avatar for jbennet

try using the irqpoll option while booting

might help. i use it as for some wierd reason a SATA controller on a server of mine wont work without it

Member Avatar for pallipika

Hi Anitha,

RHEL5 has SATA and SCSI support in its kernel.

The error shows that / partition is not mountable.
Did you go to rescue mode and change the e2labels for the /partition?

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.