I haven't done autoyast installations myself for quite a long time, so I might be wrong, but here is my comment. On Tue, 10 Feb 2004, Tom Davidson wrote:
2) *serious* I'm installing on servers ranging from HP DL360 G2/G3s up to possible DL580s (developing on a DL360 G2). The raid controller is detected and the module loaded fine, but when it comes to allocating the partitioning, it fails saying "no free space available on /dev/cciss/c0d0". There will be partitions on there as I've constantly rebuilding testing, but it shouldn't care as I've specified <use>all</use> for the disk
If there are already partitions on the disk, if I remember correctly then you should also set <reuse>all</reuse>, otherwise old partitions won't be deleted.
3) *serious* I've got a number of partitions configured, including a fixed size of swap (I've included my autoinstall file at the end - apologies for the length). / gets configures as a primary, and I let YaST sort out the rest, which numbers swap c0d0p9. So from issue 3 above, when it installs over a blank disk, it successfully creates all the filesystem partitions, but moans about being unable to create swap with another very unhelpful error message: "could not set up swap partition /dev/cciss/c0d0p9". Why should it successfully create everything but swap? It's not a space issue (they have 18Gb disks), because the "max" setting for /usr/local gobbles up the space that swap should have taken.
In your partition layout, the partition with size "max" must be the last one. I.e. you can't have partition 8 as "max" and create partition 9 behind it. To make /usr/local fill all remaining space you would have to place it at the end of your disk. -- Volkmar Glauche - Department of Neurology E-Mail glauche@uke.uni-hamburg.de UKE Hamburg Phone 49(0)40-42803-5781 Martinistr. 52 Fax 49(0)40-42803-9955 20246 Hamburg