Sponsored Content
Operating Systems Solaris Sun V445 hangs before {0} ok prompt Post 302879362 by hicksd8 on Thursday 12th of December 2013 05:35:40 AM
Old 12-12-2013
I don't know the equivalent (if there is one) for a PC keyboard.

Another thing I would do in this situation is power down, pull out the hard disks (all of them) from the backplane, and power up. This might just land you at the ok prompt. If it does we can discuss next steps.

(You mentioned earlier that "#." gave you ALOM login. To me this means that the boot process has progressed past the SC boot up and entered "autoboot" ie, looking at the hard disk. So let's pull out the disks to see if it gives an error like "can't access hard drive" and drops to "ok".)

Just an idea.
 

9 More Discussions You Might Find Interesting

1. Solaris

Jumpstart Solaris 8 on Sun Blade 150 Hangs

We had to replace a hard drive in one of our Sun Blade 150s, but now it hangs during the Jumpstart. It will show 1 or 2 Timeout for ARP/RARP messages and then start the spinning numbers. It always stops at 2ae00 and just hangs there. We have 1 combined jumpstart server and it is also our NIS+... (5 Replies)
Discussion started by: stottsja
5 Replies

2. Solaris

How to get to a OK prompt on new SUN T5140

Hi, I have a brand new SUN T5140 machine. I am trying to install Solaris 10 on the box. When I go to the machine using a KVM session I can see a blank screen , how can I get to the OK prompt to start the installation. Thanks, Suresh (10 Replies)
Discussion started by: gunnervarma
10 Replies

3. Solaris

How to get to the OK prompt without Sun keyboard

Hi all, I have just replaced the HDD on a Ultra 5 Spark machine, now I need to reinstall Solaris 9. The problem is: how do I get to the OK prompt without a Sun keyboard in order to boot from CD? At moment when I power on the machine I get the following error: Timeout Waiting for ARP/RARP... (13 Replies)
Discussion started by: sspirito
13 Replies

4. Solaris

XSCF prompt disappeared, Sun M5000

Hi, I've got an issue here: After I logon to the xscf prompt of this Sun M5000 and did 'XSCF> version -c xcp', the xscf prompt disappeared. I can't get it back and can't log out. exit rebootxscf logout #. #> #> ~# ~# exit sendbreak exit I tried to set the Mode Switch to the service... (3 Replies)
Discussion started by: aixlover
3 Replies

5. Solaris

V445 unable to boot because of an error

This is what is displayed on the screen as the system tries to boot and then hangs: 0>Test CPU(s)....Done 0>Interrupt Crosscall....| SC Alert: DHCP negotiation failed, perhaps misconfigured or no DHCP server avail able Done 0>Init Memory....| SC Alert: Host System has Reset 'Done 0>PLL... (2 Replies)
Discussion started by: kenosongo
2 Replies

6. Solaris

Failure to boot v445

Hi Guys, I have a small problem with a v445 which I have been informed will only boot with the reconfigure option enabled. It is attached to HP SAN storage using qla2300 FCA's with a Veritas encapsulated rootvoldg (No Laughing here please) when I try a reboot I get the following error. ... (5 Replies)
Discussion started by: gull04
5 Replies

7. 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

8. Solaris

Rebuild/Reset to default Sun v445

Hello, I'm quite new to Unix but I've got an old Sun v445 server that was previously used as a backup database server, these have since been moved to new hardware. The old admin who configured the box has since retired and left no notes about it, so i have no idea what the root password is and... (2 Replies)
Discussion started by: dbajtr
2 Replies

9. Solaris

Install ext DLT Sun Tape drive on V445 Solaris 10

I have a SunFire V445 running Solaris 10 and am adding a Sun DLT tape drive. From the OK prompt the probe-scsi-all does see the drive and it is the proper target of 4. When I do the boot -- -r it does build the /dev/rmt directories correctly and the links to /devices appear correct as well. When I... (8 Replies)
Discussion started by: chastings
8 Replies
vxdiskadd(1M)															     vxdiskadd(1M)

NAME
vxdiskadd - add one or more disks for use with Veritas Volume Manager SYNOPSIS
vxdiskadd disk_address_pattern_list DESCRIPTION
The vxdiskadd utility configures disks for use by Veritas Volume Manager (VxVM). Disks must already have been formatted. vxdiskadd prompts the user for a disk group name and disk name for the disks. If no disk group name specified, the disks will be left as unassigned replacement disks for future use. A new disk group may be created that will become the disks' disk group. If a disk group is specified for the disks, the user is prompted for whether the disks should be designated as spares for the disk group. For new disks, all space on the disk becomes free space in the disk's disk group. vxdiskadd interactively allows initialization to be done for all the disks specified or allows the user to ask to make the decision for each disk individually. One or more disks may be specified with a disk_address_pattern_list. The basic form of a disk address is c#t#d#. Any leading portion of this address may be specified to indicate that all disks that match that leading portion should be used. For example c2t0 may be used to specify all disks on controller 2, target 0. More than one disk address or address pattern may be specified on the command line. In case of enclosure-based names, the disk address will be of the form enclosurename_diskno. The enclosurename indicates that all disks in the specified enclosure are used. For example, emc1_ is used to specify all disks in the enclosure emc1. The word all may be used to specify all disks on the system. Disk address names relate directly to device node names in the /dev/dmp and /dev/rdmp directories. Here are more examples: all: all disks c3 c4t2: all disks on controller 3 and controller 4, target 2 c3t4d2: a single disk (in the c#t#d# naming scheme) xyz_0 : a single disk (in the enclosure based naming scheme) xyz_ : all disks on the enclosure whose name is xyz The files /etc/vx/cntrls.exclude, /etc/vx/disks.exclude and /etc/vx/enclr.exclude may be used to exclude controllers or disks from use by vxdiskadd. Each line of cntrls.exclude specifies the address of a controller to exclude, for example, c2. Each line of disks.exclude spec- ifies a disk to exclude, for example, c0t3d0. Each line of enclr.exclude specifies the name of an enclosure to exclude, for example, enc0. All courses of action that do not involve clear failure conditions require prompts from the user, with defaults supplied as appropriate. Help is made available at every prompt. Entering ? in response to a prompt displays a context-sensitive help message. OPERATIONS
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 vxrecover utility. Initialization of a disk with reserved regions Initialization of the disk is performed by calling vxdisksetup. Adding a disk to an existing disk group This operation can be performed independently of the initialization of the disk drive. The operation adds the disk to the group so that its storage is added to the free space pool in that disk group. The vxassist utility can subsequently allocate from that free space. Creation of new disk groups in which to import a new disk If disks are added that are required to be put into a disk group that does not exist, the option of creating the disk group is offered. Hardware-Specific Note Some environments provide guidelines to optimize VxVM's interaction with intelligent storage systems. If these guidelines are present, VxVM follows the guidelines when adding disks to disk groups. If the operation fails due to these guideline(s), you are prompted to use the force option. The force option ignores any such storage-specific guidelines. FILES
/etc/vx/cntrls.exclude Specifies the address of controllers to exclude from vxdiskadd operations. /etc/vx/disks.exclude Specifies the address of disks to exclude from vxdiskadd operations. /etc/vx/enclr.exclude Specifies the address of enclosures to exclude from vxdiskadd operations. NOTES
EFI disks cannot be added to a disk group that is compatible with the Cross-platform Data Sharing (CDS) feature, nor can they be formatted as CDS disks. SEE ALSO
vxassist(1M), vxdisk(1M), vxdiskadm(1M), vxdisksetup(1M), vxintro(1M), vxrecover(1M) VxVM 5.0.31.1 24 Mar 2008 vxdiskadd(1M)
All times are GMT -4. The time now is 11:31 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy