lwolfHello to all,
We just activated Event Log Monitoring for an event set that includes watching for events in the System Log, Event=7, Source=Disk, description=*has a bad block*
This was applied to about 500 Agents yesterday, and plan to apply to another 500 or so next week.
We received 50+ alerts/emails over the past 24 hours. Looking into each one, we found that a few were for hard disk drives (which I certainly care about), but the vast majority were for CD drives (which I do not care about).
I am looking for a little advice from others who have been monitoring for this event. How do you handle these? It seems we will be spending a lot of time chasing alerts for the CD drives.
I can not figure out a way (or an easy way) to watch for this event for hard disk drives, but not for CD drives - as some machines have a hard drive for D, while others have a CD-drive for D.
Any advice is appreciated. Thanks in advance.
Here is an example of the Alert
System log generated Error Event 7 on ws11.companyname For more information see http://www.eventid.net/display.asp?eventid=7&source=Disk
Agent Time: 9:19:44 am 10-Sep-08
Event Time: 1:19:44 pm 10-Sep-08 UTC
Description: The device, \Device\Harddisk0\D, has a bad block.
Hello. Thanks so much for replying.
Call me stupid, but I am confused. I suppose i need to Google DMDIAG to get some more info.
Do you run DMDIAG one time, in advance, and that changes the Source of the Event Log errors? Of do you run DMDIAG via script after a Bad Block event occurs to try to get mroe info about where it came from? or something else?
Any additional information you could provide would be greatly appreciated. Thanks!