12-04-2017
Solaris can not boot because metadb lost
how to recovery metadb?
Thanks!
10 More Discussions You Might Find Interesting
1. Solaris
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
Hi All,
If solaris has metadb services on the disk, it means that it has a HW raid controller. Or what.
Thanks in advance. (1 Reply)
Discussion started by: itik
1 Replies
3. Solaris
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
4. Solaris
I am trying to install Solaris x86 using the Jumpstart server. I run the add_install_client command with appropriate options, and reboot my x86 Target box. The installation starts fine and unattended. After the installation completes and the target goes for a re-boot, it does not boot from the HDD... (9 Replies)
Discussion started by: hemalsid
9 Replies
5. Solaris
Hi, my root pool is as follows. How can I create a metadb if I want to create SVM volumes?
zpool status
pool: rpool1
state: ONLINE
scan: none requested
config:
NAME STATE READ WRITE CKSUM
rpool1 ONLINE 0 0 0
c4t1d0s0 ... (10 Replies)
Discussion started by: incredible
10 Replies
6. What is on Your Mind?
.............. (1 Reply)
Discussion started by: siddulamadhu
1 Replies
7. Solaris
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
8. Solaris
Check Solaris VM Databases metadb does not have enough information about logical volumes. Current value is 0%
I have checked the SVM status, all disks are good state and synched perfectly. no errors in metadb -i.
what is this alert exact mean? what we have to check for the value?
Please... (1 Reply)
Discussion started by: Naveen.6025
1 Replies
9. Solaris
Hi all,
I added a new disk slice to the current metadb.
Below is what I see
bash-3.2# metadb -i
flags first blk block count
a m p luo 16 8192 /dev/dsk/c0t0d0s7
a p luo 8208 8192 ... (3 Replies)
Discussion started by: javanoob
3 Replies
10. Solaris
Hello,
I have a problem with my machine that won't boot properly.
The story is that I installed a software called apcupsd, which is a control application for my APC battery UPS. I have used version 3.14.10 earlier, but as part of restoring my previously crashed os harddrive I wanted to... (18 Replies)
Discussion started by: Zorken
18 Replies
LEARN ABOUT NETBSD
virecover
VIRECOVER(8) BSD System Manager's Manual VIRECOVER(8)
NAME
virecover -- report recovered vi edit sessions
SYNOPSIS
/usr/libexec/virecover
DESCRIPTION
The virecover utility sends emails to users who have vi(1) recovery files.
This email gives the name of the file that was saved for recovery and instructions for recovering most, if not all, of the changes to the
file. This is done by using the -r option with vi(1). See the -r option in vi(1) for details.
If the backup files have the execute bit set or are zero length, then they have not been modified, so virecover deletes them to clean up.
virecover also removes recovery files that are corrupted, zero length, or do not have a corresponding backup file.
virecover is normally run automatically at boot time using /etc/rc.d/virecover.
FILES
/var/tmp/vi.recover/recover.* vi(1) recovery files
/var/tmp/vi.recover/vi.* vi(1) editor backup files
SEE ALSO
vi(1), rc.conf(5)
HISTORY
This script, previously known as recover.script, is from nvi and was added to NetBSD in 1996. It was renamed in 2001.
AUTHORS
This man page was written by Jeremy C. Reed <reed@reedmedia.net>.
BSD
October 9, 2006 BSD