On Fri, Mar 2, 2012 at 4:58 AM, Uwe Gansert <ug@suse.de> wrote:

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

On Mon, Mar 5, 2012 at 1:52 AM, Uwe Gansert <ug@suse.de> wrote:

On 05.03.2012 09:46, Lonni J Friedman wrote:

...

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:

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?

it's a known limitation of SLES11 SP2. We support ext4 only in read only mode. I know you were able to format the disk with ext4 - let's call that a flaw in the autoyast partitioning calculation. It should have failed before the formatting.

OK, thanks. -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-autoinstall+owner@opensuse.org

On Tue, Mar 13, 2012 at 03:22:19PM -0700, Lonni J Friedman wrote:

While I'd love to chalk this up to some weird kvm bug, the only Linux distro exhibiting this problem is SLES11-SP2. It works fine with the latest releases from RHEL, Fedora, Ubuntu, and even OpenSUSE(-12.1).

I had this issue (well, not sure it wasn't set to boot, but grub wouldn't load stage 2) with a pre-release and kvm. However the GA has been fine. -- Mike Marion-Unix SysAdmin/Staff IT Engineer-http://www.qualcomm.com "DOS Computers manufactured by companies such as IBM, Compaq, Tandy, and millions of others are by far the most popular, with about 70 million machines in use worldwide. Macintosh fans, on the other hand, may note that cockroaches are far more numerous than humans, and that numbers alone do not denote a higher life form." -- New York Times article -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-autoinstall+owner@opensuse.org

So no suggestions on how to resolve this? On Tue, Mar 13, 2012 at 3:22 PM, Lonni J Friedman <netllama@gmail.com> wrote:

On Tue, Feb 28, 2012 at 2:14 AM, Uwe Gansert <ug@suse.de> wrote:

...

Moin,

JFYI - SLES11 SP2 is ready for download http://www.suse.com/de-de/products/server/eval.html

The AutoYaST changes to SP1 can be found here: http://www.suse.de/~ug/autoyast_changes_SLES11SP2.html

I'm seeing a strange problem when installing SLES11-SP2 inside of a kvm (virtualized) environment using autoyast.  The OS installs fine, but when it reboots afterwards, kvm can't find an active partition to boot from.  Sure enough when I run fdisk on the OS image file, none of the partitions have the 'boot' flag set:

######### Disk cuda-linux64-build17.img: 116.0 GB, 115964116992 bytes 255 heads, 63 sectors/track, 14098 cylinders, total 226492416 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x000f3e90

                  Device Boot      Start         End      Blocks   Id  System cuda-linux64-build17.img1           2048   226492415   113245184    f W95 Ext'd (LBA) cuda-linux64-build17.img5           4096      159743       77824   83  Linux cuda-linux64-build17.img6          161792     2248703     1043456   82  Linux swap / Solaris cuda-linux64-build17.img7         2250752   226467839   112108544   83  Linux ########

I tried to manually set the boot flag to the very first partition (which is what gets set for a non-virtualized installation), but all that seemed to do was change the "no active partition" error to a "no bootable OS" error.

Here's what the partitioning and bootloader sections of my autoyast.xml file look like:

<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">ext3</filesystem>          </partition>        </partitions>     </drive>     </partitioning>        <bootloader>              <global config:type="list">                <global_entry>                  <key>prompt</key>                  <value config:type="boolean">false</value>                </global_entry>                <global_entry>                        <key>default</key><value>0</value>                </global_entry>                <global_entry>                        <key>timeout</key><value>3</value>                </global_entry>              </global>                <kernel_parameters>console=ttyS0,115200 console=tty0 </kernel_parameters>              <loader_device></loader_device>              <loader_type>grub</loader_type>              <location>mbr</location>              <sections config:type="list"/>        </bootloader>

While I'd love to chalk this up to some weird kvm bug, the only Linux distro exhibiting this problem is SLES11-SP2.  It works fine with the latest releases from RHEL, Fedora, Ubuntu, and even OpenSUSE(-12.1).

help?

thanks -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-autoinstall+owner@opensuse.org