Convince me to stay with ReadyNAS

jelockwood wrote:
Thanks for everyones replies so far. I hear the comments about the need for SATA III for spinning metal hard disks and yet all such hard disks since about 2TB have been SATA III as standard.

SATA III is backwards compatible with SATA II. I think they probably used SATA III so they could market the drives as having it.

jelockwood wrote:
The community app for LDAP for OS 6 is an LDAP server, as far as I can see it will not enable a ReadyNAS to authenticate clients against an existing LDAP server e.g. a Linux box running OpenLDAP or a Mac box running Open Directory. There have been many previous requests posted in these forums over many years (including my own) for the ReadyNAS to be able to authenticate to existing LDAP servers.

I will pass on this feedback re LDAP.

jelockwood wrote:
The QNAP can be upgraded to 32GB of RAM and has a quad-core Intel Xeon processor. With the fact that the similar ReadyNAS 4220 supports network expansion cards and has a decent processor it would have seemed suited to running multiple VMs with independent NICs except for the lack of RAM and lack of standard software support. See http://www.qnap.com/i/station/en/virtualization.php

You could install VirtualBox, but the recommended solution would be to use the NAS as a datastore and run e.g. VMWare ESXi (or an alternative) on an ordinary server.

The 4220 comes with 8GB ECC RAM.

jelockwood wrote:

Thanks for the news about 4.2.27 and its newer SAMBA. While it is of the right version it is not clear if SMB2 is enabled in it. Has anyone tested this? A Mac client running Mavericks can show you what version of SMB it is connected via by using the "smbutil statshares -a" command. Mavericks supports up to SMB 2.1 and Yosemite will also support SMB 3.0 I have used this command previously to confirm 4.2.26 is SMB1 only. :(

Just installed 4.2.27-T4.

MDGM-NAS is running 4.2.27-T4 and MDGM-NAS2 is running 6.1.9

# smbutil statshares -a

==================================================================================================
SHARE                         ATTRIBUTE TYPE                VALUE
==================================================================================================
c                             
                              SERVER_NAME                   MDGM-NAS (CIFS)._smb._tcp.local
                              USER_ID                       501
                              SMB_NEGOTIATE                 AUTO_NEGOTIATE
                              SMB_VERSION                   SMB_1
                              SMB_SHARE_TYPE                UNKNOWN
                              EXTENDED_SECURITY_SUPPORTED   TRUE
                              UNIX_SUPPORT                  TRUE
                              LARGE_FILE_SUPPORTED          TRUE

--------------------------------------------------------------------------------------------------
data                          
                              SERVER_NAME                   mdgm-nas2
                              USER_ID                       501
                              SMB_NEGOTIATE                 AUTO_NEGOTIATE
                              SMB_VERSION                   SMB_2.1
                              SMB_SHARE_TYPE                DISK
                              SIGNING_SUPPORTED             TRUE
                              EXTENDED_SECURITY_SUPPORTED   TRUE
                              LARGE_FILE_SUPPORTED          TRUE
                              FILE_IDS_SUPPORTED            TRUE
                              DFS_SUPPORTED                 TRUE
                              MULTI_CREDIT_SUPPORTED        TRUE

So. It looks like SMB1 is still used on 4.2.x. I haven't tried forcing the use of SMB2. I think SMB2 is off by default in samba 3.6. I will ask our engineering about this.

The good news is that on OS6, we are using SMB2.