Online Pending status when a resource has failed

Hello,

I'm using EMC AutoStart Version 5.2.2 (Windows Print Services)
running on Windows Server 2003 SP1 Standard Edition.
My AutoStart domain has 2 nodes (NODENAME_A and NODENAME_B) and the
following five data sources:

Unidad_D
Unidad_E
Unidad_F
Unidad_G
Unidad_H

Yesterday at night, a resource failure occurs (see the log
information below).

===================================
Error StateMon Tue Sep 18 22:52:09 2007
By: ftStateMon on Node: NODENAME_B
MESSAGE: ID00001546 Data Source Monitor Rds_Unidad_H timed out. Problem with data source.
===================================
Error StateMon Tue Sep 18 22:52:12 2007
By: ftStateMon on Node: NODENAME_B
MESSAGE: ID00001546 Data Source Monitor Rds_Unidad_E timed out. Problem with data source.
===================================
Error StateMon Tue Sep 18 22:52:22 2007
By: ftStateMon on Node: NODENAME_B
MESSAGE: ID00001546 Data Source Monitor Rds_Unidad_D timed out. Problem with data source.
===================================
Error StateMon Tue Sep 18 22:52:38 2007
By: ftStateMon on Node: NODENAME_B
MESSAGE: ID00001546 Data Source Monitor Rds_Unidad_G timed out. Problem with data source.
===================================
Error StateMon Tue Sep 18 22:53:03 2007
By: ftStateMon on Node: NODENAME_B
MESSAGE: ID00001546 Data Source Monitor Rds_Unidad_F timed out. Problem with data source.
===================================
Error StateMon Tue Sep 18 22:54:09 2007
By: ftStateMon on Node: NODENAME_B
MESSAGE: ID00001546 Data Source Monitor Rds_Unidad_H timed out. Problem with data source.
===================================
Warning StateMon Tue Sep 18 22:54:09 2007
By: FT/Agent on Node: NODENAME_B
MESSAGE: ID00004721 Data Source Unidad_H on NODENAME_B is No Response
===================================
Info RULE Tue Sep 18 22:54:10 2007
By: FT/Rule Interpreter on Node: NODENAME_B
MESSAGE: ID00004738 Resource Group PS_FilePrint is in the Online Pending state. Current trigger is for resource Unidad_H on node NODENAME_B Cause - Data Source Failure
===================================
Error StateMon Tue Sep 18 22:54:12 2007
By: ftStateMon on Node: NODENAME_B
MESSAGE: ID00001546 Data Source Monitor Rds_Unidad_E timed out. Problem with data source.
===================================
Warning StateMon Tue Sep 18 22:54:12 2007
By: FT/Agent on Node: NODENAME_B
MESSAGE: ID00004721 Data Source Unidad_E on NODENAME_B is No Response
===================================
Error StateMon Tue Sep 18 22:54:22 2007
By: ftStateMon on Node: NODENAME_B
MESSAGE: ID00001546 Data Source Monitor Rds_Unidad_D timed out. Problem with data source.
===================================
Warning StateMon Tue Sep 18 22:54:22 2007
By: FT/Agent on Node: NODENAME_B
MESSAGE: ID00004721 Data Source Unidad_D on NODENAME_B is No Response
===================================
Info RULE Tue Sep 18 22:54:29 2007
By: FT/Rule Interpreter on Node: NODENAME_B
MESSAGE: ID00004724 About To Run Script: StartupResacn
===================================
Error StateMon Tue Sep 18 22:54:38 2007
By: ftStateMon on Node: NODENAME_B
MESSAGE: ID00001546 Data Source Monitor Rds_Unidad_G timed out. Problem with data source.
===================================
Warning StateMon Tue Sep 18 22:54:38 2007
By: FT/Agent on Node: NODENAME_B
MESSAGE: ID00004721 Data Source Unidad_G on NODENAME_B is No Response
===================================
Error StateMon Tue Sep 18 22:55:03 2007
By: ftStateMon on Node: NODENAME_B
MESSAGE: ID00001546 Data Source Monitor Rds_Unidad_F timed out. Problem with data source.
===================================
Warning StateMon Tue Sep 18 22:55:03 2007
By: FT/Agent on Node: NODENAME_B
MESSAGE: ID00004721 Data Source Unidad_F on NODENAME_B is No Response
===================================
Error StateMon Tue Sep 18 22:56:10 2007
By: ftStateMon on Node: NODENAME_B
MESSAGE: ID00001546 Data Source Monitor Rds_Unidad_H timed out. Problem with data source.
===================================
Error StateMon Tue Sep 18 22:56:12 2007
By: ftStateMon on Node: NODENAME_B
MESSAGE: ID00001546 Data Source Monitor Rds_Unidad_E timed out. Problem with data source.
===================================
Error StateMon Tue Sep 18 22:56:23 2007
By: ftStateMon on Node: NODENAME_B
MESSAGE: ID00001546 Data Source Monitor Rds_Unidad_D timed out. Problem with data source.
===================================
Error StateMon Tue Sep 18 22:56:39 2007
By: ftStateMon on Node: NODENAME_B
MESSAGE: ID00001546 Data Source Monitor Rds_Unidad_G timed out. Problem with data source.
===================================
Error StateMon Tue Sep 18 22:57:03 2007
By: ftStateMon on Node: NODENAME_B
MESSAGE: ID00001546 Data Source Monitor Rds_Unidad_F timed out. Problem with data source.
===================================
Info StateMon Tue Sep 18 22:57:10 2007
By: FT/Agent on Node: NODENAME_B
MESSAGE: ID00004712 Data Source Unidad_H on NODENAME_B is Attached
===================================
Info StateMon Tue Sep 18 22:57:12 2007
By: FT/Agent on Node: NODENAME_B
MESSAGE: ID00004712 Data Source Unidad_E on NODENAME_B is Attached
===================================
Info StateMon Tue Sep 18 22:57:23 2007
By: FT/Agent on Node: NODENAME_B
MESSAGE: ID00004712 Data Source Unidad_D on NODENAME_B is Attached
===================================
Info StateMon Tue Sep 18 22:57:40 2007
By: FT/Agent on Node: NODENAME_B
MESSAGE: ID00004712 Data Source Unidad_G on NODENAME_B is Attached
===================================
Info StateMon Tue Sep 18 22:58:04 2007
By: FT/Agent on Node: NODENAME_B
MESSAGE: ID00004712 Data Source Unidad_F on NODENAME_B is Attached
===================================

Today on morning, I found all data sources attached to NODENAME_B with
a green indicator for each one, but the Group State is Online Pending.
Also, this resource failing has been reported on the Availability Tracking
tab, and I'm seeing that the duration time is still incrementing.

I know that I can abort the resource group operation, but I didn't do
nothing yet.

I have these questions:

- What could cause these errors?

- Is normally that this online pending state persists when
all data sources are attached and working fine on NODENAME_B?

- Why the resource failed duration time is incrementing yet?

- Is recommended that I abort that pending operation?

- Can I have some problem with the data on my nodes?

Any help would be appreciated.

Regards

Juan