Skip to end of metadata
Go to start of metadata

SoftNAS® 5.1.3 Release Notes - September 9, 2021

Buurst SoftNAS 5.1.3 is a maintenance release containing the below improvements.

  • Enhanced security by updating config file permissions.

  • Disabled NFS ID mapping may impact ability to perform updates behind a firewall.

  • Deployments using S3 or Azure Blob storage may not successfully update without configuring end points.

  • Snapshot and Disk Activity may not reflect location time.

  • VNET location may not be found when deploying new HA configuration.

  • Downsizing of an AWS instance may result in boot failure.

  • Samba may crash resulting in SoftNAS drives unmounting frequently.

  • Nginx may not properly handle SSL certificates.

  • SoftNAS NFS Thread Counts low due to nfsd not starting on new deployments.

  • Identified “race condition” causing HA/SnapReplicate to fail manual takeover.

  • Monit action blocking HA giveback.

Known Issues 5.1.3

Yum update - it has been observed occasionally when running a "yum update" from the command line you may experience an error message when the kernel debug package is installed.  This is contributed to the fact SoftNAS uses a custom kernel package.  The error can be ignored and will be resolved in a future release.

winbindd log message - There are some situations where RPC functions return RPC faults and this is not a fatal condition.  In that situation a dcesrv_call_dispatch_local: DCE/RPC fault in call lsarpc:32 - DCERPC_NCA_S_OP_RNG_ERROR message will be observed in the /var/log/messages file.

SoftNAS® 5.1.2 Custom Update Release Notes - August 12, 2021

To apply this custom update, launch the StorageCenter UI and enter the SoftNAS version 5.1.2 custom update URL replacing the <SOFTNAS_IP> with your current instance IP address: https://<SOFTNAS_IP>/softnas/applets/update/?customupdate=

  • Snapshot and Disc Activity may not reflect location time.

  • VNET location may not be found when deploying new HA configuration.

  • Downsizing of an AWS instance may result in boot failure.

  • Samba may crash resulting in SoftNAS drives unmounting frequently.

  • Nginx may not properly handle SSL certificates.

  • SoftNAS NFS Thread Counts low due to nfsd not starting on new deployments.

  • Identified “race condition” causing HA/SnapReplicate to fail manual takeover.

  • Monit action blocking HA giveback.

  • SnapHA prematurely starts before remote node is ready.

  • Manually creating NFSv3 shares lack write privileges.

SoftNAS® 5.1.1 Release - July 8th, 2021

Buurst's SoftNAS 5.1.1 is a maintenance release containing the below improvements.

New in 5.1.1

  • Increased NFS thread count for improved performance.

  • Security updates and fixes, notably CVE-2021-3177.

Fixed in 5.1.1

SmartTiers Pools/Volumes/Snapclones not remounted issue - An issue occurring in some SmartTiers deployments, where pools, volumes, and associated snapclones were not mounting after a reboot has been resolved. 

HA installation failure issue - Resolved an issue where high availability (SNAP HA) would fail to install due to an assumption that the two VMs were in the same resource group. Logic added to ensure that subnet info is consulted prior to connection attempt. 

RHEL Root Corruption and Disk Unmountable issue - A known RHEL issue related to THP (transparent huge pages) default setting resulted in metadata expanding beyond memory capacity, resulting in data corruption. THP is now disabled at boot by default to prevent this issue re-occurring. 

Unable to create Azure Blob (object) Storage - An issue in which creation of blob storage on Azure would result in "unknown error" has been resolved. 

Invalid Help Link when connecting with SSH - Updated support link displayed when connecting by SSH to your SoftNAS instance/VM to ensure customers have easy access to support. 

Updated video links and content for in-app help - Updated or added video links to in-app help items, and added new help content to app features. 

Lift and Shift Azure Storage Type Selection issue - An issue in which the customer could not select disk type for Lift and Shift flows on Azure instances has been resolved. 

Failed takeover from UI - A race condition that could result from manual takeover/giveback operations that could result in takeover failure due to instance/VM roles switching places too quickly has been resolved. 

Failed error reporting issue - In some isolated cases, SnapReplication would not report failure if previous cycle completed successfully, and the next cycle was unable to start due to target node being down. This could result in replication showing as functional when it was not. This has now been resolved. 

Lift and Shift Home (Flexfiles) Repository available mappable target - An issue in which the home repository for Lift and Shift was listed as available as a target for mapping (Lift and Shift should not target the home directory) has been resolved.

Lift and Shift Failure to Create Repository - An issue in which attempts to create a Lift and Shift repository has been resolved. (19181)

SSL Certificate Issue between VMware and AWS Lift and Shift operations - Necessary communication between VMware and AWS instances for Lift and Shift operations were being blocked by certificate configurations. This has now been resolved. 

SnapReplicate Throttling issue - An issue where throttling command was not installed by default, resulting in potential poor performance, has now been resolved.  (19171)

Nginx comment line issue - An issue where a SED REGEXP would constantly add # to the nginx registry file whether commented already or not, potentially resulting in large files sizes over time, has now been resolved. 

Nginx SSL certification corruption issue - An issue in which failover for HA would not work due to Nginx SSL Cert corruption has now been resolved. 

Custom NFS IDmapping configuration issue - An issue with a custom script in a client environment has been connected to an unsupported NFS setting. NFS IDmapping has been disabled in SoftNAS 5.1.1 for security reasons. Enabling NFS IDmapping is not a recommended configuration. 

SoftNAS® 5.1.0 Release - April 21st, 2021

Buurst's SoftNAS 5.1 is a maintenance release containing the below improvements.

New in 5.1

  • Added needed support for RHEL 8.2 and supporting installer.

    • SoftNAS RHEL 8.2 BYOL Only

    • Installed onto an existing fresh install of RHEL 8.2

    • Installed via an installer script which will be downloaded from our website.  

The installer and documentation can be found at: RHEL SoftNAS Installation Steps

  • Ability to enable FIPS

  • Added AWS SSM agent

Fixed in 5.1

Failover Issue when using custom SSL certifications - An issue in which custom SSL certifications would be over-written during a failover operation, resulting in loss of high availability, has been resolved. The custom SSL certifications will no longer be over-written. 

Error when modifying NFS shares from UI - An issue in which attempts to modify an NFS share from the Create an NFS Share section of the UI would result in failure and an error message have been resolved.

Security Fixes - The following fixes have been made to secure SoftNAS 5.1.0:

  • removed vulnerability to CVE-2021-3156 (sudo related) 

  • removed kernel vulnerabilities to CESA-2020:4286, CESA-2020:4431 and CESA-2020:4685 

  • Netatalk completely removed from the system

Yum Update Issue - An issue preventing yum updates from completing has been resolved.

Known Issues 5.1

Benign Log Error - Log errors of a specific type seen occasionally on install has proven to be benign. The error reads  "Job for <service name> failed because the control process exited with error code"

Service names that have been seen for this error include:

  • webmin.service

  • php-fpm.service

  • sernet-samba-smbd.service

  • sernet-samba-winbindd.service 

These log errors will be addressed in a future release. 

SoftNAS® 5.02 Release - Feb 25th, 2021

Buurst's SoftNAS 5.02 is a maintenance release containing the below improvements.

  • Security Fixes - Recommended fixes have been applied to secure SoftNAS from recent Linux vulnerabilities, including CVE 2021-3156 and CVE 2020-9850.

  • Yum Update Fix - Fixed an issue where yum update would fail in most recent version of SoftNAS, resulting in error messages related to selinux

  • Azure Custom Data fix - Fixed an issue preventing the ability to use custom data on VM launch.

  • Deprecated Function Fix - An issue in which deprecated features (FlexFiles and UltraFast UI) were listed as available. These features are now in our separate product, Fuusion

  • DeltaSync Failed State issue - Resolved an issue where DeltaSync would fail to sync any new volumes added to an instance while HA was deactivated. 

  • Notification Email issue - If the email notification was not configured it was logged as an ERROR, but is now configured to log as INFO, to prevent users from interpreting this as an actual ERROR in the SoftNAS logs.  

  • Force Sync fix - Force sync now requires a volume selection to be made. This prevents the user from accidentally issuing a Force Sync on all volumes.

Buurst SoftNAS® 5.0.1 Release - Jan 13th, 2021

Buurst's SoftNAS 5.0.1 is a feature release containing new features, improvements and bug fixes.

New in 5.0.1

Build Packaging Fix - Fixed the build packaging for platform publishing.

Buurst SoftNAS® 5.0 Release - January 8th, 2021

Buurst's SoftNAS 5.0 is a feature release containing new features and improvements.

New in 5.0

License enforcement - As of 5.0, license enforcement will be applied to only allow SoftNAS servers to operate that are within the license entitlement performance level.

Linux version change - SoftNAS is now based on a CentOS 8.2 linux deployment.

Kernel update - SoftNAS' kernel has been updated to version 4.18.0-193.19.1.el8_2.x86_64

Samba update - Samba has been updated to version 4.12-10-15

AWS EIP Support - SoftNAS no longer supports the use of Elastic IP addresses on versions 5.0 and later

Apple File Protocol (AFP) Support - AFP is no longer supported as of versions 5.0 and later

Upgrade process improvements - SoftNAS no longer checks and interrupts the upgrade process if the version of paired instances with SnapReplicate is different. The upgrade process will proceed without issue. 

Firewall default settings change -To improve the baseline security of SoftNAS, firewallD default settings have been changed. All ports not required for use of SoftNAS will now be closed. If any services connect with SoftNAS through extraneous ports in your existing deployment, you will need to open these ports in SoftNAS's firewall.

Azure OMS Agent Support - Azure ASM and OMS Azure Extensions are now supported.

Improved performance - Performance improvements of up to 60% have been benchmarked for certain workflows with SoftNAS 5.0

SSH User change - With the update to the latest CentOS build, the centos user is now used for SSH connections to the virtual machine, rather than the ec2-user.

Fixed in 5.0

Snapshots are now time zone aware - Snapshots have now been changed to use UTC when naming snapshots and will display according to the local time zone regardless of the location and time zone of the snapshot datastore. 

Common User Configurable NTP settings - Fixed an issue in which some SoftNAS Services prioritized a hard-coded time server over user configured time server settings. 

Enable custom data for Azure - In order to allow automation of deployments and allow images to self-configure and bootstrap with predetermined values, SoftNAS now supports custom data.

Azure L2ARC Boot Hang issue - Fixed an issue where Azure instances without ephemeral drives could hang for up to 15 minutes during boot. This would typically manifest itself with the inability to login to to the instance via the UI or SSH. 

CLI License Activation Issue - An issue in which license activation via the CLI would not function has been resolved. 

Unable to edit snapshot schedule via CLI - An issue in which edits to snapshot schedule using the CLI would not be recognized as valid, resulting in a null value, has been resolved. 

Max Threads Cleared issue - An issue in which :SoftNAS.ini" script would not retain the max threads count, necessary for Lift and Shift setup, has been resolved.  

Azure Storage Expansion issue -  An issue in which  storage expansion operations on  Azure virtual machines with attached read/write logs (L2ARC or ZIL) would fail has been resolved.

Inconsistent HA State issue - Fixed an issue where the displayed HA state between two SoftNAS nodes could be inconsistent.  

SmartTiers Resize issue - Fixed an issue where the UI could hang if resizing a SmartTiers tier. Occasionally this issue could result in an invalid license alert.  

Lift and Shift Fixes

Lift and Shift EFS Source selection issue - An issue in which the EFS source could not be selected from the UI in order to be mounted (but could be mounted from the CLI) has been resolved.  

Miscellaneous Fixes

Update related bucket error - An issue in which after an update would occasionally result in an InvalidBucketName error when using CEPH based storage has been resolved.  If using CEPH based object buckets please contact support prior to the upgrade for assistance.

Known Issues 5.0

Notification Email issue - If the email notification is not configured it is logged as an ERROR, but should display as an INFO status in logs. This will be resolved in an upcoming release. 

NiFi Monit Alerts without NiFi enabled - NiFi monit alerts may appear in your logs even if NiFi has not been enabled on your SoftNAS VM. 
Recommended Action: Disable NiFi Monit Alerts in the Service Monitoring section under Settings>Administrator>Monitor Settings.

BYOL License Email not sent - Email alerts for SoftNAS BYOL performance level violations are not sent for Azure VMs. BYOL performance level violations are detected and displayed in the UI.
Recommended Action: The running VM needs to be down-sized to be compliant with the installed license or a license appropriate for the VM in use needs to be applied.

SnapReplicate/SNAP HA un-synched volume issue - A volume or volumes added while an HA pairing is deactivated will not replicate to the secondary node upon reactivation of HA. 
Recommended Action:  Run Force Sync for the unsynchronized volumes before re-enabling SnapReplicate/SNAP HA. Ensure the volumes are selected prior to issuing the Force Sync. If no volumes are selected a Force Sync will resync all volumes. 

CIFS/SMB import issue - When importing an S3 device with CIFS/SMB enabled to a new instance, the existing CIFS/SMB volume(s) are not automatically imported to the new instance.
Recommended Action: Open the Pools section of the Storage Administrator panel, and perform an import of the pool. 

yum update issue - yum updates on version 5.01 are erroring out with no action taken. This will be resolved in an upcoming release.

  • No labels