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