Thanks for the response. What seems to have happened, although I don't know why is when I created my new Vdisk on the MSA, it assigned the controller B as the owner. I don't have a second controller B. SO My host couldn't see it. I had to manually set controller A as the owner, which removed the lun assignment. Why there is no GUI option to set the LUN I don't know. I couldn't find it. I removed and recreated the volume, assigned LUN 1 and rescanned on my host. It found the LUN and I was able to access the volume. Thanks.
Main Topics
Browse All Topics





by: andyalderPosted on 2009-09-01 at 06:41:23ID: 25231452
Are you using the advanced option of creating the volume off-line and then presenting it to the host or using the default of background initialisation?
If you're using background initialization it can take ages for it to show up, at least with the software initiator. You can log onto the IQN but you can't see any disk device properly until it's completed initialising. I therefore only use the default background method for testing using RAID 0 which doesn't do any background parity scrubbing since it's not valid for RAID0 and the volume is ready in a couple of minutes.