RE: [suse-autoinstall] iscsi install/boot questions/issues for SLES10-beta8

Hi Yall:
How do you get hold of sles10 x86_64 , I have only the 32bit version , I
need to compile a cross compiler for it and need a copy of the OS to
endorse my cross compiler.

Richard Lee , (408)957-1590
[email protected]
Software Engineer , HostRAID Driver
Adaptec Inc. Milpitas, CA
(408)957-1590
http://richnote01.corp.adaptec.com/
-----Original Message-----
From: Aggarwal, VikasX [mailto:[email protected]]=20
Sent: Wednesday, March 22, 2006 1:51 PM
To: [email protected]; [email protected];
[email protected]; [email protected]
Cc: [email protected]; Kumar, Dinesh
Subject: [suse-autoinstall] iscsi install/boot questions/issues for
SLES10-beta8

Hi all

   I am trying  SLES10-beta8 installation to  iscsi-target.

 =20

  When booted from SLES-10-beta8  installation Disk1,  I could not goto
some iscsi-GUI to give iscsi-target IP and initiatorname. Is there a
iscsi-configuration-GUI/Menu  available for the user during the install
time?

To  be able to try installation to iscsi-target, I went to
command-prompt(ctrl+alt+f2) and loaded drivers(iscsi_tcp, e1000),
assigned static IP address, start iscsid, run iscsiadm -discovery +
iscsiadm -login.  I could connect to the iscsi-target  and had the
remote disk in the installation-partition menu.  Main issue appears
after the installation is started and is in the middle. The machine will
freeze, can't do anything. I tried several times , and it always will
freeze before being able to finish the installation.  Is it the
open-iscsi driver issue(version 0.5.473-11)?  Or is there something I
need to configure properly to be able to install to iscsi-target? I am
just doing a minimal base system install.

=20

Also I noticed through local-install that there is an open-iscsi support
in /sbin/mkinitrd of SLES10-beta8. Will installer automatically create
iscsi enabled initrd image, once it knows installation was made to iscsi
target?

=20

Thanks in advance

-vikas aggarwal


-- 
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]