Howdy!
You most likely got here by looking for the “iSCSI Target Support for ReadyNAS”. Unfortunately, your quest isn’t over yet, since the downloads have moved to a new location. This way it’s easier for me to release updates and, to be frank, it’s easier for you to find them.
I will still update this page whenever there’s a new release available.
Current iSCSI Releases for ReadyNAS:
- 1.4.20.1-readynas-1.0.3
This is the current release built from the “stable” branch of the iSCSI Enterprise Target Project
Pingback: iSCSI Target Support for ReadyNAS updated — WhoCares?
Pingback: ReadyNAS goes iSCSI — WhoCares?
Thanks a lot Stefan — I have iSCSItarget_0.4.17-readynas-1.0.1 running on RAIDiator 4.1.5 and nothing got bricked. ;-)
One small thing: the docs say, in step #7, to shut down the iscsi target after the line “… Rebooting”. I believe that should be after the closing fi of the if block.
Pingback: Jan-Piet Mens / iSCSI Support for ReadyNAS updated
You’re right of course. Netgear changed the
script with RAIDiator 4.1.4 and I completely forgot to update the docs. Thanks for the heads-up. The documentation in the Wiki is fixed now.
I’m really lost, i know nothing about ssh i’ve installed everything but the part about configuring the device or the file i cant. Please advise step by step for dummies…
Actually I was under the impression that the information given here for the .bin version was as close to a step by step guide than you can get.
I revised the documentation a bit now to make it clearer. Or at least I hope so. If that’s still not good enough I’d need more information about the specific problems you encounter.
Pingback: markwilson.it » Creating an iSCSI target on a Netgear ReadyNAS
I’ve got the service installed, LUN file created, config file in place, and service running seemingly happily. However when I attempt to connect to the target from an initatior there are no LUNs presented. I’ve capture the iscsi traffic in Wireshark and confirm good a successful login and the the initiator asks for all targets, but the response packet doesn’t list any targets. I’m guessing I’ve goofed somewhere, but I’m just not seeing it. Are there any logs anywhere that I could view to see what I’ve screwed up? :)
Have tried both 1.4.20.1 and 1.4.18 (when the more recent showed this problem). Current test lun file is 10GB.
There may be a problem with the location of the config files. Please check whether you have a working copy of ietd.conf in /etc/iet/ which is the new location where the daemon looks for it’s config.
The installer *should have* taken care of that but it seems that it doesn’t in all cases.
Logs should be available in the syslog or the kernel log, depending on the type of error the iSCSI daemon reports – if any.
I need to be able to have the same files visible on the readynas as on the iSCSI target.
So using a file container would not be an option (unless I locally mount the iSCSI virtual disk using an initiator on the NAS).
If instead of using a file container I use an LVM target, would this allow simultanious access to the filesystem from the NAS device and a remote initiator, without bricking the entire thing?
Firstly, awesome addon for the ReadyNAS, thanks heaps.
Just testing transfer speeds over the LAN to the ReadyNAS, CIFS vs iSCSI, and CIFS is beating the iSCSI target nearly two fold. :(
Does anyone know of any configuration options that can improve the performance of iSCSI?
Also, I second Jason’s question, can you target a device (I’m assuming by doing Lun *blah* Type=blockio)?
Well, yes, you can target a device – but you’d have to create that in the first place and I wouldn’t want to mess with the ReadyNAS that much. Also I would like to discourage the parallel use of the device used for the iSCSI target unless you add another file system layer like GFS or OCFS2 since iSCSI was never meant to handle that kind of abuse ;)
As for the tuning issue: you can try to play with the settings in ietd.conf. In addition tuning the TCP/IP stack on the ReadyNAS can be helpful. There’s not general rule what will help and what will make matters worse but there’s a lot of hints out the on Google.
I have been using iscsi 1.4.18 that i have had install and has worked fine for about 8 months now. about a week ago the iscsi volume started reporting disk errors in windows and therefor disabled VSS. The readyNas RND4000 reports all disks are fine. Any ideas as my iscsi volume is 2tb in size and would take a week to run a full scandisk
That the RND4000 reports all drives as fine unfortunately doesn’t say anything about the state of the iSCSI volume. Since the iSCSI volume essentially is just a file to the RND4000, chances are that the overall structure of the file itself is ok. However, the filesystem structure contained within that file may well be damaged without the RND4000 having any chance to detect that.
Such errors can only be detected by the machine connecting to and using the iSCSI target. So my advice would be to trust your Windows error message and at least run a simple check on the iSCSI volume from your Windows host.
Is it possible to use the iSCSI drive from the NAS (Duo) itself? Can the various pre-installed services under the standard web-admin see the disc and use it for streaming media? How about access control?
Thanks.
/Jørn
No, they can’t, at least not with this add-on. Wouldn’t make much sense anyway since an iSCSI device on the NAS itself is just a mere file on the main storage of the NAS itself. If you’re looking for a way to make the NAS use an external iSCSI disk, you might want to have a look at the open-iscsi add-on. Using this you can connect external iSCSI drives to the NAS and you should then be able to use them. I have to admit I haven’t tested this yet, so you’re on your own there.
Okay. I am asking because I want to backup my NAS using Mozy … but Mozy does not support network drives. I friend told me that a drive on my PC mounting an iSCSI drive would be backup-able by Mozy from my own PC. But that doesn’t help much if I can only backup stuff that the NAS cannot use.
Thanks for the reply.
/Jørn