Add a secound iSCSI pool?

[kcurtis]

I have an iSCSI on my Freenas 11.1 that is feeding to my Xen server. All is working great. Now I added another mirror/volume that I want to use for 2 VM on the Xen.

My question is where to start to add the 2nd share (same server, same IP)? Do I follow the steps starting at the Initiator?
I can't risk the data/shares that is running now

 

[RickH]

The easiest way to accomplish this is to simply create a new extent backed by the new volume you just added and create a new 'Associated Target' to map the new extent to the existing target (You'll either need to incriment the LUN ID by one or have both associated targets set to 'auto'). At this point all you should have to do is re-scan your ISCSI initiator from within Xen and you should see the new drive. (you'll still have to go though the steps of formatting the block storage and creating a new datastore within Xen)

The ISCSI standard allows multiple LUN's (or virtual drives) to be mapped to a single target and share all of the connection / security settings from the target. When you use an initiator to connect to a target, you effectively connect to all of the LUN's associated with that target.

The only reason not to do it this way would be if you ever saw a need to have separate access profiles for the different LUN's or the need to more tightly control the networking connecting them...

 

[kcurtis]

Thanks

 

[kcurtis]

OK, I have tried that. Everything went great. I added LUN 2 and pointed it to (file) on the new drive.
I went to the Xencenter, add new SR, pointer to the IP and it found the target find, I now see the 2 LUN's so I pick 2, it said it must format click YES, it starts for a sec. then kicks out an error "The storage repository is not available...."

Am I missing something?

 

[kdragon75]

Can you pull the log from the xenserver?

 

[kcurtis]

This is what I see in the messages log. Says there is a write error? I checked the chmod and ownership in the file it points to on Freenas and it is the same as the one I have working

Code:

Aug 22 06:34:29 UG-Zen01 xapi: [ info|UG-Zen01|2610372 INET 0.0.0.0:80|SR.create R:a08df3ca0862|storage_access] SR 883de3dd-dd9a-b617-d316-c6d2f8bde552 will be implemented by /services/SM/lvmoiscsi in VM OpaqueRef:b4356d16-6d46-4390-ed70-286979a2c4d6
Aug 22 06:34:29 UG-Zen01 xapi: [ info|UG-Zen01|2610372 INET 0.0.0.0:80|sm_exec D:763750813044|xapi] Session.create trackid=ccca294f8bf5d425567ddc1c1abf7e4e pool=false uname= originator= is_local_superuser=true auth_user_sid= parent=trackid=9834f5af41c964e225f24279aefe4e49
Aug 22 06:34:30 UG-Zen01 xapi: [ info|UG-Zen01|2610372 INET 0.0.0.0:80|sm_exec D:763750813044|xapi] Session.destroy trackid=ccca294f8bf5d425567ddc1c1abf7e4e
Aug 22 06:34:30 UG-Zen01 xapi: [error|UG-Zen01|2610372 INET 0.0.0.0:80|SR.create R:a08df3ca0862|storage_access] Re-raising as SR_BACKEND_FAILURE_47 [ ; The SR is not available [opterr=Logical Volume write error [opterr=device /dev/disk/by-id/scsi-36589cfc000000fc1df3d59ce5e1c65fd]];  ]

This is from the Freenas

Code:

Aug 22 07:46:18 ugnas2 ctld[11986]: ##.##.##.## (iqn.2016-08.com.example:a87551cd): read: connection lost
Aug 22 07:46:18 ugnas2 ctld[1918]: child process 11986 terminated with exit status 1

 

[kdragon75]

I'm not super sharp on xen. Can you test this LUN from a winows box to rule out the network?

 

[RickH]

Did you enable Xen initiator compact mode on the extent?
Also, make sure that Read-only is not checked on your new extent.

Are you using CHAP Authentication?