One of the “Storage Groups” remains suspended

During the startup of the mailbox cluster on an Exchange Server 2003 system, one of the storage groups cannot be brought online and remains suspended. The following events appear in the Event Log:

Error Source MSExchangeRepl 
Event ID 2096 
The Microsoft Exchange Replication Service was unable to perform consistency checks 
on the passive node for CLUSTER\Third Storage Group because it could not find log file \\NODE1\PATH$\E020000EC55.log on the active node. 
A full reseed of the passive node for this storage group may be required. Reseeding can be done using the Update-StorageGroupCopy cmdlet 
in the Exchange Management Shell. 

Error Source MSExchangeRepl 
Event ID 2067 
Newly copied log file F:\Exchange Server\Mailbox\Third Storage Group\inspector\E02.log for CLUSTER\Third Storage Group is corrupt. 
Re-seeding the passive node is now required. Use the Update-StorageGroupCopy cmdlet in the Exchange Management Shell to perform a re-seed 
operation. 

Information Source MSExchangeRepl 
Event ID 2013 
The replication instance for storage group CLUSTER\Third Storage Group found an invalid copy of log file 
F:\Exchange Server\Mailbox\Third Storage Group\inspector\E02.log. The log file has been moved 
to F:\Exchange Server\Mailbox\Third Storage Group\IgnoredLogs\InspectionFailed\2009-01-15T07-53-46E02.log. 
Reason: The log file has failed inspection. It is inappropriate for replay.. 

The solution is to re‑seed the passive node, as described in the event, using the cmdlet Update‑StorageGroupCopy.

Update-StorageGroupCopy -Identity NODE1\Third Storage Group