[budy]

Hi all,

I am having a problem with glbalSAN and my new Thecus NAS N5200Pro. First I had only one iSCSI target configured and eveything was well. Then I configured two more targets, but the only target that gets attached is still the first one.

The other targets do show up automatically and I can log in to them, but there is no disk attached to the Mac other than the first one. The funny thing is: whatever target I am configuring to be the fiirst in the ietd.conf on the N5200pro, that is the target that will successfully attach.

At this time I am qute unsure if globalSAN is to blame or the N5200pro and I was hoping that someone here would have a Thecus as well, and wouldn't mind to confirm this, or even better, to tell me that it's actually working.

Cheers,
budy

[budy]

I have just installed CentOS 5.2 in a Parallels VM and I have no problem to attach all three iSCSI targets from within CentOS 5.2.
This seems to point to a problem with globalSAN.
Any idea anyone?

Thanks,
budy

[budy]

Hi all,

I have found the reason why globalSAN would not mount the other iSCSI targets on my Thecus N5200Pro. The reason is, that the Thecus numbers the targets from LUN 0 up to the number of volumes one has configured. Obviously globalSAN only queries for LUN 0 and simply doesn't recognize the other targets.

Now, I know that this is a bit odd on the Thecus side, but it's technically not a bug, since SCSI of course handles not only IDs but also LUNs.

I have now been able to attach all three targets of my Thecus by changeing the ietd.cond file manually and changind each LUN X to LUN 0 which is okay, since the Thecus does create a new LV for each target anyway - as I said a little bit odd.

Unfortuanetly. the ietd.conf is generated at each boot again, so my changes wouldn't survive a reboot, and I have requested a change in the approriate script from Thecus support.

Cheers,
budy

[macdows]

budy, on Nov 1 2008, 08:38 AM, said:

Hi all,

I have found the reason why globalSAN would not mount the other iSCSI targets on my Thecus N5200Pro. The reason is, that the Thecus numbers the targets from LUN 0 up to the number of volumes one has configured. Obviously globalSAN only queries for LUN 0 and simply doesn't recognize the other targets.

Now, I know that this is a bit odd on the Thecus side, but it's technically not a bug, since SCSI of course handles not only IDs but also LUNs.

I have now been able to attach all three targets of my Thecus by changeing the ietd.cond file manually and changind each LUN X to LUN 0 which is okay, since the Thecus does create a new LV for each target anyway - as I said a little bit odd.

Unfortuanetly. the ietd.conf is generated at each boot again, so my changes wouldn't survive a reboot, and I have requested a change in the approriate script from Thecus support.

Cheers,
budy

Thanks for the tip, ihave the same problem connecting a macbook pro and a mac mini to a "tweaked" n5200....

I am able to connect only one mac at a time to only the first iscsi volume (lun0).
If the macbook is already logged in ans lun0 is accessible, i can log in the mac mini to lun1, but the disk won't
mount nor disk utility is able to "see" the lun.
A Windows Vista PC for testing purpose was able to login and access lun1 simultaneously.

I tried to edit ietd.conf, but to no avail....

Could you please post the output of your ietd.conf file so i can see what i could have done wrong....

Or could someone from SNS has an idea ?

Any help is welcome, so i can do time machine backups from both my macs

running MacOS 10.5.6, Thecus firmware 2.00.14, GlobalSAN initiator 3.3.0.43

Many thanks

macdows

[budy]

Hi all,

over at the thecus.eu forums I had posted the solution to this problem - at least with FW 2.0.14. Since I have swapped out the original Thecus FW on my N5200pro with a complete CentOS 5.3 installation, I don't need to apply any tweaks to my N5200 anymore.

Cheers,
budy

[SNSryan]

Hi,

We've just announced a beta version for globalSAN v4.0. This version addresses many incompatibilities with 3rd party targets. We'd love to hear if this v4.0 beta helps with this target. Go here for additional details and download link. I look forward to everyones feedback.

-ryan

[studiob]

SNSryan, on 11 November 2009 - 01:03 PM, said:

Hi,

We've just announced a beta version for globalSAN v4.0. This version addresses many incompatibilities with 3rd party targets. We'd love to hear if this v4.0 beta helps with this target. Go here for additional details and download link. I look forward to everyones feedback.

-ryan

Dear Ryan: Thank you so much for providing this initiator. I am pleased to report that the beta initiator was successfully able to mount two different ISCSI targets on our G5. There is no LUN ID configurable or displayed or information screen in the beta like there is in the previous release, but who can complain if it can mount the two targets! Good work. Thanks again,

Lee (Bob's assistant in Studio B at Digital Domain www.digido.com)

[amc]

budy, on 31 October 2008 - 08:44 AM, said:

Hi all,

I am having a problem with glbalSAN and my new Thecus NAS N5200Pro. First I had only one iSCSI target configured and eveything was well. Then I configured two more targets, but the only target that gets attached is still the first one.

The other targets do show up automatically and I can log in to them, but there is no disk attached to the Mac other than the first one. The funny thing is: whatever target I am configuring to be the fiirst in the ietd.conf on the N5200pro, that is the target that will successfully attach.

At this time I am qute unsure if globalSAN is to blame or the N5200pro and I was hoping that someone here would have a Thecus as well, and wouldn't mind to confirm this, or even better, to tell me that it's actually working.

Cheers,
budy

[amc]

Thecus have just released (Feb 2010) a new beta firmware (V3.01.00.4) that improves iSCSI connectivity. Check with support @ thecus.com to see if the N5200 is supported