Sponsored Content
Top Forums UNIX for Advanced & Expert Users Solaris 8 disk/mirroring issue Post 88742 by ghuber on Tuesday 8th of November 2005 11:26:37 AM
Old 11-08-2005
Solaris 8 disk/mirroring issue

Hello!

I recently inherited system administration duties for a SUN v880 box. The system has 6 physical hard disks.. In doing some basic maintenance, I found they're configured for mirroring. I ran the metastat and metadb commands, and many of the mirrors are showing they are in need of maintenance -> See the attachments.

Question is -- How do get all the mirrors back online and functional? I was considering running the metareplace utility to enable the metabases, but it seems as if one of the hard disks is no longer being recongized by the system. (c1t3d0 -> see disks.txt) I've checked the /var/adm/message files but I don't see anything that would indicate the disk has failed, and the front status panel of the server itself (Including the error condition lights for each drive) is showing no problems... I was thinking of running touch /reconfigure, seeing the disk is redetected, if it is, then replacing the failed metabases using the metareplace and rebooting. Do you guys feel this will fix the problem?

Any advice would be greatly appreciated!
 

10 More Discussions You Might Find Interesting

1. Solaris

Solaris mirroring / non-root disk

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

[HELP] mirroring disk at solaris 8 sparc v890

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

Help !! disk Mirroring

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

Disk Mirroring for Solaris 10 x86

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

Solaris 10 Disk Mirroring

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

Disk Mirroring on solaris 5.8

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

root disk mirroring in solaris volume manager for solaris 10

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

Solaris Mirroring/Hotspare Issue

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

Root disk mirroring in Solaris 10

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

Solaris 11 disk issue

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
voldiskadd(8)						      System Manager's Manual						     voldiskadd(8)

NAME
voldiskadd - Adds one or more disks for use with the Logical Storage Manager SYNOPSIS
/usr/sbin/voldiskadd disk-address-list DESCRIPTION
The voldiskadd utility sets up new disks that are added to the system after the initial system installation and configures the disks for use by the Logical Storage Manager. A valid disk label must exist on the disk before using the voldiskadd utility. One or more disks may be specified using a disk-address-list. Disk addresses in the list have the form dskn (for the entire disk) or dsknp (for a specific partition). When specifying multiple disks, use a space between entries. Disk address names relate directly to device names in the /dev/disk directory. For example, here are some valid voldiskadd disk-address-list specifications: # voldiskadd dsk1 # voldiskadd dsk2 dsk3a The file, /etc/vol/disks.exclude, may be used to exclude disks from use by voldiskadd. Each line of the file specifies the name of a disk to exclude (for example, dsk5). The voldiskadd utility prompts the user for a disk group name and disk media name for the disks. If a new disk group name is specified, that disk group is created for the new disks. If no disk group name is specified, the disks are left as unassigned replacement disks for future use. If an existing disk group name is specified, the user is prompted for whether the disks should be designated as spares for the disk group. If a disk is found to already contain non-Logical Storage Manager partitioning, the user is asked whether the disk should be encapsulated. Encapsulation turns each partition of the disk into a volume. A disk should be encapsulated if it contains file systems or data that should not be overwritten. If encapsulation is not desired for a disk, the disk can be initialized as a new disk for use by the Logical Storage Manager. For new disks, all space on the disk becomes free space in the disk's disk group. Context-sensitive help is available at every prompt by typing ?. Also, a list option can be used to get information on available target disks for an operation. The voldiskadd utility supports the following general classes of actions: Initializing a disk with reserved regions and partitions. Disk initialization is performed by calling voldisksetup command. Adding a disk to an existing disk group. This operation can be performed independently of the initialization of the disk drive to add a disk's storage space to a disk group's free space pool. The volassist command may subsequently allocate from that free space. The disk can also be added as a hot spare device. Creating new disk groups in which to import new disks. If no disk group exists for importing disks, the option of creating the disk group is offered. Encapsulating disks that have exist- ing contents. This is the default action for disks that do not have a valid, existing Logical Storage Manager private region, but that do have a disk label. Encapsulation is performed by calling volencap. Reconnecting a drive that was temporarily inaccessible. This situation is detected automatically, by noting that the specified drive has a disk ID that matches a disk media record with no currently associated physical disk. After reconnection, any stale plexes referring the disk are reattached, and any stopped volumes referring the disk are restarted. This reattach action is performed by calling the volrecover script. ERRORS
You may receive the following messages when using the voldiskadd command: Initialization of disk device special-device failed. Error: special-device or an overlapping partition is open. This message indicates that the partition you specified or an overlapping partition on the disk is actively in use. The partition could be a mounted UFS or AdvFS filesystem, initialized as an LSM disk or used as a swap device. special-device is marked in use for fstype in the disklabel. If you continue with the operation you can possibly destroy existing data. Would you like to continue?? [y,n,q,?] (default: n) This message indicates that the fstype of a partition or an overlapping partition is set in the disk label. The voldiskadd command prints this message to warn that a disk partition may have valid data which could be destroyed. If you are sure that the disk partition does not have valid data and that the partition can be added to LSM, you can ignore the warning message by entering y at the prompt. The voldiskadd command will proceed to initialize the disk partition and add it to LSM. FILES
A list of disks to exclude from use by voldiskadd. SEE ALSO
disklabel(8), volassist(8), voldisk(8), voldiskadm(8), voldisksetup(8), voldg(8), volintro(8) voldiskadd(8)
All times are GMT -4. The time now is 02:39 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy