various problems with SLSS
I've got a number of problems with SLSS autoinstall, ranging from minor to
serious:
1) *minor* Somewhere, somehow, the initial part of the textmode (and prolly
X) installer runs in German. It switched to English as configured once it
has the autoinstall XML file. But it hald reverts to German when installing
the RPMs, as the descriptions are in German. The resulting box is installed
in English OK however.
I'm installing via PXE, and I haven't specified anything on the append line
for language, but even if I specify on it, I still get the same.
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
/dev/cciss/c0d0 (configured in RAID 1 obviously). This is a pretty unhelpful
error message for debugging purposes - where can I suitable logging to tell
me why this fails? I've looked in /var/adm/autoinstall, /var/log/YaST2,
/tmp/YaST2-####/pre-scripts. Where else does stuff get logged?
I've tried a pre-install script hack of dd if=/dev/zero of=/dev/cciss/c0d0
bs=1024 count=1, and it doesn't work when booting with a system that already
has partitions - presumably these must get cached earlier on somewhere (a
bad practice IMHO). But if I abort the installation, or reboot and try
again, nothing is there to get cached, and it half works, which brings me on
to the third problem.
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.
4) *concerning* I install SP3 via a finish script that is called from the
finish script in the autoinstall file as below. However, when I install it,
the kernel it installs hangs on reading the partition table for
/dev/cciss/c0d0. I've narrowed this down to acpi, so I've put acpi=off into
the kernel parameters section on the autoinstall file, but I'm certain that
it shouldn't do that!
Please can anyone help with these, especially the serious ones. I'm sure I
have more, but I can't think of them right now...
Cheers,
Tom
<?xml version="1.0"?>
<!DOCTYPE profile SYSTEM "/usr/share/YaST2/include/autoinstall/profile.dtd">
<profile xmlns="http://www.suse.com/1.0/yast2ns"
xmlns:config="http://www.suse.com/1.0/configns">
<configure>
<users config:type="list">
<user>
<encrypted config:type="boolean">false</encrypted>
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
participants (2)
-
Tom Davidson
-
Volkmar Glauche