Hi there xeleema,
Thank you heaps for replying to this
.
Tried both the options you've mentioned but it didn't work
.
GRUB Troubleshooting (Small typo, In order to get the grub command line you have to press "c" not "e"
)
Here is the output,
grub> find /boot/grub/stage1
Error 15: File not found
grub> find /boot/statge1
Error 15: File not found
grub> find /grub/stage1
(hd0,0)
(hd1,0)
(hd2,0)
(hd3,0)
Tried both (hd0,0) and (hd1,0) without luck.
ReBuilding an initrd
Following this
https://access.redhat.com/kb/docs/DOC-1959 to build initrd but that didn't work either.
This is what it says (People who don't have access to redhat)
Start
#####
When adding hardware like SCSI, SATA, or FibreChannel controllers to the system, it may be necessary to rebuild the initial ramdisk (initrd) to contain the proper kernel modules to access these devices. After adding the proper line to the modules.conf (Red Hat Enterprise Linux 2.1 or 3) or modprobe.conf (Red Hat Enterprise Linux 4 or 5) file, execute these commands to rebuild the initial ramdisk:
# cp /boot/initrd-(kernel-version).img /boot/initrd-(kernel-version).img.bak
# mkinitrd -f initrd-$(uname -r).img $(uname -r)
For example:
# cp /boot/initrd-2.4.21-27.0.2.ELsmp.img /boot/initrd-2.4.21-27.0.2.ELsmp.img.bak
# mkinitrd -v -f /boot/initrd-2.4.21-27.0.2.ELsmp.img 2.4.21-27.0.2.ELsmp
This example rebuilds the ramdisk for a system running the 2.4.21-27.0.2 SMP kernel. Adjust the mkinitrd command as necessary to match the kernel version running on your machine or use uname -r as shown above.
* The -v verbose flag causes mkinitrd to display the names of all the modules it is including in the initial ramdisk.
* The -f option will force an overwrite of any existing initial ramdisk image for this kernel.
Note: This method has been known to fail with the ICH7 SATA chipset. Check for Linux supported drivers prior to rebuilding it.
Note: We recommend making a backup of the existing initrd img file in /boot for the current kernel if unsure of the stability or configuration of the new module before issuing the mkinitrd command:
# cp /boot/initrd-(kernel-version).img /boot/initrd-(kernel-version).img.bak
Optional: It is possible to create a separate entry in /boot/grub/grub.conf for the backup initial ramdisk image, to conveniently choose the old version at boot time without needing to restore the backup. This example configuration allows selection of either the new or old initial ramdisk image from the grub menu:
title Red Hat Enterprise Linux AS (2.4.21-27.0.2.ELsmp)
root (hd0,0)
kernel /vmlinuz-2.4.21-27.0.2.EL ro root=LABEL=/
initrd /initrd-2.4.21-27.0.2.EL.img
title Backup initrd (2.4.21-27.0.2.ELsmp)
root (hd0,0)
kernel /vmlinuz-2.4.21-27.0.2.EL ro root=LABEL=/
initrd /initrd-2.4.21-27.0.2.EL.img.bak
End
###
Regarding the RedHat licence we have paid over 2200USD but once we asked to help them they said following,
"The Red Hat Enterprise Linux (RHEL) Extended Life Cycle Support (ELS) offering provides an extension to the Production III Life Cycle Phase, allowing to continue to use a specific version of Red Hat Enterprise Linux beyond the end of its regular 7-year life cycle".
The thing is our management won't agree paying additional fee to get this thing work
.
But they asked to provide a report called "sysreport". Will put it here if someone interested,
Here is the link -
https://access.redhat.com/kb/docs/DOC-2873 (You need to log in to RedHat.com in order to access)
Here is how you do it,
Start
#####
Issue
If your system is not bootable, it may be possible to collect useful system troubleshooting information through sysreport. In this event, a Red Hat Technician may request a user to provide the results of sysreport.
Environment
Red Hat Enterprise Linux 2.1 and higher.
Resolution
To generate the sysreport / sosreport output from the rescue environment, boot the system with the installation disc of the corresponding version of Red Hat Enterprise Linux and follow this procedure:
1. Enter linux rescue into the boot prompt.
2. Once the rescue environment finishes booting, choose a language to use.
3. Choose a keyboard layout to use.
4. Wait for network interfaces to be located, and activate them, so that requested data can be transferred to another host.
5. The rescue environment will try to find the current Red Hat Enterprise Linux installation on the system. You will be prompted with the following options:
* "Continue": continue mounting all of its partitions under /mnt/sysimage/ in Read & Write mode
* "Read-Only": continue mounting all of its partitions under /mnt/sysimage/ in Read Only mode
* "Skip" : skip the mounting of the discovered Red Hat Enterprise Linux installation and proceed with manual mounting to generate a sysreport, choose "Continue". You will be presented with a shell prompt.
6. Run the following commands to continue generating sysreport / sosreport:
# chroot /mnt/sysimage
Then, if your system is running RHEL 4.5 or lower:
# sysreport
If your system is running RHEL 4.6 or higher:
# sosreport
If you are running RHEL 4.6 or higher, and the sosreport command fails, you can try the sysreport command, as it should still be available. Note that this command will not be available on RHEL 5 systems.
The sysreport / sosreport command can take some time to generate a report. It collects a significant amount of information that may help Red Hat technicians resolve your issue.
7. Once sysreport / sosreport generation completes, it will provide the output in the /tmp directory while the user is in the chroot environment. Exit the chroot environment and locate the sysreport / sosreport generated in the /mnt/sysimage/tmp directory.
Warning: During the running of the command sysreport / sosreport you will be prompted for your name and case number. Use only letters and/or numbers when filling out this field. Adding other characters could damage the system or render the report unusable.
End
###
