S10u4 x86 jumpstart - Solaris

This is a discussion on S10u4 x86 jumpstart - Solaris ; I'm attempting to setup a jumpstart system for Solaris 10u4 on x86, and I've run into a pretty obnoxious problem: pxegrub spontaniously reboots the system as it's loading the OS. The system's motherboard is a 'TYAN Thunder K8S/K8SD Pro S2882', ...

+ Reply to Thread
Results 1 to 3 of 3

Thread: S10u4 x86 jumpstart

  1. S10u4 x86 jumpstart

    I'm attempting to setup a jumpstart system for Solaris 10u4 on x86,
    and I've run into a pretty obnoxious problem: pxegrub spontaniously
    reboots the system as it's loading the OS.

    The system's motherboard is a 'TYAN Thunder K8S/K8SD Pro S2882', which
    I believe is on the HCL, though as 'reported to work'. I've got a machine
    at home with the same board running S10u4 installed via DVD, so I know it
    will run Solaris if only I can get pxegrub to stop exploding on me.

    I've attempted to jumpstart a couple different machines to rule out a bad
    system, and I've tried installing over different NICs (the board has three
    onboard interfaces, 1 iprb, 2 bge) with the same result.

    Has anyone run into a similar problem?


  2. Re: S10u4 x86 jumpstart

    On Thu, 24 Jan 2008 15:48:33 -0500, I said something similar to:
    > I'm attempting to setup a jumpstart system for Solaris 10u4 on x86,
    > and I've run into a pretty obnoxious problem: pxegrub spontaniously
    > reboots the system as it's loading the OS.

    [snip]
    > 172.20.0.61 -> 172.20.0.50 TFTP Read "boot/grub/menu.lst" (octet)
    > 172.20.0.50 -> 172.20.0.61 TFTP Data block 1 (496 bytes) (last block)
    > 172.20.0.61 -> 172.20.0.50 TFTP Ack block 1
    > 172.20.0.61 -> 172.20.0.50 TFTP Read "/boot/multiboot" (octet)
    > 172.20.0.50 -> 172.20.0.61 TFTP Data block 1 (512 bytes)
    > 172.20.0.61 -> 172.20.0.50 TFTP Error: not defined
    > 172.20.0.61 -> 172.20.0.50 TFTP Read "/boot/multiboot" (octet)
    > 172.20.0.50 -> 172.20.0.61 TFTP Data block 1 (512 bytes)
    > 172.20.0.61 -> 172.20.0.50 TFTP Ack block 1
    > 172.20.0.50 -> 172.20.0.61 TFTP Data block 2 (512 bytes)
    > 172.20.0.61 -> 172.20.0.50 TFTP Read "/boot/multiboot" (octet)


    In case someone else runs into this, it seems that pxegrub doesn't
    play nice with the in.tftpd in Solaris 8 (at least not with the
    version from 108965-06). Pointing the DHCP next-server option at
    a box running a more up to date version of tftp solved the problem.

  3. Re: S10u4 x86 jumpstart

    On Mon, 28 Jan 2008 21:35:00 -0500, Mike Delaney wrote:

    > On Thu, 24 Jan 2008 15:48:33 -0500, I said something similar to:
    >> I'm attempting to setup a jumpstart system for Solaris 10u4 on x86,
    >> and I've run into a pretty obnoxious problem: pxegrub spontaniously
    >> reboots the system as it's loading the OS.

    > [snip]
    >> 172.20.0.61 -> 172.20.0.50 TFTP Read "boot/grub/menu.lst" (octet)
    >> 172.20.0.50 -> 172.20.0.61 TFTP Data block 1 (496 bytes) (last block)
    >> 172.20.0.61 -> 172.20.0.50 TFTP Ack block 1
    >> 172.20.0.61 -> 172.20.0.50 TFTP Read "/boot/multiboot" (octet)
    >> 172.20.0.50 -> 172.20.0.61 TFTP Data block 1 (512 bytes)
    >> 172.20.0.61 -> 172.20.0.50 TFTP Error: not defined
    >> 172.20.0.61 -> 172.20.0.50 TFTP Read "/boot/multiboot" (octet)
    >> 172.20.0.50 -> 172.20.0.61 TFTP Data block 1 (512 bytes)
    >> 172.20.0.61 -> 172.20.0.50 TFTP Ack block 1
    >> 172.20.0.50 -> 172.20.0.61 TFTP Data block 2 (512 bytes)
    >> 172.20.0.61 -> 172.20.0.50 TFTP Read "/boot/multiboot" (octet)

    >
    > In case someone else runs into this, it seems that pxegrub doesn't
    > play nice with the in.tftpd in Solaris 8 (at least not with the


    Indeed, just copy the version from an S9 box, it works fine. Or upgrade
    your JumpStart to S9/S10


    > version from 108965-06). Pointing the DHCP next-server option at a box
    > running a more up to date version of tftp solved the problem.


    --
    Bruce

    "The internet is a huge and diverse community and
    not every one is friendly"
    http://www.ytc1.co.uk


+ Reply to Thread