On Fri, Mar 2, 2012 at 4:58 AM, Uwe Gansert
On 01.03.2012 11:05, Lonni J Friedman wrote:
I'm trying to get this installed with autoyast, by mounting the ISO images on loopback, and copying the contents to a web server. Unfortunately its blowing up very early on with the error: no SUSE Linux Enterprise Server 11 repository found Automatic setup not possible
do you pxe boot? Did you update your tftp server content too then?
No, its not pxe boot. I'm booting from the DVD image kernel/initrd, and passing the following: autoyast=http://172.20.232.152/distros/suse/os/SLES11-SP2/x86/autoyastcuda.xml install=http://172.20.232.152/distros/suse/os/SLES11-SP2/x86
That error isn't terribly helpful, since I have no idea what its seeking that its not finding.
maybe it helps to set linuxrc.debug=1 and linuxrc.log=/lrc.log And check the logfile. I did many SP2 installations via HTTP, so it usually works :)
oh, i have no doubt that it works, just that it wasn't working for me. I suspect the problem may have been that I copied the contents of all 3 DVD ISO images to the same location on the web server. I ended up purging the entire thing, and copying just the 1st DVD, and its now working much better. Now I've hit a new problem, where the installation fails while trying to mount /boot, with the error "mount point /mnt/boot does not exist" (right after the partitions are formatted). I've attached a screenshot (sorry for the size). Here's the relevant portion of my autoyast.xml file: <partitioning config:type="list"> <drive> <use>all</use> <initialize config:type="boolean">true</initialize> <partitions config:type="list"> <partition> <mount>/boot</mount> <size>75mb</size> <filesystem config:type="symbol">ext2</filesystem> </partition> <partition> <mount>swap</mount> <size>1012mb</size> <filesystem config:type="symbol">swap</filesystem> </partition> <partition> <mount>/</mount> <size>max</size> <filesystem config:type="symbol">ext4</filesystem> </partition> </partitions> </drive> </partitioning> After some experimentation, I determined that this only reproduces when I specify ext4 as the filesystem. If I switch to ext3, it works fine. Is this a known bug? thanks