Yes that is safe, unless it is the boot disk.
And then there is manual work:
eventually a label is to be installed, the new disk needs to be partitioned, eventually a boot block needs to be installed, a metadb needs to be installed, and each partition needs to be synced.
Please give output of metastat and metadb!
Hi, attached is the output of metastat and metadb commands.
Got an curious issue.
I applied 109147-39 to, oh 15 or so various systems all running Jumpstarted Solaris 8. When I hit the first two V440s, they both failed with Return code 139. All non shell commands segfaulted from then on.
The patch modified mainly the linker libraries and commands.
... (2 Replies)
All,
After a power loss I went to power on our sun fire v120 that is running solaris 10 and now it will not boot. I tried power cycling it from the lom and pulling the cord but nothing works. All it does is after a power cycle it will start to boot and then start to spit out a bunch of hex... (2 Replies)
Hello,
I hope you can help me. I am new to Sun servers and we have a Sun Fire v440 server in which one power supply failed, we are waiting for new one. But now our server is shutting down constantly. Is there any setting with which we can prevent this behaviour? (1 Reply)
First of all it's shut down 60 second after power on and write on console :
SC Alert: Correct SCC not replaced - shutting managed system down!
This is cured by moving out battery from ALOM card.
Now server start to loop during the testing.
That's on the console:
>@(#) Sun Fire V440,Netra... (14 Replies)
Hello,
I am seeing error messages in V440 (OS = solaris 8). I have copied here :
The system does not reboot constantly and it is up for last 67 days. One more interesting thing I found, I see errors start appearing at 4:52AM last until 6am and again start at 16:52am on same day..
I... (5 Replies)
Hi,
I was asked to connect a KVM screen to a Sun Fire V440 last night so I connected it up but no joy and nothing on the KVM screen. I was told that a reboot may fix the problem so connected to the ALOM and rebooted. On the plus side, the KVM screen now works but I lost the ALOM connection.
... (0 Replies)
Hi:
I bougth an used Sun Fire v440, and It have a firmware password. When I turn on the server, it ask for firmware password. (I don 't know what is the correct password). I can access to SC, but when I want to access to OBP, Firmware Password appears again. I remove the battery for two hours,... (1 Reply)
Dear Team,
I need some expert advice to my problem.
We have a Sun Fire v440 in our customer Place. Server is working fine and no hardware deviations are found except one problem that processors generating too much heat. I have verified and found that the room temperature was 26-27 degree.... (5 Replies)
Hi,
I have Sun Fire V440. Boot disks are mirrored. system crashed and it's not coming up. Error message is
Insufficient metadevice database replicas located. Use Metadb to delete databases which are broken.
Boot disks are mirrored and other disks are ZFS configuration. Please... (2 Replies)
Hi,
I have a Sun Fire V440 server that fails to boot up correctly. A lot of services are not started and the sytems acts really slow to commands. During boot I can see the following Error:
WARNING: /pci@1f,700000/scsi@2/sd@0,0 (sd1):
SCSI transport failed: reason 'reset': retrying... (15 Replies)
Discussion started by: oliwei
15 Replies
LEARN ABOUT LINUX
mddb.cf
mddb.cf(4) File Formats mddb.cf(4)NAME
mddb.cf - metadevice state database replica locations
SYNOPSIS
/etc/lvm/mddb.cf
DESCRIPTION
The /etc/lvm/mddb.cf file is created when the metadb(1M) command is invoked. You should never directly edit this file.
The file /etc/lvm/mddb.cf is used by the metainit(1M) command to find the locations of the metadevice state databases replicas. The metadb
command creates the file and updates it each time it is run. Similar information is entered in the /kernel/drv/md.conf file.
Each metadevice state database replica has a unique entry in the /etc/lvm/mddb.cf file. Each entry contains the driver and minor unit num-
bers associated with the block physical device where a replica is stored. Each entry also contains the block number of the master block,
which contains a list of all other blocks in the replica.
Entries in the /etc/lvm/mddb.cf file are of the form: driver_name minor_t daddr_t checksum where driver_name and minor_t represent the
device number of the physical device storing this replica. daddr_t is the disk block address. checksum is used to make certain the entry
has not been corrupted. A pound sign (#) introduces a comment.
EXAMPLES
Example 1: Sample File
The following example shows a mddb.cf file.
#metadevice database location file do not hand edit
#driver minor_t daddr_t device id checksum
sd 152 16 id1,sd@SSEAGATE_JDD288110MC9LH/a -2613
In the example above, the value for daddr_t indicates that the offset from the start of a given partition is 16 disk blocks from the start
of that partition.
FILES
/etc/lvm/mddb.cf
/kernel/drv/md.conf
SEE ALSO mdmonitord(1M), metaclear(1M), metadb(1M), metadetach(1M), metahs(1M), metainit(1M), metaoffline(1M), metaonline(1M), metaparam(1M),
metarecover(1M), metarename(1M), metareplace(1M), metaroot(1M), metassist(1M), metaset(1M), metastat(1M), metasync(1M), metattach(1M),
md.cf(4), md.tab(4), attributes(5), md(7D)
Solaris Volume Manager Administration Guide
SunOS 5.10 8 Aug 2003 mddb.cf(4)