Iscsi target problem - solaris 10 snv_10

I'm trying to connect to targets off a Sanrad vswitch from a Netra T1 running solaris express snv_10. I can see the targets, a devfsadm -i iscsi shows the system bringing the targets online, but I don't see anything in format afterwards.
Both targets are fully funcational on a Solaris 8 system running the cisco initiator.
# iscsiadm list discovery-address -v
Discovery Address: 10.1.11.79:3260
Target name: test02
Target address: 10.1.11.79:3260, 1
Target name: nete.test01
Target address: 10.1.11.79:3260, 1
# iscsiadm list target
Target: nete.test01
Target Portal Group Tag: 1
Connections: 0
Target: test02
Target Portal Group Tag: 1
Connections: 0
# devfsadm -i iscsi
Jun 7 05:53:56 netrat1-iscsi iscsi: NOTICE: iscsi session(5) nete.test01 online
Jun 7 05:53:56 netrat1-iscsi iscsi: NOTICE: iscsi session(4) test02 online
# format
Searching for disks...done
AVAILABLE DISK SELECTIONS:
0. c0t0d0 <SUN18G cyl 7506 alt 2 hd 19 sec 248>
/pci@1f,0/pci@1,1/scsi@2/sd@0,0
Specify disk (enter its number):
suggestions?

After doing the "devfsadm -i iscsi" can you post the results of "iscsiadm list target -S". Were there any additional messages around the time of the online messages?

Similar Messages

ZFS root problem after iscsi target experiment

Hello all.
I need help with this situation... I've installed solaris 10u6, patched, created branded full zone. Everything went well until I started to experiment with iSCSI target according to this document: http://docs.sun.com/app/docs/doc/817-5093/fmvcd?l=en&a=view&q=iscsi
After setting up iscsi discovery address of my iscsi target solaris hung up and the only way was to send break from service console. Then I got these messages during boot
SunOS Release 5.10 Version Generic_138888-01 64-bit
/dev/rdsk/c5t216000C0FF8999D1d0s0 is clean
Reading ZFS config: done.
Mounting ZFS filesystems: (1/6)cannot mount 'root': mountpoint or dataset is busy
(6/6)
svc:/system/filesystem/local:default: WARNING: /usr/sbin/zfs mount -a failed: exit status 1
Jan 23 14:25:42 svc.startd[7]: svc:/system/filesystem/local:default: Method "/lib/svc/method/fs-local" failed with exit status 95.
Jan 23 14:25:42 svc.startd[7]: system/filesystem/local:default failed fatally: transitioned to maintenance (see 'svcs -xv' for details)
---- There are many affected services from this error, unfortunately one of them is system-log, so I cannot find any relevant information why this happens.
bash-3.00# svcs -xv
svc:/system/filesystem/local:default (local file system mounts)
State: maintenance since Fri Jan 23 14:25:42 2009
Reason: Start method exited with $SMF_EXIT_ERR_FATAL.
See: http://sun.com/msg/SMF-8000-KS
See: /var/svc/log/system-filesystem-local:default.log
Impact: 32 dependent services are not running:
svc:/application/psncollector:default
svc:/system/webconsole:console
svc:/system/filesystem/autofs:default
svc:/system/system-log:default
svc:/milestone/multi-user:default
svc:/milestone/multi-user-server:default
svc:/system/basicreg:default
svc:/system/zones:default
svc:/application/graphical-login/cde-login:default
svc:/system/iscsitgt:default
svc:/application/cde-printinfo:default
svc:/network/smtp:sendmail
svc:/network/ssh:default
svc:/system/dumpadm:default
svc:/system/fmd:default
svc:/system/sysidtool:net
svc:/network/rpc/bind:default
svc:/network/nfs/nlockmgr:default
svc:/network/nfs/status:default
svc:/network/nfs/mapid:default
svc:/application/sthwreg:default
svc:/application/stosreg:default
svc:/network/inetd:default
svc:/system/sysidtool:system
svc:/system/postrun:default
svc:/system/filesystem/volfs:default
svc:/system/cron:default
svc:/application/font/fc-cache:default
svc:/system/boot-archive-update:default
svc:/network/shares/group:default
svc:/network/shares/group:zfs
svc:/system/sac:default
[ Jan 23 14:25:40 Executing start method ("/lib/svc/method/fs-local") ]
WARNING: /usr/sbin/zfs mount -a failed: exit status 1
[ Jan 23 14:25:42 Method "start" exited with status 95 ]
Finaly there is output of zpool list command, where everything about ZFS pools looks OK:
NAME SIZE USED AVAIL CAP HEALTH ALTROOT
root 68G 18.5G 49.5G 27% ONLINE -
storedgeD2 404G 45.2G 359G 11% ONLINE -
I would appretiate any help.
thanks in advance,
Berrosch

OK, i've tryied to install s10u6 to default rpool and move root user to /rpool directory (which it is nonsense of course, it was just for this testing purposes) and everything went OK.
Another experiment was with rootpool name 'root' and root user in /root, everything went OK as well.
Next try was with rootpool 'root', root user in /root, enabling iscsi initiator:
# svcs -a |grep iscsi
disabled 16:31:07 svc:/network/iscsi_initiator:default
# svcadm enable iscsi_initiator
# svcs -a |grep iscsi
online 16:34:11 svc:/network/iscsi_initiator:default
and voila! the problem is here...
Mounting ZFS filesystems: (1/5)cannot mount 'root': mountpoint or dataset is busy
(5/5)
svc:/system/filesystem/local:default: WARNING: /usr/sbin/zfs mount -a failed: exit status 1
Feb 9 16:37:35 svc.startd[7]: svc:/system/filesystem/local:default: Method "/lib/svc/method/fs-local" failed with exit status 95.
Feb 9 16:37:35 svc.startd[7]: system/filesystem/local:default failed fatally: transitioned to maintenance (see 'svcs -xv' for details)
Seems to be a bug in iscsi implementation, some quotas of 'root' in source code or something like it...
Martin

[SOLVED] iscsi target lio (targetcli_fb) problem

I configured the targetcli:(don't use authentication)
tpg1> set parameter AuthMethod=None
set attribute authentication=0
/etc/rc.d/target run well.
But when the initiator connects the target, target reports the error:
iSCSI Initiator Node: iqn.xxxx-xxxx-xxxx is not authorized to access iSCSI target portal group: 1
uname -a
Linux 3.2.13-1-ARCH
what else settings? Thanks.
This is the saveconfig.json
"fabric_modules": [],
"storage_objects": [
"attributes": {
"block_size": 512,
"emulate_dpo": 0,
"emulate_fua_read": 0,
"emulate_fua_write": 1,
"emulate_rest_reord": 0,
"emulate_tas": 1,
"emulate_tpu": 0,
"emulate_tpws": 0,
"emulate_ua_intlck_ctrl": 0,
"emulate_write_cache": 0,
"enforce_pr_isids": 1,
"is_nonrot": 0,
"max_sectors": 1024,
"max_unmap_block_desc_count": 0,
"max_unmap_lba_count": 0,
"optimal_sectors": 1024,
"queue_depth": 32,
"unmap_granularity": 0,
"unmap_granularity_alignment": 0
"buffered_mode": true,
"dev": "/home/faicker/test.img",
"name": "disk1",
"plugin": "fileio",
"size": 10737418240,
"wwn": "b83cf4a1-5e30-4df4-a5a2-ac7163d78a4d"
"targets": [
"fabric": "iscsi",
"tpgs": [
"attributes": {
"authentication": 0,
"cache_dynamic_acls": 0,
"default_cmdsn_depth": 16,
"demo_mode_write_protect": 1,
"generate_node_acls": 0,
"login_timeout": 15,
"netif_timeout": 2,
"prod_mode_write_protect": 0
"enable": 1,
"luns": [
"index": 0,
"storage_object": "/backstores/fileio/disk1"
"node_acls": [],
"parameters": {
"AuthMethod": "None",
"DataDigest": "CRC32C,None",
"DataPDUInOrder": "Yes",
"DataSequenceInOrder": "Yes",
"DefaultTime2Retain": "20",
"DefaultTime2Wait": "2",
"ErrorRecoveryLevel": "0",
"FirstBurstLength": "65536",
"HeaderDigest": "CRC32C,None",
"IFMarkInt": "2048~65535",
"IFMarker": "No",
"ImmediateData": "Yes",
"InitialR2T": "Yes",
"MaxBurstLength": "262144",
"MaxConnections": "1",
"MaxOutstandingR2T": "1",
"MaxRecvDataSegmentLength": "8192",
"OFMarkInt": "2048~65535",
"OFMarkInt": "2048~65535",
"OFMarker": "No",
"TargetAlias": "LIO Target"
"portals": [
"ip_address": "0.0.0.0",
"port": 3260
"tag": 1
"wwn": "iqn.2003-01.org.linux-iscsi.u205.x8664:sn.5f9e1e0139f2"
Last edited by faicker (2012-04-16 15:27:21)

/iscsi/iqn.20...1e0139f2/tpg1> ls /
o- / ..................................................................... [...]
o- backstores .......................................................... [...]
| o- block ................................................ [0 Storage Object]
| o- fileio ............................................... [1 Storage Object]
| | o- disk1 ........................ [/home/mocan/test.img (10.0G) activated]
| o- pscsi ................................................ [0 Storage Object]
| o- ramdisk .............................................. [0 Storage Object]
o- ib_srpt ....................................................... [Not found]
o- iscsi .......................................................... [1 Target]
| o- iqn.2003-01.org.linux-iscsi.u205.x8664:sn.5f9e1e0139f2 .......... [1 TPG]
| o- tpg1 ........................................................ [enabled]
| o- acls ........................................................ [1 ACL]
| | o- iqn.2003-01.org.linux-iscsi.u205.x8664:sn.5f9e1e0139f2 [1 Mapped LUN]
| | o- mapped_lun0 ............................ [lun0 fileio/disk1 (rw)]
| o- luns ........................................................ [1 LUN]
| | o- lun0 ........................ [fileio/disk1 (/home/mocan/test.img)]
| o- portals .................................................. [1 Portal]
| o- 0.0.0.0:3260 ................................................. [OK]
o- loopback ....................................................... [0 Target]
o- qla2xxx ....................................................... [Not found]
o- tcm_fc ........................................................ [Not found]
This is targetcli ls / result.
the open-iscsi initiator report error:
iscsiadm: initiator reported error (19 - encountered non-retryable iSCSI login failure)
It still wasn't solved.
Last edited by faicker (2012-04-14 15:36:07)

Reg reboot issue - console message- svc:/network/iscsi/target:default: Method or service exit timed out

Hi,
When I reboot the system I am seeing this message on the console and system is not getting rebooted.
svc.startd[10]: svc:/network/iscsi/target:default: Method or service exit timed out. Killing contract 131.
can someone help me to solve this?

There are still a few issues with Solaris 11.1 and iSCSI LUN and rebooting. I know they are working on fixes.
A possible workaround is to use the reboot command and NOT the init command. At least when you use the reboot the command the system will reboot and not hang.
If this is not your problem then it may be a different problem.
Andrew

Iscsi target rewriting sparse backing store

Hi all,
I have this particular problem when trying to use sparse file residing on zfs as backing store for iscsi target. For the sake of this post, lets say I have to use the sparse file instead of whole zfs filesystem as iscsi backing store.
However, as soon as the sparse file is used as iscsi target backing store, Solaris OS (iscsitgt process) decides to rewrite entire sparse file and make it non-sparse. Note this all happens without any iscsi initiator (client) accessed this iscsi target.
My question is why the sparse file is being rewritten at that time?
I can expect write at iscsi initiator connect time, but why at the iscsi target create time?
Here are the steps:
1. Create the sparse file, note the actual size,
# dd if=/dev/zero of=sparse_file.dat bs=1024k count=1 seek=4096
1+0 records in
1+0 records out
# du -sk .
2
# ll sparse_file.dat
-rw-r--r--   1 root     root     4296015872 Feb 7 10:12 sparse_file.dat
2. Create the iscsi target using that file as backing store:
# iscsitadm create target --backing-store=$PWD/sparse_file.dat sparse
3. Above command returns immediately, everything seems ok at this time
4. But after couple of seconds, disk activity increases, and zpool iostat shows
# zpool iostat 3
               capacity     operations    bandwidth
pool         used avail   read write   read write
mypool 5.04G   144G      0    298      0 35.5M
mypool 5.20G   144G      0    347      0 38.0M
and so on, until the write over previously sparse 4G is over:
5. Note the real size now:
# du -sk .
4193252 .Note all of the above was happening with no iscsi initiators connected to that node nor target. Solaris OS did it by itself, and I can see no reasons why.
I would like to have those files sparse, at least until I use them as iscsi targets, and I would prefer those files to grow as my initiators (clients) are filling them.
If anyone can share some thoughts on this, I'd appreciate it
Thanks,
Robert

Problem solved.
Solaris iscsi target daemon configuration file has to be updated with:
<thin-provisioning>true</thin-provisioning>
in order to iscsitgtd not to initialize the iscsi target backing store files. This is all valid only for iscsi targets having files as backing store.
After creating iscsi targets with file (sparse or not) as backing store, there is no i/o activity whatsoever, and thats' what I wanted.
FWIW, This is how the config file looks now.
# more /etc/iscsi/target_config.xml
<config version='1.0'>
<thin-provisioning>true</thin-provisioning>
</config>
#

Unable to expand/extend partition after growing SAN-based iSCSI target

Hello, all. I have odd situation regarding how to expand iSCSI-based partitions.
Here is my setup:
I use the GlobalSAN iSCSI initiator on 10.6.x server (Snow Leopard).
The iSCSI LUN is formatted with the GPT partition table.
The filesystem is Journaled HFS+
My iSCSI SAN has the ability to non-destructively grow a LUN (iSCSI target).
With this in mind, I wanted to experiment with growing a LUN/target on the SAN and then expanding the Apple partition within it using disk utility. I have been unable to do so.
Here is my procedure:
1) Eject the disk (iSCSI targets show up as external hard drives)
2) Disconnect the iSCSI target using the control panel applet (provided by GlobalSAN)
3) Grow the LUN/target on the SAN.
4) Reconnect the iSCSI initiator
5) Expand/extend the partition using Disk Utility to consume the (newly created) free space.
It works until the last step. When I reconnect to the iSCSI target after expanding it on the SAN, it shows up Disk Utility as being larger than it was (so far, so expected). When I go to expand the partition, however, it errors out saying that there is not enough space.
Investigating further, I went the command line and performed a
"diskutil resizeVolume <identifier> limits"
to determine what the limit was to the partition. The limits did NOT reflect the newly-created space.
My suspicion is that the original partition map, since it was created as 100% of the volume, does not allow room for growth despite the fact that the disk suddenly (and, to the system, unexpectedly) became larger.
Is this assumption correct? Is there any way around this? I would like to be able to expand my LUNs/targets (since the SAN can grow with the business), but this has no value if I cannot also extend the partition table to use the new space.
If anyone has any insight, I would greatly appreciate it. Thank you!

I have exactly the same problem that you describe above. My iSCSI LUN was near capacity and therefore i extended the iSCSI LUN from 100G to 150G. No problem so far.
Disk Utility shows the iSCSI device as 150G but i cannot extend the volume to the new size. It gives me the same error (in Dutch).
Please someone help us out !

Unable to use device as an iSCSI target

My intended purpose is to have iSCSI targets for a virtualbox setup at home where block devices are for the systems and existing data on a large RAID partition is exported as well. I'm able to successfully export the block files by using dd and added them as a backing-store into the targets.conf file:
include /etc/tgt/temp/*.conf
default-driver iscsi
<target iqn.2012-09.net.domain:vm.fsrv>
backing-store /srv/vm/disks/iscsi-disk-fsrv
</target>
<target iqn.2012-09.net.domain:vm.wsrv>
backing-store /srv/vm/disks/iscsi-disk-wsrv
</target>
<target iqn.2012-09.net.domain:lan.storage>
backing-store /dev/md0
</target>
but the last one with /dev/md0 only creates the controller and not the disk.
The RAID device is mounted, I don't whether or not that matters, unfortunately I can't try it being unmounted yet because it is in use. I've tried all permutations of backing-store and direct-store with md0 as well as another device (sda) with and without the partition number, all had the same result.
If anyone has been successful exporting a device (specifically a multi disk) I'd be real interested in knowing how. Also, if anyone knows how, or if it's even possible, to use a directory as the backing/direct store I'd like to know that as well, my attempts there have been unsuccessful as well.
I will preempt anyone asking why I'm not using some other technology, eg. NFS, CIFS, ZFS, etc., by saying that this is largely academic. I want to compare the performance that a virtualized file server has that receives it's content being served by both NFS and iSCSI, and the NFS part is easy.
Thanks.

Mass storage only looks at the memory expansion.
Did you have a micro SD card in it?
What OS on the PC are you running?
Click here to Backup the data on your BlackBerry Device! It's important, and FREE!
Click "Accept as Solution" if your problem is solved. To give thanks, click thumbs up
Click to search the Knowledge Base at BTSC and click to Read The Fabulous Manuals
BESAdmin's, please make a signature with your BES environment info.
SIM Free BlackBerry Unlocking FAQ
Follow me on Twitter @knottyrope
Want to thank me? Buy my KnottyRope App here
BES 12 and BES 5.0.4 with Exchange 2010 and SQL 2012 Hyper V

Failed Creation ISCSI Target on NSS324

Hello,
I configured a NSS324 4 drives of 2To in RAID5.I had not no problem
But when i would like to create a ISCSI target (one LUN of my total capacity : 5,36 To), it tooks more than 15 hours and i got this error after 15H: [iSCSI] Failed to create iSCSI target. (error code=5).
Can you help me? can i create a LUN of my whole capacity?
Thanks a lot
Sev

Please use code tags for your config and other terminal output for better readability. Still, it looks ok to me.
I have targetcli-fb on one of my Arch boxes, but it's an old version (2.1.fb35-1) built back in June (official packages are up to date). Discovery and login from another Arch box works. I don't have time to troubleshoot further, but if you haven't found a solution by Monday I can update and maybe be of more use.

ISCSI targets for the Mac

I setup a VMware vSphere 4 Server with RAID 10 direct-attached storage and 3 virtual machines:
- OpenSolaris 2009.06 dev version (snv_111b) running 64-bit
- CentOS 5.3 x64 (ran yum update)
- Ubuntu Server 9.04 x64 (ran apt-get upgrade)
I gave each virtual 2 GB of RAM, a 32 GB virtual drive and setup a 16 GB iSCSI target on each (the two Linux vms used iSCSI Enterprise Target 0.4.16 with blockio). VMware Tools was installed on each. No tuning was done on any of the operating systems.
I ran two tests for write performance - one on the server itself and one from my MacBook Pro (10.5.7) connected via Gigabit (mtu of 1500) iSCSI connection using globalSAN 3.3.0.43.
Here’s what I used on the servers:
time dd if=/dev/zero of=/root/testfile bs=1048576k count=4
and the Mac OS with the iSCSI connected drive (formatted with GPT / Mac OS Extended journaled):
time dd if=/dev/zero of=/Volumes/test/testfile bs=1048576k count=4
The results were very interesting (all calculations using 1 MB = 1,084,756 bytes).
For OpenSolaris, the local write performance averaged 86 MB/s. I turned on lzjb compression for rpool (zfs set compression=lzjb rpool) and it went up to 414 MB/s since I’m writing zeros). The average performance via iSCSI was an abysmal 16 MB/s (even with compression turned on - with it off, 13 MB/s).
For CentOS (ext3), local write performance averaged 141 MB/s. iSCSI performance was 78 MB/s (almost as fast as local ZFS performance on the OpenSolaris server when compression was turned off).
Ubuntu Server (ext4) had 150 MB/s for the local write. iSCSI performance averaged 80 MB/s.
One of the main differences between the three virtual machines was that the iSCSI target on the Linux machines used partitions with no file system. On OpenSolaris, the iSCSI target created sits on top of ZFS. That creates a lot of overhead (although you do get some great features).
Since all the virtual machines were connected to the same switch (with the same MTU), had the same amount of RAM, used default configurations for the operating systems, and sat on the same RAID 10 storage, I’d say it was a pretty level playing field.
At this point, I think I'll be using Ubuntu 9.04 Server (64-bit) as my iSCSI target for Macs.
Has anyone else done similar (or more extensive) testing?

I had a lot of trouble with SimCity4 on my iMac. It became such a headache that I returned it to compUSA. It ran very choppy and crashed repeatedly when the city began to develop. My system FAR exceeds the system requirements for the game, and after some online research I discovered that I am not the only person to have this trouble with SimCity running on 10.4. I have also read problems concerning the SIMS2. Some of what I have read indicates that 10.3 runs the games fine, but 10.4 causes them to crash. I don't know if this is the case, but I do know that I am now very weary before dropping $50 on a game that may not perform on my computer as it claims to on the box. Some people trying to run games are talking about waiting for Mac OS updates that will allow them to run smoother.
I would check out what gamers are saying before buying anything
http://www.macosx.com/forums/showthread.php?t=226286

ISCSI Target Issues

I am running MS Server 2012 and am only using this as a iscsi target server. I run VMware vspher 5.5 as the initiator. So every night around 12:30 am, my server restarts many of the services, one of them being the iscsi target service. No
errors are produced, just informational logs about the services stopping and starting again. However, when they stop my vphere client and vm's on the iscsi target lose connection. I just want them to run all the time, these are production systems.
When I come in the next day I just do a refresh on the iscsi target gui and everything reconnects. Then I have to go to the vsphere client and answer the guest question about why they lost contact with the targets and the vm's all restart without
a problem. Does anyone know about this problem and how to resolve it?

No, but I think 2012 has built in virus checker, I'll check that. Nope, but this is the info log published.
At 12:31 I got "The Microsoft iSCSI Software Target service entered the stopped state." Then when I came in this morning and hit refresh at 6:01 I got "The Microsoft iSCSI Software Target
service entered the running state.". Both were the event id below. Sometimes it puts it back in the running state automatically, but sometimes I have to manually do it, either way, when it goes into stopped state my vsphere client makes me
answer the "guest" question to bring it back live in the vmware client side. Checked antivirus, no problems there. Again, these are not errors, they a re calling these basic service operations as shown below. How can shutting down
productions systems be a normal operation, must be some way around that or who would want to use this. The nice thing is how easy it is to set up a target, but this is a problem. People use are systems around the clock sooo...any other thoughts?
Event ID 7036 — Basic Service Operations
73 out of 202 rated this helpful - Rate this topic
Updated: December 11, 2007
Applies To: Windows Server 2008
green
Service Control Manager transmits control requests to running services and driver services. It also maintains status information about those services, and reports configuration changes and state changes.
Event Details
Product: Windows Operating System
ID: 7036
Source: Service Control Manager
Version: 6.0
Symbolic Name: EVENT_SERVICE_STATUS_SUCCESS
Message: The %1 service entered the %2 state.
Resolve
This is a normal condition. No further action is required.
Related Management Information
Basic Service Operations
Core Operating System
So how c

ISCSI target setup fails: command "iscsitadm" not available?

Hello,
I want to set up a iSCSI target:
however it seems I don't have
iscsitadm
available on my system, only
iscsiadm
What to do?
Is this
http://alessiodini.wordpress.com/2010/10/24/iscsi-nice-to-meet-you/
still valid in terms of set up procedure?
Thanks

Ok,
here you go using COMSTAR:
pkg install storage-server
pkg install -v SUNWiscsit
http://thegreyblog.blogspot.com/2010/02/setting-up-solaris-comstar-and.html
svcs \*stmf\*
svcadm enable svc:/system/stmf:default
zfs create -V 250G tank-esata/macbook0-tm
sbdadm create-lu /dev/zvol/rdsk/tank-esata/macbook0-tm
sbdadm list-lu
stmfadm list-lu -v
stmfadm add-view 600144f00800271b51c04b7a6dc70001
svcs \*scsi\*
itadm create-target
devfsadm -i iscsi
reboot
Solaris 11 Express iSCSI manual:
http://dlc.sun.com/pdf/821-1459/821-1459.pdf
and that for reference
http://nwsmith.blogspot.com/2009/07/opensolaris-2009-06-and-comstar-iscsi.html
Windows iSCSI initiator
http://www.microsoft.com/downloads/en/details.aspx?familyid=12cb3c1a-15d6-4585-b385-befd1319f825&displaylang=en
works after manually adding the Server's IP (no auto detect)

Multiple Hyper-V 2012 R2 servers to access a since ISCSI target

A couple years ago the community helped me configure a CentOS file server to connect to my VMWare and HyperV Servers for the purpose of backup. At the time I created 2 LVM devices, one to connect to Esxi via NFS, and one to connect to HV via ISCSI. This has worked GREAT!I have converted almost all my production environment to HV. I had to of course rebuild the arrays and make the larger one ISCSI rather than NFS. I just noticed that file the file structure of the connected HV drives is not the same. I have (3) HV Servers connected to the same ISCSI target which resides on the CentOS file server. When you view the connected drives, the same target has different files on it from different HV Hosts. Prior to rebuilding the arrays, the ISCSI target worked as intended. I suspect that I missed a step during the rebuild. The drives were...
This topic first appeared in the Spiceworks Community

Hello,
I have installed VMM 2012 R2, this is also not allowing me to add and manage Server 2012 R2 hosts. However it is perfectly able to manage Server 2008 host.
It gives following error when tried to add Server 2012 R2 hosts:
Error (2916)
VMM is unable to complete the request. The connection to the agent windows2012.test.com was lost.
WinRM: URL: [http://windows2012.test.com:5985], Verb: [INVOKE], Method: [Associate], Resource: [http://schemas.microsoft.com/wbem/wsman/1/wmi/root/scvmm/AgentManagement]
Unknown error (0x80338012)
Recommended Action
Ensure that the WS-Management service and the agent are installed and running and that a firewall is not blocking HTTPS traffic.
This problem can also be caused by WMI service crash. Ensure that KB 982293 (http://support.microsoft.com/kb/982293) is installed on the machine if it is running Windows Server 2008 R2.
If the error persists, reboot windows2012.test.com and then try the operation again.
Any suggestions please?

Finder crashes while accessing an iscsi target

Hi all.
Since a few months I can't use my synology nas to backup my system.
The diskstation is a synology 209 with two iscsi targets, one for my mac and one for my wifes win laptop. I'm using 10.6.4 and san iscsi initiator.
Under windows there is no problem to access the target and to backup data.
SuperDuper only writes some files, it stops and the system hangs.
Only a few times it is possible to stop and restart the finder, often it quits with: the finder can't be opened -10810.
Already done: new installation of iscsi initiator, repair permissions and some other hints, even a complete new installation of mac os x.
I hope someone has a workaround.
Thx for reply.
Jan
Message was edited by: MacManaman

Hello sponger:
If no one posts a fix for you, I would consider an archive and install (NOT an erase and install):
http://docs.info.apple.com/article.html?artnum=107120
Be sure you have a good backup/retreat strategy before you proceed. In my case, I make bootable clones of my iMacs on an external firewire drive using a little program called SuperDuper (www.shirt-pocket.com).
Barry

My Windows 2012 ISCSI Target service needs to be restarted every time the server starts.

Every time I restart my Windows 2012 server, the ISCSI Target Service is unavailable to the clients even though it appears to be running.
I have to restart the service, then the clients can connect to it.
I tried to change the startup Type to Delayed, but I get an error 87: parameter is incorrect.
I've tried to delete and recreate the VHD and ISCSI Target.
I've tried to uninstall the Role, and reinstall it.
Anybody have any additional ideas to try and troubleshoot this?
Thank you
James Roper

The service is not starting correctly, even though it does start. If I restart the service, everything works correctly. Here is the event in the ISCSI Target.
Log Name: Microsoft-Windows-iSCSITarget-Service/Admin
Source: Microsoft-Windows-iSCSITarget-Service
Date: 5/8/2013 3:11:10 PM
Event ID: 10
Task Category: None
Level: Error
Keywords:
User: SYSTEM
Computer: SRV-ISCSI1
Description:
The Microsoft iSCSI Software Target service could not bind to network address 10.5.4.31, port 3260. The operation failed with error code 10049. Ensure that no other application is using this port.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-iSCSITarget-Service" Guid="{13953C6E-C594-414E-8BA7-DEB4BA1878E3}" />
<EventID>10</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000000</Keywords>
<TimeCreated SystemTime="2013-05-08T22:11:10.899843800Z" />
<EventRecordID>38</EventRecordID>
<Correlation />
<Execution ProcessID="976" ThreadID="1448" />
<Channel>Microsoft-Windows-iSCSITarget-Service/Admin</Channel>
<Computer>SRV-ISCSI1</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="IpAddress">10.5.4.31</Data>
<Data Name="dwPort">3260</Data>
<Data Name="Error">10049</Data>
</EventData>
</Event>

Error when trying to install the iSCSI target - Cannot find the Windows PowerShell data file 'ImportExportIscsiTargetConfiguration.psd1'

Hi,
I'm just attempting to setup an iSCSI target on a freshly installed Windows 2012r2 box, but I get the following error when attempting to Create and iSCSI virtual disk via the wizard after a successful
installation of the iSCSI target role.
The full error is:
Cannot find the Windows PowerShell data file 'ImportExportIscsiTargetConfiguration.psd1' in directory 'C:\Windows\System32\WindowsPowerShell\v1.0\Modules\IscsiTarget\en-GB\', or in any parent culture.
I tried to uninstall, then reinstall the role but no go.
The Server Locale and UI was all updated to en-GB but this folder does not appear to exist in this location. Rather, the folder I can see is:
'C:\Windows\System32\WindowsPowerShell\v1.0\Modules\IscsiTarget\en-US\'
I'm going to attempt to copy the 'en-US' folder to 'en-GB' to see what happens, but I would like to know why this has occurred in the first place? Other roles have installed (such as AD DS AD CS and
IIS) on other machines with no issue.
Many thanks
Chris
Chris

Hi Chris,
The error "Cannot find the Windows PowerShell data file 'ImportExportIscsiTargetConfiguration.psd1'" occured, because the file 'ImportExportIscsiTargetConfiguration.psd1' can't be loaded under the folder en-GB with current culture.
I recommend you can copy this .psd1 file under 'C:\Windows\System32\WindowsPowerShell\v1.0\Modules\IscsiTarget'. Essentially if PowerShell can’t find the specified data file for the current culture it will “fallback” to the top-level data
file in this case.
For more detailed information, please refer to this article:
Windows PowerShell 2.0 String Localization
If there is anything else regarding this issue, please feel free to post back.
Best Regards,
Anna Wang
TechNet Community Support
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

Iscsi target problem - solaris 10 snv_10

Similar Messages

Maybe you are looking for