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 DEBIAN
xnbd-watchdog
XNBD-WATCHDOG(1) General Commands Manual XNBD-WATCHDOG(1)
NAME
xnbd-watchdog -- Watch a NBD device as started by xnbd-client(1)
SYNOPSIS
xnbd-watchdog [--timeout SECONDS] [--interval SECONDS] [--recovery-command COMMAND] [--recovery-command-reboot] [NBD_DEVICE]
DESCRIPTION
With the xnbd-watchdog, you can monitor a running nbd-client and trigger actions on failure.
OPTIONS
The following options are supported:
--timeout SECONDS
Triggers the recovery command action if the watchdog process is unable to connect to the NBD_DEVICE within the given timeout. If
not given, this defaults to 10 seconds.
--interval SECONDS
Specifies the polling interval between probes. If not given, this defaults to 10 seconds.
--recovery-command COMMAND
If given, the COMMAND is executed if the watchdog is unable to connect the NBD device after timeout exceeded.
--recovery-command-reboot
This argument is a shortcut for --recovery-command 'reboot now'. That is, it will reboot the server upon failure.
POSITIONAL ARGUMENTS
The following positional options are supported:
NBD_SERVER
The local nbd-device to be associated with the remote xnbd-server.
SEE ALSO
xnbd-server (8).
AUTHOR
The NBD kernel module and the NBD tools have been written by Pavel Macheck (pavel@ucw.cz) and is now maintained by Paul Clements.
(Paul.Clements@steeleye.com).
The xNBD userland (client and server) have been written by Takahiro Hirofuchi (t.hirofuchi@aist.go.jp)
This manual page was written by Arno Toell (debian@toell.net) for the Debian GNU/Linux system (but may be used by others). Permission is
granted to copy, distribute and/or modify this document under the terms of the GNU General Public License, version 2, as published by the
Free Software Foundation.
XNBD-WATCHDOG(1)