From: Adametz, Bluejay (bluejay@fujigreenwood.com)
Date: Fri Aug 06 2004 - 07:16:41 EDT
A couple bits of information Peter Gergen asked about -
The controller and disks do show up in hwmgr -view dev and hwmgr -view
hierarchy (in the correct place in the hierarchy too).
I can run ra200info5 on the cluster and get a full report from the
controller showing all the settings, configuration, and properly functioning
disks.
The device special files are there, and dsfmgr -v reports no problems.
The schedule for this upgrade is very tight, so I'm probably going to have
to drop back to pk3. HP hasn't come up with anything yet either.
Thanks for all the ideas. Probably once this upgrade is over with I can
revisit the pk4 issue.
> Peter Gergen and Martin Koerfer, as well as HP, suggested
> that the problem
> might be with the ddr.db and/or ddr.dbase files. They are
> identical between
> the working(standalone) system and the non-working(clustered)
> systems. And,
> according to HP (upon review), the SWXCR controller isn't
> treated as a SCSI
> device anyway.
>
> Because of the tight schedule I have on this project, I may
> be forced to
> drop back to patch kit 3 if HP doesn't come up with something soon.
>
> More news as it happens...
>
> Original question:
> > I just built a new cluster and, while the non-clustered
> > system I started
> > with has no problems, when I boot the cluster system, neither
> > cluster member
> > can access it's SWXCR disks. hwmgr shows the disks, but
> > attempting to even
> > show the disk label results in "No such device or address". Before
> > attempting to access the disk, drdmgr shows a server for the
> > disks, but
> > afterwards, it reports "No Server".
- Bluejay Adametz
There is no use in having a dog and doing your own barking.
This archive was generated by hypermail 2.1.7 : Sat Apr 12 2008 - 10:50:06 EDT