RE: [suse-autoinstall] Help with installing multiple machines ove r network
Richard, Richard Hobbs wrote: [...]
I have multiple machines, all of which are identical, onto which I would like to install SuSE 10.
I have already installed one machine and got it setup the way I would like it, in terms of package selections, partitioning etc... And I would now like to replicate that across the remaining machines if possible.
I have read the first section of the SuSE 10 manual, entitled "Advanced Deployment Scenarios", but this only seems to document how to boot the system into the manual installation routine remotely. Ideally, I need to boot from the network and begin a fully automated install which duplicates every single aspect of the first system, except with a different hostname and IP (which I don't mind entering manually during the install if necessary).
Can this be done? I'm sure it can, but I can't find any guides or tutorials on how to do it, so if anyone can help, that would be very much appreciated
Yes, it can be done. Basically, you need two things: 1) The mechanism to boot from the network 2) The mechanism for the automatic installation ad 1) Regarding the boot from network, I'd recommend pxegrub: http://www.gnu.org/software/grub/manual/grub.html#Network Alternatively, you could also build a boot-CD, which contains bootloader, kernel and initrd and starts the network installation. However, this might not be your preferred way of installing the computers. ad 2) I'd recommend to use autoyast. The autoyast is the SuSE mechanism for automatic installation. Using "yast2 autoyast" you can generate an XML-File, which contains the entire configuration for the installation. To install using autoyast, you just need to boot the kernel load the Installation initrd (DVD:/boot/loader/initrd) and add the kernel-parameter install=nfs://<IP-Adressse>/<Pfad>/<XML-File> in your boot-loader configuration. Mailing-List: mailto:suse-autoinstall@suse.com Archive with search function: http://marc.theaimsgroup.com/?l=suse-autoinstall Documentation: http://www.suse.com/~ug/autoyast_doc Regards, Peter.
Hello, Thank you for your help, together with your hints, and the SuSE Advanced Deployment guide, I *almost* have a working installation routine! So far, I have created the following file structure in my TFTP server's directory: ============================================================ stg-backup:/install # ls -l /tftpboot/ total 8601 drwxr-xr-x 3 root root 208 Feb 2 16:26 . drwxr-xr-x 25 root root 808 Feb 2 16:19 .. -r--r--r-- 1 root root 7076988 Sep 14 12:05 initrd -r--r--r-- 1 root root 1606360 Sep 14 12:05 linux -r--r--r-- 1 root root 90292 Sep 14 12:05 memtest -r--r--r-- 1 root root 456 Sep 14 12:05 message -rw-r--r-- 1 root root 11822 Sep 9 16:39 pxelinux.0 drwxr-xr-x 2 root root 72 Feb 2 16:41 pxelinux.cfg stg-backup:/install # ls -l /tftpboot/pxelinux.cfg/ total 4 drwxr-xr-x 2 root root 72 Feb 2 16:41 . drwxr-xr-x 3 root root 208 Feb 2 16:26 .. -r--r--r-- 1 root root 813 Feb 2 16:41 default stg-backup:/install # ============================================================ The above files were copied from "DVD:/boot/loader/" and "/usr/share/syslinux/pxelinux.0" with "default" being copied from "DVD:/boot/loader/isolinux.cfg". I then edited "/tftpboot/pxelinux.cfg/drfault" so it contains the following: ============================================================ default harddisk # hard disk label harddisk kernel linux append SLX=0x202 showopts # install label linux kernel linux append initrd=initrd splash=silent showopts insmod=e1000 netdevice=eth0 install=nfs://192.168.3.230/install/dellrackmount.xml # noacpi label noacpi kernel linux append initrd=initrd splash=silent showopts acpi=off # failsafe label failsafe kernel linux append initrd=initrd splash=silent showopts apm=off acpi=off mce=off barrier=off ide=nodma idewait=50 i8042.nomux psmouse.proto=bare irqpoll insmod=e1000 netdevice=eth0 install=nfs://192.168.3.230/install/dellrackmount.xml # rescue label rescue kernel linux append initrd=initrd splash=silent rescue=1 showopts # memory test label memtest kernel memtest implicit 1 display message prompt 1 timeout 200 notice 6 ============================================================ The only changes I made to the original file were the following additions on the append lines for "linux" and "failsafe": insmod=e1000 netdevice=eth0 install=nfs://192.168.3.230/install/dellrackmount.xml They are actually Dell SC1425 servers, but I believe they have an Intel network card (I could be wrong) which is definitely gigabit. Also, that xml file on that NFS server definitely exists because I can mount it from other machines. However, I have two problems: 1. When the system first boots into the screen giving me the option to boot from "harddisk", "linux", "noacpi", "failsafe" etc... I get a warning that says: Unknown keyboard in config file. Missing parameter in config file. Nevertheless, I still have the option of chosing an option, so I type "linux" and hit return. It then boots up, and after a minute or two, a read box appears on screen stating: Could not find the Suse Linux Installation Source. Activating manual setup program. Does this mean I have chosen the incorrect network drivers? If so, how can I possibly start the manual setup program if it can't access the source? Or is the manual setup program part of what's been copied into the tftp sevrer? Thanks again for your help, it's most appreciated :-) Richard. -- Richard Hobbs (Systems Administrator) Toshiba Research Europe Ltd. - Speech Technology Group Web: http://www.toshiba-europe.com/research/ Normal Email: richard.hobbs@crl.toshiba.co.uk Mobile Email: mobile@mongeese.co.uk Tel: +44 1223 376964 Mobile: +44 7811 803377
-----Original Message----- From: Gunreben, Peter (Peter) [mailto:pgunreben@lucent.com] Sent: 02 February 2006 15:03 To: suse-autoinstall@suse.com Subject: RE: [suse-autoinstall] Help with installing multiple machines over network
Richard,
Richard Hobbs wrote:
[...]
I have multiple machines, all of which are identical, onto which I would like to install SuSE 10.
I have already installed one machine and got it setup the way I would like it, in terms of package selections, partitioning etc... And I would now like to replicate that across the remaining machines if possible.
I have read the first section of the SuSE 10 manual, entitled "Advanced Deployment Scenarios", but this only seems to document how to boot the system into the manual installation routine remotely. Ideally, I need to boot from the network and begin a fully automated install which duplicates every single aspect of the first system, except with a different hostname and IP (which I don't mind entering manually during the install if necessary).
Can this be done? I'm sure it can, but I can't find any guides or tutorials on how to do it, so if anyone can help, that would be very much appreciated
Yes, it can be done. Basically, you need two things: 1) The mechanism to boot from the network 2) The mechanism for the automatic installation
ad 1) Regarding the boot from network, I'd recommend pxegrub: http://www.gnu.org/software/grub/manual/grub.html#Network Alternatively, you could also build a boot-CD, which contains bootloader, kernel and initrd and starts the network installation. However, this might not be your preferred way of installing the computers.
ad 2) I'd recommend to use autoyast. The autoyast is the SuSE mechanism for automatic installation. Using "yast2 autoyast" you can generate an XML-File, which contains the entire configuration for the installation. To install using autoyast, you just need to boot the kernel load the Installation initrd (DVD:/boot/loader/initrd) and add the kernel-parameter install=nfs://<IP-Adressse>/<Pfad>/<XML-File> in your boot-loader configuration. Mailing-List: mailto:suse-autoinstall@suse.com Archive with search function: http://marc.theaimsgroup.com/?l=suse-autoinstall Documentation: http://www.suse.com/~ug/autoyast_doc
Regards, Peter.
-- To unsubscribe, e-mail: suse-autoinstall-unsubscribe@suse.com For additional commands, e-mail: suse-autoinstall-help@suse.com
_____________________________________________________________________ This e-mail has been scanned for viruses by MCI's Internet Managed Scanning Services - powered by MessageLabs. For further information visit http://www.mci.com
_____________________________________________________________________ This e-mail has been scanned for viruses by MCI's Internet Managed Scanning Services - powered by MessageLabs. For further information visit http://www.mci.com
On Thursday 02 February 2006 17:59, Richard Hobbs wrote:
The only changes I made to the original file were the following additions on the append lines for "linux" and "failsafe":
insmod=e1000 netdevice=eth0 install=nfs://192.168.3.230/install/dellrackmount.xml
that can't work. It's: "autoyast=nfs://192.168.3.230/install/dellrackmount.xml" install=... must point to the installation source in your network. For example: install=nfs://192.168.3.230/install_src_sl10 For automatic installations over the network you need the "install=..." and the "autoyast=..." parameter.
1. When the system first boots into the screen giving me the option to boot from "harddisk", "linux", "noacpi", "failsafe" etc... I get a warning that says:
Unknown keyboard in config file. Missing parameter in config file.
you can ignore that but maybe it helps if you remove the "implicit 1" and the "notice 6" line.
Nevertheless, I still have the option of chosing an option, so I type "linux" and hit return.
It then boots up, and after a minute or two, a read box appears on screen stating:
Could not find the Suse Linux Installation Source. Activating manual setup program.
that's because the install=... line is wrong. The installation source can't be found. Change the install=... line, so that it points to your installation source and add the "autoyast=nfs://192.168.3.230/install/dellrackmount.xml" line. -- 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
Hello,
Thanks again, I have now got a lot further, but I have another small
problem.
I generated the xml file from an existing machine, and during creation I
selected every single option except the DHCP server and the DNS server
(because this machine doesn't have either of them). I did this because I
need the new machines to be as close to the original as possible, so I hope
this was a good decision.
I have also added an <initialize> tag within each <drive> tag, just below
the <device> tag in order to remove the partition table on each disk before
starting, so I hope I have done this correctly as well:
============================================================
<drive>
<device>/dev/sda</device>
-----Original Message----- From: Uwe Gansert [mailto:ug@suse.de] Sent: 02 February 2006 17:18 To: suse-autoinstall@suse.com Subject: Re: [suse-autoinstall] Help with installing multiple machines over network
On Thursday 02 February 2006 17:59, Richard Hobbs wrote:
The only changes I made to the original file were the following additions on the append lines for "linux" and "failsafe":
insmod=e1000 netdevice=eth0 install=nfs://192.168.3.230/install/dellrackmount.xml
that can't work. It's: "autoyast=nfs://192.168.3.230/install/dellrackmount.xml" install=... must point to the installation source in your network. For example: install=nfs://192.168.3.230/install_src_sl10 For automatic installations over the network you need the "install=..." and the "autoyast=..." parameter.
1. When the system first boots into the screen giving me the option to boot from "harddisk", "linux", "noacpi", "failsafe" etc... I get a warning that says:
Unknown keyboard in config file. Missing parameter in config file.
you can ignore that but maybe it helps if you remove the "implicit 1" and the "notice 6" line.
Nevertheless, I still have the option of chosing an option, so I type "linux" and hit return.
It then boots up, and after a minute or two, a read box appears on screen stating:
Could not find the Suse Linux Installation Source. Activating manual setup program.
that's because the install=... line is wrong. The installation source can't be found. Change the install=... line, so that it points to your installation source and add the "autoyast=nfs://192.168.3.230/install/dellrackmount.xml" line.
-- 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
-- To unsubscribe, e-mail: suse-autoinstall-unsubscribe@suse.com For additional commands, e-mail: suse-autoinstall-help@suse.com
_____________________________________________________________________ This e-mail has been scanned for viruses by MCI's Internet Managed Scanning Services - powered by MessageLabs. For further information visit http://www.mci.com
_____________________________________________________________________ This e-mail has been scanned for viruses by MCI's Internet Managed Scanning Services - powered by MessageLabs. For further information visit http://www.mci.com
On Thursday 02 February 2006 18:41, Richard Hobbs wrote:
I have also added an <initialize> tag within each <drive> tag, just below the <device> tag in order to remove the partition table on each disk before starting, so I hope I have done this correctly as well:
============================================================ <drive> <device>/dev/sda</device>
true</initialize>
this is correct.
Finally, just after it's probed the mouse and done a few other things, I get a dialog box appearing which says:
System Profile Location: /existing/location/of/file.xml
I then have the option ot typing in a different XML file, but why is it prompting me for a different file?
that can happen in two cases. Either the profile can't be found where you have pointed to with the autoyast=... option, or the profile has a XML syntax error. Since you created the profile with the autoyast UI, a syntax error is not very likely as long as you did not change anything with a texteditor. So make sure that the profile really is where autoyast=... points to and that the machine can read it. On SUSE Linux 10.1 the error message in that case is a lot better but of course that does not help you at the moment :)
I have a feeling there's a MAC address in the xml file somewhere, so do I just need to replace the MAC address of the original machine with the MAC address of the new machine I'm trying to build?
maybe it's a good idea to replace the MAC but I'm sure that's not the problem here.
Also, I have read somewhere that I can use a configuration server to store xml files for each machine I have, and given the quantity of machines, this would be the ideal approach for me because each one obviously needs a different IP address and hostname, so I can't use the same XML file for all the machines.
why don't you use DHCP in your network? If you do "autoyast=nfs://..../" without providing the profile name, then autoyast tries to fetch a profile with the name of the MAC address of the machine like "0007E9F2FCEB". -- 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
Hello,
Thank you once again for your reply... I am once again, a step further :-)
However, I am still having the same problem, although now I think I know
why.
Current Situation:
I have one NFS export, which is exported read-only. This contains two dirs -
"suse10_64" and "configProfiles".
The relevant line in "/tftpboot/pxelinux.cfg/default" says:
append initrd=initrd splash=silent showopts insmod=e1000 netdevice=eth0
install=nfs://192.168.3.230/install/suse10_64/
autoyast=nfs://192.168.3.230/install/configProfiles/
But I am still getting the "Profile not found error". The MAC address of the
machine is 00:14:22:b0:c6:66 and it's DHCP IP address and the IP address
specified in the XML file are both 192.168.3.4. I have therefore tried
calling the xml file "001422b0c666", "001422B0C666" and even "C0A80304" (the
hex IP address), but I still get the "Profile not found" error.
I therefore decided to type "yast2 autoyast", then open the xml file, and
then validate it using the option in the "Tools" menu. The following
happened...
First of all, I click "File" | "Open" and opened the XML file I had
generated. The following got printed to either stdout or stderr:
============================================================
Pseudo-hashes are deprecated at /usr/share/YaST2/modules/SambaServer.pm line
284 (#1)
(D deprecated) Pseudo-hashes were deprecated in Perl 5.8.0 and they
will be removed in Perl 5.10.0, see perl58delta for more details.
You can continue to use the fields pragma.
============================================================
I then clicked "Tools" | "Check Validity of Profile" and after it had done
it's checking, the following got reported back to me:
============================================================
^
/tmp/YaST2-05451-xDXf8N/valid.xml:1067: element write_list: validity error :
No declaration for element write_list
-----Original Message----- From: Uwe Gansert [mailto:ug@suse.de] Sent: 02 February 2006 18:02 To: suse-autoinstall@suse.com Subject: Re: [suse-autoinstall] Help with installing multiple machines over network
On Thursday 02 February 2006 18:41, Richard Hobbs wrote:
I have also added an <initialize> tag within each <drive> tag, just below the <device> tag in order to remove the partition table on each disk before starting, so I hope I have done this correctly as well:
============================================================ <drive> <device>/dev/sda</device>
true</initialize> this is correct.
Finally, just after it's probed the mouse and done a few other things, I get a dialog box appearing which says:
System Profile Location: /existing/location/of/file.xml
I then have the option ot typing in a different XML file, but why is it prompting me for a different file?
that can happen in two cases. Either the profile can't be found where you have pointed to with the autoyast=... option, or the profile has a XML syntax error. Since you created the profile with the autoyast UI, a syntax error is not very likely as long as you did not change anything with a texteditor. So make sure that the profile really is where autoyast=... points to and that the machine can read it. On SUSE Linux 10.1 the error message in that case is a lot better but of course that does not help you at the moment :)
I have a feeling there's a MAC address in the xml file somewhere, so do I just need to replace the MAC address of the original machine with the MAC address of the new machine I'm trying to build?
maybe it's a good idea to replace the MAC but I'm sure that's not the problem here.
Also, I have read somewhere that I can use a configuration server to store xml files for each machine I have, and given the quantity of machines, this would be the ideal approach for me because each one obviously needs a different IP address and hostname, so I can't use the same XML file for all the machines.
why don't you use DHCP in your network? If you do "autoyast=nfs://..../" without providing the profile name, then autoyast tries to fetch a profile with the name of the MAC address of the machine like "0007E9F2FCEB".
-- 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
-- To unsubscribe, e-mail: suse-autoinstall-unsubscribe@suse.com For additional commands, e-mail: suse-autoinstall-help@suse.com
_____________________________________________________________________ This e-mail has been scanned for viruses by MCI's Internet Managed Scanning Services - powered by MessageLabs. For further information visit http://www.mci.com
_____________________________________________________________________ This e-mail has been scanned for viruses by MCI's Internet Managed Scanning Services - powered by MessageLabs. For further information visit http://www.mci.com
The autoyast requires the actual filename, not just the directory. e.g. autoyast=nfs://192.168.3.230/install/configProfiles/profile.xml It helped me a lot to monitor /var/log/messages of my dhcp server while booting the client. On Friday 03 February 2006 09:59, Richard Hobbs wrote:
Hello,
Thank you once again for your reply... I am once again, a step further :-)
However, I am still having the same problem, although now I think I know why.
Current Situation:
I have one NFS export, which is exported read-only. This contains two dirs - "suse10_64" and "configProfiles".
The relevant line in "/tftpboot/pxelinux.cfg/default" says:
append initrd=initrd splash=silent showopts insmod=e1000 netdevice=eth0 install=nfs://192.168.3.230/install/suse10_64/ autoyast=nfs://192.168.3.230/install/configProfiles/
But I am still getting the "Profile not found error". The MAC address of the machine is 00:14:22:b0:c6:66 and it's DHCP IP address and the IP address specified in the XML file are both 192.168.3.4. I have therefore tried calling the xml file "001422b0c666", "001422B0C666" and even "C0A80304" (the hex IP address), but I still get the "Profile not found" error.
I therefore decided to type "yast2 autoyast", then open the xml file, and then validate it using the option in the "Tools" menu. The following happened...
First of all, I click "File" | "Open" and opened the XML file I had generated. The following got printed to either stdout or stderr:
============================================================ Pseudo-hashes are deprecated at /usr/share/YaST2/modules/SambaServer.pm line 284 (#1) (D deprecated) Pseudo-hashes were deprecated in Perl 5.8.0 and they will be removed in Perl 5.10.0, see perl58delta for more details. You can continue to use the fields pragma. ============================================================
I then clicked "Tools" | "Check Validity of Profile" and after it had done it's checking, the following got reported back to me:
============================================================ ^ /tmp/YaST2-05451-xDXf8N/valid.xml:1067: element write_list: validity error : No declaration for element write_list
@ntadmin root ^ /tmp/YaST2-05451-xDXf8N/valid.xml:1068: element parameters: validity error : No declaration for element parameters </parameters> ^ /tmp/YaST2-05451-xDXf8N/valid.xml:1069: element listentry: validity error : No declaration for element listentry </listentry> ^ /tmp/YaST2-05451-xDXf8N/valid.xml:1074: element inherit_acls: validity error: No declaration for element inherit_acls
Yes ^ /tmp/YaST2-05451-xDXf8N/valid.xml:1075: element path: validity error : No declaration for element path <path>/home/groups</path> ^ /tmp/YaST2-05451-xDXf8N/valid.xml:1076: element read_only: validity error : No declaration for element read_onlyNo ^ /tmp/YaST2-05451-xDXf8N/valid.xml:1077: element parameters: validity error : No declaration for element parameters </parameters> ^ /tmp/YaST2-05451-xDXf8N/valid.xml:1078: element listentry: validity error : No declaration for element listentry </listentry> ^ /tmp/YaST2-05451-xDXf8N/valid.xml:1083: element inherit_acls: validity error: No declaration for element inherit_acls
Yes ^ /tmp/YaST2-05451-xDXf8N/valid.xml:1084: element path: validity error : No declaration for element path <path>/home</path> ^ /tmp/YaST2-05451-xDXf8N/valid.xml:1085: element read_only: validity error : No declaration for element read_onlyNo ^ /tmp/YaST2-05451-xDXf8N/valid.xml:1086: element veto_files: validity error : No declaration for element veto_files/aquota.user/groups/shares/ ^ /tmp/YaST2-05451-xDXf8N/valid.xml:1087: element parameters: validity error : No declaration for element parameters </parameters> ^ /tmp/YaST2-05451-xDXf8N/valid.xml:1088: element listentry: validity error : No declaration for element listentry </listentry> ^ /tmp/YaST2-05451-xDXf8N/valid.xml:1092: element browseable: validity error : No declaration for element browseable <browseable>No</browseable> ^ /tmp/YaST2-05451-xDXf8N/valid.xml:1094: element inherit_acls: validity error: No declaration for element inherit_acls
Yes ^ /tmp/YaST2-05451-xDXf8N/valid.xml:1095: element read_only: validity error : No declaration for element read_onlyNo ^ /tmp/YaST2-05451-xDXf8N/valid.xml:1096: element valid_users: validity error: No declaration for element valid_users
%S ^ /tmp/YaST2-05451-xDXf8N/valid.xml:1097: element parameters: validity error : No declaration for element parameters </parameters> ^ /tmp/YaST2-05451-xDXf8N/valid.xml:1098: element listentry: validity error : No declaration for element listentry </listentry> ^ /tmp/YaST2-05451-xDXf8N/valid.xml:1103: element create_mask: validity error: No declaration for element create_mask
0600 ^ /tmp/YaST2-05451-xDXf8N/valid.xml:1104: element directory_mask: validity error : No declaration for element directory_mask0700 ^ /tmp/YaST2-05451-xDXf8N/valid.xml:1105: element path: validity error : No declaration for element path <path>%H</path> ^ /tmp/YaST2-05451-xDXf8N/valid.xml:1106: element read_only: validity error : No declaration for element read_onlyNo ^ /tmp/YaST2-05451-xDXf8N/valid.xml:1107: element store_dos_attributes: validity error : No declaration for element store_dos_attributesYes ^ /tmp/YaST2-05451-xDXf8N/valid.xml:1108: element parameters: validity error : No declaration for element parameters </parameters> ^ /tmp/YaST2-05451-xDXf8N/valid.xml:1109: element listentry: validity error : No declaration for element listentry </listentry> ^ /tmp/YaST2-05451-xDXf8N/valid.xml:1110: element config: validity error : Element config was declared #PCDATA but contains non text nodes </config> ^ /tmp/YaST2-05451-xDXf8N/valid.xml:1113: element samba-server: validity error: Element samba-server content does not follow the DTD, expecting (client ,
global , role , service , shares , trusteddomains , version), got (config service version ) </samba-server> ^ /tmp/YaST2-05451-xDXf8N/valid.xml:1200: element groups: validity error : Element groups content does not follow the DTD, expecting (group)+, got (CDATA) <groups>video,dialout</groups> ^ /tmp/YaST2-05451-xDXf8N/valid.xml:1200: element groups: validity error : Element groups does not carry attribute config:type <groups>video,dialout</groups> ^ /tmp/YaST2-05451-xDXf8N/valid.xml:1205: element user_defaults: validity error : Element user_defaults content does not follow the DTD, expecting (expire? , group? , home? , inactive? , shell? , skel?), got (group groups home inactive shell skel ) ^ /tmp/YaST2-05451-xDXf8N/valid.xml:1454: element profile: validity error : Element profile content does not follow the DTD, expecting (files | firewall
| groups | inetd | ldap | mail | networking | nfs | nfs_server | nis |
nisplus | nis_server | ntp-client | printer | proxy | runlevel | samba-client | samba-server | scripts | security | sound | sysconfig | tftp-server | user_defaults | users | x11 | online_update | bootloader | classes | general | lvm | partitioning | partitioning_advanced | raid | report | software)*, got (bootloader firewall general groups inetd kerberos ldap mail networking nfs_server nis nis_server ntp-client partitioning power-management printer report runlevel samba-client samba-server security software sound user_defaults users x11 ) </profile> ^ ============================================================
I have a feeling there was more to display, but it had scrolled beyond the top of the text area.
When generating the XML file, you have the option of selecting various "Additional Resources". I tried selecting all of them, even the ones that weren't installed or configured, but it prompted me to install dhcp-server and bind, so after unselecting "DHCP Server" and "DNS Server", I tried again and it generated an XML file without displaying any errors.
However, the machine does not have a lot of these things on it (or at least they have never been configured), like a NIS Server, Samba Server, NFS Server, LDAP client, Kerberos client, and Firewall.
Should I unselect these options if they are not installed or configured, or will manual intervention be required during each install onto the new machines?
I figured that even if they're not configured, by including them in the profile, it would tell autoyast that they were not configured, so don't prompt the user, but my assumptions may be wrong. I basically just want to clone the system! Lol
Thanks again, your help is appreciated :-)
Richard.
-- Richard Hobbs (Systems Administrator) Toshiba Research Europe Ltd. - Speech Technology Group Web: http://www.toshiba-europe.com/research/ Normal Email: richard.hobbs@crl.toshiba.co.uk Mobile Email: mobile@mongeese.co.uk Tel: +44 1223 376964 Mobile: +44 7811 803377
-----Original Message----- From: Uwe Gansert [mailto:ug@suse.de] Sent: 02 February 2006 18:02 To: suse-autoinstall@suse.com Subject: Re: [suse-autoinstall] Help with installing multiple machines over network
On Thursday 02 February 2006 18:41, Richard Hobbs wrote:
I have also added an <initialize> tag within each <drive>
tag, just below
the <device> tag in order to remove the partition table on each disk before starting, so I hope I have done this correctly as well:
============================================================ <drive> <device>/dev/sda</device>
true</initialize> this is correct.
Finally, just after it's probed the mouse and done a few
other things, I
get a dialog box appearing which says:
System Profile Location: /existing/location/of/file.xml
I then have the option ot typing in a different XML file,
but why is it
prompting me for a different file?
that can happen in two cases. Either the profile can't be found where you have pointed to with the autoyast=... option, or the profile has a XML syntax error. Since you created the profile with the autoyast UI, a syntax error is not very likely as long as you did not change anything with a texteditor. So make sure that the profile really is where autoyast=... points to and that the machine can read it. On SUSE Linux 10.1 the error message in that case is a lot better but of course that does not help you at the moment :)
I have a feeling there's a MAC address in the xml file somewhere, so do I just need to replace the MAC address of the
original machine with
the MAC address of the new machine I'm trying to build?
maybe it's a good idea to replace the MAC but I'm sure that's not the problem here.
Also, I have read somewhere that I can use a configuration server to store xml files for each machine I have, and given the quantity of machines, this would be the ideal approach for me because each one obviously needs a different IP address and hostname, so I
can't use the
same XML file for all the machines.
why don't you use DHCP in your network? If you do "autoyast=nfs://..../" without providing the profile name, then autoyast tries to fetch a profile with the name of the MAC address of the machine like "0007E9F2FCEB".
-- 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
-- To unsubscribe, e-mail: suse-autoinstall-unsubscribe@suse.com For additional commands, e-mail: suse-autoinstall-help@suse.com
_____________________________________________________________________ This e-mail has been scanned for viruses by MCI's Internet Managed Scanning Services - powered by MessageLabs. For further information visit http://www.mci.com
_____________________________________________________________________ This e-mail has been scanned for viruses by MCI's Internet Managed Scanning Services - powered by MessageLabs. For further information visit http://www.mci.com
Hello, But I have read that you can simply specify a directory containing profiles and the machine being installed will look for a file with the same filename as either it's MAC address or IP address in hex form, but my filenames of "001422b0c666", for example, could be wrong. Thanks again, Richard. -- Richard Hobbs (Systems Administrator) Toshiba Research Europe Ltd. - Speech Technology Group Web: http://www.toshiba-europe.com/research/ Normal Email: richard.hobbs@crl.toshiba.co.uk Mobile Email: mobile@mongeese.co.uk Tel: +44 1223 376964 Mobile: +44 7811 803377
-----Original Message----- From: mattijs [mailto:m.janssens@opencfd.co.uk] Sent: 03 February 2006 10:17 To: suse-autoinstall@suse.com Subject: Re: [suse-autoinstall] Help with installing multiple machines over network
The autoyast requires the actual filename, not just the directory. e.g.
autoyast=nfs://192.168.3.230/install/configProfiles/profile.xml
It helped me a lot to monitor /var/log/messages of my dhcp server while booting the client.
Hello,
Thank you once again for your reply... I am once again, a step further :-)
However, I am still having the same problem, although now I
why.
Current Situation:
I have one NFS export, which is exported read-only. This contains two dirs - "suse10_64" and "configProfiles".
The relevant line in "/tftpboot/pxelinux.cfg/default" says:
append initrd=initrd splash=silent showopts insmod=e1000 netdevice=eth0 install=nfs://192.168.3.230/install/suse10_64/ autoyast=nfs://192.168.3.230/install/configProfiles/
But I am still getting the "Profile not found error". The MAC address of the machine is 00:14:22:b0:c6:66 and it's DHCP IP address and the IP address specified in the XML file are both 192.168.3.4. I have therefore tried calling the xml file "001422b0c666", "001422B0C666" and even "C0A80304" (the hex IP address), but I still get the "Profile not found" error.
I therefore decided to type "yast2 autoyast", then open the xml file, and then validate it using the option in the "Tools" menu. The following happened...
First of all, I click "File" | "Open" and opened the XML file I had generated. The following got printed to either stdout or stderr:
============================================================ Pseudo-hashes are deprecated at /usr/share/YaST2/modules/SambaServer.pm line 284 (#1) (D deprecated) Pseudo-hashes were deprecated in Perl 5.8.0 and they will be removed in Perl 5.10.0, see perl58delta for more details. You can continue to use the fields pragma. ============================================================
I then clicked "Tools" | "Check Validity of Profile" and after it had done it's checking, the following got reported back to me:
============================================================ ^ /tmp/YaST2-05451-xDXf8N/valid.xml:1067: element write_list: validity error : No declaration for element write_list
@ntadmin root ^ /tmp/YaST2-05451-xDXf8N/valid.xml:1068: element parameters: validity error : No declaration for element parameters </parameters> ^ /tmp/YaST2-05451-xDXf8N/valid.xml:1069: element listentry: validity error : No declaration for element listentry </listentry> ^ /tmp/YaST2-05451-xDXf8N/valid.xml:1074: element inherit_acls: validity error: No declaration for element inherit_acls
Yes ^ /tmp/YaST2-05451-xDXf8N/valid.xml:1075: element path: validity error : No declaration for element path <path>/home/groups</path> ^ /tmp/YaST2-05451-xDXf8N/valid.xml:1076: element read_only: validity error : No declaration for element read_onlyNo ^ /tmp/YaST2-05451-xDXf8N/valid.xml:1077: element parameters: validity error : No declaration for element parameters </parameters> ^ /tmp/YaST2-05451-xDXf8N/valid.xml:1078: element listentry: validity error : No declaration for element listentry </listentry> ^ /tmp/YaST2-05451-xDXf8N/valid.xml:1083: element inherit_acls: validity error: No declaration for element inherit_acls
Yes ^ /tmp/YaST2-05451-xDXf8N/valid.xml:1084: element path: validity error : No declaration for element path <path>/home</path> ^ /tmp/YaST2-05451-xDXf8N/valid.xml:1085: element read_only: validity error : No declaration for element read_onlyNo ^ /tmp/YaST2-05451-xDXf8N/valid.xml:1086: element veto_files: validity error : No declaration for element veto_files/aquota.user/groups/shares/ ^ /tmp/YaST2-05451-xDXf8N/valid.xml:1087: element parameters: validity error : No declaration for element parameters </parameters> ^ /tmp/YaST2-05451-xDXf8N/valid.xml:1088: element listentry: validity error : No declaration for element listentry </listentry> ^ /tmp/YaST2-05451-xDXf8N/valid.xml:1092: element browseable: validity error : No declaration for element browseable <browseable>No</browseable> ^ /tmp/YaST2-05451-xDXf8N/valid.xml:1094: element inherit_acls: validity error: No declaration for element inherit_acls
Yes ^ /tmp/YaST2-05451-xDXf8N/valid.xml:1095: element read_only: validity error : No declaration for element read_onlyNo ^ /tmp/YaST2-05451-xDXf8N/valid.xml:1096: element valid_users: validity error: No declaration for element valid_users
%S ^ /tmp/YaST2-05451-xDXf8N/valid.xml:1097: element parameters: validity error : No declaration for element parameters </parameters> ^ /tmp/YaST2-05451-xDXf8N/valid.xml:1098: element listentry: validity error : No declaration for element listentry </listentry> ^ /tmp/YaST2-05451-xDXf8N/valid.xml:1103: element create_mask: validity error: No declaration for element create_mask
0600 ^ /tmp/YaST2-05451-xDXf8N/valid.xml:1104: elementerror : No declaration for element directory_mask
0700 ^ /tmp/YaST2-05451-xDXf8N/valid.xml:1105: element path: validity error : No declaration for element path <path>%H</path> ^ /tmp/YaST2-05451-xDXf8N/valid.xml:1106: element read_only: validity error : No declaration for element read_onlyNo ^ /tmp/YaST2-05451-xDXf8N/valid.xml:1107: element store_dos_attributes: validity error : No declaration for element store_dos_attributesYes ^ /tmp/YaST2-05451-xDXf8N/valid.xml:1108: element parameters: validity error : No declaration for element parameters </parameters> ^ /tmp/YaST2-05451-xDXf8N/valid.xml:1109: element listentry: validity error : No declaration for element listentry </listentry> ^ /tmp/YaST2-05451-xDXf8N/valid.xml:1110: element config: validity error : Element config was declared #PCDATA but contains non text nodes </config> ^ /tmp/YaST2-05451-xDXf8N/valid.xml:1113: element samba-server: validity error: Element samba-server content does not follow the DTD, expecting (client ,
global , role , service , shares , trusteddomains , version), got (config service version ) </samba-server> ^ /tmp/YaST2-05451-xDXf8N/valid.xml:1200: element groups: validity error : Element groups content does not follow the DTD, expecting (group)+, got (CDATA) <groups>video,dialout</groups> ^ /tmp/YaST2-05451-xDXf8N/valid.xml:1200: element groups: validity error : Element groups does not carry attribute config:type <groups>video,dialout</groups> ^ /tmp/YaST2-05451-xDXf8N/valid.xml:1205: element user_defaults: validity error : Element user_defaults content does not follow the DTD, expecting (expire? , group? , home? , inactive? , shell? , skel?), got (group groups home inactive shell skel ) ^ /tmp/YaST2-05451-xDXf8N/valid.xml:1454: element profile: validity error : Element profile content does not follow the DTD, expecting (files | firewall
| groups | inetd | ldap | mail | networking | nfs | nfs_server | nis |
nisplus | nis_server | ntp-client | printer | proxy | runlevel | samba-client | samba-server | scripts | security | sound | sysconfig | tftp-server | user_defaults | users | x11 | online_update | bootloader | classes | general | lvm | partitioning |
report | software)*, got (bootloader firewall general groups inetd kerberos ldap mail networking nfs_server nis nis_server ntp-client
power-management printer report runlevel samba-client samba-server security software sound user_defaults users x11 ) </profile> ^ ============================================================
I have a feeling there was more to display, but it had scrolled beyond the top of the text area.
When generating the XML file, you have the option of selecting various "Additional Resources". I tried selecting all of them, even
weren't installed or configured, but it prompted me to install dhcp-server and bind, so after unselecting "DHCP Server" and "DNS Server", I tried again and it generated an XML file without displaying any errors.
However, the machine does not have a lot of these things on it (or at least they have never been configured), like a NIS Server, Samba Server, NFS Server, LDAP client, Kerberos client, and Firewall.
Should I unselect these options if they are not installed or configured, or will manual intervention be required during each install onto the new machines?
I figured that even if they're not configured, by including
profile, it would tell autoyast that they were not configured, so don't prompt the user, but my assumptions may be wrong. I basically just want to clone the system! Lol
Thanks again, your help is appreciated :-)
Richard.
-- Richard Hobbs (Systems Administrator) Toshiba Research Europe Ltd. - Speech Technology Group Web: http://www.toshiba-europe.com/research/ Normal Email: richard.hobbs@crl.toshiba.co.uk Mobile Email: mobile@mongeese.co.uk Tel: +44 1223 376964 Mobile: +44 7811 803377
-----Original Message----- From: Uwe Gansert [mailto:ug@suse.de] Sent: 02 February 2006 18:02 To: suse-autoinstall@suse.com Subject: Re: [suse-autoinstall] Help with installing multiple machines over network
On Thursday 02 February 2006 18:41, Richard Hobbs wrote:
I have also added an <initialize> tag within each <drive>
tag, just below
the <device> tag in order to remove the partition table on each disk before starting, so I hope I have done this correctly as well:
============================================================ <drive> <device>/dev/sda</device>
true</initialize> this is correct.
Finally, just after it's probed the mouse and done a few
other things, I
get a dialog box appearing which says:
System Profile Location: /existing/location/of/file.xml
I then have the option ot typing in a different XML file,
but why is it
prompting me for a different file?
that can happen in two cases. Either the profile can't be found where you have pointed to with the autoyast=... option, or the profile has a XML syntax error. Since you created the profile with the autoyast UI, a syntax error is not very likely as long as you did not change anything with a texteditor. So make sure that the profile really is where autoyast=... points to and that the machine can read it. On SUSE Linux 10.1 the error message in that case is a lot better but of course that does not help you at the moment :)
I have a feeling there's a MAC address in the xml file somewhere, so do I just need to replace the MAC address of the
original machine with
the MAC address of the new machine I'm trying to build?
maybe it's a good idea to replace the MAC but I'm sure
On Friday 03 February 2006 09:59, Richard Hobbs wrote: think I know directory_mask: validity partitioning_advanced | raid | partitioning the ones that them in the that's not the
problem here.
Also, I have read somewhere that I can use a configuration server to store xml files for each machine I have, and given the quantity of machines, this would be the ideal approach for me because each one obviously needs a different IP address and hostname, so I
can't use the
same XML file for all the machines.
why don't you use DHCP in your network? If you do "autoyast=nfs://..../" without providing the profile name, then autoyast tries to fetch a profile with the name of the MAC address of the machine like "0007E9F2FCEB".
-- 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
-- To unsubscribe, e-mail: suse-autoinstall-unsubscribe@suse.com For additional commands, e-mail: suse-autoinstall-help@suse.com
This e-mail has been scanned for viruses by MCI's Internet Managed Scanning Services - powered by MessageLabs. For further information visit http://www.mci.com
_____________________________________________________________________
This e-mail has been scanned for viruses by MCI's Internet Managed Scanning Services - powered by MessageLabs. For further information visit http://www.mci.com
-- To unsubscribe, e-mail: suse-autoinstall-unsubscribe@suse.com For additional commands, e-mail: suse-autoinstall-help@suse.com
_____________________________________________________________________ This e-mail has been scanned for viruses by MCI's Internet Managed Scanning Services - powered by MessageLabs. For further information visit http://www.mci.com
_____________________________________________________________________ This e-mail has been scanned for viruses by MCI's Internet Managed Scanning Services - powered by MessageLabs. For further information visit http://www.mci.com
On Friday 03 February 2006 10:59, Richard Hobbs wrote:
autoyast=nfs://192.168.3.230/install/configProfiles/
But I am still getting the "Profile not found error".
are you sure it's "Profile not found"? It can also be a syntax error. Instead of your profile, please try the minimal profile from the FAQ: http://www.suse.de/~ug/AutoYaST_FAQ.html#a3 That has no syntax errors and can be parsed on a 10.0
I have therefore tried calling the xml file "001422b0c666", "001422B0C666"
both should work. Autoyast tries both versions. First uppercase, then lowercase.
First of all, I click "File" | "Open" and opened the XML file I had generated. The following got printed to either stdout or stderr:
============================================================ Pseudo-hashes are deprecated at /usr/share/YaST2/modules/SambaServer.pm line 284 (#1) (D deprecated) Pseudo-hashes were deprecated in Perl 5.8.0 and they will be removed in Perl 5.10.0, see perl58delta for more details. You can continue to use the fields pragma. ============================================================
that's not a problem. I saw that a while ago and checked the code. It does not hurt. I already reported that to the developer of the SambaServer.
I then clicked "Tools" | "Check Validity of Profile" and after it had done it's checking, the following got reported back to me:
on the 10.0 the validity check is not very good. Better don't trust it too much. I hope we'll get that fixed for SLES10. -- 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
Hello,
The basic profile worked fine, so I've decided to start transplanting the
stuff I need into that file, bit by bit until I have a working solution :-)
I have done a few sections now, but am stumbling on the partitioning. I keep
getting a dialog box popping up, stating:
Error while configuring partitions, try again.
The <partitions> bit of the profile looks like this:
============================================================
<partitioning config:type="list">
<drive>
<device>/dev/sda</device>
<initialize config:type="boolean">true</initialize>
<partitions config:type="list">
<partition>
<filesystem config:type="symbol">reiser</filesystem>
<format config:type="boolean">true</format>
<mount>/boot</mount>
-----Original Message----- From: Uwe Gansert [mailto:ug@suse.de] Sent: 03 February 2006 10:27 To: suse-autoinstall@suse.com Subject: Re: [suse-autoinstall] Help with installing multiple machines over network
On Friday 03 February 2006 10:59, Richard Hobbs wrote:
autoyast=nfs://192.168.3.230/install/configProfiles/
But I am still getting the "Profile not found error".
are you sure it's "Profile not found"? It can also be a syntax error. Instead of your profile, please try the minimal profile from the FAQ: http://www.suse.de/~ug/AutoYaST_FAQ.html#a3 That has no syntax errors and can be parsed on a 10.0
I have therefore tried calling the xml file "001422b0c666", "001422B0C666"
both should work. Autoyast tries both versions. First uppercase, then lowercase.
First of all, I click "File" | "Open" and opened the XML file I had generated. The following got printed to either stdout or stderr:
============================================================ Pseudo-hashes are deprecated at /usr/share/YaST2/modules/SambaServer.pm line 284 (#1) (D deprecated) Pseudo-hashes were deprecated in Perl 5.8.0 and they will be removed in Perl 5.10.0, see perl58delta for more details. You can continue to use the fields pragma. ============================================================
that's not a problem. I saw that a while ago and checked the code. It does not hurt. I already reported that to the developer of the SambaServer.
I then clicked "Tools" | "Check Validity of Profile" and after it had done it's checking, the following got reported back to me:
on the 10.0 the validity check is not very good. Better don't trust it too much. I hope we'll get that fixed for SLES10.
-- 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
-- To unsubscribe, e-mail: suse-autoinstall-unsubscribe@suse.com For additional commands, e-mail: suse-autoinstall-help@suse.com
_____________________________________________________________________ This e-mail has been scanned for viruses by MCI's Internet Managed Scanning Services - powered by MessageLabs. For further information visit http://www.mci.com
_____________________________________________________________________ This e-mail has been scanned for viruses by Verizon Business Internet Managed Scanning Services - powered by MessageLabs. For further information visit http://www.mci.com
On Friday 03 February 2006 14:14, Richard Hobbs wrote:
I have done a few sections now, but am stumbling on the partitioning. I keep getting a dialog box popping up, stating:
Error while configuring partitions, try again.
The <partitions> bit of the profile looks like this:
10.0 had a bug in the partition cloning code. remove this from the profile:
<partition>
15 4 <size>max</size> </partition>
-- 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
Hello, Surely removing that line will stop the extended partition from being created, won't it? I have tried that solution anyway, and I get the same error. I already have some partitions on the disk if that makes a difference. I do not want to keep them though, which is why I have the <initialize> tag in the profile. What actually are the different types of partition_id? I think 130 is swap, and 131 is a standard partition, but I also thought 15 was an extended partition. Also, what is 5? I have seen 5 on some examples. Thanks again, Richard. -- Richard Hobbs (Systems Administrator) Toshiba Research Europe Ltd. - Speech Technology Group Web: http://www.toshiba-europe.com/research/ Normal Email: richard.hobbs@crl.toshiba.co.uk Mobile Email: mobile@mongeese.co.uk Tel: +44 1223 376964 Mobile: +44 7811 803377
-----Original Message----- From: Uwe Gansert [mailto:ug@suse.de] Sent: 03 February 2006 13:18 To: suse-autoinstall@suse.com Subject: Re: [suse-autoinstall] Help with installing multiple machines over network
On Friday 03 February 2006 14:14, Richard Hobbs wrote:
I have done a few sections now, but am stumbling on the partitioning. I keep getting a dialog box popping up, stating:
Error while configuring partitions, try again.
The <partitions> bit of the profile looks like this:
10.0 had a bug in the partition cloning code.
remove this from the profile:
<partition>
15 4 <size>max</size> </partition>-- 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
-- To unsubscribe, e-mail: suse-autoinstall-unsubscribe@suse.com For additional commands, e-mail: suse-autoinstall-help@suse.com
_____________________________________________________________________ This e-mail has been scanned for viruses by Verizon Business Internet Managed Scanning Services - powered by MessageLabs. For further information visit http://www.mci.com
_____________________________________________________________________ This e-mail has been scanned for viruses by Verizon Business Internet Managed Scanning Services - powered by MessageLabs. For further information visit http://www.mci.com
On Friday 03 February 2006 14:31, Richard Hobbs wrote:
Surely removing that line will stop the extended partition from being created, won't it?
autoyast will create it anyway.
I already have some partitions on the disk if that makes a difference. I do not want to keep them though, which is why I have the <initialize> tag in the profile.
remove the
What actually are the different types of partition_id? I think 130 is swap, and 131 is a standard partition, but I also thought 15 was an extended partition. Also, what is 5? I have seen 5 on some examples.
don't care about that. partition id 5 is "extended partition non LBA". Ignore the partition_id stuff. -- 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
Hello,
I have now removed the <initialize> stuff from both drives and re-tested,
but I still get the same error. Here is my <partitioning> section now:
============================================================
<partitioning config:type="list">
<drive>
<device>/dev/sda</device>
<partitions config:type="list">
<partition>
<filesystem config:type="symbol">reiser</filesystem>
<format config:type="boolean">true</format>
<mount>/boot</mount>
-----Original Message----- From: Uwe Gansert [mailto:ug@suse.de] Sent: 03 February 2006 13:37 To: suse-autoinstall@suse.com Subject: Re: [suse-autoinstall] Help with installing multiple machines over network
On Friday 03 February 2006 14:31, Richard Hobbs wrote:
Surely removing that line will stop the extended partition from being created, won't it?
autoyast will create it anyway.
I already have some partitions on the disk if that makes a difference. I do not want to keep them though, which is why I have the <initialize> tag in the profile.
remove the
for testing too. They are not needed in 99% of the cases. What actually are the different types of partition_id? I think 130 is swap, and 131 is a standard partition, but I also thought 15 was an extended partition. Also, what is 5? I have seen 5 on some examples.
don't care about that. partition id 5 is "extended partition non LBA". Ignore the partition_id stuff.
-- 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
-- To unsubscribe, e-mail: suse-autoinstall-unsubscribe@suse.com For additional commands, e-mail: suse-autoinstall-help@suse.com
_____________________________________________________________________ This e-mail has been scanned for viruses by Verizon Business Internet Managed Scanning Services - powered by MessageLabs. For further information visit http://www.mci.com
_____________________________________________________________________ This e-mail has been scanned for viruses by Verizon Business Internet Managed Scanning Services - powered by MessageLabs. For further information visit http://www.mci.com
On Friday 03 February 2006 14:48, Richard Hobbs wrote:
I have now removed the <initialize> stuff from both drives and re-tested, but I still get the same error. Here is my <partitioning> section now:
*grrrrr* Nice. I'm working on too many thing in parallel at the moment. Sorry. Add the following lines to your profile and test again please:
============================================================ <partitioning config:type="list"> <drive> <device>/dev/sda</device> <partitions config:type="list"> <partition> <filesystem config:type="symbol">reiser</filesystem> <format config:type="boolean">true</format> <mount>/boot</mount>
131 1 <size>100mb</size>primary </partition> <partition> <filesystem config:type="symbol">reiser</filesystem> <format config:type="boolean">true</format> <mount>/</mount>131 2 <size>7000mb</size>primary </partition> <partition> <filesystem config:type="symbol">reiser</filesystem> <format config:type="boolean">true</format> <mount>/usr</mount>131 3 <size>7000mb</size>primary </partition> <partition> <filesystem config:type="symbol">swap</filesystem> <format config:type="boolean">true</format> <mount>swap</mount>130 5 <size>2048mb</size> </partition> <partition> <filesystem config:type="symbol">reiser</filesystem> <format config:type="boolean">true</format> <mount>/tmp</mount>131 6 <size>1024mb</size> </partition> <partition> <filesystem config:type="symbol">reiser</filesystem> <format config:type="boolean">true</format> <mount>/stg-dell1</mount>131 7 <size>max</size> </partition> </partitions> <use>all</use> </drive> <drive> <device>/dev/sdb</device> <partitions config:type="list"> <partition> <filesystem config:type="symbol">reiser</filesystem> <format config:type="boolean">true</format> <mount>/mirror</mount>131 1 <size>max</size>primary </partition> </partitions> <use>all</use> </drive> </partitioning>
-- 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
Hello,
Thank you once again for your response, but unfortunately, it has failed
again. Here is the current <partitioning> section again...
============================================================
<partitioning config:type="list">
<drive>
<device>/dev/sda</device>
<partitions config:type="list">
<partition>
<filesystem config:type="symbol">reiser</filesystem>
<format config:type="boolean">true</format>
<mount>/boot</mount>
-----Original Message----- From: Uwe Gansert [mailto:ug@suse.de] Sent: 03 February 2006 14:07 To: suse-autoinstall@suse.com Subject: Re: [suse-autoinstall] Help with installing multiple machines over network
On Friday 03 February 2006 14:48, Richard Hobbs wrote:
I have now removed the <initialize> stuff from both drives and re-tested, but I still get the same error. Here is my <partitioning> section now:
*grrrrr* Nice. I'm working on too many thing in parallel at the moment. Sorry. Add the following lines to your profile and test again please:
============================================================ <partitioning config:type="list"> <drive> <device>/dev/sda</device> <partitions config:type="list"> <partition> <filesystem config:type="symbol">reiser</filesystem> <format config:type="boolean">true</format> <mount>/boot</mount>
131 1 <size>100mb</size>primary </partition> <partition> <filesystem config:type="symbol">reiser</filesystem> <format config:type="boolean">true</format> <mount>/</mount>131 2 <size>7000mb</size>primary </partition> <partition> <filesystem config:type="symbol">reiser</filesystem> <format config:type="boolean">true</format> <mount>/usr</mount>131 3 <size>7000mb</size>primary </partition> <partition> <filesystem config:type="symbol">swap</filesystem> <format config:type="boolean">true</format> <mount>swap</mount>130 5 <size>2048mb</size> </partition> <partition> <filesystem config:type="symbol">reiser</filesystem> <format config:type="boolean">true</format> <mount>/tmp</mount>131 6 <size>1024mb</size> </partition> <partition> <filesystem config:type="symbol">reiser</filesystem> <format config:type="boolean">true</format> <mount>/stg-dell1</mount>131 7 <size>max</size> </partition> </partitions> <use>all</use> </drive> <drive> <device>/dev/sdb</device> <partitions config:type="list"> <partition> <filesystem config:type="symbol">reiser</filesystem> <format config:type="boolean">true</format> <mount>/mirror</mount>131 1 <size>max</size>primary </partition> </partitions> <use>all</use> </drive> </partitioning>-- 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
-- To unsubscribe, e-mail: suse-autoinstall-unsubscribe@suse.com For additional commands, e-mail: suse-autoinstall-help@suse.com
_____________________________________________________________________ This e-mail has been scanned for viruses by Verizon Business Internet Managed Scanning Services - powered by MessageLabs. For further information visit http://www.mci.com
_____________________________________________________________________ This e-mail has been scanned for viruses by Verizon Business Internet Managed Scanning Services - powered by MessageLabs. For further information visit http://www.mci.com
On Friday 03 February 2006 15:39, Richard Hobbs wrote:
Thank you once again for your response, but unfortunately, it has failed again. Here is the current <partitioning> section again...
I just tested it on a SUSE Linux 10.0 and it's working fine here. Can you do a manual installation? (don't provide the autoyast=.... parameter). If you see the error message and then switch to the console via CTRL+ALT+F2 and type "cat /proc/partitions" can you see your two drives sda and sdb? -- 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
Hello, I have just begun a manual installation, and it has auto-detected the drives as /dev/sda and /dev/sdb, and I am able to create partitions on those drives and then begin installing SuSE. They both appear in "/proc/partitions" as well: ============================================================ / # cat /proc/partitions major minor #blocks name 7 0 67924 loop0 8 0 78125000 sda 8 16 244140625 sdb / # ============================================================ I then tried setting up autoyast again, but this time with a very cut-down <partitioning> section, but the following doesn't even work: ============================================================ <partitioning config:type="list"> <drive> <use>all</use> </drive> </partitioning> ============================================================ Something seems to be seriously wrong here... Even after autoyast has failed, if I switch to a console I can see the drives in "/proc/partitions", and a manual installation autodetects them as "/dev/sda" and "/dev/sdb", and even now, while the error is on screen, if I switch to a console and type "fdisk /dev/sda" or "fdisk /dev/sdb" followed by 'p' to print the partition table, I can see the two blank disks! Here's the example from sda: ============================================================ / # fdisk /dev/sda The number of cylinders for this disk is set to 9726. There is nothing wrong with that, but this is larger than 1024, and could in certain setups cause problems with: 1) software that runs at boot time (e.g., old versions of LILO) 2) booting and partitioning software from other Oss (e.g., DOS FDISK, OS/2 FDISK) Command (m for help): p Disk /dev/sda: 80.0 GB, 80000000000 bytes 255 heads, 63 sectors/track, 9726 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System Command (m for help): ============================================================ Do you have any recommendations for where to go from here? Just in case it helps, below is a URL with links to "1.jpg", "3.jpg" and "4.jpg" which show consoles 1, 3 and 4 respectively. The photos were taken immediately after autoyast produced the error. http://mongeese.co.uk/binit/ Thank you once again, Richard. -- Richard Hobbs (Systems Administrator) Toshiba Research Europe Ltd. - Speech Technology Group Web: http://www.toshiba-europe.com/research/ Normal Email: richard.hobbs@crl.toshiba.co.uk Mobile Email: mobile@mongeese.co.uk Tel: +44 1223 376964 Mobile: +44 7811 803377
-----Original Message----- From: Uwe Gansert [mailto:ug@suse.de] Sent: 03 February 2006 14:54 To: suse-autoinstall@suse.com Subject: Re: [suse-autoinstall] Help with installing multiple machines over network
On Friday 03 February 2006 15:39, Richard Hobbs wrote:
Thank you once again for your response, but unfortunately, it has failed again. Here is the current <partitioning> section again...
I just tested it on a SUSE Linux 10.0 and it's working fine here. Can you do a manual installation? (don't provide the autoyast=.... parameter). If you see the error message and then switch to the console via CTRL+ALT+F2 and type "cat /proc/partitions" can you see your two drives sda and sdb?
-- 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
-- To unsubscribe, e-mail: suse-autoinstall-unsubscribe@suse.com For additional commands, e-mail: suse-autoinstall-help@suse.com
_____________________________________________________________________ This e-mail has been scanned for viruses by Verizon Business Internet Managed Scanning Services - powered by MessageLabs. For further information visit http://www.mci.com
_____________________________________________________________________ This e-mail has been scanned for viruses by Verizon Business Internet Managed Scanning Services - powered by MessageLabs. For further information visit http://www.mci.com
On Friday 03 February 2006 17:06, Richard Hobbs wrote:
I then tried setting up autoyast again, but this time with a very cut-down <partitioning> section, but the following doesn't even work:
============================================================ <partitioning config:type="list"> <drive> <use>all</use> </drive> </partitioning> ============================================================
Something seems to be seriously wrong here...
please send me the /var/log/YaST2/y2log via personal eMail. I want to take a look at that. You can copy that file via scp from the machine to another one. -- 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)
-
Gunreben, Peter (Peter) -
mattijs -
Richard Hobbs -
Uwe Gansert