Jump to content
SNS Users' Forums
  • Announcements

    • Eric Newbauer

      Follow SNS on Twitter!

      Get notifications via Twitter! Looking for instant updates? We're now also announcing new versions and beta programs via Twitter. Follow Studio Network Solutions on Twitter. Thanks!

Recommended Posts

HISTORY (BEFORE discarding Spotlight)

-------

There are no users connected (admin only).

The server is freshly started.

No problems to connect to the target.

=> The target has about 100Gb of data already copied on it

I've tried with or without authentication.

I've tried with or without persistent.

The state of the connection become orange after a while.

On the left pane, it is still green.

After a night (without persistent) all was red. Disk was unmounted.

On orange state :

This situation blocks any opened or newly opened window from listing the content.

If there was a copy action between directories, this is friezed.

After a while, it is possible to disconnect (not eject) the iscsi drive (with bad ejection message) and after it has been ejected to reconnect (state to green).

Where can I send my logs?

Many thanks for your work at this point,

Michel

Michel, is your QNAP going to sleep?

Share this post


Link to post
Share on other sites

Michel, is your QNAP going to sleep?

Hi Eric, everybody,

My QNAP is going really well at this time.

We are now in production mode and we have 20 users (for now) connecting by afp (through VPN or not) and ftp each the days.

The users will grow (to ± 50) and much trafic (backups) will occur in the next months.

We have 2 luns 'net' and 'clients' on the same NAS.

I have not seen any hang of the iscsi network since I disable spotlight on these drives and certainly also since I disable automatic TimeMachine.

I can update my TimeMachine without hang only if done manually.

From starting the server, I have this logs but only since the last firmware upgrade of the QNAP (TS-459_3.2.7_Build0526):

Jun 2 19:30:20 intranet globalsand[96]: GLO Daemon: Successfully connected to the persistent target "iqn.2004-04.com.qnap:ts-439proii:iscsi.netnas.be0c28" at 100.100.100.124.

Jun 2 19:30:21 intranet globalsand[96]: GLO Daemon: Successfully connected to the persistent target "iqn.2004-04.com.qnap:ts-439proii:iscsi.clientsnas.be0c28" at 100.100.100.124.

Before this QNAP upgrade, the server was working but the logs showed some GLO Warnings.

Hope this help. I still have some logs available if needed.

Michel

[edit: You save my life, do you know?]

Share this post


Link to post
Share on other sites

Sorry, come back again !

So to resume, the only change from the starting configuration is the QNAP upgrade and disabling TM and Spotlight.

At this time, there is no authentification but it is persistent connection.

I can't unfortunately do more testing based on this.

I'd like to open spotlight (that I don't really need?) and automatic TimeMachine, but production mode is frozen me a bit.

I just want to point out the release note of the QNAP upgrade about the iscsi improvement.

http://qnap.com/download_detail.asp?pl=1&p_mn=144&ct_name=Firmware

Thanks again,

Michel

Share this post


Link to post
Share on other sites

Continues not to work for me, 10.6.4 didn't change anything.

Do you have authentication turned on? if so, try turning it off.

-ryan

Share this post


Link to post
Share on other sites

Do you have authentication turned on? if so, try turning it off.

-ryan

Nope, I've always had authentication off.

Share this post


Link to post
Share on other sites

Nope, I've always had authentication off.

Did you uninstall v3.3 using the v3.3 installer package prior to installing v4?

Could you please provide a refresher on the symptoms?

Share this post


Link to post
Share on other sites

Did you uninstall v3.3 using the v3.3 installer package prior to installing v4?

Could you please provide a refresher on the symptoms?

Yes, I removed 3.3 with the 3.3 uninstaller before installing 4.0 each time as this is the only way it would actually work.

I've used both the 3.3 and 4.0 initiators on 10.5 with no problems. I

recently (finally) updated to 10.6 and the 4.0 version was causing a

lot of problems. It would work fine for a while and then all traffic

to it would stop and the processes trying to use it would stall and

become non-responsive. After several occurrences I reverted back to

3.3 and things seem to be working fine again.

My target is istgt on FreeBSD 8.0 AMD64.

Welp, v3 crashed my OS a couple times so I gave v4 a go again but

first updated my target to the latest. Same old issues though, it

transfered a bunch of data and then stalled. I captured packets while

it was stalled, no traffic. Tried to stop the transfer, disconnect

session and eject the mount, still no traffic. None of the options

were able to complete so another reboot to clear it and now I'm stuck

with no reliable connection.

Share this post


Link to post
Share on other sites

Yes, I removed 3.3 with the 3.3 uninstaller before installing 4.0 each time as this is the only way it would actually work.

I've used both the 3.3 and 4.0 initiators on 10.5 with no problems. I

recently (finally) updated to 10.6 and the 4.0 version was causing a

lot of problems. It would work fine for a while and then all traffic

to it would stop and the processes trying to use it would stall and

become non-responsive. After several occurrences I reverted back to

3.3 and things seem to be working fine again.

My target is istgt on FreeBSD 8.0 AMD64.

Welp, v3 crashed my OS a couple times so I gave v4 a go again but

first updated my target to the latest. Same old issues though, it

transfered a bunch of data and then stalled. I captured packets while

it was stalled, no traffic. Tried to stop the transfer, disconnect

session and eject the mount, still no traffic. None of the options

were able to complete so another reboot to clear it and now I'm stuck

with no reliable connection.

Any progress?

Any tests or debugging I can do to figure this out?

Share this post


Link to post
Share on other sites

I would like to use the globalSAN iSCSI Initiator on OS X 10.6 Snow Leopard Server, running on a 64-bit Mac Mini Server, but the current software will not install successfully. The driver component will not install.

Does anyone from the SNS team have an indication as to when a 64-bit release or beta will be available?

thanks.

Share this post


Link to post
Share on other sites

Does anyone from the SNS team have an indication as to when a 64-bit release or beta will be available?

Good luck. Seems the last word from SNS on this was on Nov-10-09 in that "64-bit Snow Leopard compatibility will be coming in a future release..."

I've asked on here a few times since June but no one seems to be paying attention, or cares to reply. I can not really complain since it's being provided for free. We bit the bullet and purchased ATTO's iSCSI initiator. Other than the fact that it doesn't support multipathing on OS X (they claim it's a limitation imposed by Apple), it's working rather well.

Naturally I would prefer a free initiator over the ATTO one, even if we could purchase support for it from SNS, but 64-bit is a requirement in a server with 24 GB of RAM AFAIK.

Share this post


Link to post
Share on other sites

Good luck. Seems the last word from SNS on this was on Nov-10-09 in that "64-bit Snow Leopard compatibility will be coming in a future release..."

I've asked on here a few times since June but no one seems to be paying attention, or cares to reply. I can not really complain since it's being provided for free. We bit the bullet and purchased ATTO's iSCSI initiator. Other than the fact that it doesn't support multipathing on OS X (they claim it's a limitation imposed by Apple), it's working rather well.

Naturally I would prefer a free initiator over the ATTO one, even if we could purchase support for it from SNS, but 64-bit is a requirement in a server with 24 GB of RAM AFAIK.

We have not forgot about you! Hang in there, something is coming soon :)

ryan

Share this post


Link to post
Share on other sites

×