Sponsored Content
Operating Systems Solaris Boot disk crash with metadb config info Post 302605446 by bartus11 on Wednesday 7th of March 2012 12:14:14 PM
Old 03-07-2012
You might try this:
1. Restore
Code:
/etc/lvm/mddb.cf 
/etc/lvm/md.tab 
/kernel/drv/md.conf

From your latest backup.
2. Reboot
3. Run metadb -i again.
 

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... (1 Reply)
Discussion started by: Kgatliffe
1 Replies

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 Replies)
Discussion started by: DGoubine
3 Replies

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:... (7 Replies)
Discussion started by: hoff
7 Replies

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 -... (8 Replies)
Discussion started by: badoshi
8 Replies

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... (2 Replies)
Discussion started by: gxmsgx
2 Replies

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... (5 Replies)
Discussion started by: soliberus
5 Replies

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 (7 Replies)
Discussion started by: h@foorsa.biz
7 Replies

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... (0 Replies)
Discussion started by: gjackson123
0 Replies

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? ... (2 Replies)
Discussion started by: sparcman
2 Replies

10. Solaris

Solaris can not boot because metadb lost

how to recovery metadb? Thanks! (1 Reply)
Discussion started by: dzung
1 Replies
vxreattach(1M)															    vxreattach(1M)

NAME
vxreattach - reattach disk drives that have once again become accessible SYNOPSIS
/etc/vx/bin/vxreattach [-br ] [accessname...] /etc/vx/bin/vxreattach -c accessname DESCRIPTION
The vxreattach utility reattaches disks to the disk group they were in and retains the same media name. This operation may be necessary if a disk has a transient failure, or if Veritas Volume Manager (VxVM) starts with some disk drivers unloaded and unloadable. Disks then enter the failed state. If the problem is fixed, vxreattach may be able to reattach the disks without plexes being flagged as stale, as long as the reattach happens before any volumes on the disk are started. vxreattach tries to find a disk in the same disk group with the same disk ID for the disk(s) to be reattached. The reattach operation may fail even after finding the disk with the matching disk ID if the original cause (or some other cause) for the disk failure still exists. vxreattach is usually invoked by vxdiskadm when performing disk recovery. It is not intended to be run directly by an administrator. OPTIONS
-b Performs the reattach operation in the background. -c Checks if a reattach is possible. No operation is performed, but the name of the disk group and disk media name at which the disk can be reattached is displayed. -r Tries to recover stale plexes of any volumes on the failed disk. It does this by calling vxrecover. EXIT CODES
A zero exit status is returned if the reattach is performed; non-zero is returned otherwise. See vxintro(1M) for a list of standard exit codes. EXAMPLES
Check if reattachment of disk c1t2d0 is possible: /etc/vx/bin/vxreattach -c c1t2d0 If reattachment is possible, vxreattach returns with an exit status of 0 and displays the disk group name and disk media name. If reat- tachment is not possible, vxreattach returns an exit status of 2 and displays an error. Attempt to reattach the disk in the foreground and try to recover stale plexes of any volumes on the disk: /etc/vx/bin/vxreattach -r c1t2d0 If the reattachment is successful, vxreattach returns an exit status of 0. Otherwise, if an error occurs, vxreattach returns a non-zero exit code as defined on vxintro(1M). FILES
/etc/default/vxplex Standard defaults file that can be used to determine whether FastResync is used when attaching plexes. See vxplex(1M) for details. SEE ALSO
vxdiskadm(1M), vxintro(1M), vxplex(1M), vxrecover(1M) VxVM 5.0.31.1 24 Mar 2008 vxreattach(1M)
All times are GMT -4. The time now is 07:27 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy