Sponsored Content
Top Forums UNIX for Advanced & Expert Users Solaris 8 disk/mirroring issue Post 88788 by ghuber on Tuesday 8th of November 2005 05:29:11 PM
Old 11-08-2005
Quote:
Originally Posted by RTM
Re-seating the 'bad' drives can be done without powering down - they are hot-swappable so it would be like removing the old and putting in the new (just that it's the same drive). So try that first with c1t3 - if it spins up the system may see it. If not, you haven't lost anything.

You can determine the slice by looking at /etc/vfstab and finding the md device for / partiton. Then look at your metastat output for that device.

And the only way to tell if the drive is bad is to hit it - ls -Rla from top of the partition should create some errors at some point - or go into format and run an analyze (read, refresh, or test - the ones that do not harm data).

Double check that syslogd is running and configured to pop warning messages into your /var/adm/messages file (or what ever you put it in).
I tried removing and reseating the drive, but no go. The box still isn't seeing it... I ran an iostat -En and found c1t1 has a ton of hard errors and c1t3 is not listed... So I've requested two replacement drives from Sun.

Once I get them, I can hot swap them for a the new drives, right? Is there a command a need to run before yanking out the drive and putting in the new one? C1t1 seems to be a mirror of the slices of the system disk. If so I can then just run these command to setup slices automatically, right?

# prtvtoc /dev/rdsk/c1t0d0s2 > /tmp/format.out
# fmthard -s /tmp/format.out /dev/rdsk/c1t1d0s2

# prtvtoc /dev/rdsk/c1t2d0s2 > /tmp/format.out
# fmthard -s /tmp/format.out /dev/rdsk/c1t3d0s2

Then once that's done, I enable the metabases on the new disks as metastat indicates:

# /usr/opt/SUNWmd/metareplace -e d60 c1t3d0s6
# /usr/opt/SUNWmd/metareplace -e d60 c1t1d0s0
# /usr/opt/SUNWmd/metareplace -e d60 c1t1d0s1
# /usr/opt/SUNWmd/metareplace -e d60 c1t1d0s3
# /usr/opt/SUNWmd/metareplace -e d60 c1t1d0s6

The mirrors will start resyncing once metareplace is invoked, right?

Thanks!
 

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
metareplace(1M) 					  System Administration Commands					   metareplace(1M)

NAME
metareplace - enable or replace components of submirrors or RAID5 metadevices SYNOPSIS
/usr/sbin/metareplace -h /usr/sbin/metareplace [-s setname] -e mirror component /usr/sbin/metareplace [-s setname] mirror component-old component-new /usr/sbin/metareplace [-s setname] -e RAID component /usr/sbin/metareplace [-s setname] [-f] RAID component-old component-new DESCRIPTION
The metareplace command is used to enable or replace components (slices) within a submirror or a RAID5 metadevice. When you replace a component, the metareplace command automatically starts resyncing the new component with the rest of the metadevice. When the resync completes, the replaced component becomes readable and writable. If the failed component has been hot spare replaced, the hot spare is placed in the available state and made available for other hot spare replacements. Note that the new component must be large enough to replace the old component. A component may be in one of several states. The Last Erred and the Maintenance states require action. Always replace components in the Maintenance state first, followed by a resync and validation of data. After components requiring maintenance are fixed, validated, and resynced, components in the Last Erred state should be replaced. To avoid data loss, it is always best to back up all data before replacing Last Erred devices. OPTIONS
Root privileges are required for all of the following options except -h. -e Transitions the state of component to the available state and resyncs the failed component. If the failed component has been hot spare replaced, the hot spare is placed in the available state and made available for other hot spare replace- ments. This command is useful when a component fails due to human error (for example, accidentally turning off a disk), or because the component was physically replaced. In this case, the replacement component must be partitioned to match the disk being replaced before running the metareplace command. -f Forces the replacement of an errored component of a metadevice in which multiple components are in error. The component determined by the metastat display to be in the ``Maintenance'' state must be replaced first. This option may cause data to be fabricated since multiple components are in error. -h Display help message. -s setname Specifies the name of the diskset on which metareplace will work. Using the -s option will cause the command to perform its administrative function within the specified diskset. Without this option, the command will perform its function on local metadevices. mirror The metadevice name of the mirror. component The logical name for the physical slice (partition) on a disk drive, such as /dev/dsk/c0t0d0s2. component-old The physical slice that is being replaced. component-new The physical slice that is replacing component-old. RAID The metadevice name of the RAID5 device. EXAMPLES
Example 1 Recovering from Error Condition in RAID5 Metadevice This example shows how to recover when a single component in a RAID5 metadevice is errored. # metareplace d10 c3t0d0s2 c5t0d0s2 In this example, a RAID5 metadevice d10 has an errored component, c3t0d0s2, replaced by a new component, c5t0d0s2. Example 2 Use of -e After Physical Disk Replacement This example shows the use of the -e option after a physical disk in a submirror (a submirror of mirror mymirror1, in this case) has been replaced. # metareplace -e mymirror1 c1t4d0s2 Note: The replacement disk must be partitioned to match the disk it is replacing before running the metareplace command. EXIT STATUS
The following exit values are returned: 0 Successful completion. >0 An error occurred. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWmdu | +-----------------------------+-----------------------------+ |Interface Stability |Stable | +-----------------------------+-----------------------------+ SEE ALSO
mdmonitord(1M), metaclear(1M), metadb(1M), metadetach(1M), metahs(1M), metainit(1M), metaoffline(1M), metaonline(1M), metaparam(1M), metarecover(1M), metarename(1M), metaroot(1M), metaset(1M), metassist(1M), metastat(1M), metasync(1M), metattach(1M), md.tab(4), md.cf(4), mddb.cf(4), md.tab(4), attributes(5), md(7D) SunOS 5.11 26 Mar 2006 metareplace(1M)
All times are GMT -4. The time now is 03:28 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy