> 
> > Try mounting and reading some of the stuff from that disk and
> > see if you can get to it.
> >
> > Then try     boot0cfg(8)
> 
> 
> I dont know what this option means - does this matter?
> 
>      -B      Install the `boot0' boot manager.  This option causes MBR
> code to
>              be replaced, without affecting the embedded slice table.

Sounds like just what you said you wanted.

By the way, I notice that you have quit CC-ing the questions list.
You should keep that in so it gets in archives and so I don't become
the sole counselor - which you don't want, for sure!

////jerry

> 
> - Noah
> 
> 
> >
> > ////jerry
> >
> > > ******* Working on device /dev/ad2 *******
> > > parameters extracted from in-core disklabel are:
> > > cylinders=148945 heads=16 sectors/track=63 (1008 blks/cyl)
> > >
> > > Figures below won't work with BIOS for partitions not in cyl 1
> > > parameters to be used for BIOS calculations are:
> > > cylinders=148945 heads=16 sectors/track=63 (1008 blks/cyl)
> > >
> > > Media sector size is 512
> > > Warning: BIOS sector numbering starts with sector 1
> > > Information from DOS bootblock is:
> > > The data for partition 1 is:
> > > sysid 165,(FreeBSD/NetBSD/386BSD)
> > >     start 63, size 150136497 (73308 Meg), flag 80 (active)
> > >         beg: cyl 0/ head 1/ sector 1;
> > >         end: cyl 464/ head 15/ sector 63
> > > The data for partition 2 is:
> > > <UNUSED>
> > > The data for partition 3 is:
> > > <UNUSED>
> > > The data for partition 4 is:
> > > <UNUSED>
> > >
> > >
> > >
> >
> 
> 


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-questions" in the body of the message

Reply via email to