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 I read it - I also attempted the following: 1. Load modules "manually" and then start iscsistart - it starts successfully: [EMAIL PROTECTED] module]# insmod /lib/modules/2.6.18-53.1.14.el5/kernel/ drivers/scsi/scsi_mod.ko insmod: error inserting '/lib/modules/2.6.18-53.1.14.el5/kernel/ drivers/scsi/scsi_mod.ko': -1 File exists [EMAIL PROTECTED] module]# lsmod | grep scsi scsi_mod 186361 4 sg,usb_storage,libata,sd_mod [EMAIL PROTECTED] module]# lsmod | grep sd_mod sd_mod 56257 4 scsi_mod 186361 4 sg,usb_storage,libata,sd_mod [EMAIL PROTECTED] module]# insmod /lib/modules/2.6.18-53.1.14.el5/kernel/ drivers/scsi/scsi_transport_iscsi.ko [EMAIL PROTECTED] module]# insmod /lib/modules/2.6.18-53.1.14.el5/kernel/ drivers/scsi/libiscsi.ko [EMAIL PROTECTED] module]# insmod /lib/modules/2.6.18-53.1.14.el5/kernel/ drivers/scsi/iscsi_tcp.ko 2. Run iscsistart: iscsistart -i iqn.2005-03.com.max:01.7b62ec -t iqn. 2008-04.com.mycompany.lab:storage.rootdisk -g 1 -a 192.168.17.3 iscsistart: transport class version 2.0-724. iscsid version 2.0-865 iscsistart: version 2.0-865 iscsistart: connection1:0 is operational now -------------------------------------------- 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? Having gotten the above to work, I attempted to modify my init script so that I can boot to my iscsi target's root FS; sadly, I get an error when loading the first iscsi module: "insmod: error inserting '/lib/scsi_transport_iscsi.ko' -1 operation not permitted. module signed with unknown public key - signature key id fa719cfd42d5150 ver=3" Any thoughts? I'm wondering if I de-select the module-signature- verification option in my Centos 5.1 kernel (via make menuconfig) if it would address this issue. Pls let me know if my current issue is not applicable to this list, or if I should go an post in CentOS at this point? thanks again in advance, --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/open-iscsi -~----------~----~----~----~------~----~------~--~---
