RE: [suse-autoinstall] SLES 9 SP3 Network Install Issue
OK, again I'm having problems with partitions, but this time during the
autoinstall:
I tell the server the path to my autoyasttest.xml and everything looks great
until it goes to partition/format/mount the drives. It's saying it cannot
format hda6, however it shouldn't even be looking at or creating an hda6.
One thing I noticed while using the Yast2 autoinstall option is that it doesn't
let you specifically say you want to wipe and use the entire drive for a new
install.
Here's the partitioning info in my autoyasttest.xml:
--------------------------------------
<partitioning config:type="list">
<drive>
<device>/dev/hda</device>
<initialize config:type="boolean">false</initialize>
<partitions config:type="list">
<partition>
<crypt>twofish256</crypt>
<filesystem config:type="symbol">swap</filesystem>
<format config:type="boolean">true</format>
Oh, and note that I've tried: <initialize config:type="boolean">true</initialize> as well as 'false' with the same results. Any help would be greatly appreciated. Thanks, Warren Quoting warren@leetnet.com:
OK, again I'm having problems with partitions, but this time during the autoinstall:
I tell the server the path to my autoyasttest.xml and everything looks great until it goes to partition/format/mount the drives. It's saying it cannot format hda6, however it shouldn't even be looking at or creating an hda6.
One thing I noticed while using the Yast2 autoinstall option is that it doesn't let you specifically say you want to wipe and use the entire drive for a new install.
Here's the partitioning info in my autoyasttest.xml:
--------------------------------------
<partitioning config:type="list"> <drive> <device>/dev/hda</device> <initialize config:type="boolean">false</initialize> <partitions config:type="list"> <partition> <crypt>twofish256</crypt> <filesystem config:type="symbol">swap</filesystem> <format config:type="boolean">true</format>
false <mount>swap</mount>130 <size>auto</size> </partition> <partition> <crypt>twofish256</crypt> <filesystem config:type="symbol">reiser</filesystem> <format config:type="boolean">true</format>false <mount>/boot</mount>131 <size>auto</size> </partition> <partition> <crypt>twofish256</crypt> <filesystem config:type="symbol">reiser</filesystem> <format config:type="boolean">true</format>false <mount>/</mount>131 primary <size>max</size> </partition> </partitions> <use>all</use> </drive> </partitioning>---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program.
-- To unsubscribe, e-mail: suse-autoinstall-unsubscribe@suse.com For additional commands, e-mail: suse-autoinstall-help@suse.com
---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program.
On Thursday 18 May 2006 16:39, warren@leetnet.com wrote:
I tell the server the path to my autoyasttest.xml and everything looks great until it goes to partition/format/mount the drives. It's saying it cannot format hda6, however it shouldn't even be looking at or creating an hda6.
it seems that you hit a bug in SLES9SP3
autoyast gets confused by the "max" on the primary partition.
Either remove the "max" and replace it by a size (like "10GB")
or remove the
Thank you for your help. This worked wonderfully. However, once the install is complete I have /dev/hda6 and /dev/hda7 as my /boot and / partitions. Not that it's a huge issue, but to keep things clean I would obviously like to have these on /dev/hda1 and /dev/hda2. Is this because it uses /dev/hdax during the installation and can't make/mount those while the install is running? One more thing: When using the AutoYast utility to include a postinstall script, it embeds the shell script in the xml file and has a blank <location> tag, and does not run. What's the recommended way to do this? I tried specifying the <location> of the script (full path + script name), however, this didn't work either. Thanks for your help! Warren On Thursday 18 May 2006 16:39, warren@leetnet.com wrote:
I tell the server the path to my autoyasttest.xml and everything looks great until it goes to partition/format/mount the drives. It's saying it cannot format hda6, however it shouldn't even be looking at or creating an hda6.
it seems that you hit a bug in SLES9SP3
autoyast gets confused by the "max" on the primary partition.
Either remove the "max" and replace it by a size (like "10GB") or remove the
On Friday 19 May 2006 01:46, Warren Crigger wrote:
Thank you for your help. This worked wonderfully. However, once the install is complete I have /dev/hda6 and /dev/hda7 as my /boot and / partitions. Not that it's a huge issue, but to keep things clean I would obviously like to have these on /dev/hda1 and /dev/hda2.
try to add
One more thing: When using the AutoYast utility to include a postinstall script, it embeds the shell script in the xml file and has a blank <location> tag, and does not run. What's the recommended way to do this?
the <location> element is only needed if you don't have the script in the autoyast profile itself. Autoyast will try to fetch the script from the <location> then. http://www.suse.com/~ug/autoyast_doc/createprofile.scripts.html#post-insall....
I tried specifying the <location> of the script (full path + script name), however, this didn't work either.
post scripts should work. Their use is very common. Maybe there is a syntax error in the script? After the installation, you can find a log about the scripts run in /var/adm/autoinstall/logs (I should add the to the documentation). Anyway, if you don't find a log there, look at /var/log/YaST2/y2log after the installation and search for your script name. Maybe you can see errors there. -- ciao, Uwe Gansert Uwe Gansert, Server Technologies Team SUSE LINUX Products GmbH, Maxfeldstrasse 5, D-90409 Nuernberg, Germany e-mail: uwe.gansert@suse.de, Tel: +49-(0)911-74053-0, Fax: +49-(0)911-74053-476, Web: http://www.suse.de
Thank you for your help. This worked wonderfully. However, once the install is complete I have /dev/hda6 and /dev/hda7 as my /boot and / partitions. Not that it's a huge issue, but to keep things clean I would obviously like to have these on /dev/hda1 and /dev/hda2.
try to add
primary to all partitions in the profile then.
If I do this, I lose my ability to use the max size for / partition because of the autoyast bug as discussed earlier. Is there any way around this? I haven't tested partition_nr yet with size max, would this work or would that hit the bug as well?
After the installation, you can find a log about the scripts run in /var/adm/autoinstall/logs (I should add the to the documentation).
Thanks for the great piece of info. I'm now able to find out where my script bails. It's during the make depend step of compiling ProFTPD 1.3, in which I get an error 127. If I don't run the postinstall script from autoyast, I can successfully run it once installation is complete with no problems. Any suggestions here? Again, thanks for your help and the great site documenting autoyast. Warren ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program.
On Tuesday 23 May 2006 17:52, warren@leetnet.com wrote:
try to add
primary to all partitions in the profile then.If I do this, I lose my ability to use the max size for / partition because of the autoyast bug as discussed earlier.
if you add
I haven't tested partition_nr yet with size max, would this work or would that hit the bug as well?
I don't think so but you can try the hint above (third position in profile with partition_nr=1).
After the installation, you can find a log about the scripts run in /var/adm/autoinstall/logs (I should add the to the documentation).
Thanks for the great piece of info. I'm now able to find out where my script bails. It's during the make depend step of compiling ProFTPD 1.3, in which I get an error 127. If I don't run the postinstall script from autoyast, I can successfully run it once installation is complete with no problems. Any suggestions here?
I have to admit, I never tried to compile software in a post-script. Have you tried to use an autoyast init-script instead of a post-script? That runs a lot later then the post-script (actually even later than the proftpd would start, that might be a problem in you case). -- ciao, Uwe Gansert Uwe Gansert, Server Technologies Team SUSE LINUX Products GmbH, Maxfeldstrasse 5, D-90409 Nuernberg, Germany e-mail: uwe.gansert@suse.de, Tel: +49-(0)911-74053-0, Fax: +49-(0)911-74053-476, Web: http://www.suse.de
I am having difficulty in getting my classes to merge together properly.
(i have to duplicate entries to get them read or, re-order them causing
other entries to be dropped, etc)
I have a rules.xml file that does a custom script to snarf cmdline opts that
define a SITE and a NODETYPE variable. From that, i get inclusion of 3 primary
profiles:
base.xml
site-@custom1@.xml
node-@custom2@.xml
Within each of these files are some classes options that pull in other files
from {conffiles}/classes/[Base|Site@custom1@|@custom2@]/
But, the resultant merged profile often has only partial data. and the y2log
file shows that it didn't even bother to notice some of the class inclusions
in the files above. (it does show that it processed the 3 primary .xml files).
E.G. I have:
<profile>
...
<install>
<classes config:type="list">
<class>
On Wednesday 24 May 2006 21:24, Stephen Dowdy wrote:
I am having difficulty in getting my classes to merge together properly. (i have to duplicate entries to get them read or, re-order them causing other entries to be dropped, etc) ... Are there known issues with the classing system for this version? If so, any useful workarounds or debugging features that would help?
please read: http://www.suse.de/~ug/autoyast_doc/merging.html -- ciao, Uwe Gansert Uwe Gansert, Server Technologies Team SUSE LINUX Products GmbH, Maxfeldstrasse 5, D-90409 Nuernberg, Germany e-mail: uwe.gansert@suse.de, Tel: +49-(0)911-74053-0, Fax: +49-(0)911-74053-476, Web: http://www.suse.de
participants (4)
-
Stephen Dowdy -
Uwe Gansert -
Warren Crigger -
warren＠leetnet.com