Sponsored Content
Full Discussion: metainit error
Operating Systems Solaris metainit error Post 54600 by s93366 on Thursday 19th of August 2004 04:11:41 AM
Old 08-19-2004
check the /etc/system file
and remove any forceload: misc/md_*

I think that should do the trick..

/petrer
 

10 More Discussions You Might Find Interesting

1. Solaris

metainit gives coredump

SunOS unknown 5.9 Generic_118558-10 sun4u sparc SUNW,Sun-Fire-880 I'm trying to set up mirroring and am running into a problem: As you can see, I set up the metadb, but am getting a coredump when running metainit. I saw this through google, but don't know the validity of it. Any ideas? #... (5 Replies)
Discussion started by: dangral
5 Replies

2. UNIX for Dummies Questions & Answers

Error: Internal system error: Unable to initialize standard output file

Hey guys, need some help. Running AIX Version 5.2 and one of our cron jobs is writing errors to a log file. Any ideas on the following error message. Error: Internal system error: Unable to initialize standard output file I'm guessing more info might be needed, so let me know. Thanks (2 Replies)
Discussion started by: firkus
2 Replies

3. UNIX for Dummies Questions & Answers

awk Shell Script error : "Syntax Error : `Split' unexpected

hi there i write one awk script file in shell programing the code is related to dd/mm/yy to month, day year format but i get an error please can anybody help me out in this problem ?????? i give my code here including error awk ` # date-month -- convert mm/dd/yy to month day,... (2 Replies)
Discussion started by: Herry
2 Replies

4. AIX

nim mksysb error :/usr/bin/savevg[33]: 1016,07: syntax error

-------------------------------------------------------------------------------- Hello, help me please. I am trying to create a mksysb bakup using nim. I am geting this error, how to correct it ? : Command : failed stdout: yes stderr: no... (9 Replies)
Discussion started by: astjen
9 Replies

5. Solaris

Metainit issue

Hi all, After setting up SUN cluster in two nodes, I created disksets and volumes in the servers. Everything wwas working well and perfect. Today, I created a diskset and added three disks to it. When trying to create a volume, I am getting the following error: lsun3175 /dev/rdsk->... (4 Replies)
Discussion started by: manojsomanath
4 Replies

6. UNIX for Dummies Questions & Answers

> 5 ")syntax error: operand expected (error token is " error

im kinda new to shell scripting so i need some help i try to run this script and get the error code > 5 ")syntax error: operand expected (error token is " the code for the script is #!/bin/sh # # script to see if the given value is correct # # Define errors ER_AF=86 # Var is... (4 Replies)
Discussion started by: metal005
4 Replies

7. Solaris

metainit: Sol10: there are no existing databases

Hi Experts, I am in direction to mirror filesystem in solaris10. Many articles I've read but not much help. Everytime I issued command metainit I always get 'there are no existing databases'. I don't know which steps I missed. bash-3.2# metainit -f d11 1 1 c0t0d0s0 metainit: Sol10: there are... (3 Replies)
Discussion started by: Fandy Abdul
3 Replies

8. Solaris

Rpcinfo: can't contact portmapper: RPC: Authentication error; why = Failed (unspecified error)

I have two servers with a fresh install of Solaris 11, and having problems when doing rpcinfo between them. There is no firewall involved, so everything should theoretically be getting through. Does anyone have any ideas? I did a lot of Google searches, and haven't found a working solution yet. ... (2 Replies)
Discussion started by: christr
2 Replies

9. Solaris

Solaris 8 metainit space issue

I am trying to create soft partition metaclear -r d109 metainit d109 -p d100 -o 178423817 -b 33554432 After i did this i saw the df -k /dev/md/dsk/d109 0 779600337 0 0% /test df -k shows that it is full? also i have tried adding no logging entry in /etc/vfstab... (0 Replies)
Discussion started by: gull05
0 Replies

10. UNIX for Beginners Questions & Answers

Print Error in Console and both Error & Output in Log file - UNIX

I am writing a shell script with 2 run time arguments. During the execution if i got any error, then it needs to redirected to a error file and in console. Also both error and output to be redirected to a log file. But i am facing the below error. #! /bin/sh errExit () { errMsg=`cat... (1 Reply)
Discussion started by: sarathy_a35
1 Replies
obpsym(1M)						  System Administration Commands						obpsym(1M)

NAME
obpsym - Kernel Symbolic Debugging for OpenBoot Firmware SYNOPSIS
modload -p misc/obpsym DESCRIPTION
obpsym is a kernel module that installs OpenBoot callback handlers that provide kernel symbol information to OpenBoot. OpenBoot firmware user interface commands use the callbacks to convert numeric addresses to kernel symbol names for display purposes, and to convert kernel symbol names to numeric literals allowing symbolic names to be used as input arguments to user interface commands. Once obpsym is installed, kernel symbolic names may be used anywhere at the OpenBoot firmware's user interface command prompt in place of a literal (numeric) string. For example, if obpsym is installed, the OpenBoot firmware commands ctrace and dis typically display symbolic names and offsets in the form modname:symbolname + offset. User interface Commands such as dis can be given a kernel symbolic name such as ufs:ufs_mount instead of a numeric address. Placing the command forceload: misc/obpsym into the system(4) file forces the kernel module misc/obpsym to be loaded and activates the kernel callbacks during the kernel startup sequence. obpsym may be useful as a kernel debugger in situations where other kernel debuggers are not useful. For example, on SPARC machines, if obpsym is loaded, you may be able to use the OpenBoot firmware's ctrace command to display symbolic names in the stack backtrace after a watchdog reset. Kernel Symbolic Name Syntax The syntax for a kernel symbolic name is: [ module-name : ] symbol-name Where module-name is the name of the kernel module that the symbol symbol-name appears in. A NULL module name is taken as "all modules, in no particular order" by obpsym. The module name unix is equivalent to a NULL module name, so that conflicts with words defined in the firmware's vocabulary can be avoided. Typically, OpenBoot firmware reads a word from the input stream and looks the word up in its internal vocabulary before checking if the word is a literal. Thus, kernel symbols, such as reset may be given as unix:reset to avoid the unexpected side effect of the firmware find- ing and executing a matching word in its vocabulary. FILES
/etc/system system configuration information file /platform/platform-name/kernel/misc/obpsym ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWcar | +-----------------------------+-----------------------------+ SEE ALSO
kadb(1M), kernel(1M), modload(1M), modunload(1M), uname(1), system(4), attributes(5) OpenBoot 2.x Command Reference Manual WARNINGS
Some OpenBoot firmware user interface commands may use system resources incompatibly with the way they are used by the Unix kernel. These commands and the use of this feature as a kernel debugger may cause interactions that the Unix kernel is not prepared to deal with. If this occurs, the Unix kernel and/or the OpenBoot firmware user interface commands may react unpredictably and may panic the system, or may hang or may cause other unpredictable results. For these reasons, the use of this feature is only minimally supported and recommended to be used only as a kernel debugger of "last resort". If a breakpoint or watchpoint is triggered while the console frame buffer is powered off, the system can crash and be left in a state from which it is difficult to recover. If one of these is triggered while the monitor is powered off, you will not be able to see the debugger output. NOTES
platform-name can be found using the -i option of uname(1) obpsym is supported only on architectures that support OpenBoot firmware. On some systems, OpenBoot must be completely RAM resident so the obpsym symbol callback support can be added to the firmware, if the firmware doesn't include support for the symbol callbacks. On these systems, obpsym may complain that it requires that "you must use ram- forth to use this module". See the OpenBoot 2.x Command Reference Manual for details on how to use the ramforth command, how to place the command into nvramrc, and how to set use-nvramrc? to true. On systems with version 1.x OpenBoot firmware, nvramrc doesn't exist, and the ramforth command must be typed manually after each reset, in order to use this module. Once installed, the symbol table callbacks can be disabled by using the following OpenBoot firmware command: 0 0 set-symbol-lookup SunOS 5.10 13 Dec 2001 obpsym(1M)
All times are GMT -4. The time now is 10:58 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy