Re: [Testbed-admins] Can't boot after imageunzipping a customized image

[Ben Burnett <bburnett@atcorp.com>]

Leigh,
    we did that process: loaded pc2 with GENERIC then imaged it to
foo, then loaded pc3 with foo.  pc3 has the same initial boot problems
that pc2 has and the same ones we described before (Fedora panics,
FreeBSD buts ok, but is mapping the wrong drives ad's instead of da's
[bad fstab])

but the point is the booting works fine, so the MBR was copied
correctly.  do you want us to still send the foo.ndz?  for you to look
at?

Any other things we can do to test the MBR and/or get the settings
correct so we don't have to use raw compressions?

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 Tue, Jul 21, 2009 at 1:03 PM, Leigh Stoller<stoller@flux.utah.edu> wrote:
>> We've created and customized the images described in the
>> documentation, then imagezipped them back to create the ndz files on
>> boss.  but whenever we unzip them to another pc to try to boot them
>> into the new OS, the interactive mode prompt either doesn't
>> recognize the OS on the drive, or doesn't see it as bootable.  is
>> the master boot record getting copied correctly?  what information
>> can I send for you to look at to see?
>>
>> Also when we unzipped the fedora core 8 image onto the FBSD62+FC8
>> machine then remade the new image, imagezip couldn't determine the
>> superblock saw raw compression was needed.  same was true for CentOS
>> and WinXP, all are being forced to use raw compression.  this is
>> extremely slow, is there a better way to determine what compression to
>> use, is there a command line option for imagezip to specify it?
>
> I think all of these problems are related to one thing; the MBR on the
> disk is getting whacked somehow. Its my best theory at the moment,
> without being able to look at it myself.
>
> So lets do this. Lay down the generic image. Make sure it boots. Then
> boot into the admin MFS, and imagezip it with this:
>
> boss> wap node_admin on pcXXX
> boss> cd /usr/testbed/images
> boss> sudo ssh pcXXX imagezip /dev/$DSK - > foo.ndz
>
> Then lay that image back down:
>
> boss> sudo ssh pcXXX imageunzip - /dev/$DSK < foo.ndz
> boss> wap node_admin off pcXXX
>
> If the node does not boot, please upload foo.ndz to your account in
> Utah. You will have to put in /proj/AirNet/images cause of quota.
>
> Lbs
>
>
>