The new point update version of Freenas has now been released to update Freenas 188.8.131.52 to 184.108.40.206.
As usual with Freenas, the whole process only takes about 5 minutes to complete.
Note: The system automatically reboots itself after the update is applied, so make sure that the system can be restarted (i.e. there are no active users on it) before you start this process.
The release notes detail the fixes, which from a high level perspective are:
- Samba (SMB/CIFS support) upgraded to version 4.1.6
- Netatalk (AFP support) upgraded to version 3.1.1
- ZFS replication status is now provided in ZFS Replication UI
- the bug preventing FTP from starting when logging to system dataset has been fixed.
Downloading the update
Go to the download page and select the upgrade option (it’s second in the list). You’ll also need to copy the SHA256 code (circled)
The first time I went here I missed the SHA256 code printed under the download button, so I had to go back and copy it. Here is
Before the update
Log into you Freenas box and save the configuration. Go to the Settings tab, and at the bottom of the tab, press the Save Config Button
Upload the firmware
Click on the Advanced button on the settings tab. You will need to scroll through the tab to get to the bottom. The last button is labelled Firmware Update. Press this to start the updaet.
Select the location and press OK.
The update will be applied and then the system will automatically restart.
If you are have a headless (no monitor attached) system, then opening a command prompt and typing ping wil let you see when the system come back up.
tim@thing:/tmp> ping freenas PING freenas (192.168.10.111) 56(84) bytes of data. 64 bytes from 192.168.10.111: icmp_seq=1 ttl=64 time=0.087 ms From thing.ccc (192.168.10.105) icmp_seq=52 Destination Host Unreachable From thing.ccc (192.168.10.105) icmp_seq=53 Destination Host Unreachable From thing.ccc (192.168.10.105) icmp_seq=54 Destination Host Unreachable From thing.ccc (192.168.10.105) icmp_seq=55 Destination Host Unreachable . . and then several screens later . 64 bytes from 192.168.10.111: icmp_seq=1 ttl=64 time=0.086 ms 64 bytes from 192.168.10.111: icmp_seq=1 ttl=64 time=0.087 ms
(On windows, I think you need to use ping -t to make a continuous ping.)
If all went well, your browser will show you the login screen again.