Re: [Testbed-admins] Booting error in Customizing the Generic Image

["'Ryan Jackson'" <rdjackso@flux.utah.edu>]

* Cheng Cui <ccui1@tigers.lsu.edu> [091113 17:31]:
> It looks I got the reason. The whole-disk image (BSD+linux.ndz) must be
> copied into disk first, then, any separate images can be copied into the
> disk and they work. I tested it by reformat my hard disk, then, a
> separate image copy does not work, but once the whole disk image copy is
> committed, the following separated copy could work. Please refer to my
> attached file on detail.

Thanks.  I'll take a look at this later tonight to make sure
everything looks sane.

> In the one month ago question, my BSD MFS can't recognize my local image
> by the "part:1", but if I directly boot the PC from disk, it works. So
> that's why Mike want me to test a linux admin MFS now. And I really want
> to know if the customized image under Linux admin MFS can be booted
> successfully. Am I right?


Ah, right.  I forgot about all that.  Sorry. Anyway, here's how to
boot a partition manually:

1. Reboot the node and watch the console for the message 'Press ESC
for GRUB menu'.  When it appears press ESC.

2. When the menu comes up press 'c' for a Grub command line.

3. At the command line, enter the following commands ('x' is the
partition number you want to boot):

set bootinfo.orig_root=hd0,x
bootinfo_magic
boot

This uses some code we added to Grub to automatically figure out what
kind of partition hd0,x is and how to boot it.  the 'bootinfo_magic'
command should display some output detailing this information.  If
things don't work as you expect you could send me a screenshot of
this.

I realize that currently this is a bit more awkward than typing
'part:1', but it'll hopefully be simpler soon.

I'll be in the office tomorrow, so let me know if you have any more
problems this weekend (if you're working this weekend, that is).  Glad
that we've got this (nearly) working for you.