Re: 2003 Cluster Fails to start after a reboot

Tech-Archive recommends: Fix windows errors by optimizing your registry

dbarter_at_colby.edu
Date: 03/23/04 

Date: Tue, 23 Mar 2004 05:09:55 -0800

Below I have attached the last 30 or lines from the log.
It seems as though it cannot see the quorum disk on the
shared resource, but I cannot determine why.

00000230.00000d98::2004/03/23-13:04:31.358 INFO [FM]
OfflineWaitingResourceTree: Exit, status=0 for <Disk Q:
G:>.
00000230.00000d98::2004/03/23-13:04:31.358 INFO [FM]
FmpOfflineWaitingTree: Quorum resource is in the same
group,Moving list=0x00000000
00000230.00000d98::2004/03/23-13:04:31.358 INFO [FM]
FmpOfflineWaitingTree: returned status 0 for <Disk Q: G:>.
00000230.00000d98::2004/03/23-13:04:31.358 INFO [FM]
FmpHandleResStateChangeProc: Exit...
00000230.0000058c::2004/03/23-13:04:33.139 INFO [FM]
FmpOfflineGroup, Group=5f422c0e-3471-4198-b9e8-b1faf8b6902c
00000230.0000058c::2004/03/23-13:04:33.139 INFO [FM]
FmpOfflineGroup: Bring quorum resource offline
00000230.0000058c::2004/03/23-13:04:33.139 INFO [DM]
DmpQuoObjNotifyCb: Quorum resource
offline/offlinepending/preoffline
00000230.0000058c::2004/03/23-13:04:33.139 INFO [MM]
MmSetQuorumOwner(0,0), old owner 0.
00000c9c.00000c50::2004/03/23-13:04:33.139 INFO Physical
Disk <Disk Q: G:>: Terminate, ResourceEntry @ 0009B500
Valid 0
00000c9c.00000cd8::2004/03/23-13:04:33.139 INFO Physical
Disk <Disk Q: G:>: [PnP] Stop watching PnP events for disk
d30fb4f
00000c9c.00000cd8::2004/03/23-13:04:33.139 WARN Physical
Disk <Disk Q: G:>: [PnP] RemoveDisk: WatchedList is empty
00000c9c.00000cd8::2004/03/23-13:04:33.139 INFO Physical
Disk <Disk Q: G:>: [PnP] Stop watching disk d30fb4f -
processed
00000c9c.00000c50::2004/03/23-13:04:33.139 INFO Physical
Disk <Disk Q: G:>: DiskCleanup started.
00000c9c.00000c50::2004/03/23-13:04:33.139 INFO Physical
Disk <Disk Q: G:>: [DiskArb] StopPersistentReservations is
called.
00000c9c.00000c50::2004/03/23-13:04:33.139 INFO Physical
Disk <Disk Q: G:>: [DiskArb] StopPersistentReservations is
complete.
00000c9c.00000c50::2004/03/23-13:04:33.139 INFO Physical
Disk <Disk Q: G:>: DiskCleanup returning final error 0
00000230.0000058c::2004/03/23-13:04:33.139 INFO [CP]
CppResourceNotify for resource Disk Q: G:
00000230.0000058c::2004/03/23-13:04:33.139 INFO [FM]
RmTerminateResource: 3b521280-b389-46aa-afec-d5ded764fbd4
is now offline
00000230.0000058c::2004/03/23-13:04:33.139 INFO [FM]
FmpMoveGroup: Entry
00000230.0000058c::2004/03/23-13:04:33.139 INFO [FM]
FmpMoveGroup: Exit group <Cluster Group>, status = 5005
00000230.0000058c::2004/03/23-13:04:33.139 INFO [FM]
FmpNotifyGroupStateChangeReason: Notifying group Cluster
Group [5f422c0e-3471-4198-b9e8-b1faf8b6902c] of state
change reason 3...
00000230.0000058c::2004/03/23-13:04:33.139 INFO [FM]
FmpRmCreateResource: creating resource a58b492d-3804-474c-
bb4f-2dec090c7a5b in shared resource monitor
00000c9c.00000d10::2004/03/23-13:04:33.139 ERR IP Address
<Cluster IP Address>: Unable to get local node ID, status
70.
00000c9c.00000d10::2004/03/23-13:04:33.139 INFO IP Address
<Cluster IP Address>: Resource closed.
00000c9c.00000d10::2004/03/23-13:04:33.139 WARN [RM]
RmpInsertResourceList failed, returned 70
00000c9c.00000d10::2004/03/23-13:04:33.139 ERR [RM]
Failed creating resource a58b492d-3804-474c-bb4f-
2dec090c7a5b, error 70.
00000230.0000058c::2004/03/23-13:04:33.139 INFO [FM]
FmpRmCreateResource: unable to create resource a58b492d-
3804-474c-bb4f-2dec090c7a5b
00000230.0000058c::2004/03/23-13:04:33.139 INFO [FM]
FmpRmCreateResource: creating resource 66bc49bc-06aa-4b1b-
9b3c-1d074660b61f in shared resource monitor
00000c9c.00000c50::2004/03/23-13:04:33.139 ERR Network
Name <Cluster Name>: Unable to get local node name, status
70.
00000c9c.00000c50::2004/03/23-13:04:33.139 INFO Network
Name <Cluster Name>: Open failed, status 70
00000c9c.00000c50::2004/03/23-13:04:33.139 WARN [RM]
RmpInsertResourceList failed, returned 70
00000c9c.00000c50::2004/03/23-13:04:33.139 ERR [RM]
Failed creating resource 66bc49bc-06aa-4b1b-9b3c-
1d074660b61f, error 70.
00000230.0000058c::2004/03/23-13:04:33.139 INFO [FM]
FmpRmCreateResource: unable to create resource 66bc49bc-
06aa-4b1b-9b3c-1d074660b61f
00000230.0000058c::2004/03/23-13:04:33.139 INFO [FM]
FmpCleanupGroupsPhase2: Exit
00000230.00000c78::2004/03/23-13:04:33.139 INFO [FM]
FmpCleanupGroups: Cleanup thread finished in time
00000230.00000c78::2004/03/23-13:04:33.139 INFO [FM]
FmpCleanupGroups: Exit
00000230.00000c78::2004/03/23-13:04:33.139 INFO [Dm]
DmShutdown
00000230.00000c78::2004/03/23-13:04:33.139 INFO [DM]
DmpShutdownFlusher: Entry
00000230.00000c78::2004/03/23-13:04:33.139 INFO [DM]
DmpShutdownFlusher: Setting event
00000230.00000a04::2004/03/23-13:04:33.139 INFO [DM]
DmpRegistryFlusher: got 0
00000230.00000a04::2004/03/23-13:04:33.139 INFO [DM]
DmpRegistryFlusher: exiting
00000230.00000c78::2004/03/23-13:04:33.139 WARN [MM]
MMLeave is called when rgp=NULL.
00000230.00000c78::2004/03/23-13:04:33.139 ERR [CS]
Service Stopped. exit code = 5029

00000c9c.00000d5c::2004/03/23-13:04:33.358 WARN [RM] Going
away, Status = 1, Shutdown = 0.
00000c9c.00000d5c::2004/03/23-13:04:33.358 INFO [RM]
Posting shutdown notification.
00000c9c.00000e70::2004/03/23-13:04:33.358 INFO [RM]
NotifyChanges shutting down.
00000c9c.00000d5c::2004/03/23-13:04:33.858 INFO Physical
Disk <Disk Q: G:>: DisksRelease started, Inserted = 0
00000c9c.00000d5c::2004/03/23-13:04:33.858 INFO Physical
Disk <Disk Q: G:>: [DiskArb] StopPersistentReservations is
called.
00000c9c.00000d5c::2004/03/23-13:04:33.858 INFO Physical
Disk <Disk Q: G:>: [DiskArb] StopPersistentReservations is
complete.
00000c9c.00000d5c::2004/03/23-13:04:33.858 INFO Physical
Disk <Disk Q: G:>: Terminate, ResourceEntry @ 0009B500
Valid 0
00000c9c.00000cd8::2004/03/23-13:04:33.858 INFO Physical
Disk <Disk Q: G:>: [PnP] Stop watching PnP events for disk
d30fb4f
00000c9c.00000cd8::2004/03/23-13:04:33.858 WARN Physical
Disk <Disk Q: G:>: [PnP] RemoveDisk: WatchedList is empty
00000c9c.00000cd8::2004/03/23-13:04:33.858 INFO Physical
Disk <Disk Q: G:>: [PnP] Stop watching disk d30fb4f -
processed
00000c9c.00000d5c::2004/03/23-13:04:33.858 INFO Physical
Disk <Disk Q: G:>: DiskCleanup started.
00000c9c.00000d5c::2004/03/23-13:04:33.858 INFO Physical
Disk <Disk Q: G:>: [DiskArb] StopPersistentReservations is
called.
00000c9c.00000d5c::2004/03/23-13:04:33.858 INFO Physical
Disk <Disk Q: G:>: [DiskArb] StopPersistentReservations is
complete.
00000c9c.00000d5c::2004/03/23-13:04:33.858 INFO Physical
Disk <Disk Q: G:>: DiskCleanup returning final error 0
00000c9c.00000d5c::2004/03/23-13:04:33.858 INFO Physical
Disk <Disk Q: G:>: DisksMountPointCleanup: Cleanup mount
point information
00000c9c.00000d5c::2004/03/23-13:04:33.858 INFO Physical
Disk <Disk Q: G:>: [DiskArb] ArbitrationInfoCleanup.
00000c9c.000009d0::2004/03/23-13:04:33.858 INFO [RM]
RmpPollerThread: Asked to exit...
00000c9c.000009d0::2004/03/23-13:04:33.858 INFO [RM]
PollerThread stopping. Shutdown = 1, Status = 1,
WaitFailed = 0, NotifyEvent address = 196.
>-----Original Message-----
>Hi David
>
>Please try looking into cluster.log to see if you get
more clues on why the
>service fails to start. The cluster log is located in
>%WINDIR%\cluster folder.
>
>--Regards
> Amit Kumar
>This posting is provided "AS IS" with no warranties, and
confers no rights.
>"Please do not send e-mail directly to this alias. This
alias is for
>newsgroup purposes only."
>
>"dbarter" <anonymous@discussions.microsoft.com> wrote in
message
>news:cf1901c4104a$e28dbaa0$a001280a@phx.gbl...
>> Hello,
>>
>> I have a 2003 fileserver cluster that I have built.
After
>> first setup and restarts it works very well. However
after
>> a while (couple of days), I might have to restart the
>> cluster, the cluster service fails to start. The error
>> message that I get is: "The cluster service has
terminated
>> unexpectedly" I get and event id of 7031. Any ideas
would
>> be appreciated.
>>
>> David
>
>
>.
>

Relevant Pages

  • Phisical disk resource
    ... I'm setting up a 2 node cluster under 2003 ent. ... is working but I am not able to bring the shared disk ... INFO FmpPropagateResourceState: resource a94c4968- ... INFO Physical Disk: ...
    (microsoft.public.windows.server.clustering)
  • Re: Windows 2003/SQL 2000 Cluster SAN Migration
    ... Isin't the W2K3 Cluster Server Recovery tool designed to ... > 4) assume the Old disk drive is O: and the New disk Drive is N: ... > 4) Create a new Disk Resource for the new disk and have that in the SQL ... >>just fine but not the data drives, basically on step 14 my old drives ...
    (microsoft.public.windows.server.clustering)
  • Re: Unable to start the cluster service when creating a new 2 node
    ... existing cluster and could no form a new cluster. ... node 1 as possible host for resource 6add91be-f8ae-4fb7-b78d-2488c502ad0a. ... FmpAddPossibleNodeToList for restype Physical Disk ... [DiskArb] ...
    (microsoft.public.windows.server.clustering)
  • Re: Windows 2003/SQL 2000 Cluster SAN Migration
    ... yeta lot of times it depends on each customer's enviornment and the complexity of the SAN migration. ... 305793 How to Replace a Disk That Is on a Windows 2000 or a Windows 2003 Server ... Windows NT/2000/2003 Cluster Technologies ... >> 4) Create a new Disk Resource for the new disk and have that in the SQL ...
    (microsoft.public.windows.server.clustering)
  • Re: Error installing SQL 2005 on a cluster
    ... I had created an "Unused Drives" resource group to keep my unused physical ... disk resources from becoming corrupted but hadn't brought them online. ... On a 32bit cluster it's usually C or D. If all ...
    (microsoft.public.sqlserver.clustering)