Hi Fred, Okay. So it looks the problem with DID. Let's start with the VTOC for the disk also.
# scdidadm -L d145 <<< You will see CTD disk here>> # prtvtoc <ctd_disk_path> The scdpmd used <did_path>s0 to check the disk status. --Check that ctd disk is accessible through s0 slice ... After enusuring that for ctd paths are fine, run the following commands # devfsadm # scdidadm -C # scdidadm -r # scgdevs Now check the DID paths s0 and s2 slices whether they are accessible. If it is then scdpm will mark the disk as OK after 10mins which the probe interval. Thanks -Venku On 10/29/09 16:06, Fred wrote: > Hi Venkateswarlu. I think you got the point. > > Actually prtvtoc /dev/did/rdsk/d145s2 says no such device ...where I can > access the disk through format and also Veritas is managing them. > > So I don't know why is that... is it possible to fix this now? Veritas > ha put data on it > > Fred > > > > On Thu, Oct 29, 2009 at 11:09 AM, Venkateswarlu Tella > <Venkateswarlu.Tella at sun.com <mailto:Venkateswarlu.Tella at sun.com>> > wrote: > > Hi Fred, > Can you check whether the DID devices are accessible? > What is o/p of > # prtvtoc /dev/did/rdsk/d145s2 > # dd if=/dev/did/rdsk/d145s0 of=/dev/null count=1 > > I might also helps to check the syslog messages to see for any other > error messages related to the "Failed" devices. > > Thanks > -Venku > > > On 10/29/09 15:33, Fred wrote: > > Hi Joerg. > > I already tried format -e etc etc and everything seems to be > similar to the other disks... > > If I try to look at the reservation keys on those disks I got an > error like couldn't open the device.... errno 6. > I think somehow Veritas can manage the disks but Sun Cluster > could not.. It there a way to put manually a key (like Sun > cluster does) on a disk? > > FRED > > > On Wed, Oct 28, 2009 at 5:29 PM, joerg noack <jnoack at gmx.de > <mailto:jnoack at gmx.de> <mailto:jnoack at gmx.de > <mailto:jnoack at gmx.de>>> wrote: > > if I remember correct scdpm just makes a SCSI inquiry to test. I > would read the vtoc and > format -e >> scsi>> inq to dig deeper. Probably there is simply a > connection issue or some config speciality of EMC ;) > > HTH, > jono > -- > This message posted from opensolaris.org > <http://opensolaris.org> <http://opensolaris.org> > > _______________________________________________ > ha-clusters-discuss mailing list > ha-clusters-discuss at opensolaris.org > <mailto:ha-clusters-discuss at opensolaris.org> > <mailto:ha-clusters-discuss at opensolaris.org > <mailto:ha-clusters-discuss at opensolaris.org>> > > http://mail.opensolaris.org/mailman/listinfo/ha-clusters-discuss > > > > > ------------------------------------------------------------------------ > > > _______________________________________________ > ha-clusters-discuss mailing list > ha-clusters-discuss at opensolaris.org > <mailto:ha-clusters-discuss at opensolaris.org> > http://mail.opensolaris.org/mailman/listinfo/ha-clusters-discuss > >
