Re: Help: Driver not found Problem

2009-11-12 Thread bjornnoss



On 11 Nov, 17:24, Mike Christie  wrote:
> Could you tell me when you run make install or depmod -a does a file in
> /lib/modules/$your_kernel/modules.dep get updated or created? In that
> file do you see some info for libiscsi_tcp? When you reboot your system
> is the file still there?

It works fine after reboot, so any changes the first depmod -a did is
still there.
And if a now (when its working) run depmod -a again, all the
timestamps on the files i the /lib/modules/$your_kernel/ dir is
updated, but the filesizes is the same.
Output of cat modules.dep | grep -B 2 -A 2 iscsi_tcp :
/lib/modules/2.6.26-2-openvz-amd64/kernel/drivers/scsi/qla1280.ko: /
lib/modules/2.6.26-2-openvz-amd64/kernel/drivers/scsi/scsi_mod.ko
/lib/modules/2.6.26-2-openvz-amd64/kernel/drivers/scsi/ips.ko: /lib/
modules/2.6.26-2-openvz-amd64/kernel/drivers/scsi/scsi_mod.ko
/lib/modules/2.6.26-2-openvz-amd64/kernel/drivers/scsi/iscsi_tcp.ko: /
lib/modules/2.6.26-2-openvz-amd64/kernel/drivers/scsi/libiscsi.ko /lib/
modules/2.6.26-2-openvz-amd64/kernel/drivers/scsi/
scsi_transport_iscsi.ko /lib/modules/2.6.26-2-openvz-amd64/kernel/
drivers/scsi/scsi_mod.ko
/lib/modules/2.6.26-2-openvz-amd64/kernel/drivers/scsi/mvsas.ko: /lib/
modules/2.6.26-2-openvz-amd64/kernel/drivers/scsi/libsas/libsas.ko /
lib/modules/2.6.26-2-openvz-amd64/kernel/drivers/ata/libata.ko /lib/
modules/2.6.26-2-openvz-amd64/kernel/drivers/acpi/dock.ko /lib/modules/
2.6.26-2-openvz-amd64/kernel/drivers/base/firmware_class.ko /lib/
modules/2.6.26-2-openvz-amd64/kernel/drivers/scsi/
scsi_transport_sas.ko /lib/modules/2.6.26-2-openvz-amd64/kernel/
drivers/scsi/scsi_mod.ko
/lib/modules/2.6.26-2-openvz-amd64/kernel/drivers/scsi/BusLogic.ko: /
lib/modules/2.6.26-2-openvz-amd64/kernel/drivers/scsi/scsi_mod.ko

does this help?
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"open-iscsi" group.
To post to this group, send email to open-iscsi@googlegroups.com
To unsubscribe from this group, send email to 
open-iscsi+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/open-iscsi
-~--~~~~--~~--~--~---



Re: Help: Driver not found Problem

2009-11-11 Thread Mike Christie

bjornnoss wrote:
> Why did it not work the first time, and do have have to issue the
> depmod -a command after every reboot of the system before modprobe
> iscsi_tcp witch is done in the open-iscsi startup script? Any other
> things a have to be awere of befause of this?
> 

Not sure yet. I cannot replicate it here and no one follows up :)

In fedora at least, when I run make install I get this:
make[2]: Entering directory `/usr/src/kernels/2.6.27.25-78.2.56.fc9.i686'
   INSTALL 
/home/mnc/kernel/iscsi/open-iscsi/git/open-iscsi/open-iscsi-2.0-871.1/kernel/iscsi_tcp.ko
   INSTALL 
/home/mnc/kernel/iscsi/open-iscsi/git/open-iscsi/open-iscsi-2.0-871.1/kernel/libiscsi.ko
   INSTALL 
/home/mnc/kernel/iscsi/open-iscsi/git/open-iscsi/open-iscsi-2.0-871.1/kernel/libiscsi_tcp.ko
   INSTALL 
/home/mnc/kernel/iscsi/open-iscsi/git/open-iscsi/open-iscsi-2.0-871.1/kernel/scsi_transport_iscsi.ko
   DEPMOD  2.6.27.25-78.2.56.fc9.i686


and the depmod step above will edit 
/lib/modules/$kernel_version/modules.dep
So when I do modprobe iscsi_tcp (or when the init script does it) it 
loads fine.

Maybe it is due to a diff in fedora and debian.

Could you tell me when you run make install or depmod -a does a file in 
/lib/modules/$your_kernel/modules.dep get updated or created? In that 
file do you see some info for libiscsi_tcp? When you reboot your system 
is the file still there?

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"open-iscsi" group.
To post to this group, send email to open-iscsi@googlegroups.com
To unsubscribe from this group, send email to 
open-iscsi+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/open-iscsi
-~--~~~~--~~--~--~---



Re: Help: Driver not found Problem

2009-11-11 Thread bjornnoss



On 29 Okt, 19:01, Mike Christie  wrote:
> Lee Amy wrote:
>
> > It builds well but when I want to load the module it always shows the
> > error messages I pasted.
>
> > Could you tell me how to deal with it?
>
> I am still trying to figure that out :)
>
> If after you do make install if you do a
>
> depmod -a
>
> then try modprobe iscsi_tcp does that load all the modules
> iscsi_tcp
> libiscsi_tcp
> libiscsi
> scsi_transport_iscsi
>
> ?

Hi, I had the exact same problem as Eric and I tried to do: depmod -a;
modprobe iscsi_tcp and it seems to work:
lsmod | grep iscsi_tcp
iscsi_tcp  17036  0
libiscsi_tcp   22148  1 iscsi_tcp
libiscsi   45712  2 iscsi_tcp,libiscsi_tcp
scsi_transport_iscsi36512  3 iscsi_tcp,libiscsi
scsi_mod  161016  10
iscsi_tcp,libiscsi,scsi_transport_iscsi,sg,sr_mod,usb_storage,ses,sd_mod,libata,megaraid_sas

So thank you...

Why did it not work the first time, and do have have to issue the
depmod -a command after every reboot of the system before modprobe
iscsi_tcp witch is done in the open-iscsi startup script? Any other
things a have to be awere of befause of this?

Enviroment: Debian Lenny x64
iSCSI: Dell PowerVault MD3000i

-bjornoss
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"open-iscsi" group.
To post to this group, send email to open-iscsi@googlegroups.com
To unsubscribe from this group, send email to 
open-iscsi+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/open-iscsi
-~--~~~~--~~--~--~---



Re: Help: Driver not found Problem

2009-10-29 Thread Mike Christie

Lee Amy wrote:
> 
> It builds well but when I want to load the module it always shows the
> error messages I pasted.
> 
> Could you tell me how to deal with it?
> 

I am still trying to figure that out :)

If after you do make install if you do a

depmod -a

then try modprobe iscsi_tcp does that load all the modules
iscsi_tcp
libiscsi_tcp
libiscsi
scsi_transport_iscsi

?

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"open-iscsi" group.
To post to this group, send email to open-iscsi@googlegroups.com
To unsubscribe from this group, send email to 
open-iscsi+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/open-iscsi
-~--~~~~--~~--~--~---



Re: Help: Driver not found Problem

2009-10-28 Thread Lee Amy

On Wed, Oct 28, 2009 at 9:22 AM, Lee Amy  wrote:
> On Wed, Oct 28, 2009 at 6:13 AM, Mike Christie  wrote:
>>
>> Eric Lee wrote:
>>> Hi,
>>>
>>> I encountered such errors when login the target. The target was
>>> implemented by using iET.
>>>
>>> #iscsiadm -m node -l
>>> Logging in to [iface: default, target:
>>> iqn.2009-10.master:storage.disk1.sys1.xyz, portal:
>>> 192.168.140.136,3260]
>>> iscsiadm: Could not login to [iface: default, target:
>>> iqn.2009-10.master:storage.disk1.sys1.xyz, portal:
>>> 192.168.140.136,3260]:
>>> iscsiadm: initiator reported error (12 - iSCSI driver not found.
>>> Please make sure it is loaded, and retry the operation)
>>>
>>> Then I notice that the system does not load iscsi_tcp module. So I'm
>>> trying to load this module.
>>> #modprobe iscsi_tcp
>>> iscsi_tcp: Unknown symbol iscsi_tcp_segment_done
>>> iscsi_tcp: Unknown symbol iscsi_segment_seek_sg
>>> iscsi_tcp: Unknown symbol iscsi_tcp_segment_unmap
>>> iscsi_tcp: Unknown symbol iscsi_tcp_hdr_recv_prep
>>> iscsi_tcp: Unknown symbol iscsi_tcp_cleanup_task
>>> iscsi_tcp: Unknown symbol iscsi_tcp_conn_setup
>>> iscsi_tcp: Unknown symbol iscsi_tcp_r2tpool_alloc
>>> iscsi_tcp: Unknown symbol iscsi_tcp_r2tpool_free
>>> iscsi_tcp: Unknown symbol iscsi_tcp_task_xmit
>>> iscsi_tcp: Unknown symbol iscsi_tcp_recv_skb
>>> iscsi_tcp: Unknown symbol iscsi_segment_init_linear
>>> iscsi_tcp: Unknown symbol iscsi_tcp_conn_get_stats
>>> iscsi_tcp: Unknown symbol iscsi_tcp_task_init
>>> iscsi_tcp: Unknown symbol iscsi_tcp_dgst_header
>>> iscsi_tcp: Unknown symbol iscsi_tcp_conn_teardown
>>> FATAL: Error inserting iscsi_tcp
>>> (/lib/modules/2.6.18-128.el5/kernel/drivers/scsi/iscsi_tcp.ko):
>>> Unknown symbol in module, or unknown parameter (see dmesg)
>>>
>>> So obviously I cannot load the module properly. So I don't know how to
>>> fix that.
>>>
>>> My OS is Cent OS 5.3 32bits. The kernel source codes are provided by
>>> distributor.
>>>
>>> Could anyone tell me how to fix that problem?
>>>
>>
>> You are missing libiscsi_tcp. Are you running the kernel modules from
>> the open-iscsi.org tarball or from a kernel you built?
>>
>> >>
>>
> Mike,
>
> I downloaded the tarball from open-iscsi.org then build from source
> and install. It runs well when build.
>
> Thanks.
>
> Eric
>

Hi,

It builds well but when I want to load the module it always shows the
error messages I pasted.

Could you tell me how to deal with it?

Thanks.

Eric

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"open-iscsi" group.
To post to this group, send email to open-iscsi@googlegroups.com
To unsubscribe from this group, send email to 
open-iscsi+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/open-iscsi
-~--~~~~--~~--~--~---



Re: Help: Driver not found Problem

2009-10-27 Thread Lee Amy

On Wed, Oct 28, 2009 at 6:13 AM, Mike Christie  wrote:
>
> Eric Lee wrote:
>> Hi,
>>
>> I encountered such errors when login the target. The target was
>> implemented by using iET.
>>
>> #iscsiadm -m node -l
>> Logging in to [iface: default, target:
>> iqn.2009-10.master:storage.disk1.sys1.xyz, portal:
>> 192.168.140.136,3260]
>> iscsiadm: Could not login to [iface: default, target:
>> iqn.2009-10.master:storage.disk1.sys1.xyz, portal:
>> 192.168.140.136,3260]:
>> iscsiadm: initiator reported error (12 - iSCSI driver not found.
>> Please make sure it is loaded, and retry the operation)
>>
>> Then I notice that the system does not load iscsi_tcp module. So I'm
>> trying to load this module.
>> #modprobe iscsi_tcp
>> iscsi_tcp: Unknown symbol iscsi_tcp_segment_done
>> iscsi_tcp: Unknown symbol iscsi_segment_seek_sg
>> iscsi_tcp: Unknown symbol iscsi_tcp_segment_unmap
>> iscsi_tcp: Unknown symbol iscsi_tcp_hdr_recv_prep
>> iscsi_tcp: Unknown symbol iscsi_tcp_cleanup_task
>> iscsi_tcp: Unknown symbol iscsi_tcp_conn_setup
>> iscsi_tcp: Unknown symbol iscsi_tcp_r2tpool_alloc
>> iscsi_tcp: Unknown symbol iscsi_tcp_r2tpool_free
>> iscsi_tcp: Unknown symbol iscsi_tcp_task_xmit
>> iscsi_tcp: Unknown symbol iscsi_tcp_recv_skb
>> iscsi_tcp: Unknown symbol iscsi_segment_init_linear
>> iscsi_tcp: Unknown symbol iscsi_tcp_conn_get_stats
>> iscsi_tcp: Unknown symbol iscsi_tcp_task_init
>> iscsi_tcp: Unknown symbol iscsi_tcp_dgst_header
>> iscsi_tcp: Unknown symbol iscsi_tcp_conn_teardown
>> FATAL: Error inserting iscsi_tcp
>> (/lib/modules/2.6.18-128.el5/kernel/drivers/scsi/iscsi_tcp.ko):
>> Unknown symbol in module, or unknown parameter (see dmesg)
>>
>> So obviously I cannot load the module properly. So I don't know how to
>> fix that.
>>
>> My OS is Cent OS 5.3 32bits. The kernel source codes are provided by
>> distributor.
>>
>> Could anyone tell me how to fix that problem?
>>
>
> You are missing libiscsi_tcp. Are you running the kernel modules from
> the open-iscsi.org tarball or from a kernel you built?
>
> >
>
Mike,

I downloaded the tarball from open-iscsi.org then build from source
and install. It runs well when build.

Thanks.

Eric

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"open-iscsi" group.
To post to this group, send email to open-iscsi@googlegroups.com
To unsubscribe from this group, send email to 
open-iscsi+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/open-iscsi
-~--~~~~--~~--~--~---



Re: Help: Driver not found Problem

2009-10-27 Thread Mike Christie

Eric Lee wrote:
> Hi,
> 
> I encountered such errors when login the target. The target was
> implemented by using iET.
> 
> #iscsiadm -m node -l
> Logging in to [iface: default, target:
> iqn.2009-10.master:storage.disk1.sys1.xyz, portal:
> 192.168.140.136,3260]
> iscsiadm: Could not login to [iface: default, target:
> iqn.2009-10.master:storage.disk1.sys1.xyz, portal:
> 192.168.140.136,3260]:
> iscsiadm: initiator reported error (12 - iSCSI driver not found.
> Please make sure it is loaded, and retry the operation)
> 
> Then I notice that the system does not load iscsi_tcp module. So I'm
> trying to load this module.
> #modprobe iscsi_tcp
> iscsi_tcp: Unknown symbol iscsi_tcp_segment_done
> iscsi_tcp: Unknown symbol iscsi_segment_seek_sg
> iscsi_tcp: Unknown symbol iscsi_tcp_segment_unmap
> iscsi_tcp: Unknown symbol iscsi_tcp_hdr_recv_prep
> iscsi_tcp: Unknown symbol iscsi_tcp_cleanup_task
> iscsi_tcp: Unknown symbol iscsi_tcp_conn_setup
> iscsi_tcp: Unknown symbol iscsi_tcp_r2tpool_alloc
> iscsi_tcp: Unknown symbol iscsi_tcp_r2tpool_free
> iscsi_tcp: Unknown symbol iscsi_tcp_task_xmit
> iscsi_tcp: Unknown symbol iscsi_tcp_recv_skb
> iscsi_tcp: Unknown symbol iscsi_segment_init_linear
> iscsi_tcp: Unknown symbol iscsi_tcp_conn_get_stats
> iscsi_tcp: Unknown symbol iscsi_tcp_task_init
> iscsi_tcp: Unknown symbol iscsi_tcp_dgst_header
> iscsi_tcp: Unknown symbol iscsi_tcp_conn_teardown
> FATAL: Error inserting iscsi_tcp
> (/lib/modules/2.6.18-128.el5/kernel/drivers/scsi/iscsi_tcp.ko):
> Unknown symbol in module, or unknown parameter (see dmesg)
> 
> So obviously I cannot load the module properly. So I don't know how to
> fix that.
> 
> My OS is Cent OS 5.3 32bits. The kernel source codes are provided by
> distributor.
> 
> Could anyone tell me how to fix that problem?
> 

You are missing libiscsi_tcp. Are you running the kernel modules from 
the open-iscsi.org tarball or from a kernel you built?

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"open-iscsi" group.
To post to this group, send email to open-iscsi@googlegroups.com
To unsubscribe from this group, send email to 
open-iscsi+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/open-iscsi
-~--~~~~--~~--~--~---