Re: [Testbed-admins] MFS images, Generic Images, and customization

[Ben Burnett <bburnett@atcorp.com>]

ok, moving the nodes to HWDOWN worked to get interactive mode.   I am
now using pxeboot.emu-vga (we don't have our tips server running yet,
to use sio) ...

so we've tried to boot both partitions, and they both fail, here is
what happens:

Results from
Part:1   (FreeBSD)

Loading MBR and booting system partition 1
Pxe-end failed 1

BTX loader 1.00 BTX version is 1.01
Console: internal video/keyboard
BIOS drive c: is disk0
BIOS 640kB.......

FreeBSD/i386 boostrap loader, rev 1.1
(root@node.newimage.em........
Loading /boot/defaults/loader.conf

And there is where it stops and does nothing more
ping from boss... nothing, times out
ssh from boss... nothing, times out



Results from
Part:2  (sysid 131)    (Linux)

Enter boot spec sysid:131
Boot
Loading MBR and booting system 131
GRUB loading stage 2
Press any key to continue
Press any key to continue
Press any key to continue
Press any key to continue
Press any key to continue
Uncompressing linux...ok, booting the kernel

Then It does nothing
Unable to slogin from console(boss)
ping from boss... nothing, times out
ssh from boss... nothing, times out



Any help/ideas?   has anyone seen this behavior before?

Thanks,
--Ben




Ben Burnett
  R&D Software Engineer: wired, wireless, ad hoc, mesh networking,
    network monitoring and data visualization
  ATC (Architecture Technology Corporation)   http://www.atcorp.com/
  bburnett@atcorp.com                         (952) 829-5864 x167
  --------Views expressed are mine and not those of ATC--------
  Personal:
    ben@burnett.ws                            http://www.burnett.ws/
http://ben.burnett.ws/
http://www.linkedin.com/in/benburnett



On Thu, Jun 25, 2009 at 7:04 AM, Jonathan
Walsh<jonathan.d.walsh@lmco.com> wrote:
> Leigh Stoller wrote:
>>>
>>> It is in "reloading" I'm guessing it needs to be in "hwdown"...  do
>>> I move the node into hwdown with nfree? or is there another way?
>>
>> If it is in reloading, you should be able to boot it. Take a look at
>> /usr/testbed/log/bootinfo.log to see if pxeboot is getting far enough
>> to query it.
>>
>> But probably best to move it to hwdown:
>>
>> boss> wap sched_reserve emulab-ops hwdown pcXXX
>> boss> wap nfree emulab-ops reloading pcXXX
>>
>>> So what do I lose by using pxeboot.emu-null instead of pxeboot.emu-sio
>>> or pxeboot.emu-vga?
>>
>> I think it means no console, output goes into the bit bucket. :-)
>>
>> Lbs
>>
>> _______________________________________________
>> Testbed-admins mailing list
>> Testbed-admins@flux.utah.edu
>> http://www.flux.utah.edu/mailman/listinfo/testbed-admins
>
> Ben,
>
> I have some machines that are pretty similar to yours, and I was able to
> boot using pxeboot.emu-sio successfully.  Is that failing for you in
> some way?  It is going to be harder to work without console or vga...
>
> -Jonathan
>
>