Cluster runs CHKDSK - permissions issue

[reach567]

I have setup an HP MSA1000 with two nodes that are clustered. They
are the only two nodes that are currently connected to the MSA1000.
The two nodes, ML370 G2s, are running Windows 2000 Adv Server with
SP3. HP had multiple issues with the MSA1000, but I believe all are
fixed with the latest firmware, drivers, etc. I have updated
everything that is recommended by HP (EMU, 6 port switch firmware,
HBAs drivers, MSA1000 controllers, etc).

The cluster seems to be working great when the cluster service is run
under a domain admin account. However, if the service account is
switched to another account other than the domain admin account it
runs a chkdsk as soon as the service is started. It also sporatically
runs the chkdsk whenever it feels like (it has a mind of it's own).
Additionally, it will run a chkdsk when the cluster is failed over
(either by "move group" option in Cluster Administrator or when
rebooting the primary node).

The account that I have setup for the cluster service has Local
Administrative privileges on both nodes. It also has Logon as Service
right.

What am I missing? This is driving me nuts, and lots of hours of
pulling my hair out. Any help is much appreciated!!!!

Thank you

reach

 

[JT]

The Cluster service account requires the following rights on all nodes in
the cluster to function properly:

- Act as part of the operating system (only required with Windows 2000).
- Back up files and directories.
- Increase quotas.
- Increase scheduling priority.
- Load and unload device drivers.
- Lock pages in memory.
- Log on as a service.
- Restore files and directories.

You should read the following KB article for more details:

How to Manually Re-Create the Cluster Service Account
http://support.microsoft.com/default.aspx?scid=kb;en-us;269229

Additionally, you could disable chkdsk'ing for cluster volumes by setting
the /priv
properties of the cluster disk resource using the cluster.exe command line
utility. If you want to prevent cluster from chkdsk'ing a drive when it
believes that it is "dirty", issue the following command:

cluster res "Disk Q:" /priv Skipchkdsk=1

You can read more about this and other private properties in the following
KB article:

Enhanced Disk Resource Private Properties Using Cluster Server
http://support.microsoft.com/default.aspx?scid=kb;en-us;223023

Regards,
JT

 

[reach567]

Thanks JT!!! I will give it a try and let you know how it goes...

reach