Sponsored Content
Operating Systems Solaris OBP - root / mirror disk syntax Post 302339631 by Sun Fire on Friday 31st of July 2009 04:19:55 AM
Old 07-31-2009
It means that you're looking at the raw physical device itself...and this address is not to be used for booting. The device we use for booting is a link to the one you just printed.
 

9 More Discussions You Might Find Interesting

1. HP-UX

HP UX Disk Mirror

Being somewhat extremely new to Unix, I have just had a system crash One of my Volume Groups has crashed However, this Volume Group is actually mirrored How do I switch to use the mirrored copy? Any assistance greatly appreciated Thanks (1 Reply)
Discussion started by: cobdeng
1 Replies

2. UNIX for Dummies Questions & Answers

disk suite to mirror both d0 and d2

I have 2 drives on a sun solaris 8 server that is a live server. I am putting in an additional 2 drives and want to mirror the the first 2. I was thinking of using disksuite but one drive is the root drive with 1 maybe 2 free paritions. The other is only one partition (36G). I was wondering... (2 Replies)
Discussion started by: csgonan
2 Replies

3. AIX

How to remove disk from mirror?

Hello, I've got 2 system disks (hdisk0 and hdisk1) in the mirror (RAID1) on AIX 5.3. Since the hdisk1 makes some troubles, we want to replace it with the new one. How can I disable this hdisk1 disk and prepare the mirror to use the new physical disk? As far as I know, I must remove disk from the... (3 Replies)
Discussion started by: Yac
3 Replies

4. Solaris

Root Mirror is broken

Hi all, Root mirror is broken under veritas control. so could you please help me how to boot the system now step by step procedure. i really thankful to all. regards krishna (3 Replies)
Discussion started by: murthy76
3 Replies

5. Solaris

Mirror the root disk

Hi all I wish to mirror for the root disk, but last time i do, make the server cannot boot up. :p So this time, hope you guys can assist me on it. =) At the last code, is the step i wish to do. Please help to check and correct me if got any wrong. root@leo # format </dev/null Searching for... (17 Replies)
Discussion started by: SmartAntz
17 Replies

6. AIX

Clone or mirror your AIX OS larger disk to smaller disk ?

hello folks, I have a 300GB ROOTVG volume groups with one filesystem /backup having 200GB allocated space Now, I cannot alt disk clone or mirrorvg this hdisk with another smaller disk. The disk size has to be 300GB; I tried alt disk clone and mirrorvg , it doesn't work. you cannot copy LVs as... (9 Replies)
Discussion started by: filosophizer
9 Replies

7. HP-UX

What is the difference between DRD and Root Mirror Disk using LVM mirror ?

what is the difference between DRD and Root Mirror Disk using LVM mirror ? (3 Replies)
Discussion started by: maxim42
3 Replies

8. Solaris

How to detach root mirror pool?

I have to do patching in single user mode in solaris 10 zfs root pool. Before that I have to detach the root mirror pool so that if patching fails then I can boot from detached root mirror pool. Please let me know how can I detach root pool bash-3.2# zpool status pool: rpool state: ONLINE... (5 Replies)
Discussion started by: hb00
5 Replies

9. Solaris

Mirror root disk - V490

Got a V490 with one existing root disk. Other disk slot was never populated. Want to ensure we've got disk mirroring. Currently vfstab mounts the physical disk - no mirroring set up. Whats best way to achieve this without losing current disk? (1 Reply)
Discussion started by: psychocandy
1 Replies
prtconf(1M)                                                                                                                            prtconf(1M)

NAME
prtconf - print system configuration SYNOPSIS
/usr/sbin/prtconf [-V] | [-F] | [-x] | [-bpv] | [-acDPv] [dev_path] The prtconf command prints the system configuration information. The output includes the total amount of memory, and the configuration of system peripherals formatted as a device tree. If a device path is specified on the command line for those command options that can take a device path, prtconf will only display informa- tion for that device node. The following options are supported: -a Display all the ancestors device nodes, up to the root node of the device tree, for the device specified on the command line. -b Display the firmware device tree root properties for the purpose of platform identification. These properties are "name", "compat- ible", "banner-name" and "model". -c Display the device subtree rooted at the device node specified on the command line, that is, display all the children of the device node specified on the command line. -D For each system peripheral in the device tree, displays the name of the device driver used to manage the peripheral. -F Returns the device path name of the console frame buffer, if one exists. If there is no frame buffer, prtconf returns a non-zero exit code. This flag must be used by itself. It returns only the name of the console, frame buffer device or a non-zero exit code. For example, if the console frame buffer on a SUNW,Ultra-30 is ffb, the command returns: /SUNW,ffb@1e,0:ffb0. This option could be used to create a symlink for /dev/fb to the actual console device. -p Displays information derived from the device tree provided by the firmware (PROM) on SPARC platforms or the booting system on platforms.The device tree information displayed using this option is a snapshot of the initial configuration and may not accu- rately reflect reconfiguration events that occur later. -P Includes information about pseudo devices. By default, information regarding pseudo devices is omitted. -v Specifies verbose mode. -V Displays platform-dependent PROM (on SPARC platforms) or booting system (on platforms) version information. This flag must be used by itself. The output is a string. The format of the string is arbitrary and platform-dependent. -x Reports if the firmware on this system is 64-bit ready. Some existing platforms may need a firmware upgrade in order to run the 64-bit kernel. If the operation is not applicable to this platform or the firmware is already 64-bit ready, it exits silently with a return code of zero. If the operation is applicable to this platform and the firmware is not 64-bit ready, it displays a descriptive message on the standard output and exits with a non-zero return code. The hardware platform documentation contains more information about the platforms that may need a firmware upgrade in order to run the 64-bit kernel. This flag overrides all other flags and must be used by itself. The following operands are supported: dev_path The path to a target device minor node, device nexus node, or device link for which device node configuration information is displayed The following exit values are returned: 0 No error occurred. non-zero With the -F option (SPARC only), a non-zero return value means that the output device is not a frame buffer. With the -x option, a non-zero return value means that the firmware is not 64-bit ready. In all other cases, a non-zero return value means that an error occurred. See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWesu | +-----------------------------+-----------------------------+ |Interface Stability |Unstable | +-----------------------------+-----------------------------+ fuser(1M), modinfo(1M), sysdef(1M), attributes(5) Sun Hardware Platform Guide SPARC Only openprom(7D) The output of the prtconf command is highly dependent on the version of the PROM installed in the system. The output will be affected in potentially all circumstances. The driver not attached message means that no driver is currently attached to that instance of the device. In general, drivers are loaded and installed (and attached to hardware instances) on demand, and when needed, and may be uninstalled and unloaded when the device is not in use. On platforms, the use of prtconf -vp provides a subset of information from prtconf -v. The value of integer properties from prtconf -vp might require byte swapping for correct interpretation. 9 Aug 2005 prtconf(1M)
All times are GMT -4. The time now is 01:08 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy