11-08-2005
M p unknown unknown /dev/dsk/c1t1d0s4 << bad disk
M p unknown unknown /dev/dsk/c1t3d0s4 << bad disk
Note in your metadb - looks like someone added to the metadb but never rebooted - that's usually why you get the unknown in the status although it's possible you are also getting it because the disks are bad. The good thing is that there are so many copies of the metadb - so you can replace the bad disks without no worry about losing anything.
As far as the bad disk, get the replacement disk drives and you can use the metareplace command. Or you can use metadetach and metaclear to remove them from the metastat and replace the drives, format, and readd them. You can hot swap the drives so you should not need any down time.
Also, insure that the boot device is c1t0d0s0 and not c1t1d0s0. You don't want to hot swap or remove the drive you are booted off of (inital boot will be off one drive and then the mirrors come into play). Just check the output of eeprom and look for boot-device - hopefully it isn't simply "disk:a" but gives you the output that you would be able to tell which drive it really is. If not, then you can play it safe and reboot into single user to do the drive replacements. More info can be found
in this thread
10 More Discussions You Might Find Interesting
1. Solaris
Hi Guys,
Need to add 2 disks into a JBOD array (3310).
Does anyone see anything wrong with my Procedure / Doco below?
1> Logon to system, check system logs for abnormal entries.
2> Make backups of related system files:
A>cp -p /etc/system /etc/system.backup.081505
B>cp -p /etc/vfstab... (3 Replies)
Discussion started by: BG_JrAdmin
3 Replies
2. Solaris
hi expert,
sorry i'm new in solaris system, need more advice and help :)
i'm confusing with mirroring disk at my sparc v890 solaris 8, i have 6 harddisk which the structure shown below :
format :
AVAILABLE DISK SELECTIONS:
0. c1t0d0 <SUN146G cyl 14087 alt 2 hd 24 sec 848>
... (4 Replies)
Discussion started by: bucci
4 Replies
3. Solaris
Hi
I have a Sunfire X4100 box with a 4 disk Chassis (although I only have 2 disks in it). I have been asked to add two more disks into the chassis so that I can mirror the original two using SVM .....Ive read through a couple of SVM docs but am finding it a little confusing, and if any of you... (1 Reply)
Discussion started by: hcclnoodles
1 Replies
4. Solaris
I am having an issue with setting up disk mirroring for Solaris 10 on an x86 server. My main problem is that the volumes and slices have already been setup and our proprietary software has already been installed and configured. The entire drive has been allocated in this configuration and the... (2 Replies)
Discussion started by: chuck43
2 Replies
5. Solaris
Has anyone managed to set up disk mirroring in Solaris 10 yet? If so can you point me in the direction of some useful documentation please.
Cheers (25 Replies)
Discussion started by: korfnz
25 Replies
6. Solaris
Hi Friends,
I am having Sun Solaris 5.8 OS installed having 2 different size hard disk, sizes are c0t0d0s0(160 GB) and c0t2d0s0 (40GB). I have installed Sun Solaris 5.8 OS in c0t0d0s0 (160GB) harddisk.
I have configured all the parameters required for disk mirroring. But when executing... (4 Replies)
Discussion started by: Vijayakumarpc
4 Replies
7. Solaris
Need a procedure document to do "root disk mirroring in solaris volume manager for solaris 10". I hope some one will help me asap. I need to do it production environment.
Let me know if you need any deatils on this.
Thanks,
Rama (1 Reply)
Discussion started by: ramareddi16
1 Replies
8. Solaris
Hi Guys,
I have an issue with my Hotspares/Metastat on an x4270m2.
I have no hotspares available, when i printed out my metastat i got
d21: Concat/Stripe
Size: 33559785 blocks (16 GB)
Stripe 0:
Device Start Block Dbase Reloc
... (0 Replies)
Discussion started by: A-Train
0 Replies
9. Solaris
I would like to perform root disk mirroring task. Can someone please help me out on this.
Thanks !!
Regards,
Rama (2 Replies)
Discussion started by: ramagore85
2 Replies
10. Solaris
I have 2 disks in my system.I recently added a zpool to the disk, but today I changed my mind and deleted the zpool ,
zpool destroy -f extra
The zpool is now deleted and I want to partition the disk, so I delete the only partition on the disk.
Now when I run format again,
format... (13 Replies)
Discussion started by: cbtshare
13 Replies
LEARN ABOUT SUNOS
metaimport
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)