Sponsored Content
Operating Systems Linux Red Hat No VolGroup00 found after restart of the system Post 303012331 by Anjan Ganguly on Friday 2nd of February 2018 08:24:33 AM
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

 

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
MKRESCUE(8)						      System Manager's Manual						       MKRESCUE(8)

NAME
mkrescue - make rescue floppy or CD SYNOPSIS
/sbin/mkrescue makes a bootable rescue floppy or CD using the default kernel specified in lilo.conf. DESCRIPTION
mkrescue takes its specifation for the kernel from the default image specified in /etc/lilo.conf. If the actual default is an other= spec- ification, then use the first image= specification. Any associated initial ramdisk (initrd=), and append= options will also be used. The root directory will be taken to be the current root. A bootable floppy or CD-image will be created using LILO version 22.5.5 or later. mkrescue normally requires no options, unless a CD-image is desired (--iso). OPTIONS
--append <string> Override any append= options taken from the default image. If there is any doubt about whether the lilo.conf options are correct, then specify no kernel parameters by providing the null string (--append ""). --debug Provide verbose output of the operation of mkrescue, pausing to allow the setting of internal operating parameters to be viewed. <CR> must be hit to proceed from these pauses. --device <device> Make the floppy on a device other than /dev/fd0. The floppy disk will always be made to boot on BIOS device code 0x00 (A: drive), without regard to the drive on which it is created. --fast Use a faster method of creating the boot floppy. This involves first creating a file of --size 1k blocks (default is 1440) mounted using a loopback device, creating the bootable floppy, then copying the entire file to the disk. --fs [ ext2 | msdos | minix ] Specify the type of filesystem to create on the drive. ext2 is the default, but msdos and minix allow slightly more disk sectors for really big kernels. --help Print a short usage synopsis, including a list of command options. --image <label> Specifies the label or alias of the particular image from which the append, initial ramdisk, root, keytable, and kernel information is to be taken. --initrd <filepath> and --kernel <filepath> These options, which must be used together, allow specification of an arbitrary kernel file and initial ramdisk file to be used on the created boot floppy. Be sure you know what you are doing before you use these options. If no inital ramdisk is needed with a particular kernel, then you MUST specify --initrd "", meaning a null pathname. --install [ text | menu ] Allows overriding the default human interface used with the rescue bootloader (configuration file "install=" option). text is the default on 1.2MB and 1.44MB floppy disks, and menu is the default on 2.88MB floppies and HD emulation on CD-R media. --iso Create an ISO-9660 bootable CD image (El Torito Format) suitable for burning to a CD-R or CD-RW. The --device specification defaults to the filename rescue.iso, and the --size defaults to 2880. A utility such as "wodim" may be used to burn the ISO file to a recordable CD medium. With this ISO option, the --size HD option is allowed. --nocompact For faster kernel loading from a floppy, LILO map compaction is normally enabled. This option will disable map compaction by omit- ting the lilo -c switch. --noformat Suppresses creation of a new filesystem on the boot floppy. This option may be used ONLY when you know that the floppy you will be writing upon is formatted with the same filesystem as specified by --fs XXX (default is ext2). --root <device> Specify the root filesystem for the kernel on the boot floppy. The currently mounted root is taken as the default specification. --size [ 1440 | 1200 | 2880 | HD ] The default floppy disk size is 1440, meaning a 1.44MB floppy. When --iso is specified, the default size is 2880. Allowed specifi- cations are 1200, 1440, or 2880, meaning a 1.2MB, 1.44MB or 2.88MB floppy, respectively. No other floppy disk sizes are supported. The HD specification, meaning "hard disk", may only be used with the --iso option, to indicate a 16MB hard disk is to be generated for emulation. This allows for very large kernel/initial ramdisk combinations on CD-R. The hard disk image is created using loop- back devices /dev/loop0 and /dev/loop1, which must be free to utilize this size option. --version Print the version number of mkrescue, then terminate. SEE ALSO
cdrecord(1), dd(1), wodim(1), lilo.conf(5), lilo(8), mkfs(8), mkinitrd(8), mkisofs(8), mount(8) 6 Mar 2011 MKRESCUE(8)
All times are GMT -4. The time now is 04:29 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy