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