Issue finding ISCI target with ReadyNAS DUO

[sjk34]

Hi , im trying to set up an ISCI target it on my ReadyNAS DUO, I followed http://readynasfreeware.org/projects/nas-iscsi-target/wiki/New_Version and http://www.markwilson.co.uk/blog/2009/09/creating-an-iscsi-target-on-a-netgear-readynas.htm however when I try and find the target with Microsoft iSCSI Initiator after adding the IP under discovery, and refreshing targets. The target does not appear, I'm pretty sure i am using all the default setting.I also have tryed to locate it in the Vsphere to use a datastore however it can't find it either. Using WinSCP I checked on the NAS and the ISCI file is there so it add correctly. I also have checked by starting using SSH and it does work. "backup:/etc/iet# /etc/init.d/rfw-iscsi-target start
Starting iSCSI Target: ietd.".

config file main parts is-
Target iqn.2001-04.com.example:readyduo.iscsi.target0
Lun 0 Path=/c/iscsi_0,Type=fileio

Thanks For your help
Steven

[WhoCares?]

If the Microsoft initiator doesn't find the target chances are it wasn't started properly. To verify you can check the system logs and see what the output of the iscsi target deamon ietd is. Also you should check the output of 'ps ax' and see whether the actual target deamon [istiod1] is running. You should see multiple instances of it.

-Stefan

[sjk34]

Thanks for the quick reply!
I can't see it on the list but underneath is the output from the ps ax. Which looks like it isn't running then. Any ideas what ive missed out?
Do you mind me asking where the system logs are located? or is it just the logs in the frontview?. I forgot to mention earlyer that I had data on the readyNAS before I set up ISCI but I don't think that would effect it
backup:~# ps ax
PID TTY STAT TIME COMMAND
1 ? Ss 0:04 init [3]
2 ? SN 0:00 [ksoftirqd/0]
3 ? S< 0:00 [events/0]
4 ? S< 0:00 [khelper]
5 ? S< 0:00 [kthread]
10 ? S< 0:00 [kblockd/0]
13 ? S< 0:00 [khubd]
41 ? S 0:00 [pdflush]
42 ? S 3:07 [pdflush]
43 ? S 0:06 [kswapd0]
44 ? S< 0:00 [aio/0]
45 ? S< 0:00 [cifsoplockd]
46 ? S< 0:00 [cifsdnotifyd]
92 ? S< 0:00 [kvblade]
93 ? S 0:00 [mtdblockd]
106 ? S 0:00 [hotplug-sata]
116 ? S 0:00 [djsyncd]
117 ? S 0:00 [djcheckd]
120 ? S 0:00 [hotplug-gmac]
291 ? S< 0:00 [kjournald]
416 ? Ss 0:00 /usr/sbin/sshd
546 ? S< 0:07 [kjournald]
594 ? Ss 0:00 /sbin/portmap
601 ? Ss 0:00 /sbin/syslogd -m 0
605 ? Ss 0:00 /sbin/klogd -x -c 3
607 ? Ss 0:00 /usr/sbin/atd
612 ? Ss 0:00 /usr/sbin/inetd
621 ? Ss 0:00 /usr/sbin/cron
625 ? Ss 0:00 avahi-daemon: running [backup.local]
629 ? Ss 0:00 /usr/sbin/cupsd
647 ? Ss 0:00 /usr/sbin/smbd -D
652 ? Ss 0:00 /usr/sbin/rpc.rquotad
654 ? S 0:00 /usr/sbin/smbd -D
659 ? Ss 0:00 /sbin/rpc.statd -p 32765 -o 32766
669 ? S< 0:00 [nfsd4]
670 ? S 0:00 [nfsd]
671 ? S 0:00 [nfsd]
673 ? S 0:00 [lockd]
674 ? S< 0:00 [rpciod/0]
675 ? Ss 0:00 /usr/sbin/rpc.mountd
724 ? Ss 0:15 /usr/sbin/apache-ssl -f /etc/frontview/apache/httpd.c
891 ? Ss 0:00 /usr/sbin/raidard
914 ? Ss 0:00 /usr/sbin/upnpd eth0
917 ? S 0:00 /usr/sbin/lld2d eth0
926 ? S 0:00 /usr/sbin/cnid_metad
931 ? S 0:00 /usr/sbin/afpd -U uams_dhx.so,uams_guest.so -c 50 -n
934 ? Ss 0:00 /usr/sbin/ietd
961 ? S 2:24 /usr/sbin/apache-ssl -f /etc/frontview/apache/httpd.c
985 ? Ss 0:00 nmbd -D
1042 ? Ss 0:01 /frontview/bin/monitor_enclosure
1168 ttyS1 Ss+ 0:00 /sbin/getty -L ttyS1 9600 vt100
1173 ? S 2:26 /usr/sbin/apache-ssl -f /etc/frontview/apache/httpd.c
1340 ? Ss 0:09 sshd: root@pts/0
1342 pts/0 Ss 0:00 -bash
1716 ? Ss 0:05 sshd: root@notty
1739 ? Ss 0:00 -bash
2695 ? Ss 0:05 sshd: root@notty
2697 ? Ss 0:00 -bash
4388 pts/0 R+ 0:00 ps ax

Thanks for all your help
Steven

[WhoCares?]

As you can see from the output, the major iSCSI daemon ietd is runing whereas the target daemons aren't. The log files to consult are stored in the /var/log directory. The most likely candidates to look for information in are system.log ans messages.

-Stefan

[sjk34]

Sep 1 02:22:57 backup kernel: iSCSI Enterprise Target Software - version 1.4.20.2
Sep 1 02:22:57 backup kernel: iscsi_trgt: Registered io type fileio
Sep 1 02:22:57 backup kernel: iscsi_trgt: Registered io type blockio
Sep 1 02:22:57 backup kernel: iscsi_trgt: Registered io type nullio
Sep 1 02:22:57 backup ietd: unable to create server socket (Address family not supported by protocol) 10 1 6!

Also noticed this but I don't think it is the cause.
Sep 1 02:26:31 backup ietd: unable to lock pid file: Resource temporarily unavailable
I think this might be where it tells me where the error is, i'm not 100% sure, I can paste the rest of the logs from roughly when ISCI was installed if needed?

Thanks
Steven

Thanks

[WhoCares?]

No need for the complete logs. What I'd like to see though is the whole config file and I also need to know the location of it. As it seems the iSCSI target deamon doesn't find any configuration at all.

-Stefan

[sjk34]

Target iqn.2001-04.com.example:readyduo.iscsi.target0
# Users, who can access this target. The same rules as for discovery
# users apply here.
# Leave them alone if you don't want to use authentication.
#IncomingUser joe secret
#OutgoingUser jim 12charpasswd
# Logical Unit definition
# You must define one logical unit at least.
# Block devices, regular files, LVM, and RAID can be offered
# to the initiators as a block device.
Lun 0 Path=/c/iscsi_0,Type=fileio
# Alias name for this target
# Alias SunStorage
# various iSCSI parameters
# (not all are used right now, see also iSCSI spec for details)
# MaxConnections 8
# InitialR2T No
# ImmediateData Yes
#MaxRecvDataSegmentLength 8192
#MaxXmitDataSegmentLength 8192
#MaxBurstLength 262144
#FirstBurstLength 65536
#DefaultTime2Wait 2
#DefaultTime2Retain 20
#MaxOutstandingR2T 8
#DataPDUInOrder Yes
#DataSequenceInOrder Yes
#ErrorRecoveryLevel 0
# HeaderDigest CRC32C,None
# DataDigest CRC32C,None
# various target parameters
#Wthreads 8

/etc/iet/ited.conf is the location the file. I did download the file using Wget but it doesn't appear to exist anymore so i copyed and pasted the information from the guide using WinSCP

Thanks
Steven

[WhoCares?]

Ok, the config file lokks good and the location is ok as well. What's the output of

Code: Select all

ls -al /c

? Also, did you try restarting the iSCSI stuff using

Code: Select all

/etc/init.d/rfw-iscsi-target restart

?

-Stefan

[sjk34]

ls -al /c output is:
drwxrwxrwx 8 root root 16384 Sep 1 01:32 .
drwxr-xr-x 23 root root 16384 Sep 1 02:23 ..
-rw------- 1 root root 7168 Sep 1 02:22 aquota.group
-rw------- 1 root root 8192 Sep 1 02:22 aquota.user
drwxrwxrwt 4 nobody nogroup 16384 Aug 31 07:40 backup
drwxrwxrwx 2 esx nogroup 16384 Aug 31 05:13 esx
drwxr-xr-x 3 admin admin 16384 Aug 19 04:04 home
-rw-r--r-- 1 root root 42949672960 Sep 1 03:07 iscsi_0
drwx------ 2 root root 16384 Aug 19 04:01 lost+found
drwxrwxrwt 6 nobody nogroup 16384 Aug 19 04:02 media
drwxr-xr-x 2 ReadyNAS root 16384 Aug 19 04:04 .timemachine

Two of them are shares.

Yep I've tryed that and starting and stopping it.

Thanks
Steven

[WhoCares?]

Hmm, looking good as well. Can you try restarting the ReadyNAS and see whether that helps?

-Stefan

[sjk34]

..........okay now im realy confused, its appeared now but I've done that before and it hadn't appeared.
Thanks for all your help, hopefully won't have too many issues now with it

Steven

[WhoCares?]

Chances are that there was a stale pid file lying around which made the iSCSI daemon start script believe that there was already an instance up and running and thus it didn't really restart where it should have. A reboot cleans out alk the stale pid files so maybe that was all that was needed.

-Stefan