Boot disk crash with metadb config info Post: 302605419

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Disk Crash

We have a Unix system with two hard drives. When we tried to access it this morning it had frozen, and when we rebooted it couldn't find one of the hard drives, and had quite a few bad data blocks on the other. Of course we fear the worst: that the drive is completely gone, but were not sure how...

2. Filesystems, Disks and Memory

System crash and Disk erasure !!!

I need some expert help, and would appreciate any feedback on the following problem: After power outage the machine didn't allow the login. When we checked it , it looked like both disks were completely empty. Luckily, we have a backup machine, and we can restore the disks. Has anybody seen...

3. Filesystems, Disks and Memory

HP-UX Disk crash?

Hi, First post. I am not to experienced in the Unix or HP-UX world but I'm learning. We have some problem with a HP rx4640 server. During boot it states the following: Checking for LVM volume groups and Activating (if any exist) Volume group "/dev/vg00" has been successfully changed. vgchange:...

4. Solaris

mirroring root disk using svm - but no free slices for metadb's

Hi all, we have an existing system that was configured using just one of the (two) internal disks. I want to mirror the disk using SVM, but have realised there is no free slice for creating the metadb's. Is there a workaround I can use for this? In the past we have always kept slice 7 free -...

5. Solaris

scconf crash: registering a Veritas local disk on Sun Cluster (localonly=true)

Hi all, I want to put a local disk on a Sun Cluster node but scconf command explodes :eek: My system: * two node cluster on two VMWare virtual machines * Solaris 10 SunOS 5.10 Generic_141415-05 i86pc i386 i86pc * Sun Cluster 3.2 u2 * Veritas Volume manager The situation...

6. Solaris

metadb problem - server unable to boot

Hi everyone I have a problem. My configuration is as follows: Sun 280R server 2 x internal disks 3 x state databases on disk 1 3 x state databases on disk 2 Disk 1 was giving errors, so I cleared the mirrors on it, deleted the state databases and replaced the disk. Before attaching...

7. Emergency UNIX and Linux Support

HP-UX 11iv3 crash on integrity bl870c during os kernel boot

I have a problem it seems to me as kernel panic during os booting i attached screen shots for the error

8. Solaris

How to specify local boot up disk in CD boot Grub?

Hi Solaris 10 Experts, I am wondering what is the correct syntax to edit in Grub when trying to specify the local ZFS boot disk while booting up from a Solaris 10 x86 64bits DVD installation disk. In other word, I try to boot up from local disk without removing the Solaris installation disk...

9. Solaris

Use 'dd' to copy boot disk to larger target disk

Hi, I'm looking to copy a boot disk on an old Solaris 8 system using dd. I'll bring the system down to single user mode and begin from there. I'm copying my source disk to a larger target disk. Do I need to do anything other than the 'dd' command below because the target disk is bigger? ...

10. Solaris

Solaris can not boot because metadb lost

how to recovery metadb? Thanks!

LEARN ABOUT HPUX

vxbootsetup

vxbootsetup(1M) 														   vxbootsetup(1M)

NAME

       vxbootsetup - set up system boot information on a Veritas Volume Manager disk

SYNOPSIS

       /etc/vx/bin/vxbootsetup [-g diskgroup] [medianame ... ]

DESCRIPTION

       The  vxbootsetup utility configures physical disks so that they can be used to boot the system. Before vxbootsetup is called to configure a
       disk, the required volumes, standvol, rootvol and swapvol (and optionally, dumpvol) must be created on the disk.  All of these volumes must
       be contiguous with only one subdisk.

       The -g option may be used to specify the boot disk group.

       If  no  medianame arguments are specified, all disks that contain usable mirrors of the root, swap, /usr and /var volumes are configured to
       be bootable.

       If medianame arguments are given, only the disks that are associated with the specified disk names are configured to be bootable.

       vxbootsetup requires that:

       o    The root volume must be named rootvol and must have a usage type of root.

       o    The swap volume must be named swapvol and must have a usage type of swap.

       o    The volumes containing /usr and /var (if any) must be named usr and var, respectively.

       See the chapter "Recovery from Boot Disk Failure" in the Veritas Volume Manager Troubleshooting Guide for detailed information on  how  the
       system boots and how VxVM impacts the system boot process.  The vxmirror, vxrootmir, and vxresize utilities call vxbootsetup automatically.
       If you use vxassist, or vxmake and vxplex to create mirrors of the root volume on a disk, you must run vxbootsetup explicitly to  make  the
       disk bootable.

ARGUMENTS

       medianame
	    Specifies the disk name (disk media name) of a VM disk that is to be configured as bootable.

SEE ALSO

       disksetup(1M),  edvtoc(1M),  vxassist(1M),  vxevac(1M),	vxinstall(1M),	vxintro(1M),  vxmake(1M),  vxmirror(1M), vxplex(1M), vxresize(1M),
       vxrootmir(1M)

       Veritas Volume Manager Troubleshooting Guide

VxVM 5.0.31.1							    24 Mar 2008 						   vxbootsetup(1M)

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Disk Crash

Discussion started by: Kgatliffe

2. Filesystems, Disks and Memory

System crash and Disk erasure !!!

Discussion started by: DGoubine

3. Filesystems, Disks and Memory

HP-UX Disk crash?

Discussion started by: hoff

4. Solaris

mirroring root disk using svm - but no free slices for metadb's

Discussion started by: badoshi