[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference decwet::winnt-clusters

Title:WinNT-Clusters
Notice:Info directories moved to DECWET::SHARE1$:[NT_CLSTR]
Moderator:DECWET::CAPPELLOF
Created:Thu Oct 19 1995
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:863
Total number of notes:3478

678.0. "Crash doing upgrade" by ROMTSS::MATTACCHIONE () Mon Mar 10 1997 11:08

Hi

I have use the field test Digital Cluster 1.1 in a new installation and
in upgrade.

In the first case installation is gone without problem.

In the second case I have as final result a crash when attempt to 
access at digital cluster.

I have followed instruction in release note.

In detail:

I have used the manually fail my node to the other service.
Then deinstalled the Digital Cluster version 1.0a. 
Upgraded Nt 3.51 service pack 5 to Nt 4.0 service pack 2.
Checked for Hszdisk version 3.01.
Installed Digital Cluster 1.1 .
Then reboot it.

Logging to upgraded node after few minutes the machine goes in crash dump.

The first line is:

*** STOP 0X0000001E (0xC00000005,Ox80201C46,0x00000000,0x00000028)
KMODE_EXCEPTION_NOTHANDLED ***

Address 80201c46 has base at 80201000  CLASS2.SYS

.................................................

Have anyone upgraded a cluster and obtain a similar error?
There is a workaround about?

Thanks Gabriele
T.RTitleUserPersonal
Name
DateLines
678.1More infos ...NETRIX::"[email protected]"Mon Mar 10 1997 13:37100
I insert here the fmxxx.logDigital Clusters for Windows NT(TM) 1.1-1165 Beta
(expires Jul 1, 1997) (Build 1165)
Digital Equipment Corporation
Windows NT(TM) is a trademark of Microsoft Corporation.
Cluster Failover Manager Trace File
Opened on cluster NTCLUSTCED node NT2CED at 10/03/97 17.08.26
by program D:\Program Files\Digital\Cluster\fmcore.exe

17:08:27.343 tid=89  trace started
17:08:27.531 tid=89  Cfmd Server is not ready, waiting...
17:08:59.312 tid=89  Loading failover object dll fmdisk.dll...
17:09:02.796 tid=89  Disk Failover Object DLL Process Attach
17:09:03.000 tid=89  Disk Failover Object DLL Establish Linkage
17:09:03.203 tid=89  Loading failover object dll fmip.dll...
17:09:04.062 tid=89  IP Failover Object DLL Process Attach
17:09:04.359 tid=89  IP Failover Object DLL Establish Linkage
17:09:04.609 tid=89  Loading failover object dll fmoracle.dll...
17:09:05.125 tid=89  Oracle Failover Object DLL Process Attach
17:09:05.390 tid=89  Oracle Failover Object DLL Establish Linkage
17:09:05.656 tid=89  Loading failover object dll fmscript.dll...
17:09:06.359 tid=89  Script Failover Object DLL Process Attach
17:09:06.578 tid=89  Script Failover Object DLL Establish Linkage
17:09:06.843 tid=89  Loading failover object dll fmsql.dll...
17:09:07.562 tid=89  Sql Failover Object DLL Process Attach
17:09:07.906 tid=89  Sql Failover Object DLL Establish Linkage
17:09:13.078 tid=89  Entering Failover Manager Main
17:09:13.453 tid=89  Created GROUP nexus "Raid_1"
17:09:13.609 tid=89  GROUP nexus "Raid_1" node NT1CED inital state Offline
17:09:13.812 tid=89  Created GROUP nexus "Raid_2"
17:09:13.812 tid=192 Monitoring group "Raid_1"
17:09:14.078 tid=89  GROUP nexus "Raid_2" node NT1CED inital state Offline
17:09:14.671 tid=89  Script DLL Initialize
17:09:14.671 tid=193 Monitoring group "Raid_2"
17:09:15.828 tid=193 Waiting 30 seconds for connections to stabilize.
17:09:15.828 tid=89  IP DLL Initialize
17:09:15.828 tid=192 Waiting 30 seconds for connections to stabilize.
17:09:16.218 tid=89  AdapterKey =DC21X41
17:09:16.687 tid=89  Subkey number: -1-
17:09:16.953 tid=89  ServiceName = DC21X41
17:09:17.156 tid=89  TitleName = [1] DEC PCI Ethernet DECchip 21041
17:09:17.296 tid=89  Subkey number: -2-
17:09:17.406 tid=89  ServiceName = Defpa2
17:09:17.703 tid=89  IpDataCreate IP address string = 10.10.92.13�
17:09:17.812 tid=89  IpDataCreate Subnet Mask string = 255.255.252.0
17:09:17.906 tid=89  IpDataCreate pIpObject -> IpAddressString = 10.10.92.13�
17:09:18.062 tid=89  IpDataCreate pIpObject -> SubnetMaskString =
255.255.252.0
17:09:18.187 tid=89  IpDataCreate pIpObject -> IpAddress -> s_addr = 0D5C0A0A
17:09:18.390 tid=89  AdapterKey =Defpa2
17:09:18.609 tid=89  Subkey number: -1-
17:09:18.828 tid=89  ServiceName = DC21X41
17:09:18.921 tid=89  Subkey number: -2-
17:09:19.031 tid=89  ServiceName = Defpa2
17:09:19.140 tid=89  TitleName = [2] DEC FDDIcontroller/PCI Adapter
17:09:19.343 tid=89  IpDataCreate IP address string = 192.0.44.24�
17:09:19.593 tid=89  IpDataCreate Subnet Mask string = 255.255.255.0
17:09:19.843 tid=89  IpDataCreate pIpObject -> IpAddressString = 192.0.44.24�
17:09:19.984 tid=89  IpDataCreate pIpObject -> SubnetMaskString =
255.255.255.0
17:09:20.093 tid=89  IpDataCreate pIpObject -> IpAddress -> s_addr = 182C00C0
17:09:20.437 tid=89  Disk Failover Object DLL Initialize
17:09:20.921 tid=89  Disk arbitration interval set to 30 seconds
17:09:21.109 tid=89  Disk error threshold set to 5 errors
17:09:21.312 tid=89  Disk error separation interval set to 90 seconds
17:09:21.968 tid=89  Step Ib: Forcing Scsi disk driver to discover new devices
17:09:22.578 tid=89  Disk device: \\.\PhysicalDrive0
Reason: DISK FIND NEW DEVICES function failed
Error: Unknown error code 3780189064 (sev=3,fac=0x151,id=0x1b88)

    File: E:\CluBuild\src\fm\fmdisk\device.c    Line: 2007
17:09:22.953 tid=89  Disk device: \\.\PhysicalDrive1
Reason: DISK FIND NEW DEVICES function failed
Error: Unknown error code 3780161096 (sev=3,fac=0x150,id=0xae48)

    File: E:\CluBuild\src\fm\fmdisk\device.c    Line: 2007
17:09:23.328 tid=89  Step II: Identifying shared devices by probing Dos
physical drives
17:09:23.484 tid=89  \Device\Harddisk0 is 
scsi address (0, 0, 5, 0) product id 'DEC     SWXRC-04        V30Z'
17:09:23.578 tid=89  \Device\Harddisk1 is 
scsi address (0, 0, 5, 1) product id 'DEC     SWXRC-04        V30Z'
17:09:23.750 tid=89  The driver for \Device\ScsiPort0 is aic78xx
17:09:23.921 tid=89  The initiator id for \Device\ScsiPort0 is 6
17:09:24.078 tid=89  This system has 1 initiators, 3 disks, 2 shared disk(s)
17:09:24.265 tid=89  Step IIIa: bus excl. prot. read partition table/sig
17:09:24.531 tid=196 FindNewPartitionsPerInitiator thread id 196
17:09:46.125 tid=193 Waited long enough for group "Raid_2" nexus to come up
17:09:46.484 tid=192 Waited long enough for group "Raid_1" nexus to come up
17:09:46.765 tid=196 Send: node NT1CED is not connected through the nexus-no
msg
17:09:47.765 tid=196 Request FINDPT: not transmitted, Response TAKEOVER,
Status: 8ca
17:09:47.984 tid=196 SubStateCode: THANKS
17:09:48.046 tid=177 Listening for data for group "Raid_1"
17:09:48.046 tid=103 Group Raid_2 waiting for Fm Core Running
17:09:48.046 tid=97  Listening for data for group "Raid_2"
17:09:48.046 tid=44  Group Raid_1 waiting for Fm Core Running
17:09:48.093 tid=196 Process Response TAKEOVER - PerformFindNewPartitions

[Posted by WWW Notes gateway]
678.2typo?SWETSC::NORDBERGCon Brio Mon Mar 10 1997 15:297
    17:09:19.843  IpDataCreate pIpObject -> IpAddressString =192.0.44.24�
                                                                      ===
    		Seems to be a typo in your Ip-config ------------------^
    
Maybe thats your problem..
    
    //AndersN