No VolGroup00 found after restart of the system


Login or Register to Reply

 
Thread Tools Search this Thread
# 1  
Old 02-02-2018
No VolGroup00 found after restart of the system

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.

Code:
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

# 2  
Old 02-02-2018
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?




Robin
# 3  
Old 02-02-2018
This is the root cause of your problem:

Quote:
Originally Posted by Anjan Ganguly
Code:
Red Hat nash version 5.1.19.6 starting
  Reading all physical volumes.  This may take a while...
  No volume groups found

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?

I hope this helps.

bakunin
# 4  
Old 02-02-2018
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
Code:
 Unable to mount filesystem /mnt/sysimage

# 5  
Old 02-02-2018
Quote:
Originally Posted by Anjan Ganguly
Can you tell how to boot into single user from external media as you mentioned in your reply.
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.

I hope this helps.

bakunin
# 6  
Old 02-03-2018
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?
# 7  
Old 02-03-2018
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.
Login or Register to Reply

|
Thread Tools Search this Thread
Search this Thread:
Advanced Search

More UNIX and Linux Forum Topics You Might Find Helpful
Cloning a system via mksysb backup from one system and restore to new system gull05 AIX 4 03-13-2016 04:02 PM
ksh file not found error for various files across system Chthonic AIX 6 03-19-2014 11:26 AM
Operating system not found Laxxi Solaris 3 01-04-2013 10:46 AM
/etc/rc.d/named restart issue (command not found) zongo BSD 3 11-27-2011 08:38 AM
Rename VolGoup00 with active VolGroup00 dokhebi Linux 1 09-24-2011 09:07 PM
Does inittab needs system restart? rakeshkumar UNIX for Advanced & Expert Users 3 06-08-2011 10:23 AM
Restart SMSPI hedkandi Red Hat 2 04-06-2010 03:09 AM
The system (Solaris 8) has not found required fonts. wolfgang Solaris 0 02-08-2010 03:59 AM
20EE0008 : No adapters found Adapter, Riser, System Bd. filosophizer AIX 1 05-21-2009 08:12 PM
How to prevent grep command from throwing a system trap if No match is found. cool.aquarian UNIX for Advanced & Expert Users 2 01-08-2009 01:42 PM
RHEL4 Upt(2): Operating System Not Found ? Muhammad Ahmad Red Hat 1 05-10-2007 10:42 PM
how can i check in csh if command found or not found ? umen Shell Programming and Scripting 2 03-03-2007 07:38 PM
Execute a command at the system restart brookingsd AIX 1 03-17-2006 11:26 AM
Bad PBR Sig Operating System Not Found...why ? abidmalik UNIX for Dummies Questions & Answers 3 12-16-2002 05:46 PM