https://bugzilla.novell.com/show_bug.cgi?id=630434 https://bugzilla.novell.com/show_bug.cgi?id=630434#c48 --- Comment #48 from Lee Duncan <lduncan@novell.com> 2012-04-05 10:29:13 PDT --- (In reply to comment #45)
Well, I do not any longer have access to an iSCSI environment, but I would like to give the sources a review (I just cannot test in a live environment presently).
For SLES 12 SP2 GM??? I do believe, you mean SLES 11 SP2 GM, right?
My apologies: I was off-by-one. Yes, I meant SLES 11 SP2 GM. Note: I am trying to reproduce this problem to verify your suggested changes, and I am not having luck. Perhaps you can hep me. Here's what I'm doing: * Created an iSCSI target volume on a remote system * Set up my SLE 12 SP2 GM client with open-iscsi * Made sure client could connect to target * Created a filesystem on the target disc from the client (EXT3) * Set node.startup and node.conn[0].startup to "onboot" * Updated /etc/init.d/boot.open-iscsi and /etc/init.d/open-iscsi as you suggested * added your suggested initrd template and ran mkinitrd When I reboot, the /etc/init.d/boot.open-iscsi service finds no sessions, since it appears to not have logged into the target. And when I get up full running (after /etc/init.d/open-iscsi has ran), the session still is not present, i.e. no login has been attempted to my target! If I change the "startup" variables to "automatic" instead of "onboot", then I get automatic login to the target, so when I get to full multi-user mode, the disk is present (in my case, as /dev/sdc). So why is this not working when I set startup to "onboot", i.e. who/what is supposed to login to the target when its startup value is set to onboot? Is it initrd? Do I need to make changes to initrd itself? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.