01-17-2013
Quote:
Originally Posted by
thecobra151
my friend is restarting the system in this case can be a sloution
This might help, but is not guaranteed to work. When the system restarts it runs "cfgmgr" in mode 1, which isn't possible at any other time. This might correct any inconsistencies in the ODM if this is indeed the cause - it was just a guess of mine, although the most probable reason for the behavior you describe.
If it doesn't work and the problem is indeed the ODM you might need to correct it otherwise. Take a "mksysb" backup and restore it to another - identic - system to a fresh disk, then try to boot from this disk. (You have not told us so far, but i am assuming this is an ordinary LPAR, nothing anything fancy?)
I hope this helps.
bakunin
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
how can i determine that
what percentage of stack region is currently is used?
(i am using tru64 unix) (2 Replies)
Discussion started by: yakari
2 Replies
2. AIX
Dear All,
I have two h.disks.
Please advice for how to create a new folder/directory in hdisk1 instead of the hdisk0? I need to use the folder to store for xmlfiles for my application accessing to read it.
Thank a lots.
Best Regards,
Tom (3 Replies)
Discussion started by: lwy2020
3 Replies
3. Solaris
Hello experts,
I am using Veritas Volume Manager 5.0. How can i take private region backup and restoration.
thanks in advance... (3 Replies)
Discussion started by: younus_syed
3 Replies
4. UNIX for Advanced & Expert Users
Hello all,
I have a question about what you think the best practice is to determine what region you are running on when you have a system setup with a DEV/TEST, QA, and PROD regions running the same scripts in all.
So, when you run in DEV, you have a different directory structure, and you... (4 Replies)
Discussion started by: Rediranch
4 Replies
5. Programming
Hi guys,
I hope everybody is doing fine. I have written this small program which solves the critical region problem. Only on of the two threads can make changes to a common variable called counter. I am using two semaphores, is it possible to write the same program using only one semaphore? Here... (0 Replies)
Discussion started by: gabam
0 Replies
6. Shell Programming and Scripting
How can I find the regions between specific lines?
I have a file which contains lines like this:
chr1 0 17388 0
chr1 17388 17444 1
chr1 17444 17599 2
chr1 17599 17601 1
chr1 17601 569791 0
chr1 569791 569795 1
chr1 569795 569808 2
chr1 569808 569890 3
chr1 569890 570047 4 ... (9 Replies)
Discussion started by: linseyr
9 Replies
7. Shell Programming and Scripting
portsuf=25
port=20925
I need to replace 09 with 25
It should be like 22525.
Can some please help with command or script. (4 Replies)
Discussion started by: bhas85
4 Replies
8. Programming
Hello, I am trying to concatenate two strings by merging the overlapped region. E.g.
Seq1=ACGTGCCC
Seq2=CCCCCGTGTGTGT
Seq_merged=ACGTGCCCCCGTGTGTGTFunction strcat(char *dest, char *src) appends the src string to the dest string, ignoring the overlapped parts (prefix of src and suffix of dest).... (30 Replies)
Discussion started by: yifangt
30 Replies
9. UNIX for Dummies Questions & Answers
Hi,
I would like to know how can I get a mean score value by ID over a defined genomic region. Here it is an example:
file1
12 100 103 id1
12 110 112 id1
12 200 203 id2
file2
12 100 101 1
12 101 102 0.8
12 102 103 0.7
12 110 111 2.5
12 111 112 2.8
12 200 201 10.1
12 201 202... (7 Replies)
Discussion started by: fadista
7 Replies
10. AIX
Hello,
I have a P-series running AIX 5.3 and hdisk1 is failing.
hdisk0 and hdisk1 are mirrored rootvg.
My question is, I have an expansion cabinet that has two disks in it that I believe have never been used. I want to replace hdisk1 with one of the unused disks. (hdisk36 or hdisk37)
... (1 Reply)
Discussion started by: DanCampbell
1 Replies
LEARN ABOUT HPUX
bootconf
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)