Raid alert stopped working slobs5/20/2023 ![]() The quickest way (though per usual not the most elegant) to get RAID notifications is to create a batch file (e.g. Which will yield the same results as above, without the need of an “instruction” file. ![]() This makes sense, since diskpart can automate partitioning, which can certainly result in a dozen or so commands.įor our purposes however it’s overkill, so we can trick diskpart by running a single command: Technically, scripting diskpart is a bit cumbersome, as the creators of the tool want you to specify any commands to pass to diskpart in a text file, and in turn specify that text file with the /s parameter. Volume 1 C NTFS Mirror 141 GB Failed Rd Boot However, when a disk fails, the status is updated and reads “Failed Rd” instead: Notice the “Status” column, which indicates that our “BOOT” volume is feeling dandy right now. Volume 2 D System Rese NTFS Simple 100 MB Healthy Volume 1 C NTFS Mirror 141 GB Healthy Boot Volume 0 System Rese NTFS Simple 100 MB Healthy System Volume # Ltr Label Fs Type Size Status Info If you just run diskpart and execute the “list volume” command, you will see output similar to this: An event log filter looks for a 10200 error event, possibly looking at the event message as well (for custom routing).ĭiskpart’s output is pretty straightforward.When a problem is detected, EventSentry logs an error event 10200 to the application event log, including output from step 1.EventSentry runs our VBScript (which in turn runs diskpart) and captures the output.So how can we turn diskpart’s output into an email (or other) alert? Simple: We use EventSentry‘s application scheduler to run diskpart.exe on a regular basis (and since the tool doesn’t stress the system it can be run as often as every minute) and generate an alert. Since we’re interested as to whether a particular RAID-enabled logical drive is “Healthy”, we’ll be looking at logical drives. ![]() ![]() With a few small steps we’ll be able to log an event to the event log when a drive in a software RAID fails, and send an alert via email or other notification methods.ĭiskpart is pretty much the command-line interface to the Disk Management MMC snap-in, which allows you to everything the MMC snap-in does – and much more! One of the things you can do with the tool is to review the status of all (logical) drives. What gives?Įven though a discussion on why that is (or is not) seems justified, I will focus on the solution instead.įortunately, there is a way to be notified when a RAID is “broken”, thanks in part to the diskpart.exe tool (which is part of Windows) and EventSentry. What’s peculiar is that this is a step back from Windows 2003, where RAID problems were actually logged to the System event log with the dmboot and dmio event sources. tray), and even WMI is silent as a grave. The event logs are quiet, there are no notifications (e.g. If the RAID is in a degraded state (usually because a hard disk is dead) then you will not know unless you navigate to the Disk Management view. Unfortunately, despite all the positive things about software RAID, there is a major pitfall on Windows 2008: The OS will not tell you when the RAID has failed.
0 Comments
Leave a Reply. |