Again, the drive failed - but this time I seemed to catch it in the process of failing.
The symptoms included the constantly-on LED (which is what I noticed first), a failure of the WD Utilities to find the drive and when it did, it reported a failure of SMART and a size of 0 for the drive. However, the WD Quick View still functioned - sort of - showing the drive name and the % used but nothing else. I grabbed screenshots of some of the effects.
This time though the OS (WinXpSP3) didn’t report write failures.
So I rebooted/reset the drive, and it seemed to come back up OK.
This time I went into Admin Tools > Event Viewer and noted that around the time I spotted the constantly-on LED, two warnings cropped up:
WDRulesService (text is: The description for Event ID ( 0 ) in Source ( WDRulesService ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: Service started/resumed.)
WDBackup (text is: The description for Event ID ( 0 ) in Source ( WDBackup ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: Service started/resumed.)
I checked the Services and three were listed as running. Next time (there will be a next time, I am confident) I will check the Services before I do anything else.
Any suggestions?