nemesis1782
Contributor
- Joined
- Mar 2, 2021
- Messages
- 105
I've been working towards setting up my first Truenas (Scale) setup. I've run Synologies and fully custom setups without many issues.
After the initial setup and taking it into "production" I'm starting to doubt if relying on Truenas is a good idea...
I've run into multiple issues out of the box. Many of the "features" do not work on a clean system and need fiddling to get them running. Now I'm not agianst fiddling, however that is NOT the point of this system. It also shouldn't be the case for production ready software.
Up to this point I've run into:
- A lack of proper error logging, context and information in alerts messages
- Apps (Kubernetes) not working without removing and reading the Dataset multiple times
- UPS connection not working properly, yet to resolve this, let alone that the UI does not seem to provide any information about the UPS. From what I understand it's a permissions issue
- LAG - LACP is not working, still need to resolve this. I've setup tons of LAGs and never had ANY issues
-> I've resolved this. For some reason NIC 1 was listening for DHCP, NIC 3 got an IP address as this was the one that was connected.
Much of these are to be expected from a Beta or Alpha. However, I'm running a release version.
Some will probably argue it's free and I shouldn't complain, this however is not my intention. I need something stable, so I pose the question "Is it stable and reliable?".
As for the choice of SCALE over CORE. This is because the feature set fits my use cases better. I could get the same result with CORE, it would take a lot of fiddling. The more I fiddle the more chances of reliability issues.
With kind regards and hoping for some useful replies,
Davy Vaessen
Updates
After the initial setup and taking it into "production" I'm starting to doubt if relying on Truenas is a good idea...
I've run into multiple issues out of the box. Many of the "features" do not work on a clean system and need fiddling to get them running. Now I'm not agianst fiddling, however that is NOT the point of this system. It also shouldn't be the case for production ready software.
Up to this point I've run into:
- A lack of proper error logging, context and information in alerts messages
- Apps (Kubernetes) not working without removing and reading the Dataset multiple times
- UPS connection not working properly, yet to resolve this, let alone that the UI does not seem to provide any information about the UPS. From what I understand it's a permissions issue
- LAG - LACP is not working, still need to resolve this. I've setup tons of LAGs and never had ANY issues
-> I've resolved this. For some reason NIC 1 was listening for DHCP, NIC 3 got an IP address as this was the one that was connected.
Much of these are to be expected from a Beta or Alpha. However, I'm running a release version.
Some will probably argue it's free and I shouldn't complain, this however is not my intention. I need something stable, so I pose the question "Is it stable and reliable?".
As for the choice of SCALE over CORE. This is because the feature set fits my use cases better. I could get the same result with CORE, it would take a lot of fiddling. The more I fiddle the more chances of reliability issues.
With kind regards and hoping for some useful replies,
Davy Vaessen
Updates
Last edited: