Sponsored Content
Operating Systems Solaris metadb problem - server unable to boot Post 302384167 by soliberus on Monday 4th of January 2010 08:51:16 AM
Old 01-04-2010
Doh!!!

I've followed the advice above, but when I boot from the good disk and run metadb, it returns the following error message:

there are no existing databases

I don't know how this is possible, but what can I do now?

Last edited by soliberus; 01-04-2010 at 10:34 AM..
 

10 More Discussions You Might Find Interesting

1. Solaris

solaris boot problem boot error loading interpreter(misc/krtld)

When I installed the SOLARIS 10 OS first time, the desktop would not start up, this was because of network setup. Reinstalled worked. After a week due to some problem I had to reinstall OS, installation went fine and but when i reboot I get this error. cannot find mis/krtld boot error loading... (0 Replies)
Discussion started by: johncy_j
0 Replies

2. Solaris

unable to boot from disk1

I had installed solaris 10 on 440 on disk 0. I had done ufsrestore on disk1 from tape and then rebooted Rebooting with command: boot disk1 Boot device: /pci@1f,700000/scsi@2/disk@1,0 File and args: SunOS Release 5.10 Version Generic_118833-24 64-bit Copyright 1983-2006 Sun Microsystems,... (3 Replies)
Discussion started by: vr76413
3 Replies

3. Red Hat

Unable to boot Fedora 10

Hello, I have a test PC running Fedora 10. Friday evening it was working fine, I have some perl scripts which are scheduled to run every morning. But when I started work this morning, I found I cannot ping the machine. When I switched on the monitor, I saw the GRUB promt :(. I am not sure... (10 Replies)
Discussion started by: SivaramaRaju
10 Replies

4. Ubuntu

grub problem - unable to boot

I am not able to boot into my ubuntu. Grub gives me this message How do I boot linux? (6 Replies)
Discussion started by: locoroco
6 Replies

5. Solaris

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

6. Solaris

Unable to boot from mirror disk on x86 server configured under VxVM

Hi, Can you help me on booting x86 server configured under VxVM. Server boots fine normally from both the disks but if I try to boot server from mirror disk without starting veritas, then it does not boot. vxplex -g rootdg dis var-02 vxplex -g rootdg dis swapvol-02 vxplex -g rootdg dis... (2 Replies)
Discussion started by: milindphanse604
2 Replies

7. Solaris

Solved: Disk Unable to Boot

Update: The / file system (/dev/rdsk/c1t0d0s0) is being checked fsck unable to stat WARNING - unable to repair the / filesystem. Run fsck manually (fsck -F ufs /dev/rdsk/c1t0d0s0). Root password for system maintenance (control-d to bypass): I am unable to hit control-d to by pass. I... (50 Replies)
Discussion started by: br1an
50 Replies

8. Ubuntu

Unable to boot Ubuntu server 15.10

Hi; I had Windows Server 2003 and performed a fresh Ubuntu Server 15 installation. After installation, Ubuntu server not booting I guess there is boot problem conflicting with my old Windows Server. This is my pastebin: http://paste.ubuntu.com/13851828/ Any help to start my new... (1 Reply)
Discussion started by: gc_sw
1 Replies

9. Red Hat

Unable to boot up after P2V

Hi, I just P2V an old machine running Redhat 5.5 on a physical server. After P2V was completed, when boot up it got an error. Please refer to the attachment for the error. Please assist. Thanks. (2 Replies)
Discussion started by: freshmeat
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)						  System Administration Commands					    metaimport(1M)

NAME
metaimport - imports disk sets into existing Solaris Volume Manager configurations SYNOPSIS
metaimport -s setname [-n] [-f] [-v] [disks]... metaimport -r [-v] [disks]... metaimport -V metaimport -? DESCRIPTION
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. OPTIONS
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 cor- rupt 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 cor- rupted 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 operation, 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, metaimport 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. This option can be used in conjunction with the -v option to give verbose output on each disk set reported. -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. It also provides detailed information about the disk set configuration and status similar to the "metastat -c" output. -V Version information. -? Display a help message. EXAMPLES
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 EXIT STATUS
0 Successful completion. >0 An error occurred. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWmdu | +-----------------------------+-----------------------------+ |Interface Stability |Stable | +-----------------------------+-----------------------------+ SEE ALSO
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), metastat(1M), metasync(1M), metattach(1M), md.tab(4), md.cf(4), mddb.cf(4), attributes(5) SunOS 5.11 28 Oct 2005 metaimport(1M)
All times are GMT -4. The time now is 05:03 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy