From: Gordan B. <go...@bo...> - 2007-10-15 14:13:58
|
>>>>> I have attached a tar ball of files that I changed (or added) in the >>>>> standard setup to get iSCSI to work. >>>>> >>>>> Please let me know if I omitted anything. >>>>> >>>>> There is probably some pruning that could be done to this (I went for >>>>> including full RPMs + configs), which was arguably sub-optimal - there is >>>>> likely to be some docs/man pages included (not that anyone is likely to >>>>> notice next to 70MB of drivers :^). >>>>> >>>>> I also hard-removed (C)LVM stuff - something that you probably won't want >>>>> to merge into the main tree. >>>>> >>>>> Thanks for all the help over the last few days, and for accepting my >>>>> patches. I really appreciate it. This is by far the most postive OSS >>>>> experience I have had to date. :-) >>>>> >>>> Attached you'll find the latest rpm with iscsi included. >>>> Last thing you should have to have is either rootsource=iscsi as bootparam or >>>> in com_info <rootsource name="iscsi"/>. >>>> Also add to the /etc/comoonics/bootimage/files.initrd.d/user_edit.list >>>> the /var/lib/iscsi/nodes/iqn.2001-05.com.equallogic\:1-234567-89abcdef0-123456789abcdef0-ssi-root/10.10.10.1\,3260 >>>> >>>> Let me know if it works. >>> >>> It appears to be broken. The new initrd fails to fire up iSCSI. Where my >>> old hard-coded version would modprobe the required modules and start up >>> iscsid and iscsi, the new version doesn't. >>> >>> I added <rootsource name="iscsi"/> to the com_info section on every node. >>> >>> Did I miss something? >> >> I just added the rootsource=iscsi kernel boot option, and that doesn't fix >> it. Carefully looking at the screen log, the iSCSI TCP transport module >> does appear to get loaded, but the iscsid and iscsi services don't get >> started. > > Hmm... It looks like iSCSI is getting started correctly after all. It does > come up and brings up the block device. The problem is somewhere else. It > may be a good idea to not silence the iscsi startup, just for easier > overview of what happens and what doesn't (unless you particularly object > to a few green OKs among the blues). Something very weird is happening. With full debug enabled, configfs module is loaded, but mounting the configfs fails. :-/ Gordan |