Since we released Home Server SMART Classic last fall, I've gotten a fair amount of feedback that the add-in is not reporting data for the HP EX470 and EX475 servers. All internal disks are showing blue question marks and no SMART data, even though they showed data in the older version (which was last updated in 2011).

If you are running an HP EX470/475 server and are still running WHS v1, I have an updated version that I hope fixes the problem. Or, if it doesn't fix it, I've added some debug code that will allow me to collect additional debugging details. Your feedback is respectfully requested to put this bug to rest! I have an EX487 and EX490, but not an EX47x so your input is important.

If you are running HSS Classic and it's reporting correctly, there is no need to install this build. If you have an EX47x and it's not working right, please install this one. Likewise for anyone running HSS Classic on another server and the results are incorrect.

You can grab the build (v3.2.2.17) here -- https://www.dojonorthsoftware.net/dl/be ... 7_BETA.msi

Installation Instructions

1. Please UNINSTALL any version of Home Server SMART installed on your EX47x server. It'll either be called Home Server SMART (old version) or Home Server SMART Classic (new version from fall 2013).
2. After uninstalling, please REBOOT your server. This ensures the old C++ DLL is unloaded from memory. This is especially important if you were running the older Home Server SMART software.
3. After rebooting, please install the v3.2.2.17 version of Home Server SMART Classic.

Reporting Results

Once you've got v3.2.2.17 of HSS Classic installed, please do the following, regardless of whether the add-in is now reporting correctly. Also, please disregard update notices saying 3.1.10.9 is a newer version.

1. Go into HSS Classic Settings.
2. On the Advanced tab, check the option "Enable SmartInspect logging" and then click the Apply button.
3. Click the Service Control tab and click Restart Service (you can also reboot your server).
4. After the service restart (or full reboot), log out of and back into the Console.
5. In the main HSS Classic UI, click Avanced Items > Report a Bug/Diagnostics.
6. HSS will collect some data, including the debug logs.
7. In the report window, you will be given the opportunity to describe the problem. Please indicate whether or not the build worked for you (it's now reporting correctly or not) and optionally your username on this site (so I can reach out to you directly, if necessary). Then click the Zip and Send button, which generates an encrypted zip file and delivers it direct to our servers.
8. You may then follow steps 1-3 above, except you'll uncheck the checkbox to disable the debug logging. You may leave it checked if you want to perform additional debug help in the future.
9. Please report your findings back here so the community can benefit!

_________________
Matt Sawyer
Owner, Dojo North Software, LLC

HP EX490, 4GB, E5300, 15TB - Server 2012 - Sharing and Streaming
HP EX487, 4GB, E5300, 13TB - Server 2012 Essentials - Backups

Hi Matt,

First thanks for looking into this issues!

While I am not certain the issue may have more to do with AMD Based systems. I have a custom built server which is AMD. Also the HHS2013 when I tested it on an EX470 running WHS2011 I experienced the same results.

I will install this ADD-IN on two EX470's and my custom built WHSv1 server and let you know what I see.

_________________
Exploring the possibilities!

Migrated from WHS2011 to WS2012E: HIGHLANDER

~ Norco 4220 Enclosure
~ Gigabyte GA-990FXA-UD5
~ AMD Phenom II X4 995 3.2 GHz
~ 8 GB Corsair Vengeance DDR3 1600 (PC3 12800)
~ 3 Supermicro AOC-SASLP-MV8

I'm not quite sure this is a problem that's specific to AMD as it is to the disk controller. The way Home Server SMART (HSS) and WindowSMART gathers data is through C++ code. It makes various calls to the controller for the data, and if the IOCTL call to Windows returns a success code (S_OK or 0x0), then the call is assumed to be successful. If an error code is returned, then a different method is tried.

HSS and WindowSMART make their calls in the following order for SATA/eSATA/IDE disks: Silicon Image SiI, CSMI, SAT and finally WMI. If a success code is returned, then the subsequent methods are not attempted. If the controller is not an SiI controller, the SiI method is skipped, and then the order is CSMI, SAT and finally WMI. For USB disks, only the SAT method is used, although there are several sub-methods, depending on the USB controller bridge chip (i.e. SunPlus vs. JMicron).

I have seen instances of CSMI calls returning a success code (0x0) but the 512-byte array which holds the SMART data structure is all zeros. The bug is that the code only checks success vs. failure; if successful the array returned is stored and no subsequent IOCTL calls are made on the disk. If the data is all zeros when assessed later, the disk status is set to unknown.

The SMART specification says a disk may possess 0-30 attributes, and so our SMART software is designed to iterate up to 30 attributes. On each iteration, the attribute ID number is checked. If the ID is 0 (invalid SMART ID), then we've reached the end of the attributes and are done processing for that disk. If the first attribute turns out to be zero, the data is presumed to be invalid and the disk is set to unknown (hence the blue question mark).

The fix presented in this beta goes back to each of the calls--CSMI, SiI, SAT, etc. and does an immediate check of the first attribute. If the IOCTL call returns success but the first attribute is zero, the data is assumed invalid and the method returns false (fail), forcing the next method to be attempted.

Home Server SMART always worked on the EX47x servers, but complaints started flowing in once the HSS Classic release came out in the fall. This was the first HSS Classic release that included the CSMI methods, so my guess is that the CSMI calls are "succeeding" but returning all zeros--hence the unknown disks. By discarding invalid queries, the problem should (hopefully) be fixed.

_________________
Matt Sawyer
Owner, Dojo North Software, LLC

HP EX490, 4GB, E5300, 15TB - Server 2012 - Sharing and Streaming
HP EX487, 4GB, E5300, 13TB - Server 2012 Essentials - Backups

I have just sent over the 3rd bug report for my Custom WHSv1 server and yesterday I sent over two reports for two EX470's they all do not report the SMART Info for the drives. Also the HSS2013 did the same thing on an EX470 running WHS2011 but I have no way to test that at this time unless I reinstall WHS2011 on one of the units.

Let me know if you want me to try WHS2011 on an EX470 and HSS2013 but I will not be able to get to it until the weekend.

_________________
Exploring the possibilities!

Migrated from WHS2011 to WS2012E: HIGHLANDER

~ Norco 4220 Enclosure
~ Gigabyte GA-990FXA-UD5
~ AMD Phenom II X4 995 3.2 GHz
~ 8 GB Corsair Vengeance DDR3 1600 (PC3 12800)
~ 3 Supermicro AOC-SASLP-MV8

Can you please perform the service restart? This can be done after enabling the debug logging. Check the box to enable logging, then click Apply to commit the setting. Then go to the Service Control tab and click Restart Service.

The reason I ask is because the logs you sent over contain only the text report and a lone UI log file. If you don't perform the service restart, the service--which does the background "dirty work"--doesn't start logging. That's where I'd be able to see what's going on behind the scenes.

You can also reboot the server after enabling the logging, but the service restart is faster.

_________________
Matt Sawyer
Owner, Dojo North Software, LLC

HP EX490, 4GB, E5300, 15TB - Server 2012 - Sharing and Streaming
HP EX487, 4GB, E5300, 13TB - Server 2012 Essentials - Backups

I actually followed your instructions line by line but I will do it again to the two servers I have here and will do the other when I am at work.

_________________
Exploring the possibilities!

Migrated from WHS2011 to WS2012E: HIGHLANDER

~ Norco 4220 Enclosure
~ Gigabyte GA-990FXA-UD5
~ AMD Phenom II X4 995 3.2 GHz
~ 8 GB Corsair Vengeance DDR3 1600 (PC3 12800)
~ 3 Supermicro AOC-SASLP-MV8

Please give me a few minutes...looking into this now. I just noticed I'm not getting service logs on my EX490 but I am getting UI logs.

_________________
Matt Sawyer
Owner, Dojo North Software, LLC

HP EX490, 4GB, E5300, 15TB - Server 2012 - Sharing and Streaming
HP EX487, 4GB, E5300, 13TB - Server 2012 Essentials - Backups

My apologies, it looks like there was a bug in that version and the log wasn't getting created. I found the problem and fixed it.

Please use this version here: https://www.dojonorthsoftware.net/dl/be ... 4_BETA.msi which contains the fix for the logging.

_________________
Matt Sawyer
Owner, Dojo North Software, LLC

HP EX490, 4GB, E5300, 15TB - Server 2012 - Sharing and Streaming
HP EX487, 4GB, E5300, 13TB - Server 2012 Essentials - Backups

ok I got the 3.2.2.24 installed on 2 servers and have sent the reports. Will follow with the 3rd soon and hopefully you will find what your looking for.

_________________
Exploring the possibilities!

Migrated from WHS2011 to WS2012E: HIGHLANDER

~ Norco 4220 Enclosure
~ Gigabyte GA-990FXA-UD5
~ AMD Phenom II X4 995 3.2 GHz
~ 8 GB Corsair Vengeance DDR3 1600 (PC3 12800)
~ 3 Supermicro AOC-SASLP-MV8

To Download the version which works with the EX47x click on the following link: viewtopic.php?f=2&t=13737

_________________
Exploring the possibilities!

Migrated from WHS2011 to WS2012E: HIGHLANDER

~ Norco 4220 Enclosure
~ Gigabyte GA-990FXA-UD5
~ AMD Phenom II X4 995 3.2 GHz
~ 8 GB Corsair Vengeance DDR3 1600 (PC3 12800)
~ 3 Supermicro AOC-SASLP-MV8

work with WD20EZRX (EX470)

Thanks

cheers

_________________
EX470 + AMD X2 +2*2TB WG Green WD20EZRX 2GB RAM + silent Fan MB40201VX-A99 in PSU + APC BACK 350 CS + Grid Junction 1.6