How do you install this software and have it not take up the entire drive? Please tell me they didn’t design this software to lock down an entire drive for the OS! Been struggling to install things I plan to run on the server and I am getting nothing but permission issues even though I have made my account part of every root group available.
3 Likes
Arguing for a feature that isn’t going to happen? How is it not part of the natural installation process to be able to choose a partition instead of sacrificing an entire drive? Would everyone use Windows if it took the entirety of you install drive? Don’t worry, stepping away from this software and not looking back. I have no problem letting people know if you’re not Enterprise enough to use this software don’t bother looking into it.
Actually there is a pretty good rationale for this - which is that fixing an OS issue is as easy as installing again and restoring the system configuration file, and that allowing partitions would complicate this recovery process.
If you’d bothered to read the docs–or even the installer–you wouldn’t need to ask this question. It’s the way the software’s designed. It’s always been the way it’s designed. In all likelihood, it will always be the way it’s designed. If that doesn’t meet your requirements, there are plenty of alternative NAS OSs.
2 Likes
Just wondering what your plan if it did not take up the entire drive.
TrueNAS does not lock the drive and with minimal knowledge you are able to run it in a partition… just it’s not how it is supposed to be used, hence there is no built-in option to do so.
TrueNAS has never been for anyone.
This is NOT really anything that is tied to Enterprises as you are alleging. It is much more to do with the idea of TrueNAS Scale as an “appliance” rather than as a general purpose extensible operating system.
It is entirely up to you whether you want to:
-
Use TrueNAS Scale as supported i.e. with a dedicated boot drive.
-
Use TrueNAS Scale in an unsupported configuration where you partition the boot drive and use the remainder for something else - but you need to be comfortable with both being outside support if anything goes wrong dealing with the reinstallation of the operating system when it is on a drive with other stuff i.e. you may lose the other stuff during reinstallation, and you need to be comfortable with the technical difficulties of going “off-piste” on both the installation and the recovery of your boot pool in the event of a later problem. (And just so you know, my own O/S is on a small partition with another pool on the same disk - but I fully accept the risks and the consequences and I think (or hope) that I have the technical skills to deal with the consequences of needing an o/s reinstall.)
-
Use a different operating system.
But please let’s not criticise iX for a technical decision with a clear and supportable rationale - instead let’s be grateful to iX for producing such a great NAS environment and making it available to us for nothing, nada, zilch, sweet FA, zero cost.
1 Like
I’m just not sure which one meets the “requirement” here.
OMV is just like TrueNAS and takes a dedicated boot device.
1 Like
…and unRAID works the same way, and so does XigmaNAS. Maybe it isn’t such a ridiculous way of doing things after all.
Don’t have a whole lot of patience with someone who can’t even be bothered to read the installer screens, much less to RTFM, and joins here just to crap on the product.
1 Like
Because Windows isn’t an appliance firmware. It’s a consumer or server operating system; same as if you just installed bare bones Debian it won’t take the whole try.
Because this is bad practice
Enterprise NAS and SANs (such as Dell’s) firmware also take up dedicated drives by default/best practice, which is why they usually boot off a tiny drive - which is what most people probably do for TrueNAS as well.