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

Community Reputation

0 Neutral

About jerryz

  • Rank
  1. I was using an iSCSI volume to limit the size of my Time Machine backups, as TM will eat up any capacity it can find. I have a Synology NAS system, so I created a separate volume to store my Time Machine backups, and dumped the iSCSI volume. I did like using iSCSI, but I was always worried about what would happen if the iSCSI driver failed? My fears were realized. In this case, since I didn't have a clue as to when the globalSAN iSCSI driver would be available, I cut the cord, deleted the iSCSI volume (lost my backups, but after considering this, I really didn't need anything in it,) and started TM anew in a regular NAS volume. It was painful, but I am no longer dependent on third-party free software for my backups - which was probably stupid in the first place. All is well in the world again.
  2. During this extraordinary delay in getting out an updated product, I've found an alternative to using iSCSI and will no longer need globalSAN. Lost a customer. Too frustrating. Not worth the pain.
  3. Happy that it worked for you. Took me a little bit to figure it out for myself. I've only been reading here the issues others are having, so I haven't read about anyone having your specific problem. For me, the problem is that it installs and says "Connected" but won't mount the drive. I have several months of backups that I can't access. When I absolutely have to access the data on the backup drive, I reboot using a SL disk I saved where the driver still works. Painful, but functional. Good luck.
  4. I used the process described above by Pribanic, except that globalSAN is case sensitive in the TERMINAL window. Both cases are used, so you'll need to search for both. One option if that doesn't work, a poor one, but an option, is go revert back to SL if you preserved a backup.
  5. I am very happy it worked for you. Unfortunately it didn't work for me. It finds the iSCSI target, etc, but fails to mount it. Arrrrgggh!
  6. I believe that everyone just got frustrated and left the building.
  7. Yes, it would be nice to have a more specific target delivery date. That would help us loyal folks plan our alternatives until the issue is resolved. I know SNS responded recently, but with a vague timeframe. Please - it's really putting a crimp on which direction I need to go. I have several months worth of backups that I can't access, and I already had a requirement to recover a file that I couldn't get to. A better time frame would be really helpful. Thanks. ------------
  8. Caspian, Although I certainly appreciate the issues, for me, doing a clean install would be quite challenging and very time consuming. Reinstalling dozens of applications, upgrades to older versions, etc, is not fun. Not that it is impossible, but it's the last thing that I'd like to do. That was one of my major reasons for moving to OSX from Windows - to avoid a lot of the maintenance. I do have a backup of SL that I can revert to, but I'm slogging through this for now. -------------
  9. Thank you SNSryan. Just having been heard is good news. -------
  10. This is the problem with an unsupported product. They'll get to it when they feel like it. GlobalSAN initiator is great, agreed. But when OS changes come about, we should expect to have problems every time. Welcome to the world of no support. But I also agree it would be nice to hear from SNS just to let us know what the roadmap looks like to correct the problem.
  11. Same issue here. Shows connected but isn't mounted after Lion upgrade. I disconnected the drive and it now cannot connect at all. Was using it for Time Machine backups. Well, looks like those are gone until an update is available.
  12. My iSCSI drive disappears whenever I start my VPN. Obviously the VPN is preventing the OS from seeing the drive on the network. I've added the following information into the hosts file, but it hasn't helped: IPaddress:port iqn...... Is there any way to make this work? I can access all other local 192 addresses so I know that the VPN is configured properly. Thanks.
  13. I just installed and am having the same problem. Had this with an earlier version as well. There is no file called iSCSIConfig.plist. Looking for other resolutions. Running OSX v 10.6.6. Thanks. Got it working. Uninstalled and reinstalled and it's working now. - Jerry