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!

SNS Hal

Members
  • Content count

    182
  • Joined

  • Last visited

Everything posted by SNS Hal

  1. You should be able to connect the Drobo directly to the machine with a USB cable and then use the Dashboard to view or configure the IP address. I believe the iSCSI service will not start while connected via USB, so you'll need to disconnect before establishing a connection with globalSAN. Feel free to open a support case if you still have trouble.
  2. The iSANmp application simply sends a request to the operating system to unmount the volume, so it seems that Finder would also be unable to eject the disk when this happens. To protect the storage, the operating system will refuse to unmount any volume that is still being accessed by an application. It's not uncommon for Pro Tools to continue silently accessing the volume and prevent an unmount, but in most cases it's Spotlight preventing the unmount, since it indexes SAN storage. We typically recommend mounting all SANmp volumes R/W and then dragging them to Spotlight's Privacy tab in System Preferences. If you continue to have trouble, please open a support case, and we'll be able to find out exactly what is accessing the volume to prevent unmounting.
  3. Could you clarify what is meant by Isan? Is this iSANmp, or globalSAN? The operating system will prevent ejection of a disk while it is still in use, in order to protect the contents of the file system. If I understand correctly, it sounds like an application is still using the volume, and OS X is trying to protect the storage by preventing the unmount.
  4. Hi Stephen, The globalSAN Trial Mode has two functional limitations: first, only one target may be connected; and second, no targets may be set to “persistent” mode. This sounds like a storage configuration issue -- the initiator is strictly a connection mechanism, with no awareness of the contents of the file system. We can take a look at your system to be sure, if you'd like to open a support case, but from your description it seems globalSAN is working as expected.
  5. This KB article may help - feel free to open a case if it doesn't.
  6. If Disk Utility is prompting you to initialize the disk, then it sounds as though the initiator is working as expected, and the target LUN just needs to be formatted. Feel free to open a support case if you still have trouble.
  7. The installation won't survive migration or a restore. Assuming this is the same machine that was originally activated, simply reinstalling the initiator should ensure the correct Product Key is generated and allow you to reactivate it at globalsan.net.
  8. There are no known issues with the initiator and Yosemite. Have you tried removing and re-adding the targets since the upgrade?
  9. Formatting your new logical disks won't affect your existing SANmp disks. Feel free to open a support case for more assistance with this process.
  10. Are you able to first test without CHAP, to ensure the trouble connecting is strictly related to the authentication method? What is the target storage?
  11. Different storage systems have different requirements, and we try to make the globalSAN initiator as robust as possible to allow it to connect with as many devices as possible, so I can't provide an absolute answer, but... When CHAP is enabled on our shared storage solution (EVO), only the "User Authentication" section in globalSAN needs to be defined. CHAP does also require a 12-16 character password. For EVO, a shorter password may be used, but zeros will be appended in order to meet the minimum length requirement. Hope that helps.
  12. It sounds like sleep may be enabled for the workstation or the storage. With a SAN, there is no mechanism for the workstation to tell the storage that it is sleeping (or vice versa), so from the perspective of the storage, the client has disconnected, often without a clean unmount. This mismatch can also lead to application crashing and/or filesystem corruption. We recommend disabling disk sleep for the workstation and the target device.
  13. Hi Alan, Eric and I were just discussing this and we remembered something another user had done that may be applicable here. We posted it in a KB article, if you'd like to check it out. Let us know how you fare!
  14. The globalSAN installation cannot be restored, but as long as it's the same hardware, simply reinstalling it will generate the correct Product Key and allow it to be relicensed at globalsan.net.
  15. For reference, a support case was created for this, and it seems there was an issue with the format on the Areca storage. Reformatting resolved this.
  16. You'll find the uninstaller in the /Applications/globalSAN folder. Choose to remove all components before reinstalling the correct version. If you still have trouble, feel free to open a support case, and we'll be happy to assist.
  17. If you're sure the Thecus supports multi-pathing, then it shouldn't matter whether you choose option 1 or 2, as long as the router can support it (and based on your AFP results, it seems like it can). It may be obvious, but multi-pathing won't be supported over AFP. Typical results from iSCSI would be more in line with what you're seeing on AFP, but it's unclear what could be limiting the speed. One thing to check would be that the error detection settings match for the initiator and target.
  18. What OS X version are you referring to? I know Apple has made some changes to Xsan component compatibility in each release, and especially with Yosemite - this article and this article may help. While it's not something that's officially supported, we do have quite a few customers using the globalSAN initiator successfully in an Xsan environment.
  19. Please contact us and reference this post if you would like to preview a version of the initiator with support for CTL.
  20. It sounds like the storage isn't connected - are you able to see it in Disk Utility? This video may help - feel free to open a support case if you still have trouble.
  21. SANmp Synchronize

    The EVO is unaware of the contents of the SAN; this is managed entirely by the workstations. It sounds like the volume may still be in use when you first perform sync. One common culprit is Spotlight. Check that the volumes are hidden from Spotlight's indexing service - mount them R/W and drag them to the Privacy tab in Spotlight in System Preferences. If you continue to have trouble, feel free to open a support ticket.
  22. SANmp Volume renaming

    Renaming was only supported in SANmp Admin in the early days, but with the newer operating systems and SANmp versions, either method is acceptable. The most likely problem that could occur from users changing volume names would be some confusion on the part of other users — that reason alone may be enough to discourage the practice, but there's no simple way to prevent a user from doing so, since the operating system sees the R/W SAN storage as its own. *edited 12/5/14
  23. Hi Luis - Xtarget requires a separate activation to run, but the Framework does need to be installed for globalSAN to function correctly.
 
 From the System Preferences menu, you can select View and then choose to show the panes alphabetically, or click Customize and uncheck the box next to globalSAN. The initiator will still run from Applications, or can be called by hitting ⌘+spacebar and beginning to type globalSAN.
  24. Please confirm this license screen is on the Xtarget tab rather than the Initiator tab. The driver for the activation key should have installed with the software. Try reinstalling, click Customize, and ensure all boxes are checked. Please open a support case if you still have trouble.
×