I keep DW > Hardware > Automatic Diagnostics set to "Automatically check all drives for hardware malfunction" hourly, but since I updated to v 4.3 I haven't seen the three reports (i.e. S.M.A.R.T. status, temperature, and spare blocks) I've seen in Console > Console Messages since time immemorial.

I've trashed all my DW related files (Edit: and reinstalled DW, too) with no joy, and two e-mails to Alsoft, sent on 3-11 and 3-24, have not been acknowledged, let alone responded to.

I just reverted to DW 4.2, and Automatic Diagnostics is once again reporting in Console as expected.

Am I alone in experiencing this issue, or is it pervasive?

Thanks.

I just enabled the DW 4.3 Automatic Diagnostics setting, so I should soon know if this DW feature works for me.

BTW, what is it (DW) supposed to check, and presuming an affirmative report is generated in Console, what will it look like?

If you see what I didn't see it'll be in Console > Console Messages, and it'll look like this (which is the output from my reinstalled DW 4.2):

4/13/11 6:02:48 AM [0x0-0x1e01e].com.alsoft.diskwarriorstarter DiskWarriorDaemon: Wed Apr 13 06:02:48 EDT 2011. Running scheduled hardware tests.
4/13/11 6:02:48 AM [0x0-0x1e01e].com.alsoft.diskwarriorstarter DiskWarriorDaemon: [Wed Apr 13 06:02:48 EDT 2011] : ATA device 'WDC WD5000BEVT-00A0RT0', serial number 'WD-WX21A30L8760', reports it is functioning normally.
4/13/11 6:02:48 AM [0x0-0x1e01e].com.alsoft.diskwarriorstarter DiskWarriorDaemon: [Wed Apr 13 06:02:48 EDT 2011] : ATA device 'WDC WD5000BEVT-00A0RT0', serial number 'WD-WX21A30L8760', reports it is functioning at a temperature of 91.4F (33C) degrees.
4/13/11 6:02:48 AM [0x0-0x1e01e].com.alsoft.diskwarriorstarter DiskWarriorDaemon: [Wed Apr 13 06:02:48 EDT 2011] : Spare blocks for ATA device 'WDC WD5000BEVT-00A0RT0', serial number 'WD-WX21A30L8760', appear to still be available. (Total Available: 140) (Use Attempts: 0)

Easiest way to look is to filter Console > Console Messages for "warrior."

If that doesn't return any results try filtering Console > All Messages and see what you get. (The only thing I got were temp and block reports, and that was only when I ran Diagnostics > Manual.)

By the way... Setting it for "Hourly," if you haven't already, is a good idea.

OK, Hourly set and here's what I got (even if I don't understand and appreciate the data):

4/13/11 6:03:49 AM [0x0-0x199199].com.alsoft.diskwarrior[3233] DiskWarriorFileTestsServer: Resource header check: EOF(75202) is less than the sum of the map length(1330847832), data length(1298228000), and file header size(256)
4/13/11 6:03:49 AM [0x0-0x199199].com.alsoft.diskwarrior[3233] DiskWarriorFileTestsServer: Resource check returned error 9350 for file: TestFile.png
4/13/11 6:04:05 AM [0x0-0x199199].com.alsoft.diskwarrior[3233] DiskWarriorFileTestsServer: Resource check: Skipping AppleSingle-encoded data fork resource file: dialogs.rsrc
4/13/11 6:04:05 AM [0x0-0x199199].com.alsoft.diskwarrior[3233] DiskWarriorFileTestsServer: Resource check: Skipping AppleSingle-encoded data fork resource file: errors.rsrc
4/13/11 6:04:06 AM [0x0-0x199199].com.alsoft.diskwarrior[3233] DiskWarriorFileTestsServer: Resource check: Skipping AppleSingle-encoded data fork resource file: dialogs.rsrc
4/13/11 6:04:06 AM [0x0-0x199199].com.alsoft.diskwarrior[3233] DiskWarriorFileTestsServer: Resource check: Skipping AppleSingle-encoded data fork resource file: errors.rsrc
4/13/11 6:04:07 AM [0x0-0x199199].com.alsoft.diskwarrior[3233] DiskWarriorFileTestsServer: Resource check: Skipping AppleSingle-encoded data fork resource file: dialogs.rsrc
4/13/11 6:04:07 AM [0x0-0x199199].com.alsoft.diskwarrior[3233] DiskWarriorFileTestsServer: Resource check: Skipping AppleSingle-encoded data fork resource file: errors.rsrc

If the above is bad news, apparently the news is not so devastating as to elicit an Alert. At least none appeared.

That doesn't look like it has anything to do with the issue we're investigating; it looks like it relates to DW > Files > Check All Files & Folders, and, at any rate I've never seen it before.

Give diagnostics a few hours, and check back in both logs later.

I'm wondering how you're making out, Harv?

Artie,

It's a long and sad story (though hardly important), the sum of which necessitated me starting over.

BTW, do you leave DW running or do you quit it, e.g., will Automatic Diagnosis run in the background?

No need to leave DW running, Harv; Automatic Diagnostics runs in the background. You can check Activity Monitor for DiskWarrioirDaemon to confirm.

You should have an answer within a coupl'a hours of starting your experiment.

Artie,

I've has DW enabled now for 7+ hours, and so far, nada. A search of Alsoft was to no avail.

If this "feature" works, indeed I am missing the benefit.

Perhaps if it were a Growl alert…

I assume that covers both Console > All Messages and Console > Console Messages? If so, you second my experience.

I've got no idea if the functionality runs but doesn't report or just plain doesn't run, which is why I've reverted to DW 4.2, since 4.3 apparently doesn't include any critical changes.

Thanks for giving me an excuse to nudge Alsoft tech support (and mention V1's issue).

"I assume that covers both Console > All Messages and Console > Console Messages? If so, you second my experience."

Exactly!

What amazes me, is that I at least got something in my post of 4-13-11.

Perhaps an offering to the Alsoft gods-

What you posted in that post looks like the results of DW > Files > Check All Files & Folders, which, if so, has nothing to do with Hardware > Diagnostics.

If you run Manual Diagnostics you should see something in Console > All Messages, but that, of course, has nothing to do with Automatic Diagnostics.

Silly me... I just ran the "Files" test with these results:

4/16/11 6:47:12 PM [0x0-0x498498].com.alsoft.diskwarrior[2925] DiskWarriorFileTestsServer:
4/16/11 6:47:12 PM [0x0-0x498498].com.alsoft.diskwarrior[2925] Resource check: Skipping AppleSingle-encoded data fork resource file: errors.rsrc
4/16/11 6:47:13 PM [0x0-0x498498].com.alsoft.diskwarrior[2925] DiskWarriorFileTestsServer: Resource check: Skipping AppleSingle-encoded data fork resource file: dialogs.rsrc
4/16/11 6:47:13 PM [0x0-0x498498].com.alsoft.diskwarrior[2925] DiskWarriorFileTestsServer: Resource check: Skipping AppleSingle-encoded data fork resource file: errors.rsrc

So your initial Console entries had absolutely nothing to do with "Diagnostics."

FWIW, I just started an Automatic check with DW 4.3 (on an iMac G5 20" iSight running Mac OS X 10.5.8), quit DW, after which it does produce on-screen findings via pop-up dialogs, with Console items to match under All Messages.

As you noted, the 'DiskWarriorFileTestsServer' findings listed pertain to the Check All Files & Folders test.

> FWIW, I just started an Automatic check with DW 4.3 (on an iMac G5 20" iSight running Mac OS X 10.5.8), quit DW, after which it does produce on-screen findings via pop-up dialogs, with Console items to match under All Messages.

That's interesting, even though it doesn't shed a clue as to what's happening in my case.

Actually, I have no idea which option you're running, because unless there's a new one in DW 4.3 that I don't remember, the only option of which I'm aware that generates pop-ups is "Alert"/"An alert will be presented on the screen whenever a malfunction of any attached hard disk device is detected."

What do your pop-up dialogs say? Do they match the ones I've posted? (Even if they do, they're not something I'd want popping up on my screen every hour.)

And, at any rate, Alsoft tech support is working on my issue, and I don't know whether it would be a good idea to throw a new set of facts at them, particularly since yours relate to Leopard, not Snow Leopard.

I ran DiskWarrior's Hardware tab/ Automatic Diagnostics/ Hourly Auto check all drives... w/ Alert notification.

The Console entries referred to temperature and spare blocks. The (single) alert I received was about the HD running 'too hot'. This particular call is an interpretation of the manufacturer's SMART data based on the relevant temperature sensor's response, not an absolute 'fact'. This 'error' was also reported by TechTool Pro 4, but no longer by TTP 5 (or 6), due to Micromat's re-interpretation of the standard. As if to prove this, the HD in question has been running since January 2006 without problem.

OK... The alert confused me, because you didn't mention that it was an issue alert. (No S.M.A.R.T. entry in Console?)

Apologies, though, for forgetting to update my original post... At the outset I wasn't seeing any messages in either Console > All Messages or Console > Console Messages, but during the course of my playing around I discovered that DW 4.3 exhibits another change in behavior...

Alsoft has always advised running DW from /Apps/Utils, but it has always worked just fine for me running from a separate partition (which makes it readily available to whichever volume I'm running from at the moment).

DW 4.3 does not generate the messages we're discussing in All Messages, though, unless it is located in /Apps/Utils, and even when located there it does not generate the messages in Console Messages (as you've confirmed).

I'm now left wondering why Harv isn't seeing any messages, anywhere. Maybe he's running DW from a verboten location?

Verboten? Oy veh, no weigh, José.

I'm running DW from my Utilities. Well, I did launch it from the Sidebar, but AFAIK, that matters knot.

Confusion rains.

DW doesn't even need to be running (and, under any circumstances, launching it from your SideBar doesn't make a lick of difference).

You don't see hourly messages in Console > All Messages, huh?

If you launch /Apps/Utils/Activity Monitor and select "My Processes," do you see DiskWarriorDaemon running?

If neither, maybe check your settings in DW > Hardware > Automatic Diagnostics just to be sure.

I just lucked into what's probably happening on your Mac... I inadvertently left DW (4.2) running, and it did not generate hourly reports in either Console > Console or All Messages at the expected time, rather it did so only after I quit the app, so DW apparently may not be running if "Automatic Diagnostics" is to run; I guess they're not quite as automatic as they're made out to be.

Yep, that's probably it.

So now I'll start over again, again.

Curious... I guess I'll update my bug report with Alsoft again as long as they're working on the issue.

Still, nada. The only Alsoft hit I got was when I rebuilt the directory.

Almost makes the next 10 days with my MIL look like a vacation...

I dunno, Harv; there's no reason I can even guess at for your not seeing diagnostics messages in Console > All Messages if DW has been quit.

If you launch /Apps/Utils/Activity Monitor and select "My Processes," do you see DiskWarriorDaemon running?

Have you rechecked your settings in DW > Hardware > Automatic Diagnostics just to be sure?

Yes & yes.

Though you are wise to suspect Operator Error...

Sorry, should have included:

"If you launch /Apps/Utils/Activity Monitor and select "My Processes," do you see DiskWarriorDaemon running?

Have you rechecked your settings in DW > Hardware > Automatic Diagnostics just to be sure?"

The answer it both questions is "yes".

The operator error comment is just a musing...

You misunderstood my ... I understood your post and was displaying confusion over what's going on with DW on your Mac.

Try this: Launch DW > Hardware > Manual Diagnostics and hit "Test Device;" you should see something in Console > All Messages, at the least.

Artie,

I would love to get this resolved, but am in the midst of packing, etc. for a 10 day trip to see my MIL, AKA, She Who Will Be Obeyed. Ergo, I'll be out of pocket until 1 May.

On the plus side, my MIL is nearly 89 years old, and loves her iPad.

Enjoy your trip, Harv, and give you MIL a kiss for me.

DiskWarrior can wait.