Re: [foxboro] Broken Concatenated Disk

OK, So: the problem has gone away?
I suggest we enjoy the moment.

When I follow your procedure (in theory, I haven't tried it for real) I
seems to me that you first restored everything and you ran into trouble
after which you restore all partitions manually but NO the metabd partition.
Maybe there somewhere hidden deep below lies the clue. I don't have another.
Unable to mount the "root" does ring a "metadb bell".

Regards

Ron Deen

-----Original Message-----
From: Murray, Steve [mailto:SMurray@xxxxxxxxxx]
Sent: Tuesday, February 12, 2002 7:00 AM
To: 'foxboro@xxxxxxxxxxxxx'
Subject: Re: [foxboro] Broken Concatenated Disk



Hi Ron,

  I did look at HH835 earlier today, but it did not seem to address my
particular problem.

  After trying some of the replace procedures I wound up with a primary
drive that would not boot either - it claimed it could not mount the root
partition.

  So I dropped two new drives in, booted from the cdrom, and did a
restore_8MM.  Somewhere after restoring the /, /var, /usr, & Informix and
before setting up the /opt concatenation, I had problems with the new
drives.

  Initially dft show_status showed d1 through d5 as "okay", but newfs gave
me a write error and said the NEW disk needs maintenance.

  I was able to dft format_disk and add_to_sys and then newfs worked ok, but
I still had a nds_maintenance on the new disk.  I finished the usfrestore of
the opt partition, and the first reboot worked fine, but after another
reboot the NEW main drive lost it's / root partition just like the old disk
had earlier.

  I rebooted from the cdrom again and just restored the /, /var/, /usr, and
Informix raw and skipped the /opt partition.

  Now I am online again, dft show_status shows all "okay", and I have no
idea what the original problem was.

  Just for kicks I replaced the external scsi cable to the drive enclosure,
but I doubt that was the problem.

  Thanks for the help,

  Steve Murray

-----Original Message-----
From: Ron Deen [mailto:r.deen@xxxxxxxxx]
Sent: Monday, February 11, 2002 2:15 PM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] Broken Concatenated Disk



I think the answer in the response from the "metastat" command you have 
supplied:

>     Invoke: after replacing "Maintenance" components:
>                 metareplace d5 c0t2d0s7 <new device>

Did you try that?

HH 835 may be of some help too. Some translation I did from this HH to the 
newer id's used today:
When a device (this example could be for your drive but the example was for
a 
mirrored drive that "nds_maint"):

metadetach -f d5 d15<cr>
metattach d5 d15<cr>

I'm almost sure you will need to roll back a tape by the way. I don't think 
that the data can be trusted when only one of the two disks is replaced.


Regards

Ron Deen
On Monday 11 February 2002 21:32, you wrote:
>   Anyone familiar with repairing a concatenated drive?
>
>   I have a AW51B with a simple concatenated drive (NOT mirrored).  From
> single user mode I can mount /opt and look at all the /opt files (at least
> all the SAM files, our operator displays, all the /opt/fox files, and
every
> other directory I checked).
>
>   The Informix historian conked out over the weekend and the last
timestamp
> on our "cooked" file was the same time that the concatenated disk went
into
> "needs maintenance" status.
>
>   If I drop in another disk and mount /opt I can tell which directories
are
> on the "bad" cat disk because I can't access them on the "new" cat disk -
> which is to be expected because the new disk is empty.
>
>   So if I CAN access directories that are on the "bad" disk, but the
status
> is "Nds_Maint", how can I  re-concatenate the disk?  There is a lot of
info
> in the Foxdoc on repairing mirrored drives, but not much on a simple
> concatenation.  The DiskSuite manual on docs.sun.com doesn't seem to
> address my problem either.
>
>   Any ideas?
>
> Steve Murray
> Asarco
> smurray@xxxxxxxxxx
>
>
>   My md.tab has:
> d15 2 1 /dev/dsk/c0t3d0s7 1 /dev/dsk/c0t2d0s7
>
>   3FFAW1# dft show_status
>
> Metamirror      Submirror      Size       Device        State
>
>    d0:             d10:        76000    ESP0 / SCSI3    Okay
>    d1:             d11:       197600    ESP0 / SCSI3    Okay
>    d2:             d12:        57760    ESP0 / SCSI3    Okay
>    d3:             d13:       258400    ESP0 / SCSI3    Okay
>    d4:             d14:      1231200    ESP0 / SCSI3    Okay
>    d5:             d15:      6478240    ESP0 / SCSI3    Nds_Maint
>
> Operation SUCCEEDED
>
> 3FFAW1# metastat -t
> .
> .
> .
> d5: Mirror
>     Submirror 0: d15
>       State: Needs maintenance Sun Feb 10 03:42:31 2002
>     Pass: 1
>     Read option: roundrobin (default)
>     Write option: parallel (default)
>     Size: 6478240 blocks
>
> d15: Submirror of d5
>     State: Needs maintenance Sun Feb 10 03:42:31 2002
>     Invoke: after replacing "Maintenance" components:
>                 metareplace d5 c0t2d0s7 <new device>
>     Size: 6478240 blocks
>     Stripe 0:
>       Device     Start  Dbase  State        Hot Spare  Time
>       c0t3d0s7       0  No     Okay                    Wed Apr 07
08:39:01
> 1999
>     Stripe 1:
>       Device     Start  Dbase  State        Hot Spare  Time
>       c0t2d0s7       0  No     Last Erred              Sun Feb 10
03:42:31
> 2002
>
>
>
>

<><><><><><><><<><><><><><><><<><><><><><><><>

This e-mail and any files transmitted with it are the property of Americas
Mining Corporation and/or its affiliates, are confidential, and are intended
solely for the use of 
the individual or entity to whom this e-mail is addressed. If you are not a
named recipient or otherwise have reason to believe that you have received
this message in error, 
please notify the sender and delete this message immediately from your
computer. Any other use, retention, dissemination forwarding, printing or
copying of this e-mail is 
strictly prohibited.  Although this email and any attachments are believed
to be free of any virus or other defect that might affect any computer
system into which it is 
received, and opened, it is the responsibility of the recipient to ensure
that it is virus free and no responsibility is accepted by Americas Mining
Corporation and/or its 
affiliates for any loss or damage arising in any way from its use

This e-mail has been scanned and cleared by MailMarshal 
www.marshalsoftware.com

<><><><><><><><<><><><><><><><<><><><><><><><>
 
 
_______________________________________________________________________
This mailing list is neither sponsored nor endorsed by Invensys Process
Systems (formerly The Foxboro Company). Use the info you obtain here at
your own risks. Read http://www.thecassandraproject.org/disclaimer.html
 
foxboro mailing list:             http://www.freelists.org/list/foxboro
to subscribe:         mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe:      mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
 
 
 
_______________________________________________________________________
This mailing list is neither sponsored nor endorsed by Invensys Process
Systems (formerly The Foxboro Company). Use the info you obtain here at
your own risks. Read http://www.thecassandraproject.org/disclaimer.html
 
foxboro mailing list:             http://www.freelists.org/list/foxboro
to subscribe:         mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe:      mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave

Other related posts: