DX4000 Dashboard Health monitor

WD Legacy Products Sentinel Products
1

Hi WD Community,

We use the DX4000 for most of our customers, one of them is giving me a hardtime.

When i open up the dashboard, and i choose monitor.

Gathering information is shown, after a short while gathering completes: “Information not available”

No data is displayed in the upper right corner.

Eventvwr.exe is working

The problem is the NAS can’t detect if there is a defect HDD, or other health incidents. Also the mail notification is not working, the mail enable button is greyed out.

See the screenshot below:

Capture.PNG
Capture.PNG1436×871 101 KB

Does anyone know, what service is responsible for getting the information, or have other ideas about this incident.

Kind regards,

Lars van Egmond

2

First check the system date on the DX and make sure it is not 2 or 3 months in the past

then look through this thread

http://community.wd.com/t5/WD-Sentinel-Products/DX4000-Computer-Monitoring-Error/td-p/794605/page/2

1 Like
3

Hey Gramps,

Thank you so much for your reply.

I tried the steps in the linked topic, changing the model to WDBLGT and restarting the “WD Enclosure provider” and reopening dashboard. no luck for me unfortunatly.

What i do notice are these events after restarting the WD Enclosure Provider

Service started successfully.

CreateNewAlertManager: Creating Alert Manager.

CreateNewAlertManager: Connecting Alert Manager.

Detected model number WDBLGT

Result from command ‘cscript.exe //NoLogo “C:\Program Files\Western Digital\WD Enclosure Provider\SyncTime.vbs”’ : 'Sending resync command to local computer
The command completed successfully.
Resync succeeded
’

In SetUEFIDate setting to 10-6-2015 17:53:20

Result from command ‘mountvol x: /s’ : ‘’

Result from command ‘mountvol x: /d’ : ‘’

Changed date in uefidate.nsh to : 6/10/2015

ClearPowerAlert: Alert Manager is not connected.

ClearPowerAlert: Alert Manager is not connected.

If you prefer i can make an export of the eventlog.

Thanks in advance,

Lars

4

Not sure the logs would mean anything to me.  I just learn from what I have broken.  If I can’t duplcate yours…

So you did not have the model in the registry, but putting it there was no help?

Your system date is correct?  I just checked mine and it was a month off again

In Services.msc there are sever WD services, they all started?

5

You have to stop the service, make the regedit, then start the service.

But that just fixes like half of the monitoring stuff.  Your screenshoot shows all of them broken

6

First of all i checked the date and time, those were correct and synced.

When i looked at the register value it had the full model name: WDBLGT0160KBK-42, i stopped the service, edited the value to WDBLGT and started the service. After this is I started the dashboard, no result.

Restarting the DX4000 clears the changes, same as you have been experiencing in the previous post.

All the WD services are started.

Lars

7

I get this when I resart, then the rest is like yours

Service started successfully.

CreateNewAlertManager: Creating Alert Manager.

CreateNewAlertManager: Connecting Alert Manager.

Detected model number WDBLGT

AlertMgrConnectionOpened: Alert Manager is now connected.

ClearPowerAlerts: Clearing all existing Power alerts.

Result from command ‘cscript.exe //NoLogo “C:\Program Files\Western Digital\WD Enclosure Provider\SyncTime.vbs”’ : 'Sending resync command to local computer

The command completed successfully.

Resync succeeded

In SetUEFIDate setting to 6/10/2015 3:03:28 PM

8

I have created a case at WD, otherwise it takes too much time to fix.

Thank you for your time and knowledge !

9

Let us know if they come up with anything short of reinstall.

Thanks,

Grey

10

I think the only answer you will get is to reinstall everything. I had this problem once (for the hard drive recognition only) and the solution was to reinstall from scratch. Pity this takes days :frowning:

11

I see reïnstalling as a workaround, not a fix. =)

We have 12 DX4000’s, around 5 of them have this issue.

Two weeks ago i send all of the requested logs, still waiting for an answer…

12

I agree 100% with you, the problem is that for most of the problems I had (similar to yours) the only final fix I was suggested (which of course in general worked but it required days of work without the NAS available and many hours spent as IT manager to follow the various steps) was to perform a clean re-install.

This happened for instance when the DX4000 did not automatically upgrade from RAID1 to RAID5 after having installed two additional disks even if this is one the key features reported in the DX4000 specifications.