https://bugzilla.novell.com/show_bug.cgi?id=465187
User erik@brakkee.org added comment
https://bugzilla.novell.com/show_bug.cgi?id=465187#c6
Erik Brakkee changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |erik@brakkee.org
--- Comment #6 from Erik Brakkee 2009-01-24 16:44:08 MST ---
Please have a look at
http://forums.opensuse.org/install-boot-login/405745-iscsi-initrd-11-1-a.htm...
I got iscsi boot to work and had to make several modifications.
Basically the issues were:
1. /lib/mkinitrd/scripts/boot-iscsi.sh:
the issue reported in this bug. This can be solved by explicitly connecting
to
the configured iscsi target
2. /lib/mkinitrd/scripts/boot-iscsi.sh:
The directory /etc/iscsi must exist before the initiatorname.iscsi file
is created
3. the /etc/init.d/boot.open-iscsi script appears to be enabled by default but
this interferes with the already setup iscsi connection.
Other problems are that the network card that is already setup through the
initrd should not be setup again by the network scripts. Currently solving this
by setting it to On NFS Root and specifying No IP. Perhaps at least the GUI of
Yast2 could have a separate option indicating that the card is already setup by
initrd.
In the end an 'ideal' yast2 gui would probably allow the user to indicate that
a network device is to be setup by initrd (for iscsi and nfs root filesystems).
And as a result of that, that network interface would be ignored by
/etc/init.d/network. More advanced would be to allow to specify an iscsi root
during installation of open suse.
--
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.