[yast-devel] Problems with autoyast from sles10 to sles10 sp1....
Yast Developers, My customer took their sles10 GA autoyast which was working great and tried it on sles10 sp1. It's failing. I'm attaching a tarred gzip of yast logs and contro.xml file. Here is customer writeup: The problem I am seeing is with respect to the disk partitioning. During the auto install, I get the error "Error with partition plan". The control files I am using are no different from those I used with our SLES 10 SP0 media, so I am thinking there are some changes to autoyast that are causing this. I double checked the online documentation but couldn't find anything that might cause this. Interestingly enough, if I initialize the disk via the RAID BIOS, the install will go through. However, if I have a service partition installed, it will fail. The control file we use asks autoyast to initialize the disks, effectively destroying the partition table, so I am not sure why this would be a problem. Again, this worked fine in SLES 10 SP0. I have included a zip file with our logs and control files. Any help would be greatly appreciated. I've looked at the y2log file and the only errors I see are these: 2007-09-28 16:06:34 <3> linux(3121) [bash] ShellCommand.cc(shellcommand):78 error: cannot open Packa ges index using db3 - No such file or directory (2) 2007-09-28 16:06:34 <3> linux(3121) [bash] ShellCommand.cc(shellcommand):78 error: cannot open Packa ges database in /var/lib/rpm -robert
Hi Roberto! I suggest to open a bug report for this. Stano Dňa Monday 01 October 2007 20:41:34 Roberto Angelino ste napísal:
Yast Developers, My customer took their sles10 GA autoyast which was working great and tried it on sles10 sp1. It's failing. I'm attaching a tarred gzip of yast logs and contro.xml file. Here is customer writeup:
The problem I am seeing is with respect to the disk partitioning. During the auto install, I get the error "Error with partition plan". The control files I am using are no different from those I used with our SLES 10 SP0 media, so I am thinking there are some changes to autoyast that are causing this. I double checked the online documentation but couldn't find anything that might cause this. Interestingly enough, if I initialize the disk via the RAID BIOS, the install will go through. However, if I have a service partition installed, it will fail. The control file we use asks autoyast to initialize the disks, effectively destroying the partition table, so I am not sure why this would be a problem. Again, this worked fine in SLES 10 SP0. I have included a zip file with our logs and control files. Any help would be greatly appreciated.
I've looked at the y2log file and the only errors I see are these:
2007-09-28 16:06:34 <3> linux(3121) [bash] ShellCommand.cc(shellcommand):78 error: cannot open Packa ges index using db3 - No such file or directory (2) 2007-09-28 16:06:34 <3> linux(3121) [bash] ShellCommand.cc(shellcommand):78 error: cannot open Packa ges database in /var/lib/rpm
-robert
-- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
On Monday 01 October 2007 20:41, Roberto Angelino wrote:
initialize the disk via the RAID BIOS, the install will go through. However, if I have a service partition installed, it will fail. The control file we use asks autoyast to initialize the disks, effectively destroying the partition table, so I am not sure why this would be a problem.
the initialize tag in SP1 is broken. It does not wipe out the partition table. You can find a fix-script here: ftp://ftp.suse.com/pub/people/ug/autoyast If you run the script a driverupdate file is created which has to be copied to the root of the installation source. Then it should work again (if that is the only problem). -- ciao, Uwe Gansert Uwe Gansert, Server Technologies Team SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Business: http://www.suse.de/~ug -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
participants (3)
-
Roberto Angelino -
Stanislav Visnovsky -
Uwe Gansert