Sponsored Content
Operating Systems Solaris Boot disk crash with metadb config info Post 302605419 by Handon on Wednesday 7th of March 2012 11:13:56 AM
Old 03-07-2012
Boot disk crash with metadb config info

Hello all;

We have a SunFire V240 with three disks that were part of a metadb. One of those disks, the boot disk, experienced a horrible death Monday night and we're now trying to recover from that.

I know very little about metadb stuff, so please be gentle with me...

I'm assuming (yes, I know about assuming Smilie ) that the config files for the metadb were also on the boot disk. I reinstalled Solaris 10 on a new disk, but now am stuck as to how to create a new metadb without losing the data that is on two disks that were part of the old metadb.

I know that if I create a new metadb and connect the other two disks, the data on those disks will be lost, so I'm wondering if there's a way to do this without losing the data?

This is on a production system, so I'm really in the hot seat right now...
Please Help!!

Handon
 

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
volreattach(8)						      System Manager's Manual						    volreattach(8)

NAME
volreattach - Reattaches disk drives that have once again become accessible SYNOPSIS
/usr/sbin/volreattach [-rb] [accessname...] /usr/sbin/volreattach -c accessname OPTIONS
The volreattach utility has the following options: Calls the volrecover utility to attempt to recover stale plexes of any volumes on the failed disk. Performs the reattach operation in the background. Checks whether 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. DESCRIPTION
The volreattach utility attempts to reattach disks using the same disk group and media names they had before detachment. This operation may be necessary if a disk has a transient failure, or if some disk drivers are unloaded or unloadable when the Logical Storage Manager is started, causing disks to enter the failed state. If the problem is fixed, the volreattach command can be used to reattach the disks without plexes being flagged as stale, as long as the reattach happens before any volumes on the disk are started. The volreattach command is called from the voldiskadm menus as part of disk recovery. The volreattach utility tries to find a disk with a disk group and disk ID matching that of the disk(s) being reattached. If the matching disk is found, the reattach operation may still fail if the original cause (or some other cause) for the disk failure still exists. EXIT CODES
A zero exit status is returned if it is possible to perform a reattach. Otherwise, non-zero is returned. SEE ALSO
volintro(8), voldiskadm(8), volrecover(8) volreattach(8)
All times are GMT -4. The time now is 11:23 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy