Hello all,
I am trying to setup an iscsi root disk; googled instructions that
suggests to make changes to init in the initrd; before doing so I
wanted to test the "iscsistart" CLI. I am able to connect to my
target when I start the iscsi daemon via the: service iscsi start.
However, I am unabl
thank you for the response ..
On Apr 8, 12:21 pm, Mike Christie <[EMAIL PROTECTED]> wrote:
>
> When you run iscsistart you cannot have iscsid running and you must load
> the modules by hand. So you have to do the modprobe iscsi_tcp that the
> init script would normally do for you.
>
in fact as
, Mike Christie <[EMAIL PROTECTED]> wrote:
> v i n c e wrote:
>
>
>
> > I'd like to find out if anyone has successfully performed the above by
> > inserting into an init script for initrd - for the purpose of booting
> > a diskless server on an iscsi-root?
> &g
Hello all,
I finally configured a proof-of-concept iSCSI target to export a root-
FS and have an iSCSI initiator PXE boot into the root image ... all
done in CentOS 5.1 for both target and root.
I have been trying to read the docs and mans for the target as well as
initiator configuration files,
Hello all,
I added edited my /etc/ietd.conf in my target and restarted - now it
has a different target-lun exported; I try to stop and start my iscsi-
initiator, and it is unable to "read" the NEW target, but seems like
there is some log it is reading and persistently wants to load the old
targe
t;[EMAIL PROTECTED]> wrote:
> v i n c e wrote:
>
>
>
> > Hello all,
>
> > I added edited my /etc/ietd.conf in my target and restarted - now it
> > has a different target-lun exported; I try to stop and start my iscsi-
> > initiator, and it is unable to "
Hello all,
Wanted to check if my initiators are connecting to the targets that I
have passed on to them (pxebooting to iSCSI root).
i noticed the following:
1. cat /proc/net/iet/volume ---> seems to disply what volumes have
been "exported" via the /etc/ietd.conf - is this correct?
cat /proc
Hello again,
Trying to remake an iSCSI root; I noticed in my golden-initiator-
workstation, when I start iscsi initiator (service iscsi start), the
following ib_iser related error messages are logged in dmesg:
Loading iSCSI transport class v2.0-865.
iscsi: registered transport (tcp)
ib_iser: di
Hello ...
I noticed that when I start iscsi ( service iscsi start) - I observed
some errors from "ib_user" ... seems like a bunch of them appear in
dmesg:
ib_iser: disagrees about version of symbol iscsi_conn_setup
ib_iser: Unknown symbol iscsi_conn_setup
ib_iser: disagrees about version of symb