Jump to content
SNS Users' Forums
  • Announcements

    • Eric Newbauer

      Forum closed   06/30/2018

      PLEASE NOTE: This forum is closed and no longer moderated. Please visit https://www.studionetworksolutions.com/support/ for assistance with your SNS products. Follow Studio Network Solutions on Twitter. Thank you!


  • Content count

  • Joined

  • Last visited

Everything posted by SNS Hal

  1. Hi Alex, If a single iSCSI connection is to be used, then the machine with the connection can share the mounted volume to the other machines using AFP (or SMB). The iSCSI workstation manages the data, since SAN storage is seen as local, and then shares it as it would any other local volume it owns. There is no need for Xsan, since the other machines will not have a block level (iSCSI or FC) connection to the storage. You said there is no plan to have multiple initiators, but if you change your mind and would like the other machines to have the speed benefit of a SAN connection, then some sort of SAN management will be required; otherwise, if multiple machines concurrently connected to the same block level target, they'd each assume ownership and quickly corrupt the file system. While Xsan can be made to work with iSCSI, we do offer a much simpler alternative, SANmp (or iSANmp), which does not require a metadata network, and allows for cross-platform sharing. You can read more about iSCSI sharing here.
  2. The initiator provides the iSCSI connection, but has no awareness of the file system on the target disk, which is handled only by the operating system. When a LUN is grown, the underlying disk expands, but the file system on top of it typically has no awareness this has happened. Disk Utility will sometimes allow the partition(s) to be resized, but may require disk repair first.
  3. Is SANmp installed as well? If not, this sounds like it may be a bug in Disk Utility. As a troubleshooting step, it may be a good idea to try formatting using an older version of OS X, or using the diskutil command line options to format the disk instead.
  4. Hi Glenn, The SANmp Admin and Client guides have a reference section for the command line interface, if you'd like to set it up that way. Otherwise, you could configure an Auto Sync interval in SANmp Admin. Please see the guide for details about the use of this feature before configuring it.
  5. I was surprised to find this seems to be missing from our globalSAN documentation, but you'll find gsutil in /opt/local/bin. Thank you for drawing our attention to it, and I'll make sure that gets added to the manual! You may also wish to set the PATH variable rather than navigating to the appropriate directory each time you use it. By doing this, you can access the CLI immediately after opening Terminal, and it will persist after rebooting. To set the path permanently, create the file .bash_login in your home folder, containing the following command: PATH=$PATH:/opt/local/bin If this file already exists, simply add that line to the end of it. The next time you start the Terminal window, your new path will be active. We apologize for the oversight. Let us know if we can help with anything else!
  6. Ah, understood! In that case, the initiator does provide a CLI. You'll find the options in Section 3.3 of the guide in the /Applications/globalSAN folder.
  7. Hello, Checking the Persistent box for the target in globalSAN will set it to always attempt a connection when the machine starts, so there's no need for scripting for the initiator, but are you also using SANmp to manage shared SAN storage?
  8. I thought AppleRAID may not be what you were after, but could be an alternative solution.. Multipathing is handled by the operating system, rather than the initiator. The OS can correctly collapse targets if the same target is seen over multiple paths, but in this case the OS has no awareness that there is actually only one intended target. We expect if you can get the Starwind software to make each LUN appear identical to the OS, that you're correct that multipathing could be the solution.
  9. Hi, If we're understanding correctly what you're after, creating an AppleRAID (RAID 1) for the two targets should take care of it. In this case, SANmp (iSANmp) would only see one volume, and continue writing without trouble in the event one of the targets went down. The software RAID could then be rebuilt once access was restored. Hope that helps - feel free to open a support case if we can be of further assistance.
  10. Hi Glenn, It looks like we failed to update you last year, but we did investigate this at the time, and we took another look this last week. We found that adding support for this target would not be a trivial task. We've been listening for users who want an alternative software RAID, but haven't had enough buzz to warrant the development that would be required to add and maintain future support for any third-party solutions. Note that Apple RAID can still be configured in the current OS versions from the command line, and that this is supported in Xtarget.
  11. If you haven't done so yet, please open a support case so we may get a clearer picture of the current and desired behavior. Thanks!
  12. The initiator will continually try to reacquire the targets when in Persistent mode. It sounds like the storage was not available at first, and was then found. Has the issue persisted? Please open a support case if you'd like us to take a closer look.
  13. Hello. We don't actually have a version 6.2 for EVO, but from the description, it sounds like the EVO may be automatically repairing logical disks, typically as a result of an unexpected shutdown. If you haven't yet done so, please open a support case so we can take a closer look at this.
  14. We received a support case for this ticket as well, and it was apparent from the screenshots that Error Detection (CRC32C) was enabled in globalSAN, and not in the other initiator. The initiator itself should not be affecting the speed, but the CRC policy does tell the operating system to perform extra calculations for every transfer, and the impact is especially noticeable when using 10Gb. Turning it off in globalSAN or enabling it in the other initiator should result in consistency between the two. The slower read speed is most likely a connectivity or configuration issue. There may be an MTU mismatch in ports on the workstation, switch, or storage. OS X also often requires some stack tuning to optimize 10Gb performance, and many adapters have recommendations for this. We'll watch for an update to the support case.
  15. Additionally, please note that depending on your EVO model, there may already be a spare drive included in the rear of the chassis. On current systems, the EVO configuration data is replicated across the data disks to provide for an automatic recovery in the event of OS disk replacement. Let us know and we'll be happy to help with the transition, if needed.
  16. The preference to allow user passwords to be remembered can be found in the ShareBrowser Admin application on the "Manage Users" tab.
  17. No Response from Sharebrowser Server

    The quickest path to resolution for each of these would likely be with a support case, so we could get remote access if needed. Please also see our El Capitan compatibility article.
  18. SANmp client Log in

    Glad you were able to get it sorted. You'll find the Client and Admin guides in the /Applications/SANmp folder, and these videos may help as well. SANmp Admin SANmp Client Feel free to open a support case if you have any more questions or concerns.
  19. We were unable to reproduce this behavior. Is the machine running 64-bit Windows 7 and SANmp? Was the NTFS volume formatted in its native environment or in OS X? Feel free to open a support case for further investigation if needed.
  20. The EVO guide can be accessed by clicking Help from within the GUI, and will explain how to remap existing logical disks for NAS usage, but we can also offer more direct assistance if you'd like to open a support case.
  21. Glad you got it sorted out. The only issue we were aware of concerned updating to DSM version 6, for which there's this fix.
  22. Please see this article. Feel free to open a support case if you still have any trouble.
  23. Is the initiator in Trial Mode, or is it licensed? What version of DSM is the new Synology running? If it's version 6, please see this article.
  24. We haven't had any other reports of this happening - Have you tried reinstalling the initiator? What is the target storage? Feel free to open a support case if you still have trouble.
  25. Lost network activity

    This was brought up in the support case the same day, and the switch caught up with the change on its own.