Sponsored Content
Operating Systems Linux Red Hat No VolGroup00 found after restart of the system Post 303012315 by rbatte1 on Friday 2nd of February 2018 04:44:28 AM
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
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Bad PBR Sig Operating System Not Found...why ?

Well i install successfully Solaris on my Second Hard disk, although i had to make it primary Master and my orignal hard disk as pirmary slave, because solaris will not let Windows on primary master. Anyway after installation when i try to boot from hard disk , it shows message bad PBR Sig ... (3 Replies)
Discussion started by: abidmalik
3 Replies

2. AIX

Execute a command at the system restart

Hi Folks, I have an AIX server and I would like the server to run the command saprouter -r at every system restarts. It needs to be run by a specific user. How would I do that? Thanks!!! (1 Reply)
Discussion started by: brookingsd
1 Replies

3. Red Hat

RHEL4 Upt(2): Operating System Not Found ?

Hi, My HP-Proliant Machine have faced abnormal shutdown due to a power failure. after the event : "Operating System not found" appears & the system could not load operating system. O/S: RHEL AS 4 update 2 Software Raid 1+0 were configured. Facts Gathered: All mount points are... (1 Reply)
Discussion started by: Muhammad Ahmad
1 Replies

4. AIX

20EE0008 : No adapters found Adapter, Riser, System Bd.

Hello, When I try to upgrade AIX from 5.1 to 5.3 I get this error message 20EE0008 : No adapters found Adapter, Riser, System Bd. Anyone know anything about it ? (1 Reply)
Discussion started by: filosophizer
1 Replies

5. Solaris

The system (Solaris 8) has not found required fonts.

Hi guys and ladies! The application not found required fonts. I checked, the packages SUNWi5rf, SUNWi5of are installed. Then I checked availability the directories iso8859-5, iso8859_5 at /usr/openwin/lib/locale. I checked after that. % xlsfonts | grep "lucida-" The system showed only ... (0 Replies)
Discussion started by: wolfgang
0 Replies

6. UNIX for Advanced & Expert Users

Does inittab needs system restart?

Hi currently my linux instance is running in runlevel 3 ( someone has set the default to 3) i have to change it to runlevel 5 . my question 1) does the editing of /etc/inittab needs system restart to enter runlevel 5. 2) how can we avoid system restart because if some users are... (3 Replies)
Discussion started by: rakeshkumar
3 Replies

7. Linux

Rename VolGoup00 with active VolGroup00

I have a Xen VM guest image with a lost root password. In order to get to /etc/passwd and /etc/shadow I need to mount the filesystems within the image with everything but /boot is in a LVM partition. The VM host also have an LVM image, and both (host and guest) are called VolGroup00. I want to... (1 Reply)
Discussion started by: dokhebi
1 Replies

8. BSD

/etc/rc.d/named restart issue (command not found)

Guys, I am new to FreeBSD. I have this weird issue where when i issue the command "/etc/rc.d/named restart" i get --> command not found. I am running BIND 9.6.-ESV-R3 on FreeBSD 8.2 I have added named_enable="YES" in rc.conf as per manual named works great: No issue there. I just would like... (3 Replies)
Discussion started by: zongo
3 Replies

9. Solaris

Operating system not found

Hi, Iam trying to instal a solaris operating system in a vmware on my local windows system via an iso image named as "solaris10.vmx". but as soon as the vm console opens i get an error message as: "PXE-MOF: Exiting Intel PXE ROM. Operating system not found" Please help me out in... (3 Replies)
Discussion started by: Laxxi
3 Replies

10. AIX

ksh file not found error for various files across system

Our AIX system is currently having an issue where calls to various executables are returning errors such as ksh: /usr/bin/oslevel: not found. This is even happening with system files, third party scripts, and with the full path included. Telnet connections are also closing immediately upon... (6 Replies)
Discussion started by: Chthonic
6 Replies
bootconf(4)						     Kernel Interfaces Manual						       bootconf(4)

NAME
bootconf - boot device configuration table DESCRIPTION
The file contains the address and disk layout type of the system's boot devices or lif volumes. It is used by the and HP-UX kernel control scripts (fileset to determine how and where to update the initial boot loader. Normally the kernel's script queries the system's hardware and creates the file. In rare cases when either the system configuration cannot be automatically determined or additional and/or alternate boot devices should be automatically updated, the administrator must edit the file manually. There is one line in the file for each boot device. Each line contains the following blank-separated fields in the order shown: disk type A flag indicating how the file system(s) on the disk are laid out. The flag must be one of the following: Indicates that the root disk is in LVM or VERITAS Volume Manager (VxVM) format. If LVM or VxVM mirrors are used, then each of the "mirrors" must have its own line in the file. Indicates that the root disk is in the "whole disk" format with no partitions, but boot and swap space are reserved outside the file system. device file The absolute path of the device special file that accesses the physical device where the boot area is located. For LVM root disks, the device special file is the physical volume(s) returned by the command. For "whole disks" this is the device file that references the entire disk. Blank lines are permitted. Any line beginning with a is considered to be a comment. DIAGNOSTICS
The Software Distributor log file contains diagnostic messages under the fileset if the file is incorrect. Most of the messages are self- explanatory; a few warrant additional explanation: If there are no other messages about the file is probably empty. Otherwise, the file is not in the proper format, and the other messages will explain what the problem is. The specified device file does not point to a disk where there is a lif which contains the file Some character other than or is in the first field of a line. As of release 10.0, the boot areas in must all be on the same type of disk layout. There are characters after the device file specification. EXAMPLES
The boot area is on an LVM root disk: l /dev/disk/disk7_p2 The boot area is on a whole disk layout: w /dev/disk/disk7 WARNINGS
All of the boot devices in the file must have the same disk layout. AUTHOR
was developed by the Hewlett-Packard Company. FILES
SEE ALSO
mediainit(1), hpux(1M), hpux.efi(1M), mkboot(1M), vgdisplay(1M), lif(4), intro(7). documentation. bootconf(4)
All times are GMT -4. The time now is 09:53 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy