|
|
Post by usernametaken on May 23, 2007 9:14:33 GMT 7
I'm trying to configure and install a module for iSCSI and have hit a snag. It has two drivers that need to go into /lib/modules/2.6.13N5200/kernel/drivers/scsi/ to work. This directory is read only. Does anyone know a way to make that dir read-write ?
|
|
|
|
Post by omega on May 23, 2007 17:02:10 GMT 7
Hi, welcome to this forum...  Basically there is no way to make that location r/w as it is mounted on an compressed (and unfortunately encrypted) image. Becuase it is encrypted we cannot just create a new one containing your two additional modules. To overcome this limitation I've written the DUPMOD module, but unfortunately this only mirrors everything below /img/... I fear it is impossible to use the same idea for /lib/... as this directory is used just from the very start. But why do you need them in that directory. To load the modules they can stay in any directory you want them to stay and after loading the modules you don't need 'em anyway..... !? Keep us informed.... I'm interested in what you're doing! Andreas |
|
|
|
Post by kniteowl on May 24, 2007 1:02:15 GMT 7
I hope you get it working, I am looking for this feature also. I started working on this a while back, but ran into the same snag and have not gone back yet.
depending on if you happen to get yours working or not, I may have to go back and look at my old notes and restart that project.
Keep us informed, hopefully you have luck, or we can come up with some help.
Just as a side note, I was testing with IET. There were rumors that Thecus might be looking at adding iSCSI in later, and the firmware looks like they may have been testing it already, but removed it out again for the release.
teng
|
|
|
|
Post by usernametaken on May 24, 2007 7:03:34 GMT 7
In theory I've got it worked out, but I can't manage to get it to install the modules. insmod gives errors, and dmesg shows unknown symbol errors. I think I'm gonna give up and hope Thecus add the support in sometime.
|
|
|
|
Post by omega on May 24, 2007 15:18:18 GMT 7
As long as you get unresolved symbols you initial issue not being able to place your modules in /lib/modules/.... is not really important - you need to fix the unresolved symbols first.
What source for the iSCSI drivers are you actually using? In what build environment did you build them?
Andreas
|
|
|
|
Post by usernametaken on May 25, 2007 7:01:33 GMT 7
I'm using open-iscsi-1.0-485 which is the only one I found with support for the 2.6.13 kernel.
I compiling on a CentOS 4.3 box, with the Thecus source on the local drive and using GCC 3.3.6.
compiling with 'make KSRC=/usr/local/src/thecus/kernel/linux'
Once done, I'm SCP'ing the kernel drivers to the thecus box, and running 'insmod /raid/data/tmp/iscsi_tcp.ko'
I don't suppose someone else wants to give it a go in case it's something in my environment ?
|
|
|
|
Post by kniteowl on May 25, 2007 12:58:53 GMT 7
OK, dumb question here, are you trying to setup a target or an initiator?  ? I had just assume that you were trying to setup the N5200 to share its drives out as an iSCSI device, in which case you needed the target, but if you are trying to compile open-iscsi, did I understand wrong, and you are actually trying to get the N5200 to connect to an iSCSI target to get more disk space??? Initator mode instead? Just trying to make sure that I understand what you are trying to do, as if you are trying to use the N5200 as an iSCSI device and share out its drives, you are using the wrong program, you need to use IET found at iscsitarget.sourceforge.net/ instead. Teng |
|
|
|
Post by usernametaken on May 25, 2007 16:37:29 GMT 7
Open ISCSI will also act as a target server. It's the only one I could fine with semi-easy support for the 2.6.13 kernel. I'd much rather be using the iscsitarget project, but it seemed harder to compile for the thecus kernel.
|
|
?