open-iscsi vs. initiator-tools ... in Gentoo
aspasia
I am just curious, I installed the open-iscsi (emerge sys-block/open-
iscsi).... various iscsi binaries are installed:
r04s23 scsi # iscsiadm -V
iscsiadm version 2.0-868
r04s23 scsi # iscsistart -v
iscsistart version 2.0-868
r04s23 scsi #
seems like it's ok ... then I try to start the daemon - /etc/init.d/
iscsi start and it seems like unlike other distros a startup script
was not automatically created i did which:
which iscsid
/usr/sbin/iscsid
r04s23 scsi #
The binary seems to be there ... running it does not seem to work -
and I did not see any of the modules installed ...
So I emerged search and noticed the following:
emerge --search iscsi
Searching...
[ Results for search key : iscsi ]
[ Applications found : 3 ]
* sys-block/iscsi-initiator-core-tools [ Masked ]
Latest version available: 2.3
Latest version installed: [ Not Installed ]
Size of files: 50 kB
Homepage: http://iscsi-initiator-core.org/
Description: iscsi-initiator-core is a full featured iSCSI
Initiator stack.
License: GPL-2
* sys-block/iscsitarget
Latest version available: 0.4.15-r1
Latest version installed: [ Not Installed ]
Size of files: 100 kB
Homepage: http://iscsitarget.sourceforge.net/
Description: Open Source iSCSI target with professional
features
License: GPL-2
* sys-block/open-iscsi
Latest version available: 2.0.868_rc1
Latest version installed: 2.0.868_rc1
Size of files: 269 kB
Homepage: http://www.open-iscsi.org/
Description: Open-iSCSI is a high performance, transport
independent, multi-platform implementation of RFC3720
License: GPL-2
.....
seems like the initiator-tools is not installed - so what is the
difference between the initiator-tools and open-iscsi? I thought
the latter is a superset?
Finally, wouldn't the installation of these automatically also include
the necessary modules? I do not see them in the usual /lib/modules/
<version>/<kernel>/drivers/scsi ??
thanks in advance,
Aspasia
Please advise.
Shaun Meyer
> then I try to start the daemon - /etc/init.d/
> iscsi start and it seems like unlike other distros a startup script
> was not automatically created i did which:
Don't you mean /etc/init.d/iscsid ?
--
Shaun
a s p a s i a
YES! ... sorry ...
yes, /etc/init.d/iscsid or (in other flavors the script is -
/etc/rc.d/open-iscsi) ... does not seem to exist.
I also noticed the iscsi modules have not been installed.
Do I need to install the initiator-tools also?
- a.
Shaun Meyer
>
> > Don't you mean /etc/init.d/iscsid ?
>
> YES! ... sorry ...
>
> yes, /etc/init.d/iscsid or (in other flavors the script is -
> /etc/rc.d/open-iscsi) ... does not seem to exist.
I'm not sure how or where you got this alternative ebuild from but you
can install the init.d file as per my other emails.
> I also noticed the iscsi modules have not been installed.
> Do I need to install the initiator-tools also?
No. At least, I don't have them installed and it is working.
> - a.
>
>
>
> >
>
--
Shaun
a s p a s i a
On Tue, May 6, 2008 at 2:31 PM, Shaun Meyer <shaun...@gmail.com> wrote:
>
1. I downloaded the tarball and compiled from temp.
2. I copied the initd.debian sample startup script into the
/etc/init.d/open-iscsi (is what I called it) and ensured it's chmod'ed
to +x
3. Ensured to edit the script to fit my environment: (paths, the
/etc/init.d/functions.sh, .... etc.)
4. I still had issues in starting the daemon or even connecting to a
disk; with debugging turned on, I noticed the following error:
iscsistart: initiator reported error (9 - internal error)
Which the /var/log/messages explicitly informed me that:
May 6 08:50:30 localhost session4: couldn't create a new
connection.<6>scsi12 : iSCSI Initiator over TCP/IP
May 6 08:50:30 localhost connection5:0: Could not create connection
due to crc32c loading error. Make sure the crc32c module is built as a
module or into the kernel
5. I know I did load the crc32c module in my make menuconfig,
HOWEVER, I did not update the automodules file, so I did the following
(for future reboots):
echo "crc32c" >> /etc/modules.autoload.d/kernel-2.6
and also just did a modprobe -q crc32c ....
6. Upon re-starting the iscsiadm command, I was able to login and
connect to disk!
thanks a lot!
- a.
--
A S P A S I A
. . . . . . . . . . ..