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
metaimport(1M)															    metaimport(1M)

NAME
metaimport - imports disk sets into existing Solaris Volume Manager configurations SYNOPSIS
metaimport -s setname [-n] [-v] [-f] [disks...] metaimport -r [disks...] metaimport -V metaimport -? The metaimport command allows the importing of disk sets, including replicated disk sets, into an existing Solaris Volume Manager configu- ration. Replicated disk sets are disk sets created using remote replication software. The default Solaris Volume Manager configuration specifies a maximum number of disk sets that can be configured. The metaimport command fails if importing the disk set would result in exceeding the number of disk sets configured on the system. To increase the number of disk sets allowed on a system, see the . Use metaset(1M) or metastat(1M) to view the configuration of the imported set. You must run metaimport as root. metaimport requires a functional Solaris Volume Manager configuration before it runs. The following options are supported: -f Force the import, even if a quorum of replicas from the imported disk set is not available. This option could result in corrupt configurations and should only be used when metaimport fails with the "Insufficient quorum detected; exiting" error. If only a partial disk set is available, this option might be necessary to successfully import. Some or all data could be corrupted or unavailable when importing a partial set or a set lacking a replica quorum. -n Does not actually perform the operation, but shows the output or errors that would have resulted from the opera- tion, had it been run. -r Report on the non-configured disk sets found on the system. If no disk device or LUN is specified, metaimport reports on all non-configured disk sets attached to the system. When the name of one disk is specified, metaimport reports on the disk set (or virtual LUN) containing the specified disk. If two or more disks are specified, metaim- port reports on the set (or sets, if they belong to different disk sets) containing the specified disks. If two or more disks are specified, metaimport reports on the set (or sets, if they belong to different disk sets) containing the specified disks. -s setname Specify the disk set name to use when importing. The imported disk set will be called setname, without regard to the name it may have had on a different system. -v Verbose. Provides detailed information about the metadb replica location and status. -V Version information. -? Display a help message. Example 1: Importing a Disk Set The following example creates a disk set called blue and identifies c1t5d0 as a disk containing a state database replica from the disk set being imported. # metaimport -s blue c1t5d0 Example 2: Reporting Disk Sets to Import The following example scans all disks and LUNs attached to the system and configured as part of the system. It scans for disks that could be part of a disk set to be imported. Components that are already part of the Solaris Volume Manager configuration are ignored. This use of metaimport provides suggested forms of the metaimport command to use to actually import the disk sets that have been found. You can specify a component on the command line to reduce the scope of the scan and generate results more quickly. # metaimport -r 0 Successful completion. >0 An error occurred. See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWmdu | +-----------------------------+-----------------------------+ |Interface Stability |Stable | +-----------------------------+-----------------------------+ mdmonitord(1M), metaclear(1M), metadb(1M), metadetach(1M), metahs(1M), metainit(1M), metaoffline(1M), metaonline(1M), metaparam(1M), metarecover(1M), metareplace(1M), metaroot(1M), metaset(1M), metasync(1M), metattach(1M), md.tab(4), md.cf(4), mddb.cf(4), attributes(5) 16 May 2005 metaimport(1M)
All times are GMT -4. The time now is 09:06 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy