Sponsored Content
Operating Systems Solaris System is stuck at the OK prompt Post 302750313 by Martincorneuk on Monday 31st of December 2012 12:00:57 PM
Old 12-31-2012
Quote:
Originally Posted by bluridge

The last file executed before the system boots up is /etc/inittab so does that mean the boot block was successfully executed if I coem to the ok prompt?
I'm no genius but..... Your machine would come to the ok> prompt with no disks in it.... OBP sits beneath the OS and is totally independant of it so the bootblk isn't a factor in getting to the ok> .... :0/

What are you using to mirror the disks SDS/SVM or VxVM?

By rights there should be no need to break the mirrors neatly.... The whole point of mirroring them is to protect against a catestrophic failure in a disk.... Which you would have created by pulling one of them.... I'd have thought both should be bootable, you need to be absolutely sure the boot paths for rootdisk & rootmirror are correct, it's easy to miss a slice or somesuch....

Martin
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

wiping system from ok prompt

So last week I posted about my system that will not completely boot. It reports a bad trap and reboots in an endless cycle. I'm at a point where I just want to wipe the system clean, reload the software and basically start from scratch. I can interrupt the boot cycle and get to an ok prompt.... (2 Replies)
Discussion started by: forbin24
2 Replies

2. Solaris

system get stuck on stand by mode

Hi Im using a Sun blade 1500 with solaris 8 and when the monitor goes to stand by mode, the machine doesnt return to the normal mode anymore. Then i have to reboot it always. Does anybody have a clue how can i solve it or turn off the stand by mode? Thanks (2 Replies)
Discussion started by: dougpss
2 Replies

3. UNIX for Dummies Questions & Answers

System Specs in OK Prompt

Hello to all! In the OK prompt, which command should I use to see RAM memory, CPU, and disks partition and capacity? I have in my hands an ancient Ultra5 machine, which Im trying to install Solaris, but don't know if the configuration is the original one. Thanks! (4 Replies)
Discussion started by: Pablo_BR
4 Replies

4. Programming

I'm stuck :(

Suppose that I have some data: 12,30 12,45 2,3 7,8 3,9 30, 8 45,54 56,65 Where (a,b) indicates that a is connected to b. I want to get all connected nodes to one point. For instance, the output of the above example should be something like: Group 1 2,3 3,9 Group 2 12,30 12,45... (4 Replies)
Discussion started by: Legend986
4 Replies

5. Solaris

system won't start to GUI it stuck

Hi. I got this message in our sun station and it stuck Setting default IPv4 interface for multicast: add net 224.0/4: gateway pecsun22 but i can still telenet the station... who could i fix this.. appreciate your help (7 Replies)
Discussion started by: eykyn17
7 Replies

6. Solaris

How to change the system prompt and BG of terminal?

Hi all, I was wondering how to change the PS1 to my liking? I tried changing it using PS1='my choice' it worked but the subsequent terminals i open will not have it as the default PS1 ,how do i change it? also i am running as super user, and i need to exec bash, to get the bash environment...... (4 Replies)
Discussion started by: wrapster
4 Replies

7. Solaris

Can't bring E25K system controller to OK prompt

Hi, Due to some changes at our company, we lost the password for the root and sms-svc account on the primary system controller (E25K). We connected a serial console to the system controller but we never managed to break the session to bring it to the OK prompt. (tried: ~#, ~ b, ~, , a b,... (9 Replies)
Discussion started by: Solarius
9 Replies

8. Solaris

System stuck up in maintanence mode

Hi All, I got a big problem here. While setting up a sun cluster, I accidentally tried out "bootadm update-archive" as I was unable to bring the cluster up. After which, i tried a reconfiguration reboot. Now The system is always booting into maintanence mode with error message... (8 Replies)
Discussion started by: manojsomanath
8 Replies

9. UNIX for Dummies Questions & Answers

How to Change the % prompt to - prompt in UNIX?

how to Change the % prompt to - prompt in unix :wall: ---------- Post updated at 07:40 AM ---------- Previous update was at 07:38 AM ---------- How To display the last modification time of any file in unix ---------- Post updated at 07:40 AM ---------- Previous update was at 07:40 AM... (2 Replies)
Discussion started by: manjiri sawant
2 Replies

10. Solaris

Unable to move from rsc prompt to ok prompt

Hi, on sunfire v890 unable to move from rsc prompt to ok prompt, i have executed the command break. (9 Replies)
Discussion started by: manoj.solaris
9 Replies
voldiskadd(8)						      System Manager's Manual						     voldiskadd(8)

NAME
voldiskadd - Adds one or more disks for use with the Logical Storage Manager SYNOPSIS
/usr/sbin/voldiskadd disk-address-list DESCRIPTION
The voldiskadd utility sets up new disks that are added to the system after the initial system installation and configures the disks for use by the Logical Storage Manager. A valid disk label must exist on the disk before using the voldiskadd utility. One or more disks may be specified using a disk-address-list. Disk addresses in the list have the form dskn (for the entire disk) or dsknp (for a specific partition). When specifying multiple disks, use a space between entries. Disk address names relate directly to device names in the /dev/disk directory. For example, here are some valid voldiskadd disk-address-list specifications: # voldiskadd dsk1 # voldiskadd dsk2 dsk3a The file, /etc/vol/disks.exclude, may be used to exclude disks from use by voldiskadd. Each line of the file specifies the name of a disk to exclude (for example, dsk5). The voldiskadd utility prompts the user for a disk group name and disk media name for the disks. If a new disk group name is specified, that disk group is created for the new disks. If no disk group name is specified, the disks are left as unassigned replacement disks for future use. If an existing disk group name is specified, the user is prompted for whether the disks should be designated as spares for the disk group. If a disk is found to already contain non-Logical Storage Manager partitioning, the user is asked whether the disk should be encapsulated. Encapsulation turns each partition of the disk into a volume. A disk should be encapsulated if it contains file systems or data that should not be overwritten. If encapsulation is not desired for a disk, the disk can be initialized as a new disk for use by the Logical Storage Manager. For new disks, all space on the disk becomes free space in the disk's disk group. Context-sensitive help is available at every prompt by typing ?. Also, a list option can be used to get information on available target disks for an operation. The voldiskadd utility supports the following general classes of actions: Initializing a disk with reserved regions and partitions. Disk initialization is performed by calling voldisksetup command. Adding a disk to an existing disk group. This operation can be performed independently of the initialization of the disk drive to add a disk's storage space to a disk group's free space pool. The volassist command may subsequently allocate from that free space. The disk can also be added as a hot spare device. Creating new disk groups in which to import new disks. If no disk group exists for importing disks, the option of creating the disk group is offered. Encapsulating disks that have exist- ing contents. This is the default action for disks that do not have a valid, existing Logical Storage Manager private region, but that do have a disk label. Encapsulation is performed by calling volencap. Reconnecting a drive that was temporarily inaccessible. This situation is detected automatically, by noting that the specified drive has a disk ID that matches a disk media record with no currently associated physical disk. After reconnection, any stale plexes referring the disk are reattached, and any stopped volumes referring the disk are restarted. This reattach action is performed by calling the volrecover script. ERRORS
You may receive the following messages when using the voldiskadd command: Initialization of disk device special-device failed. Error: special-device or an overlapping partition is open. This message indicates that the partition you specified or an overlapping partition on the disk is actively in use. The partition could be a mounted UFS or AdvFS filesystem, initialized as an LSM disk or used as a swap device. special-device is marked in use for fstype in the disklabel. If you continue with the operation you can possibly destroy existing data. Would you like to continue?? [y,n,q,?] (default: n) This message indicates that the fstype of a partition or an overlapping partition is set in the disk label. The voldiskadd command prints this message to warn that a disk partition may have valid data which could be destroyed. If you are sure that the disk partition does not have valid data and that the partition can be added to LSM, you can ignore the warning message by entering y at the prompt. The voldiskadd command will proceed to initialize the disk partition and add it to LSM. FILES
A list of disks to exclude from use by voldiskadd. SEE ALSO
disklabel(8), volassist(8), voldisk(8), voldiskadm(8), voldisksetup(8), voldg(8), volintro(8) voldiskadd(8)
All times are GMT -4. The time now is 05:43 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy