I know just enough of basic commands, shell scripts and using PuTTY to get by and can follow when someone more knowledgeable lays down some instructions. This is my first foray into FreeNAS, hence me asking for instruction. ;)@jbernie51 : this subject presupposes a great deal of knowledge on your part, e.g., setting up datasets, setting up shell access for logging on to the FreeNAS server, mastery of basic UNIX commands, writing shell scripts, etc. It sounds like you may not be familiar with some of these items, so you may have to do some studying to get going. That said...
You will need to remove the directory you created from the command line (/mnt/tank/sysadmin) -- we always use the FreeNAS GUI to create datasets, as this is how FreeNAS is designed to be used. I created my system admin dataset using the FreeNAS GUI under 'Storage' on the main menu. This is where you create datasets to be used as shares and so forth. On my system, I named my pool 'tank' and my system admin dataset 'sysadmin', but you can use any names that strike your fancy. FreeNAS always mounts your pool in the 'mnt' directory on the boot drive, so this is where the path /mnt/tank/sysadmin came from in my earlier post. Again, your system may differ from mine, depending on your pool name and so forth.
Once your dataset is configured, you can log on the FreeNAS server with a shell session and create your script. Many folks use a Windows program called PuTTY for this purpose, but there are numerous ways of establishing a shell session with your FreeNAS server. You will want to execute the
smartctl -l scterc,70,70 /dev/???command on each of the drives for which you wish to specify a TLER/ERC value. To get a list of the drives on your system, you can run
smartctl --scan. Your drive list will almost certainly differ from mine, which is why I used the
I guess I was getting confused as I thought 'tank' was a folder created under the FreeNAS filesystem and not a dataset.
I was trying to avoid creating a dataset on my volume of four 8TB drives just because I like things neat and clean, and giving the volume the name 'Media' was my intention to store all Music/Photo/Video on there, and nothing else...
In my setup, I have a single SSD I've used to create a volume called 'Jails' which I've configured as the Jail Root. Would creating a second dataset here be better?
Although, now that I just finsihed typing above, I realized that this script would benefit from living in the Media volume as those are the drives I am trying to make sure are TLER enabled, and the script should be moved along with the drives, ex: moving to another or upgraded FreeNAS system..