05-08-2007
SparcStation 20 Crashed. Doesn't boot.
I have sparc Station 20 which is crashed and doesn't boot from the OK prompt except gives me bunch of errors. How can i retrieve my data from the root drive before go for re-installation. This system has Veritas Volume manager on it don't know the version but assume its 2.xxx.
Thanks
-Adeel
10 More Discussions You Might Find Interesting
1. Solaris
Hey guys...hopefully this will be a fairly easy one.
I've got an old SPARCstation 5 running Sun 5.5.1 that I just hooked up to the network so that I can run HP OpenView. The box is working fine, but it is broadcasting as a boot server. In other words, when co-workers come in and get ready to log... (2 Replies)
Discussion started by: cdunavent
2 Replies
2. UNIX for Advanced & Expert Users
Hey guys...hopefully this will be a fairly easy one.
I've got an old SPARCstation 5 running Sun 5.5.1 that I just hooked up to the network so that I can run HP OpenView. The box is working fine, but it is broadcasting as a boot server. In other words, when co-workers come in and get ready to... (2 Replies)
Discussion started by: cdunavent
2 Replies
3. Solaris
Hi all,
This is my first post here :) Hope some guru here will be able to help ...
I'm in a predicament - my Ultra 60 worked fine before it was put into storage a year ago ... now, I've set it up in my PC room and I get the following message on startup:
Can't open input device.
Keyboard... (3 Replies)
Discussion started by: montezumola
3 Replies
4. Solaris
I apologize in advance that this is probably more of a hardware question than a unix/software one.
I've got a seemingly brand-new sparcstation 20 that came with 2 memory modules and that's about it.
I've added a new 2 GB HDD and a VSIMM Onboard SX Graphics module.
So, I assume with the... (2 Replies)
Discussion started by: ErikTheHAck
2 Replies
5. UNIX for Dummies Questions & Answers
at the end of October i upgraded the distro to 8.10 at first it seemed fine until i restarted my machine the boot seqence started i logged in after that nothing? tried booting again and the same thing happened did i do something wrong during the upgrade to 8.10 did everything the computer asked me... (1 Reply)
Discussion started by: ksnovice
1 Replies
6. UNIX for Dummies Questions & Answers
I am away from my Unix sparcstation and need to work on it remotely via a
PC. I can open a PuTTy window and execute line commands. But I've
forgotten how to be able to work on a graphical program, like xfig. I know
there are some commands to enable this, but can't remember them. (6 Replies)
Discussion started by: leveson
6 Replies
7. Ubuntu
Hey i am running both ubuntu 10.10 and windows 7, trying to make the default boot be windows 7 instead of ubuntu but it doesn't want to work. Ive tried changing default in the grub file it didnt work, then i installed startup-manager and set windows 7 as the OS and it still boots into ubuntu. Thx... (3 Replies)
Discussion started by: Era555
3 Replies
8. Hardware
Hello,
Just wanted to let interested people know that we've recently released a Linux freeware version of SparcStation 20 emulator. It emulates SS20 with some basic peripherals: a single SPARC V8 32bit CPU, up to 512MB RAM, an NCR53C94 SCSI controller, 2 serial lines, disks, a network adapter,... (7 Replies)
Discussion started by: Thlan
7 Replies
9. AIX
any ideas ??????? (2 Replies)
Discussion started by: livehho
2 Replies
10. Solaris
Hi, one of my server won't boot. I restarted system while sysconfig configure was running. I can't boot into normal user mode. I always get error svc:/system/config-user:default is in maintenance mode and some lib exists with status 95.
I tried to boot into single user mode and to clear this... (6 Replies)
Discussion started by: solaris_user
6 Replies
LEARN ABOUT HPUX
vx_emerg_start
vx_emerg_start(1M) vx_emerg_start(1M)
NAME
vx_emerg_start - start Veritas Volume Manager from recovery media
SYNOPSIS
vx_emerg_start [-m] [-r root_daname] hostname
DESCRIPTION
The vx_emerg_start utility can be used to start Veritas Volume Manager (VxVM) when a system is booted from alternate media, or when a sys-
tem has been booted into Maintenance Mode Boot (MMB) mode. This allows a rootable VxVM configuration to be repaired in the event of a cat-
astrophic failure.
vx_emerg_start verifies that the /etc/vx/volboot file exists, and checks the command-line arguments against the contents of this file.
OPTIONS
-m Mounts the root file system contained on the rootvol volume after VxVM has been started. Prior to being mounted, the rootvol volume
is started and fsck is run on the root file system.
-r root_daname
Specifies the disk access name of one of the members of the root disk group that is to be imported. This option can be used to spec-
ify the appropriate root disk group when multiple generations of the same root disk group exist on the system under repair. If this
option is not specified, the desired root disk group may not be imported if multiple disk groups with the same name exist on the sys-
tem, and if one of these disk groups has a more recent timestamp.
ARGUMENTS
hostname
Specifies the system name (nodename) of the host system being repaired. This name is used to allow the desired root disk group to be
imported. It must match the name of the system being repaired, as it is unlikely to be recorded on the recovery media from which you
booted the system.
NOTES
HP-UX Maintenance Mode Boot (MMB) is intended for recovery from catastrophic failures that have prevented the target machine from booting.
If a VxVM root volume is mirrored, only one mirror is active when the system is in MMB mode. Any writes that are made to the root file sys-
tem in this mode can corrupt this file system when both mirrors are subsequently configured.
The vx_emerg_start script allows VxVM to be started while a system is in MMB mode, and marks the non-boot mirror plexes as stale. This
prevents corruption of the root volume or file system by forcing a subsequent recovery from the boot mirror to the non-boot mirrors to take
place.
USAGE
After VxVM has been started, various recovery options can be performed depending on the nature of the problem. It is recommended that you
use the vxprint command to determine the state of the configuration.
One common problem is when all the plexes of the root disk are stale as shown in the following sample output from vxprint:
v rootvol root DISABLED 393216 - ACTIVE -
pl rootvol-01 rootvol DISABLED 393216 - STALE -
sd rootdisk01-02 rootvol-01 ENABLED 393216 0 - -
pl rootvol-02 rootvol DISABLED 393216 - STALE -
pl rootvol-02 rootvol DISABLED 393216 - STALE -
sd rootdisk02-02 rootvol-02 ENABLED 393216 0 - -
In this case, the volume can usually be repaired by using the vxvol command as shown here:
vxvol -g 4.1ROOT -f start rootvol
If the volume is mirrored, it is put in read-write-back recovery mode. As the command is run in the foreground, it does not exit until the
recovery is complete. It is then recommended that you run fsck on the root file system, and mount it, before attempting to reboot the sys-
tem:
fsck -F vxfs -o full /dev/vx/rdsk/4.1ROOT/rootvol
mkdir /tmp_mnt
mount -F vxfs /dev/vx/dsk/4.1ROOT/rootvol /tmp_mnt
SEE ALSO
fsck(1M), mkdir(1M), mount(1M), vxintro(1M), vxprint(1M), vxvol(1M)
VxVM 5.0.31.1 24 Mar 2008 vx_emerg_start(1M)