Date: Sun, 12 Feb 2006 08:48:05 -0500 (EST) From: Peter <petermatulis@yahoo.ca> To: Jerry McAllister <jerrymc@clunix.cl.msu.edu> Cc: freebsd-questions <freebsd-questions@freebsd.org> Subject: Re: MBR blown away Message-ID: <20060212134805.12064.qmail@web60021.mail.yahoo.com> In-Reply-To: <200602120405.k1C45LI6019502@clunix.cl.msu.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
--- Jerry McAllister <jerrymc@clunix.cl.msu.edu> wrote: > > > > > > --- Jerry McAllister <jerrymc@clunix.cl.msu.edu> wrote: > > > > > > I added a slice to a single hard drive dual-boot (windows) system > and > > > now > > > > I guess that scrambled my MBR. I get three options from the > FreeBSD > > > (5.4) > > > > boot manager: > > > > > > > > 1. DOS > > > > 2. FreeBSD > > > > 3. FreeBSD > > > > > > > > I can boot to FreeBSD (the new slice is fine) by choosing option 3 > but > > > the > > > > windows/dos option is fried. > > > > > > The MBR itself looks OK. According to that piece of menu you > > > posted, you just added another bootable slice. So, there are now two > > > bootable FreeBSD slices and one bootable Microsloth slice. > > Correct, I chose '1' and then the system hangs (no messages/errors). > > I simply converted a 6GB FAT32 partition into a UFS2 slice (chopped > > into three 2GB partitions). > Well, I still am guessing the problem lies in individual slices' boot > sectors and not the MBR. just try and set the bootable flags in the > slices the way you think they should be and see what happens. In sysinstall I toggle bootable but it puts an 'A' which seems to mean auto-bootable. I can only set one 'A' here. -- Peter __________________________________________________________ Find your next car at http://autos.yahoo.ca
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060212134805.12064.qmail>