Comment 6 for bug 227848

Having similar major problems utilizing iSCSI effectively with Heron. I have changed the Boot script order in rcS.d so iSCSI is now S44 instead of S25 ( starts iscsi AFTER networking ) and I now have iSCSI drives available to the system. However, it's proving difficult to get the boot order right for initiation and mounting of iSCSI drives to be automatic and effective as part of the boot process.
For example, if we want to hold service data on SAN iSCSI drives ( e.g. SAMBA file shares, LDAP or MySQL databases) we need to have the iSCSI drives fully mounted and available at the service startup scripts kick in. Currently with the default setup of iSCSI, this does not happen.
Continuing to investigate and experiment , but any further tips to effectively get iSCSI usable as a system drive would be appreciated.