RE: [suse-autoinstall] YaST2 not starting from inst-sys
Thanks Volkmar. I tried replacing the root image using mkcramfs and I was successful to a certain degree. Now my problem is that I'm unable to partition the hard drive. YaST2 complains that the hard drive's partition table is unsupported. I've seen this error before and it was due to YaST trying to create all partitions as primary. See http://www.suse.de/~nashif/autoinstall/bugs.html#AEN60. That's why I wanted to use the inst-sys directory, so that I could use the updated package. Using the updated package has worked before on a standard IDE hard drive, but now I'm using two SCSI drives with RAID support and can't get the auto-partitioning to work. Has anyone had any success using autoyast with this type of configuration? Any hints? Thanks, Robert
-----Original Message----- From: Volkmar Glauche [mailto:glauche@uke.uni-hamburg.de] Sent: Sunday, July 07, 2002 11:11 AM To: Robert Alonso Cc: suse-autoinstall@suse.com Subject: Re: [suse-autoinstall] YaST2 not starting from inst-sys
On Fri, 5 Jul 2002 ralonso@lis.state.oh.us wrote:
Hi all,
For some reason, the root image (<path to suse installation>/suse/images/root) is still being read instead of inst-sys (<path to suse installation>/suse/inst-sys). I needed the inst-sys directory so that I could run the updated version yast2-module-autoinst. I did this according to the directions at http://www.suse.de/~nashif/autoinstall/bugs.html#AEN110. This worked successfully when I tested installation of my workstation. YaST2 started from inst-sys. But now I'm trying to do the installation onto another machine, and it keeps trying to read the the root image instead of inst-sys. Any idea why the behavior differs between these two machines?
I did not get the installation booting from the inst-sys directory at all. However, I did not find it very difficult to mkcramfs the updated installation directory to create a new root image. So I replaced the original image with the updated one and everything worked fine.
Volkmar
-- Volkmar Glauche
Department of Neurology E-Mail glauche@uke.uni-hamburg.de UKE Hamburg WWW http://glauche.home.pages.de/ Martinistr. 52 Phone 49(0)40-42803-5781 20246 Hamburg Fax 49(0)40-42803-9955
-- To unsubscribe, e-mail: suse-autoinstall-unsubscribe@suse.com For additional commands, e-mail: suse-autoinstall-help@suse.com
On Mon, 8 Jul 2002 ralonso@lis.state.oh.us wrote:
Thanks Volkmar. I tried replacing the root image using mkcramfs and I was successful to a certain degree. Now my problem is that I'm unable to partition the hard drive. YaST2 complains that the hard drive's partition table is unsupported. I've seen this error before and it was due to YaST trying to create all partitions as primary. See http://www.suse.de/~nashif/autoinstall/bugs.html#AEN60. That's why I wanted to use the inst-sys directory, so that I could use the updated package. Using the updated package has worked before on a standard IDE hard drive, but now I'm using two SCSI drives with RAID support and can't get the auto-partitioning to work.
Which RAID support do you use? If you want to create lvm volume groups from partitions on both drives, this will not work with even the newest available autoinstall module. I have got such a configuration on all workstations (15+) in our department and I am still waiting with the update until SuSE releases a working patch to the autoinstall module. I hope such a patch will be made available for 8.0 before the 8.1 release is shipped.
Has anyone had any success using autoyast with this type of configuration? Any hints?
Volkmar -- Volkmar Glauche Department of Neurology E-Mail glauche@uke.uni-hamburg.de UKE Hamburg WWW http://glauche.home.pages.de/ Martinistr. 52 Phone 49(0)40-42803-5781 20246 Hamburg Fax 49(0)40-42803-9955
participants (2)
-
ralonso＠lis.state.oh.us -
Volkmar Glauche