Simultaneous SuSE 10.0 Autoyast installs fail!
Hello, I have a working and fully tested DHCP server, TFTP server, NFS file server and XML config profile which I have used to build the first of many servers. The whole system has worked fine, but now I've hit a rather critical problem - doing more than one server at a time seems to break them all! I have rebuilt our first server perhaps 15 times due to testing the XML profile, and each time it worked perfectly. I now have 8 machines which I would like to install, so I've copied the 001422B0C61F XML file to a filename which matches the other MAC addresses, and I have told our DHCP server to give out the necessary MAC addresses as well. The only things I have changed in our XML config profile is the any reference to the hostname, and the MAC address and IP address. Everything else is the same. When I boot up all 8 machines from the network, they all boot into the boot loader from the TFTP server, and they all boot into autoyast. They all load their own XML config files, but part of the way through installing the packages, the machines hang. Ctrl + Alt + F[1-6] does nothing, so all I can do is reboot using Ctrl + Alt + Del. The TFTP Server, NFS Server and the server hosting the config profiles (also over NFS) is the same machine, which can easily keep up with the demand for files... So much so, in fact, that the system load hardly increases at all during an install of a remote machine. What could be stopping me doing multiple NFS autoyast installs?? Any suggestions are welcome. Thanks in advance, 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 _____________________________________________________________________ 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
I don't know whether this is applicable to your situation but I have a cluster where if I boot them all at the same time some of the machine don't get their hostname set. Don't know whether the network isn't ready or maybe the dhcp server gets overloaded. I can imagine for your booting this might upset the installation. Another thing: the machines can see the xml file. Can they also see the installation source? Richard Hobbs wrote:
Hello,
I have a working and fully tested DHCP server, TFTP server, NFS file server and XML config profile which I have used to build the first of many servers.
The whole system has worked fine, but now I've hit a rather critical problem - doing more than one server at a time seems to break them all!
I have rebuilt our first server perhaps 15 times due to testing the XML profile, and each time it worked perfectly. I now have 8 machines which I would like to install, so I've copied the 001422B0C61F XML file to a filename which matches the other MAC addresses, and I have told our DHCP server to give out the necessary MAC addresses as well.
The only things I have changed in our XML config profile is the any reference to the hostname, and the MAC address and IP address. Everything else is the same.
When I boot up all 8 machines from the network, they all boot into the boot loader from the TFTP server, and they all boot into autoyast. They all load their own XML config files, but part of the way through installing the packages, the machines hang. Ctrl + Alt + F[1-6] does nothing, so all I can do is reboot using Ctrl + Alt + Del.
The TFTP Server, NFS Server and the server hosting the config profiles (also over NFS) is the same machine, which can easily keep up with the demand for files... So much so, in fact, that the system load hardly increases at all during an install of a remote machine.
What could be stopping me doing multiple NFS autoyast installs??
Any suggestions are welcome.
Thanks in advance, Richard.
-- Best regards, Mattijs Mattijs Janssens OpenCFD Ltd. The Mews, Picketts Lodge, Picketts Lane, Salfords, Surrey RH1 5RG. Tel: +44 (0)1293 821272 Email: M.Janssens@OpenCFD.co.uk URL: http://www.OpenCFD.co.uk
Hello, Mattijs: I can appreciate that if I boot all 8 machines simultaneously, they might overload the DHCP Server, but if I boot one machine up first, wait for it to begin installing the packages, and then boot a second machine up, as soon as the second machine starts it's installation, the first machine (and the second machine) hangs. And yes, the machines can see the XML file (or else they won't not begin installing) and they can also see the installation source (or they would not start installing the packages). Remember, it breaks after installing quite a few packages (maybe 25% complete). Hans-Joachim: I have a different XML config file for each MAC address of the machine I am installing, see below: ============================================================ nfsserver:/install/configProfiles # ls -l total 220 drwxr-xr-x 3 root root 400 Feb 14 10:14 . drwxr-xr-x 6 root root 176 Feb 8 08:52 .. -rw-r--r-- 1 root root 24032 Feb 14 10:12 000E0C062613 -rw-r--r-- 1 root root 24021 Feb 13 16:21 001422B0351F -rw-r--r-- 1 root root 24020 Feb 13 16:25 001422B0C567 -rw-r--r-- 1 root root 24021 Feb 13 16:42 001422B0C624 -rw-r--r-- 1 root root 24020 Feb 13 16:25 001422B0C633 -rw-r--r-- 1 root root 24020 Feb 13 16:23 001422B0C666 -rw-r--r-- 1 root root 24020 Feb 13 16:28 001422B0C726 -rw-r--r-- 1 root root 24021 Feb 13 16:28 001422B0C993 -rw-r--r-- 1 root root 24021 Feb 13 16:29 001422B0C9FC drwxr-xr-x 2 root root 88 Feb 7 15:59 oldProfiles -rw-r--r-- 1 root root 610 Feb 3 11:26 template.xml nfsserver:/install/configProfiles # ============================================================ So, if I want to install a new machine of identical hardware, I simply copy an existing profile, and modify the hostname and IP address. Why will this approach not work? Also, I am using DHCP to boot the machines, but the XML file has a static IP address (which is the same as the IP address given to the machine from DHCP). 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 Janssens [mailto:m.janssens@opencfd.co.uk] Sent: 14 February 2006 09:59 Cc: suse-autoinstall@suse.com Subject: Re: [suse-autoinstall] Simultaneous SuSE 10.0 Autoyast installs fail!
I don't know whether this is applicable to your situation but I have a cluster where if I boot them all at the same time some of the machine don't get their hostname set. Don't know whether the network isn't ready or maybe the dhcp server gets overloaded. I can imagine for your booting this might upset the installation.
Another thing: the machines can see the xml file. Can they also see the installation source?
Richard Hobbs wrote:
Hello,
I have a working and fully tested DHCP server, TFTP server, NFS file server and XML config profile which I have used to build the first of many servers.
The whole system has worked fine, but now I've hit a rather critical problem - doing more than one server at a time seems to break them all!
I have rebuilt our first server perhaps 15 times due to testing the XML profile, and each time it worked perfectly. I now have 8 machines which I would like to install, so I've copied the 001422B0C61F XML file to a filename which matches the other MAC addresses, and I have told our DHCP server to give out the necessary MAC addresses as well.
The only things I have changed in our XML config profile is the any reference to the hostname, and the MAC address and IP address. Everything else is the same.
When I boot up all 8 machines from the network, they all boot into the boot loader from the TFTP server, and they all boot into autoyast. They all load their own XML config files, but part of the way through installing the packages, the machines hang. Ctrl + Alt + F[1-6] does nothing, so all I can do is reboot using Ctrl + Alt + Del.
The TFTP Server, NFS Server and the server hosting the config profiles (also over NFS) is the same machine, which can easily keep up with the demand for files... So much so, in fact, that the system load hardly increases at all during an install of a remote machine.
What could be stopping me doing multiple NFS autoyast installs??
Any suggestions are welcome.
Thanks in advance, Richard.
-- Best regards,
Mattijs
Mattijs Janssens
OpenCFD Ltd. The Mews, Picketts Lodge, Picketts Lane, Salfords, Surrey RH1 5RG. Tel: +44 (0)1293 821272 Email: M.Janssens@OpenCFD.co.uk URL: http://www.OpenCFD.co.uk
-- 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
So, if I want to install a new machine of identical hardware, I simply copy an existing profile, and modify the hostname and IP address. Why will this approach not work?
Also, I am using DHCP to boot the machines, but the XML file has a static IP address (which is the same as the IP address given to the machine from DHCP).
Why don't you have your xml file specify the machine to use dhcp to pick up the hostname? Guess you have your reason for that but since you use dhcp anyway during the boot process ... This is quite unknown territory for me but since the install goes through 25% this might be the point at which it needs the hostname. 2) Do you use the vnc option? Maybe your machine has problems trying to set up vnc?
Hello, I have an update, and it doesn't appear to be anything to do with multiple installs going on simultaneously! We have a total of 9 machines. On 7 of these machines, SuSE 10.0 fails to install using AutoYast. They all fail in the same way. In the middle of installing the package, and with 428 packages remaining, it tries to install "emacs-21.3". It gets 56% of the way through this package, and then the machine hangs. On the other two servers, it installs perfectly. All servers are exactly the same hardware, apart from one. Here is the list: Custom Server - Install OK. Dell SC1425 1 - Install OK. Dell SC1425 2 - Install FAILS. Dell SC1425 3 - Install FAILS. Dell SC1425 4 - Install FAILS. Dell SC1425 5 - Install FAILS. Dell SC1425 6 - Install FAILS. Dell SC1425 7 - Install FAILS. Dell SC1425 8 - Install FAILS. All of the Dell servers are identical, apart from their MAC addresses, of course. What can I do to try and find out why some of the machines fail 56% of the way through "emacs-21.3" every single time?? 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: Richard Hobbs [mailto:richard.hobbs@crl.toshiba.co.uk] Sent: 14 February 2006 10:35 To: suse-autoinstall@suse.com Subject: RE: [suse-autoinstall] Simultaneous SuSE 10.0 Autoyast installs fail!
Hello,
Mattijs: I can appreciate that if I boot all 8 machines simultaneously, they might overload the DHCP Server, but if I boot one machine up first, wait for it to begin installing the packages, and then boot a second machine up, as soon as the second machine starts it's installation, the first machine (and the second machine) hangs.
And yes, the machines can see the XML file (or else they won't not begin installing) and they can also see the installation source (or they would not start installing the packages).
Remember, it breaks after installing quite a few packages (maybe 25% complete).
Hans-Joachim: I have a different XML config file for each MAC address of the machine I am installing, see below:
============================================================ nfsserver:/install/configProfiles # ls -l total 220 drwxr-xr-x 3 root root 400 Feb 14 10:14 . drwxr-xr-x 6 root root 176 Feb 8 08:52 .. -rw-r--r-- 1 root root 24032 Feb 14 10:12 000E0C062613 -rw-r--r-- 1 root root 24021 Feb 13 16:21 001422B0351F -rw-r--r-- 1 root root 24020 Feb 13 16:25 001422B0C567 -rw-r--r-- 1 root root 24021 Feb 13 16:42 001422B0C624 -rw-r--r-- 1 root root 24020 Feb 13 16:25 001422B0C633 -rw-r--r-- 1 root root 24020 Feb 13 16:23 001422B0C666 -rw-r--r-- 1 root root 24020 Feb 13 16:28 001422B0C726 -rw-r--r-- 1 root root 24021 Feb 13 16:28 001422B0C993 -rw-r--r-- 1 root root 24021 Feb 13 16:29 001422B0C9FC drwxr-xr-x 2 root root 88 Feb 7 15:59 oldProfiles -rw-r--r-- 1 root root 610 Feb 3 11:26 template.xml nfsserver:/install/configProfiles # ============================================================
So, if I want to install a new machine of identical hardware, I simply copy an existing profile, and modify the hostname and IP address. Why will this approach not work?
Also, I am using DHCP to boot the machines, but the XML file has a static IP address (which is the same as the IP address given to the machine from DHCP).
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 Janssens [mailto:m.janssens@opencfd.co.uk] Sent: 14 February 2006 09:59 Cc: suse-autoinstall@suse.com Subject: Re: [suse-autoinstall] Simultaneous SuSE 10.0 Autoyast installs fail!
I don't know whether this is applicable to your situation but I have a cluster where if I boot them all at the same time some of the machine don't get their hostname set. Don't know whether the network isn't ready or maybe the dhcp server gets overloaded. I can imagine for your booting this might upset the installation.
Another thing: the machines can see the xml file. Can they also see the installation source?
Richard Hobbs wrote:
Hello,
I have a working and fully tested DHCP server, TFTP server, NFS file server and XML config profile which I have used to build the first of many servers.
The whole system has worked fine, but now I've hit a rather critical problem - doing more than one server at a time seems to break them all!
I have rebuilt our first server perhaps 15 times due to testing the XML profile, and each time it worked perfectly. I now have 8 machines which I would like to install, so I've copied the 001422B0C61F XML file to a filename which matches the other MAC addresses, and I have told our DHCP server to give out the necessary MAC addresses as well.
The only things I have changed in our XML config profile is the any reference to the hostname, and the MAC address and IP address. Everything else is the same.
When I boot up all 8 machines from the network, they all boot into the boot loader from the TFTP server, and they all boot into autoyast. They all load their own XML config files, but part of the way through installing the packages, the machines hang. Ctrl + Alt + F[1-6] does nothing, so all I can do is reboot using Ctrl + Alt + Del.
The TFTP Server, NFS Server and the server hosting the config profiles (also over NFS) is the same machine, which can easily keep up with the demand for files... So much so, in fact, that the system load hardly increases at all during an install of a remote machine.
What could be stopping me doing multiple NFS autoyast installs??
Any suggestions are welcome.
Thanks in advance, Richard.
-- Best regards,
Mattijs
Mattijs Janssens
OpenCFD Ltd. The Mews, Picketts Lodge, Picketts Lane, Salfords, Surrey RH1 5RG. Tel: +44 (0)1293 821272 Email: M.Janssens@OpenCFD.co.uk URL: http://www.OpenCFD.co.uk
-- 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
-- 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 Tuesday 14 February 2006 11:46, Richard Hobbs wrote:
We have a total of 9 machines. On 7 of these machines, SuSE 10.0 fails to install using AutoYast. They all fail in the same way.
In the middle of installing the package, and with 428 packages remaining, it tries to install "emacs-21.3". It gets 56% of the way through this package, and then the machine hangs. On the other two servers, it installs perfectly. All servers are exactly the same hardware, apart from one. Here is the list:
2 Questions: if you check the proposal dialog at the beginnig of the installation (that's where you can see the partitioning and so on), is autoyast doing the correct partitioning there on the machines that fail? I'm asking that because it sounds a little bit like autoyast has not created a root partition on those machines and so the ramdisk is used as root (you might run out of memory then). Can you do manual installations on the machines that fail with autoyast? -- 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, Ah... It's the partitioning!! The Dell Servers ship with a 38MB utility partition and a 1.9GB FAT16 partition, and for some reason, AutoYast isn't wiping these partitions first. I thought the "<use>all</use>" section was the bit that said use the entire disk? Thanks, Hobbs. -- 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: 14 February 2006 10:55 To: suse-autoinstall@suse.com Subject: Re: [suse-autoinstall] Simultaneous SuSE 10.0 Autoyast installs fail!
On Tuesday 14 February 2006 11:46, Richard Hobbs wrote:
We have a total of 9 machines. On 7 of these machines, SuSE 10.0 fails to install using AutoYast. They all fail in the same way.
In the middle of installing the package, and with 428 packages remaining, it tries to install "emacs-21.3". It gets 56% of the way through this package, and then the machine hangs. On the other two servers, it installs perfectly. All servers are exactly the same hardware, apart from one. Here is the list:
2 Questions:
if you check the proposal dialog at the beginnig of the installation (that's where you can see the partitioning and so on), is autoyast doing the correct partitioning there on the machines that fail? I'm asking that because it sounds a little bit like autoyast has not created a root partition on those machines and so the ramdisk is used as root (you might run out of memory then).
Can you do manual installations on the machines that fail with autoyast?
-- 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 Tuesday 14 February 2006 12:05, Richard Hobbs wrote:
Ah... It's the partitioning!!
thought so.
The Dell Servers ship with a 38MB utility partition and a 1.9GB FAT16 partition, and for some reason, AutoYast isn't wiping these partitions first.
I thought the "<use>all</use>" section was the bit that said use the entire disk?
actually <use>all</use> should delete those partitions unless your profile makes them stay or it's some weird exception (triggered by special hardware) Do you use <initialize ...>true</initialize> to wipe out the partition table? -- 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 wasn't using <initialize> to begin with, but I have just added it into the config. Now, though, the partition table gets wiped, but no partitions get created on the first disk! Here is the <partitioning> section of the config: ============================================================ <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> <partition_id config:type="integer">131</partition_id> <partition_nr config:type="integer">1</partition_nr> <size>100mb</size> <partition_type>primary</partition_type> </partition> <partition> <filesystem config:type="symbol">reiser</filesystem> <format config:type="boolean">true</format> <mount>/</mount> <partition_id config:type="integer">131</partition_id> <partition_nr config:type="integer">2</partition_nr> <size>7000mb</size> <partition_type>primary</partition_type> </partition> <partition> <filesystem config:type="symbol">reiser</filesystem> <format config:type="boolean">true</format> <mount>/usr</mount> <partition_id config:type="integer">131</partition_id> <partition_nr config:type="integer">3</partition_nr> <size>7000mb</size> <partition_type>primary</partition_type> </partition> <partition> <filesystem config:type="symbol">swap</filesystem> <format config:type="boolean">true</format> <mount>swap</mount> <partition_id config:type="integer">130</partition_id> <partition_nr config:type="integer">5</partition_nr> <size>2048mb</size> </partition> <partition> <filesystem config:type="symbol">reiser</filesystem> <format config:type="boolean">true</format> <mount>/tmp</mount> <partition_id config:type="integer">131</partition_id> <partition_nr config:type="integer">6</partition_nr> <size>1024mb</size> </partition> <partition> <filesystem config:type="symbol">reiser</filesystem> <format config:type="boolean">true</format> <mount>/stg-dell2</mount> <partition_id config:type="integer">131</partition_id> <partition_nr config:type="integer">7</partition_nr> <size>max</size> </partition> </partitions> <use>all</use> </drive> <drive> <device>/dev/sdb</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>/mirror</mount> <partition_id config:type="integer">131</partition_id> <partition_nr config:type="integer">1</partition_nr> <size>max</size> <partition_type>primary</partition_type> </partition> </partitions> <use>all</use> </drive> </partitioning> ============================================================ Here is the partitioning I saw from within AutoYast before (roughly): ============================================================ /dev/sda (80GB) - 38MB - Dell Utility (existing) - 1.9GB - FAT16 (existing) /dev/sdb (250GB) - 250GB - reiser (proposed, and correct) ============================================================ And finally, here is the partitioning I can see now from within AutoYast, having added "<initialize>" into the config as above: ============================================================ /dev/sda (80GB) - No partitions /dev/sdb (250GB) - 250GB - reiser (proposed, and correct) ============================================================ It's almost as if it's removed the partition table, and just not bothered to create any new partitions! lol Hobsb. -- 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: 14 February 2006 11:17 To: suse-autoinstall@suse.com Subject: Re: [suse-autoinstall] Simultaneous SuSE 10.0 Autoyast installs fail!
On Tuesday 14 February 2006 12:05, Richard Hobbs wrote:
Ah... It's the partitioning!!
thought so.
The Dell Servers ship with a 38MB utility partition and a 1.9GB FAT16 partition, and for some reason, AutoYast isn't wiping these partitions first.
I thought the "<use>all</use>" section was the bit that said use the entire disk?
actually <use>all</use> should delete those partitions unless your profile makes them stay or it's some weird exception (triggered by special hardware) Do you use <initialize ...>true</initialize> to wipe out the partition table?
-- 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 Tuesday 14 February 2006 12:49, Richard Hobbs wrote:
I wasn't using <initialize> to begin with, but I have just added it into the config. Now, though, the partition table gets wiped, but no partitions get created on the first disk!
a known bug in 10.0 Try to use it only once. If you really need it on both disks, then you have to wipe out the partition table in a pre-script -- 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, Perfect. It appears to be working :-) I only needed to nuke the first hard drive, fortnuately, so I've removed <initialize> from /dev/sdb. 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: 14 February 2006 12:06 To: suse-autoinstall@suse.com Subject: Re: [suse-autoinstall] Simultaneous SuSE 10.0 Autoyast installs fail!
On Tuesday 14 February 2006 12:49, Richard Hobbs wrote:
I wasn't using <initialize> to begin with, but I have just added it into the config. Now, though, the partition table gets wiped, but no partitions get created on the first disk!
a known bug in 10.0 Try to use it only once. If you really need it on both disks, then you have to wipe out the partition table in a pre-script
-- 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
participants (3)
-
Mattijs Janssens -
Richard Hobbs -
Uwe Gansert