Considering the above, reproducing the issue should be dead easy: 1. Install latest version of TrueNAS. 2. Go to the reporting tab
Just a few example points why it may not be that easy:
- Installation
- Locale setting (not sure TrueNAS offers this, but it is meant as an example and often the reason why things fail on some systems only)
- Boot device file system details
- Pool setup details
- Going to reporting
- Browser version, plugins, non-default settings
- Workstation OS incl. non-default fonts installed
- Language settings of workstation
The tricky thing, and that is what I am trying to convey with those examples, is to identify the difference between your system and others. There are situations when this is relatively obvious, and those cases are easy to fix then. Overall, it is a bit like going to a doctor with an "obscure" disease. The diagnosis is often more difficult than devising a therapy.
Coming back to software: Just like in the health context, sometimes the symptom and the root cause can only be connected via a chain of multiple intermediate causes. I once had a case where two systems from the same vendor were designed to work on the same business situation (think of something like processing an order as an example). Those were client-server applications with fat clients running on Windows. The two clients never talked to each directly but would set a flag on their own server to indicate that the order could be picked up by the other server for the next step.
This had been tested not by thousands of installations, but it was certainly more than 100. However, on our setup the hand-off never worked, duplicates were created, which then caused consistency errors down the road. It took a whole week and more than 200 person hours to isolate the culprit: One of the clients (not a server) had a non-US locale setting for its Java Virtual Machine (automatically done by the Java installer, based on the OS settings), which somehow affected a string comparison. So two strings that were used as global identifiers (aka UUIDs) were considered to be different, although they were actually identical (and no, they did not contain non-ASCII characters). As a consequence records could not be matched and things went south from there ...
I have a huge amount of respect for people like
@ChrisRJ who can work in the modern web environment. And I know it is equally hard to work on the backend of that, transforming the stuff that hardware emits into a more comprehensible and usable format for the end user.
Thanks,
@jgreco , but my web knowledge is actually rather limited. In fact I am primarily working on the back-end side and specifically distributed systems. Those, because of the by definition unreliable nature of connections, have some fascinating challenges.
In closing: Why am I writing all this? I am a developer by heart and almost all developers I know take a lot of pride in doing a good job, whatever their practical experience and formal seniority level. So "we" are generally upset and frustrated if someone like you,
@hjarnek, run into issues like you described. But unfortunately, those issues are typically very hard to diagnose, especially when communication happens only via an issue tracker and not something like a video call with screen sharing.
My personal recommendation would be to do a fresh install and write down literally every click and key stroke you make. With luck, the problem goes away, because sub-consciously you do something just a tiny little bit differently. If the issue persists, you have a very comprehensive log that can be used to reproduce things, or at least exclude a lot of factors.
Hope that helps!