Christopher Meiklejohn wrote:
>
> I have a E3500 here running DiskSuite 4.2.1. We have a mirror (d1) composed
> of submirrors (d11 and d10, each a stripe on a FC-AL disk).
>
> At one point, one of the disks failed, (submirror d11 ) and went into
> "Needs Maintanance". We replaced the failed
> disk, and put a new one in, the new disk showed up and we ran metareplace to
> sync the mirror up back up. It took about 1 hour.

That's a little slow for FC-AL disks.

> On the next system reboot the machine came up and the d11 submirror was back
> to needing maintenance. This happens every system reboot.
>
> Someone said that the luxadm command should have been used to remove the
> disk, which it wasn't.

Well, was it or wasn't it? Your next paragraph says it was.

> Luxadm stop and remove_device were used to stop the disk and remove it. We
> verified that the disk no longer showed up in 'format'. It did not.
> Luxadm insert was then used, and the new disk inserted,
> luxadm insert then exited with the "no new device enclousures found"
> message, but when 'format' was run the disk showed up.

It might be the old disk. Fiberchannel disks each have a unique
WWN so you need to reconfigure. The luxadm command should handle
this but you can also run devfsadm manually.

> At this point everytime the system is rebooted, the submirror comes up in
> 'Needs Maintainence'.
>
> I was just wondering if anyone else has had this issue with DiskSuite
> before?

No, if its not the WWN problem check if you have SDS patched.

-am © 2003

----- Original Message -----
From: "Anthony Mandic" <oy@hotmail.com>
Newsgroups: comp.sys.sun.admin
Sent: Wednesday, July 30, 2003 9:07 AM
Subject: Re: Issues with E3500 running DiskSuite 4.2.1


> Christopher Meiklejohn wrote:
> >
> > I have a E3500 here running DiskSuite 4.2.1. We have a mirror (d1)
composed
> > of submirrors (d11 and d10, each a stripe on a FC-AL disk).
> >
> > At one point, one of the disks failed, (submirror d11 ) and went into
> > "Needs Maintanance". We replaced the failed
> > disk, and put a new one in, the new disk showed up and we ran
metareplace to
> > sync the mirror up back up. It took about 1 hour.
>
> That's a little slow for FC-AL disks.
>
> > On the next system reboot the machine came up and the d11 submirror was
back
> > to needing maintenance. This happens every system reboot.
> >
> > Someone said that the luxadm command should have been used to remove the
> > disk, which it wasn't.
>
> Well, was it or wasn't it? Your next paragraph says it was.

It wasn't used initially. Initally the disk was removed and then the new
one installed and devfsadm run.

>
> > Luxadm stop and remove_device were used to stop the disk and remove it.
We
> > verified that the disk no longer showed up in 'format'. It did not.
> > Luxadm insert was then used, and the new disk inserted,
> > luxadm insert then exited with the "no new device enclousures found"
> > message, but when 'format' was run the disk showed up.
>
> It might be the old disk. Fiberchannel disks each have a unique
> WWN so you need to reconfigure. The luxadm command should handle
> this but you can also run devfsadm manually.
>
> > At this point everytime the system is rebooted, the submirror comes up
in
> > 'Needs Maintainence'.
> >
> > I was just wondering if anyone else has had this issue with DiskSuite
> > before?
>
> No, if its not the WWN problem check if you have SDS patched.

Which patch are you referring to?

>
> -am © 2003

Christopher Meiklejohn wrote:

> > > Someone said that the luxadm command should have been used to remove the
> > > disk, which it wasn't.
> >
> > Well, was it or wasn't it? Your next paragraph says it was.
>
> It wasn't used initially. Initally the disk was removed and then the new
> one installed and devfsadm run.

That should amount to the same thing.

> > > At this point everytime the system is rebooted, the submirror comes up
> in
> > > 'Needs Maintainence'.
> > >
> > > I was just wondering if anyone else has had this issue with DiskSuite
> > > before?
> >
> > No, if its not the WWN problem check if you have SDS patched.
>
> Which patch are you referring to?

There's an SDS patch for 4.2.1 on Solaris 8. I can't recall the
number but you can find it easily with PatchDiag. Just get this
from SunSolve, install and run it.

-am © 2003

Thanks alot.

"Anthony Mandic" <p9@hotmail.com> wrote in message
news:3F27E12E.BD5A5F50@hotmail.com...
> Christopher Meiklejohn wrote:
>
> > > > Someone said that the luxadm command should have been used to remove
the
> > > > disk, which it wasn't.
> > >
> > > Well, was it or wasn't it? Your next paragraph says it was.
> >
> > It wasn't used initially. Initally the disk was removed and then the
new
> > one installed and devfsadm run.
>
> That should amount to the same thing.
>
> > > > At this point everytime the system is rebooted, the submirror comes
up
> > in
> > > > 'Needs Maintainence'.
> > > >
> > > > I was just wondering if anyone else has had this issue with
DiskSuite
> > > > before?
> > >
> > > No, if its not the WWN problem check if you have SDS patched.
> >
> > Which patch are you referring to?
>
> There's an SDS patch for 4.2.1 on Solaris 8. I can't recall the
> number but you can find it easily with PatchDiag. Just get this
> from SunSolve, install and run it.
>
> -am © 2003