03-05-2019
Has this box been abruptly powered off (power failure or kernel panic ?)
That would be the reason for error regarding journal recovery.
Course of action would be to boot rescue / live, active the root volume group and run a fsck on root logical volume.
Or do a clean reboot, and it should run fsck automatically during boot.
As for the error in the first post, well, looks like data and catalog directories of <insert application> exist, so you need to delete those before rerun.
Hope that helps
Regards
Peasant.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
i am a newbie to unix admin stuff so bare with me. -- i get this message when executing mysql_install_db during the installation of mysql. what is the cause of this and how can it be fixed. btw - i have tried installing as root and other accounts also.
scripts/mysql_install_db:... (6 Replies)
Discussion started by: theDirtiest
6 Replies
2. UNIX for Dummies Questions & Answers
Hi There,
I'm trying to install LyX 1.4.3 on a machine running Redhat 7.3. I can't upgrade the OS since I don't have root, but I've been given permission to install sw into pkgs by the Sys Admins.
./configure using the Qt frontend worked, but when I then enter make I get:
make: Entering... (3 Replies)
Discussion started by: dirgni
3 Replies
3. Red Hat
Dear All I want to configure DNS in redhat linux. i am following these steps but when i restart the services it is showing status failed. Please any body can help me on urgent basis.
#service named restart
Stopping named:
Starting named:
---------Edited in named.conf... (2 Replies)
Discussion started by: sahu.tapan
2 Replies
4. HP-UX
Hi,
I'm new to HP-UX.
I have LVM on /var with 92Gig. I would like to reduce it to create another LVM for Oracle client with 800 meg or so. How to do it. I'm running 11.iv3
Thanks (4 Replies)
Discussion started by: lamoul
4 Replies
5. Red Hat
Hi Expert,
I am trying to restart automount as it's consume much CPU.
Tasks: 2392 total, 7 running, 2352 sleeping, 25 stopped, 8 zombie Cpu(s): 9.3% us, 28.5% sy, 0.0% ni, 61.5% id, 0.2% wa, 0.2% hi, 0.2% si Mem: 15799928k total, 11029764k used, 4770164k free, 162424k buffers Swap: 22773752k... (2 Replies)
Discussion started by: regmaster
2 Replies
6. Red Hat
hi all ,
I'm trying for the Red-hat cluster setup with the ' Enable shared storage support'. But hang up with a error that
"Packages of set "Clustered Storage" are not present in any available repository". I made this setup by installing the rpm manually..I ve attached the rpm list and error... (0 Replies)
Discussion started by: sriniv666
0 Replies
7. UNIX for Dummies Questions & Answers
Hi Guys,
I m using redhat 6, I have installed root partition as non-LVM .
Is there any way i can convert it to LVM? (1 Reply)
Discussion started by: pinga123
1 Replies
8. UNIX for Dummies Questions & Answers
i have several lv (data , data1 , data2) under same volume group,
i just want to test 1 lv for data errors is that possible?
this test all sdc disk , but i just want to test lv_data
smartctl -a /dev/sdc
because lv_data2 is corrupt , but i don't know if this lv uses sdc disk (1 Reply)
Discussion started by: prpkrk
1 Replies
9. UNIX for Advanced & Expert Users
Hi,
I am having a text file with the following contents
###########
File1
###########
some
page1.txt
text
page.txt
When I sort this file on Red Hat 5, then I get the following output
###########
File1
###########
page1.txt
page.txt
some (3 Replies)
Discussion started by: sarbjit
3 Replies
10. Red Hat
Dear all,
I am reciving the following error in the /var/log/messages of my system
Jul 18 11:14:27 airtest xinetd: START: echo-dgram pid=0 from=::ffff:XX.XX.XX.X
Jul 18 11:14:27 airtest xinetd: START: echo-dgram pid=0 from=::ffff:XX.XX.XX.X
Jul 18 11:19:17 airtest xinetd: START: echo-dgram... (1 Reply)
Discussion started by: pistachio
1 Replies
LEARN ABOUT HPUX
vx_emerg_start
vx_emerg_start(1M) vx_emerg_start(1M)
NAME
vx_emerg_start - start Veritas Volume Manager from recovery media
SYNOPSIS
vx_emerg_start [-m] [-r root_daname] hostname
DESCRIPTION
The vx_emerg_start utility can be used to start Veritas Volume Manager (VxVM) when a system is booted from alternate media, or when a sys-
tem has been booted into Maintenance Mode Boot (MMB) mode. This allows a rootable VxVM configuration to be repaired in the event of a cat-
astrophic failure.
vx_emerg_start verifies that the /etc/vx/volboot file exists, and checks the command-line arguments against the contents of this file.
OPTIONS
-m Mounts the root file system contained on the rootvol volume after VxVM has been started. Prior to being mounted, the rootvol volume
is started and fsck is run on the root file system.
-r root_daname
Specifies the disk access name of one of the members of the root disk group that is to be imported. This option can be used to spec-
ify the appropriate root disk group when multiple generations of the same root disk group exist on the system under repair. If this
option is not specified, the desired root disk group may not be imported if multiple disk groups with the same name exist on the sys-
tem, and if one of these disk groups has a more recent timestamp.
ARGUMENTS
hostname
Specifies the system name (nodename) of the host system being repaired. This name is used to allow the desired root disk group to be
imported. It must match the name of the system being repaired, as it is unlikely to be recorded on the recovery media from which you
booted the system.
NOTES
HP-UX Maintenance Mode Boot (MMB) is intended for recovery from catastrophic failures that have prevented the target machine from booting.
If a VxVM root volume is mirrored, only one mirror is active when the system is in MMB mode. Any writes that are made to the root file sys-
tem in this mode can corrupt this file system when both mirrors are subsequently configured.
The vx_emerg_start script allows VxVM to be started while a system is in MMB mode, and marks the non-boot mirror plexes as stale. This
prevents corruption of the root volume or file system by forcing a subsequent recovery from the boot mirror to the non-boot mirrors to take
place.
USAGE
After VxVM has been started, various recovery options can be performed depending on the nature of the problem. It is recommended that you
use the vxprint command to determine the state of the configuration.
One common problem is when all the plexes of the root disk are stale as shown in the following sample output from vxprint:
v rootvol root DISABLED 393216 - ACTIVE -
pl rootvol-01 rootvol DISABLED 393216 - STALE -
sd rootdisk01-02 rootvol-01 ENABLED 393216 0 - -
pl rootvol-02 rootvol DISABLED 393216 - STALE -
pl rootvol-02 rootvol DISABLED 393216 - STALE -
sd rootdisk02-02 rootvol-02 ENABLED 393216 0 - -
In this case, the volume can usually be repaired by using the vxvol command as shown here:
vxvol -g 4.1ROOT -f start rootvol
If the volume is mirrored, it is put in read-write-back recovery mode. As the command is run in the foreground, it does not exit until the
recovery is complete. It is then recommended that you run fsck on the root file system, and mount it, before attempting to reboot the sys-
tem:
fsck -F vxfs -o full /dev/vx/rdsk/4.1ROOT/rootvol
mkdir /tmp_mnt
mount -F vxfs /dev/vx/dsk/4.1ROOT/rootvol /tmp_mnt
SEE ALSO
fsck(1M), mkdir(1M), mount(1M), vxintro(1M), vxprint(1M), vxvol(1M)
VxVM 5.0.31.1 24 Mar 2008 vx_emerg_start(1M)