Re: [Testbed-admins] panic: Could not load/verify partition X boot record

[Mike Hibler <mike@flux.utah.edu>]

If it happens for both part 1 and 2 then it sounds like the MBR partition
table is not in synch with where the partitions actually are, or the BIOS
read routines are not working correctly.  Boot a node into the admin MFS
(on boss: "node_admin on pcXXX") and then use "fdisk" to make sure it can
read the MBR and then maybe try "fsck -n /dev/da0s1[aef]" to see if it can
find the partitions.

On Fri, Jun 25, 2010 at 02:44:06PM -0700, Chris Benninger wrote:
> Hi,
> 
> I completed the steps where you setup your *-STD.ndz images (a couple times
> over) and none of my nodes will boot either OS from the FBSD62+FC6-STD.ndz
> image.
> 
> When i fire up an experiment (or run part:1/part:2 from the tftp prompt) the
> node spits out:
> 
> Loading MBR and booting system partition 2
> panic: Could not load/verify partition 2 boot record
> -- Press a key to reboot --
> 
> Any Ideas? Ive regenerated the images a few times thinking that I missed a
> step but I'm confident now that I did it correctly.
> 
> Thanks
> 
> 
> -- 
> Chris Benninger
> University of Victoria, Computer Science
> cbenning@cs.uvic.ca
> http://syfor.com
> 
> -- 
> This message has been scanned for viruses and
> dangerous content by MailScanner, and is
> believed to be clean.
> 

> _______________________________________________
> Testbed-admins mailing list
> Testbed-admins@flux.utah.edu
> http://www.flux.utah.edu/mailman/listinfo/testbed-admins