Last week @Mik and I came across a member (@bakongi) from the ThreeFold Farmer’s TG group reporting probable bugs with V3 Explorer rendering incorrect HW specs.
In @bakongi ’s case; 2TB SSD recognized as 1TB and 64GB Ram recognized as 32GB.
Similarly, a second user (over support chat) had also reported MRU being detected as 33.56GB as opposed to 64GB.
For the benefit of the farmers; I created a ticket for the Dev Team to analyze and here’s a look into their observation. Thanks @leesmet for reviewing and sharing.
ZOS only detects capacity right after it boots:
Case 1 - There are 2 possibilities. First, the SSD might not be detected by the OS. If this is the case, ensure the connection is good. The second option is that the SSD got misinterpreted as an HDD. This could be the case if it is on the slower side. If this is the case then there would be 1 additional TB of HDD (in all probability if this is the case).
Case 2 – MRU is reported by the kernel. If this value is lower, it means the kernel is unable to access some of the memory. Ensure the memory is properly installed and maybe run a memtest to make sure there are no errors which might cause the kernel to not use the DIMM.
Regardless, capacity detection is only done at boot. This means that for this value to change, the node would have to reboot (considering low uptime on both nodes, that is what likely happened).
Note: in both cases, the explorer did periodically update accurate specs within a few minutes.