I am facing the following issue after giving a restart (init 6) of my RHEL 5.9 system.
As a result,the system is not starting after a restart.
Can somebody help me to trouble shoot the issue.
Red Hat nash version 5.1.19.6 starting
Reading all physical volumes. This may take a while...
No volume groups found
Volume group "VolGroup00" not found
Volume group "myvolumegroup" not found
Unable to access resume device (UUID= "some Hex code ID)
mount: could not find filesystem '/dev/root'
setuproot: moving /dev failed: No such file or directory
setuproot: error mounting /proc: No such file or directory
setuproot: error mounting /sys: No such file or directory
switchroot: mount failed: No such file or directory
Kernel panic - not syncing: Attempted to kill init!
---
Kernel alive
Kernel direct mapping tables up to 103ffff000 @10000-52000
Okay, so this is going to be difficult. I suppose knowing what was happening to disk partitions between the previous boot and this one will be key.
Can you boot into single user from external media? That would let us examine the disks you have at least. It's almost as though the devices have been ungracefully dropped.
How much can you tell us?
Can we see the output for fdisk -l for the affected disk perhaps?
Everything else is just a consequence of that. It seems that your system has lost touch with the hard disk(s) once attached to it. Reasons could be (the list is not exhaustive):
disk(s) have been removed physically
adapter(s) to which the disk(s) is/are attached is/are removed/broken
if disks are LUNs the zoning has been changed
and many reasons more. Can you tell us how your system was built (hardware-wise) so that we can narrow the possible reasons down?
We have gone to rescue mode and typed rescue#fdisk -l
It is showing nothing.
Can you tell how to boot into single user from external media as you mentioned in your reply.
---------- Post updated at 08:24 AM ---------- Previous update was at 08:20 AM ----------
Also while going to rescue mode (from RHEL ISO CD) , an error occurred.It says
Take an unused USB-stick (or one which data you do not need any more) and create a "live system" with it. You can use "unetbootin" or any similar tool, you can even do it with dd , there are thousands of how-tos in the internet, search for "create bootable USB stick linux".
Then put this stick into the system in question and boot from there. You may need to configure the BIOS accordingly so that it uses the USB stick to boot from.
On further digging on the same, I found that Kernel initrd-2.6.18-348.el5.img
is modified while upgrading BackupAndRecoveryAgent-11.5 to BackupAndRecoveryAgent-11.7 in RHEL 5.9 servers. I have 4 such identical servers. Initrd is modified in 3 servers with dates of January 2018 and on the same date and time BackupAndRecoveryAgent-11.7 is installed by some other person.In 1 server I found Initrd is not modified and it is of old date in /boot directory. Out of 3 servers where Initrd is of latest date, 1 server is given a restart and it did not rebooted. Now I am in soup and do not know how to come out from this situation
Is there any way to recover/repair the Initrd? I have seen in the 2 servres (out of 3 where Initrd is modified)system that there is a file initrd-2.6.18-348.el5.img_dup_original of older date and I guess that this is the correct file priror to updation of BackupAndRecoveryAgent. So can I revert it back from there? And what for the system for which I have already given a restart and that is not rebooting?
If you need to edit/modify/restore a hard disk root filesystem (that will not boot) the standard approach is to boot from DVD (typically a 'live' version), then mount the hard disk root filesystem on a DVD mountpoint so that you can 'cd' to the hard disk and make the changes you want and/or restore files.