Re: mbr loader
On Wednesday 08 December 2010 22:08:56 xinyou yan wrote: > 1. when i install freebsd . I can write mbr and not write > if i write mbr . freebsd can Identification windows and load it first, you are talking about boot loaders or boot managers; its different from MBR witch means master boot record When you say "FreeBSD can identify windows and load it", you have wrong the concept of FreeBSD can identify, because FreeBSD its not loaded yet, a program called BootEasy its the one identifying windows (an others OS) and display F1: Windows etc.. > > 2 if i do not write . How windows load bsd http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/disks.html#NT-BOOTLOADER > > 3. Can freebsd load linux (fedora)? and how ? http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/disks.html#BOOTEASY- LOADER Look in ports for boot loaders (manager) http://www.freebsd.org/cgi/ports.cgi?query=boot+loader&stype=text&sektion=all http://www.freebsd.org/cgi/ports.cgi?query=boot+manager&stype=text&sektion=all Its a good idea to read Chapter 9 (Disks, File Systems, and Boot Loaders) of FAQ http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/disks.html HTH ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: mbr loader
On 12/09/10 15:08, xinyou yan wrote: 1. when i install freebsd . I can write mbr and not write if i write mbr . freebsd can Identification windows and load it 2 if i do not write . How windows load bsd 3. Can freebsd load linux (fedora)? and how ? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org" I can't remember winblow$ method, but I know fedora can load BSD. I have a temporary setup to test my new bright shiny AND STABLE FreeBSD media server (many thanks to all those involved in getting dvb cards working on BSD), but I have left the default F10 setup so I can iron out bugs and still have a tv if it breaks. So I setup grub.conf- the man pages are rather useful, but the long and the short of it is that its simple to work out: Name the system you want to boot, and provide a root for it. Don't chainload. So the core of it (from memory mind, so check the man and anyone else correct the errors) was as follows: title FreeBSD 8.1 root(hd 1,a) Root will vary according to your needs. Mine was on a second disk, slice 1a. I assume from what you have said regarding BSD loading winblow$ that the reverse (BSD load linux) would be true too in the same fashion. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: MBR blown away
Peter wrote: --- Jerry McAllister <[EMAIL PROTECTED]> wrote: --- Jerry McAllister <[EMAIL PROTECTED]> 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 I tend to agree with Jerry and others that the problem is not with the MBR, but with the Windows boot sector in the first partition. If that's true, you can't fix it with sysintall or FreeBSD. You have fix it with Windows tools. If you were running Windows 2000 or XP in the Windows partition, I would recommend that you use the Windows 2000 System Recovery Console and run the fixboot program to install a new Windows boot sector on the Windows partition. If you're running an older version of Windows, you need to find out what tool it uses to restore a boot sector. Chances are in the process you'll wipe out the FreBSD MBR which you'll have to fix using FreeBSD. I guess that's where boot0cfg comes in, but I've never used it. The best advice, though, is to backup everything you can before proceeding. -- Ken Stevenson Allen-Myland Inc. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: MBR blown away
--- Jerry McAllister <[EMAIL PROTECTED]> wrote: > > > > > > --- Jerry McAllister <[EMAIL PROTECTED]> 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 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: MBR blown away
> Date: Fri, 10 Feb 2006 21:19:07 -0500 (EST) > From: Peter <[EMAIL PROTECTED]> > Subject: MBR blown away > To: freebsd-questions > Message-ID: <[EMAIL PROTECTED]> > Content-Type: text/plain; charset=iso-8859-1 > > I need help. > > 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. > > My current strategy is to use boot0cfg: > > # boot0cfg -B > > But I'm a little squeemish. I don't want to be locked out of FreeBSD (I > barely use Windows but I still would like it back for Visio). Any > guidance? Start by making a full backup of your FreeBSD installation. Then you'll feel less squeamish about whatever you do next. Jim ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: MBR blown away
> > > --- Jerry McAllister <[EMAIL PROTECTED]> wrote: > > > > > > > I need help. > > > > > > 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. > > > The thing is, I never ran the boot manager after changing the (existing > FAT32) windows partition to a FreeBSD slice. The boot manager config > would be the same and so it continues to list DOS as a bootable partition > when it is/may not. > > > Are you saying that the MS slice will no longer boot if you select '1' > > from > > the menu?If that is the case, it is not the MBR that was messed up. > > > Correct, I chose '1' and then the system hangs (no messages/errors). > > > It is something in the MS slice - probably their boot sector. I don't > > even > > pretend to know how MS sets up theirs if it is any different from > > FreeBSD. > > > > But, the MBR is doing what it is supposed to do. It discovers all the > > bootable slices and makes a menu and transfers control to the selected > > slice. What happens after that is not the problem of the MBR. > > > I don't think the MBR discovers anything. It is pre-defined to just point > to the bootable partitions. And it is the boot manager that creates the > menu probably by looking at the MBR. AFAIK, the boot manager must be > explicitly instructed to do that (sysintall must provide this instruction > during a full install). > > > Did you use some utility to shrink the original two slices to fit in > > the new one? Or was there already unused space (previously unallocated) > > that you were using? > > 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. jerry > > -- > Peter > > > > > > > __ > Find your next car at http://autos.yahoo.ca > ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: MBR blown away
--- Jerry McAllister <[EMAIL PROTECTED]> wrote: > > > > I need help. > > > > 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. The thing is, I never ran the boot manager after changing the (existing FAT32) windows partition to a FreeBSD slice. The boot manager config would be the same and so it continues to list DOS as a bootable partition when it is/may not. > Are you saying that the MS slice will no longer boot if you select '1' > from > the menu?If that is the case, it is not the MBR that was messed up. Correct, I chose '1' and then the system hangs (no messages/errors). > It is something in the MS slice - probably their boot sector. I don't > even > pretend to know how MS sets up theirs if it is any different from > FreeBSD. > > But, the MBR is doing what it is supposed to do. It discovers all the > bootable slices and makes a menu and transfers control to the selected > slice. What happens after that is not the problem of the MBR. I don't think the MBR discovers anything. It is pre-defined to just point to the bootable partitions. And it is the boot manager that creates the menu probably by looking at the MBR. AFAIK, the boot manager must be explicitly instructed to do that (sysintall must provide this instruction during a full install). > Did you use some utility to shrink the original two slices to fit in > the new one? Or was there already unused space (previously unallocated) > that you were using? I simply converted a 6GB FAT32 partition into a UFS2 slice (chopped into three 2GB partitions). -- Peter __ Find your next car at http://autos.yahoo.ca ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: MBR blown away
Jerry McAllister wrote: I need help. 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. Are you saying that the MS slice will no longer boot if you select '1' from the menu?If that is the case, it is not the MBR that was messed up. It is something in the MS slice - probably their boot sector. I don't even pretend to know how MS sets up theirs if it is any different from FreeBSD. But, the MBR is doing what it is supposed to do. It discovers all the bootable slices and makes a menu and transfers control to the selected slice. What happens after that is not the problem of the MBR. That may be bad news, I suppose. It might be easier to fix the MBR than the MS slice boot code if it is actually messed up. It might be as simple as you managed to mark the MS slice as not bootable in some way, but in that case, I wouldn't expect the MBR to be able to see that slice and put it in the menu as bootable. Did you use some utility to shrink the original two slices to fit in the new one? Or was there already unused space (previously unallocated) that you were using?Maybe the utility you used to shrink the other slices messed something up.You might need to go back to it and check it out. Was the MS slice an NTFS type file system? Many of the free utilities for resizing slices do not work properly on NTFS systems. So, it is possible, in that case, that the MS slice was not shrunk properly and so it got trashed at that stage. Just some thing to consider. Good luck, jerry My current strategy is to use boot0cfg: # boot0cfg -B But I'm a little squeemish. I don't want to be locked out of FreeBSD (I barely use Windows but I still would like it back for Visio). Any guidance? As per my comments above, I don't think rewriting the MBR will help any. /jrm -- Peter Hi, Just out of curiosity, did you try using sysinstall again to take a look at things? Maybe you can mark your Windows partition bootable? Trying this might at least tell you whether your Windows slice is "fried" or not. I know I seem to have some sort of trouble along these lines every time I do a fresh install because I'm always trying to run so many different systems on one machine. Windows just doesn't play nice. But so far I have always been able to get things straightened out. --Duane ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: MBR blown away
> > I need help. > > 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. Are you saying that the MS slice will no longer boot if you select '1' from the menu?If that is the case, it is not the MBR that was messed up. It is something in the MS slice - probably their boot sector. I don't even pretend to know how MS sets up theirs if it is any different from FreeBSD. But, the MBR is doing what it is supposed to do. It discovers all the bootable slices and makes a menu and transfers control to the selected slice. What happens after that is not the problem of the MBR. That may be bad news, I suppose. It might be easier to fix the MBR than the MS slice boot code if it is actually messed up. It might be as simple as you managed to mark the MS slice as not bootable in some way, but in that case, I wouldn't expect the MBR to be able to see that slice and put it in the menu as bootable. Did you use some utility to shrink the original two slices to fit in the new one? Or was there already unused space (previously unallocated) that you were using?Maybe the utility you used to shrink the other slices messed something up.You might need to go back to it and check it out. Was the MS slice an NTFS type file system? Many of the free utilities for resizing slices do not work properly on NTFS systems. So, it is possible, in that case, that the MS slice was not shrunk properly and so it got trashed at that stage. Just some thing to consider. Good luck, jerry > My current strategy is to use boot0cfg: > > # boot0cfg -B > > But I'm a little squeemish. I don't want to be locked out of FreeBSD (I > barely use Windows but I still would like it back for Visio). Any > guidance? As per my comments above, I don't think rewriting the MBR will help any. /jrm > > -- > Peter > > > > > > > __ > Find your next car at http://autos.yahoo.ca > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > > ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: MBR blown away
Peter wrote: I need help. 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. My current strategy is to use boot0cfg: # boot0cfg -B But I'm a little squeemish. I don't want to be locked out of FreeBSD (I barely use Windows but I still would like it back for Visio). Any guidance? -- Peter This article might provide a clue: http://www.extremetech.com/article2/0,1697,1918391,00.asp -- Ken Stevenson Allen-Myland Inc. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: MBR blown away
Peter wrote: I need help. 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 would think that the appearance of the above menu, and the fact that it functions correctly when you choose FreeBSD indicates that the MBR is intact. I would presume, then, that the Windows partition has been damaged. If the file system the Windows partition is healty in general with just a few files in the boot sequence being damaged or missing you should be able to re-install Windows in that partition and find all your data and applications present and in good shape. If however the filesystem in the Windows partition is messed up you may have lost everything. If you do re-install windows it will probably replace the MBR that is there with what Windows consideres to be a 'standard' MBR. I think you can use dd to copy the MBR that is currently there. Then to get back to FreeBSD you'll have to use fdisk to set the active partition to FreeBSD. Then you can, hopefully, restore the MBR you saved. I can boot to FreeBSD (the new slice is fine) by choosing option 3 but the windows/dos option is fried. My current strategy is to use boot0cfg: # boot0cfg -B But I'm a little squeemish. I don't want to be locked out of FreeBSD (I barely use Windows but I still would like it back for Visio). Any guidance? -- Peter __ Find your next car at http://autos.yahoo.ca ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: mbr and boot disks?
> > Mark wrote: > > > I am currently dual booting between windows and freebsd but I need to > > reinstall windows on the other partition. How do I create a freebsd boot > > disk so that after windows rewrites my mbr I can still get back to bsd? > > Then how would I re-install freebsd's boot manager so I can continue to > > dual boot? > > Hello Mark, > > use disc1* of FreeBSD. Boot from CD-ROM and choose "Fixit" and then > "CDROM/DVD" and run "boot0cfg -B /dev/ad0". That's it. > > *) The live filesystem is on disc2 if you use FreeBSD 5.3 or previous > versions. That should work, but if at all possible, make a good backup with dump(8) before getting started. jerry > Regards > Björn > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > > ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: mbr and boot disks?
Mark wrote: I am currently dual booting between windows and freebsd but I need to reinstall windows on the other partition. How do I create a freebsd boot disk so that after windows rewrites my mbr I can still get back to bsd? Then how would I re-install freebsd's boot manager so I can continue to dual boot? Hello Mark, use disc1* of FreeBSD. Boot from CD-ROM and choose "Fixit" and then "CDROM/DVD" and run "boot0cfg -B /dev/ad0". That's it. *) The live filesystem is on disc2 if you use FreeBSD 5.3 or previous versions. Regards Björn ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: MBR not overwritable with dd?
Am Montag, 11. Oktober 2004 04:37 schrieb Jerry McAllister: > > I tried to null out the MBR with the BETA7 fixit CD with the follwoing=20 > > command: > > dd if=3D/dev/zero of=3D/dev/ad0 count=3D16 > > > > After that fdsik still showed me a valid partition tabel! > > How? Does GEOM map the beginning of the raw device? > > Was it getting it from the in-memory informatino? After a lowlevel format fdisk still showed me a partition in slice 1 with id 165. So fdisk is misbehaving here. A hexdump of the first 512 Bytes validated that fdisk is wrong. Another question is why does sysinstall complain about wrong geometry? It claims the CHS values, but why? I heard that it's the fault of "other OSes" becaus they're writing wrong info onto the disk. But this disk has nothing but NULLs on it and sysinstall is presenting CHS values, also fdisk reads CHS Values "from in-core labels". Can anybody entlighten me what in-core labels are? Then there's another error in sysinstall but I'll post that on current (when creating two slices, the partition table ends up in having two active entries) Thanks, -Harry > > jerry > > > Thank you in advance, > > ___ > [EMAIL PROTECTED] mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to > "[EMAIL PROTECTED]" pgpQlP37pstJk.pgp Description: PGP signature
Re: MBR not overwritable with dd?
> > I tried to null out the MBR with the BETA7 fixit CD with the follwoing=20 > command: > dd if=3D/dev/zero of=3D/dev/ad0 count=3D16 > > After that fdsik still showed me a valid partition tabel! > How? Does GEOM map the beginning of the raw device? Was it getting it from the in-memory informatino? jerry > > Thank you in advance, > ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: MBR problem.
if you have the FAQ installed, check the question 3.9. Windows 95/98 killed my boot manager! How do I get it back? file:/usr/share/doc/faq/install.html#WIN95-DAMAGED-BOOT-MANAGER or give a try to the question 9.10. How can I use the NT loader to boot FreeBSD? file:/usr/share/doc/faq/disks.html#NT-BOOTLOADER -HTH maps On Wednesday 22 September 2004 19:12, Eric Boucher wrote: > Hi, > > I have this problem. I was using FreeBSD 5.1 along > with Windows XP for a while. I had to re-install > Windows for some reasons. Before the re-installation, > I was using the dual boot system from FreeBSD (the one > with which you have to choose with the "F" keys the OS > you want to boot). But when I re-installed Windows, > the MBR seems to be reseted so that now, I can only > boot Windows (even if my FreeBSD is still on my > machine, because I re-installed Windows on the same > partition it was). Is there a way, with the FreeBSD CD > or something, to re-initialise the MBR so that I can > see both FreeBSD and Windows (or to be like when you > install a fresh copy of FreeBSD after installing it > after Windows )? > > Thanks, > > Eric > > > > __ > Do you Yahoo!? > Read only the mail you want - Yahoo! Mail SpamGuard. > http://promotions.yahoo.com/new_mail > ___ > [EMAIL PROTECTED] mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to > "[EMAIL PROTECTED]" ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: MBR problem with FreeBSD 5.3 beta
Whats your motherboard make and BIOS version? Off late I have seen some Phoenix BIOS incorporate something called "Enhanced MEmory Driving" Signals which are necessary to make some DRAMs work correctly. Regards S. On Mon, 6 Sep 2004 22:01:07 -0400, JJB <[EMAIL PROTECTED]> wrote: > Pedro > I do not understand what you mean by > "I just reinstalled the my "win boot device" and obviously, windows > started to run again." > What is a win boot device? > > Are you trying to say you reinstalled windows from scratch using the > MS/Windows install cd? > That you lost your old windows partition and all the data in it? > > Or that this win boot device thing fixed your hard drive so the > FreeBSD operating system boot menu F1 boots your windows system and > F2 boots your 5.3 FreeBSD system? > > > > > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Behalf Of pedro > Sent: Monday, September 06, 2004 9:15 PM > To: jason > Cc: [EMAIL PROTECTED] > Subject: Re: MBR problem with FreeBSD 5.3 beta > > Ok, > >I just reinstalled the my "win boot device" and obviously, > windows > started to run again... although the horrible "beep" problem happens > everytime I reboot my pc from FreeBSD (whenever I boot my pc from > windows, > it resets normally!). According to my motherboard manual, the beep > sound > matches the one that is described as no DRAM installed or detected. >As told by one of you guys here, about the LBA, I just couldn't > find any > option in my bios to change this... :( >I tried to load my bios default configuration (in order to clear > whatever the FreeBSD instalation has done to it) but the problem > remained... >Does anyone have any idea about what to do? > > I just got happy when I saw you answered my question, > Thank you. > > - Original Message - > From: "jason" <[EMAIL PROTECTED]> > To: "Pedro n/a" <[EMAIL PROTECTED]> > Cc: <[EMAIL PROTECTED]> > Sent: Monday, September 06, 2004 2:51 AM > Subject: Re: MBR problem with FreeBSD 5.3 beta > > > Pedro n/a wrote: > > > > > In the first time I rebooted my computer, after I've finished > the > > > installation of this version, my motherboard started to beep and > I > > > didn't know what to do. > > > After reseting the computer I realized that I could no longer > "boot" > > > my Windows. I did selected it from BootMng and it gave no > response. > > > Even though I tried to use FDISK /MBR to rewrite the MBR, all my > > > effords were in vain and I couldn't start windows again. > > > Recently I've reinstalled an old release version (trustworthy) > but > > > windows still unable to boot. > > > Does anyone know anything that could be helpful? > > > > > > Thanks in advance, > > > Pedro > > > > > > > _ > > > MSN Messenger: converse com os seus amigos online. > > > http://messenger.msn.com.br > > > > > > ___ > > > [EMAIL PROTECTED] mailing list > > > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > > > To unsubscribe, send any mail to > > > "[EMAIL PROTECTED]" > > > > Can you boot freebsd? What was the beep code, you mb manual will > tell > > what it means. Sounds like a hardware problem with the beeping. > Try > > looking for a boot disk image online and boot windows from that. > I have > > 5.3beta3 from yesterday, no problems. > > ___ > > [EMAIL PROTECTED] mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > > To unsubscribe, send any mail to > "[EMAIL PROTECTED]" > > > ___ > [EMAIL PROTECTED] mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to > "[EMAIL PROTECTED]" > > ___ > [EMAIL PROTECTED] mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > -- Subhro Sankha Kar School of Information Technology Block AQ-13/1 Sector V ZIP 700091 India ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: MBR problem with FreeBSD 5.3 beta
Actually that didn't really mean anything special. I just had a very small partition where WINDOWS wrote the boot stuff, I think it was about 200MB (but it only uses aprox. 3MB). Sorry for the missunderstood :) - Original Message - From: "JJB" <[EMAIL PROTECTED]> To: "pedro" <[EMAIL PROTECTED]>; "jason" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Monday, September 06, 2004 11:01 PM Subject: RE: MBR problem with FreeBSD 5.3 beta > Pedro > I do not understand what you mean by > "I just reinstalled the my "win boot device" and obviously, windows > started to run again." > What is a win boot device? > > Are you trying to say you reinstalled windows from scratch using the > MS/Windows install cd? > That you lost your old windows partition and all the data in it? > > Or that this win boot device thing fixed your hard drive so the > FreeBSD operating system boot menu F1 boots your windows system and > F2 boots your 5.3 FreeBSD system? > > > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Behalf Of pedro > Sent: Monday, September 06, 2004 9:15 PM > To: jason > Cc: [EMAIL PROTECTED] > Subject: Re: MBR problem with FreeBSD 5.3 beta > > > Ok, > > I just reinstalled the my "win boot device" and obviously, > windows > started to run again... although the horrible "beep" problem happens > everytime I reboot my pc from FreeBSD (whenever I boot my pc from > windows, > it resets normally!). According to my motherboard manual, the beep > sound > matches the one that is described as no DRAM installed or detected. > As told by one of you guys here, about the LBA, I just couldn't > find any > option in my bios to change this... :( > I tried to load my bios default configuration (in order to clear > whatever the FreeBSD instalation has done to it) but the problem > remained... > Does anyone have any idea about what to do? > > I just got happy when I saw you answered my question, > Thank you. > > - Original Message - > From: "jason" <[EMAIL PROTECTED]> > To: "Pedro n/a" <[EMAIL PROTECTED]> > Cc: <[EMAIL PROTECTED]> > Sent: Monday, September 06, 2004 2:51 AM > Subject: Re: MBR problem with FreeBSD 5.3 beta > > > > Pedro n/a wrote: > > > > > In the first time I rebooted my computer, after I've finished > the > > > installation of this version, my motherboard started to beep and > I > > > didn't know what to do. > > > After reseting the computer I realized that I could no longer > "boot" > > > my Windows. I did selected it from BootMng and it gave no > response. > > > Even though I tried to use FDISK /MBR to rewrite the MBR, all my > > > effords were in vain and I couldn't start windows again. > > > Recently I've reinstalled an old release version (trustworthy) > but > > > windows still unable to boot. > > > Does anyone know anything that could be helpful? > > > > > > Thanks in advance, > > > Pedro > > > > > > > _ > > > MSN Messenger: converse com os seus amigos online. > > > http://messenger.msn.com.br > > > > > > ___ > > > [EMAIL PROTECTED] mailing list > > > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > > > To unsubscribe, send any mail to > > > "[EMAIL PROTECTED]" > > > > Can you boot freebsd? What was the beep code, you mb manual will > tell > > what it means. Sounds like a hardware problem with the beeping. > Try > > looking for a boot disk image online and boot windows from that. > I have > > 5.3beta3 from yesterday, no problems. > > ___ > > [EMAIL PROTECTED] mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > > To unsubscribe, send any mail to > "[EMAIL PROTECTED]" > > > ___ > [EMAIL PROTECTED] mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to > "[EMAIL PROTECTED]" > > ___ > [EMAIL PROTECTED] mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: MBR problem with FreeBSD 5.3 beta
Pedro I do not understand what you mean by "I just reinstalled the my "win boot device" and obviously, windows started to run again." What is a win boot device? Are you trying to say you reinstalled windows from scratch using the MS/Windows install cd? That you lost your old windows partition and all the data in it? Or that this win boot device thing fixed your hard drive so the FreeBSD operating system boot menu F1 boots your windows system and F2 boots your 5.3 FreeBSD system? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of pedro Sent: Monday, September 06, 2004 9:15 PM To: jason Cc: [EMAIL PROTECTED] Subject: Re: MBR problem with FreeBSD 5.3 beta Ok, I just reinstalled the my "win boot device" and obviously, windows started to run again... although the horrible "beep" problem happens everytime I reboot my pc from FreeBSD (whenever I boot my pc from windows, it resets normally!). According to my motherboard manual, the beep sound matches the one that is described as no DRAM installed or detected. As told by one of you guys here, about the LBA, I just couldn't find any option in my bios to change this... :( I tried to load my bios default configuration (in order to clear whatever the FreeBSD instalation has done to it) but the problem remained... Does anyone have any idea about what to do? I just got happy when I saw you answered my question, Thank you. - Original Message - From: "jason" <[EMAIL PROTECTED]> To: "Pedro n/a" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Monday, September 06, 2004 2:51 AM Subject: Re: MBR problem with FreeBSD 5.3 beta > Pedro n/a wrote: > > > In the first time I rebooted my computer, after I've finished the > > installation of this version, my motherboard started to beep and I > > didn't know what to do. > > After reseting the computer I realized that I could no longer "boot" > > my Windows. I did selected it from BootMng and it gave no response. > > Even though I tried to use FDISK /MBR to rewrite the MBR, all my > > effords were in vain and I couldn't start windows again. > > Recently I've reinstalled an old release version (trustworthy) but > > windows still unable to boot. > > Does anyone know anything that could be helpful? > > > > Thanks in advance, > > Pedro > > > > _ > > MSN Messenger: converse com os seus amigos online. > > http://messenger.msn.com.br > > > > ___ > > [EMAIL PROTECTED] mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > > To unsubscribe, send any mail to > > "[EMAIL PROTECTED]" > > Can you boot freebsd? What was the beep code, you mb manual will tell > what it means. Sounds like a hardware problem with the beeping. Try > looking for a boot disk image online and boot windows from that. I have > 5.3beta3 from yesterday, no problems. > ___ > [EMAIL PROTECTED] mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: MBR problem with FreeBSD 5.3 beta
Ok, I just reinstalled the my "win boot device" and obviously, windows started to run again... although the horrible "beep" problem happens everytime I reboot my pc from FreeBSD (whenever I boot my pc from windows, it resets normally!). According to my motherboard manual, the beep sound matches the one that is described as no DRAM installed or detected. As told by one of you guys here, about the LBA, I just couldn't find any option in my bios to change this... :( I tried to load my bios default configuration (in order to clear whatever the FreeBSD instalation has done to it) but the problem remained... Does anyone have any idea about what to do? I just got happy when I saw you answered my question, Thank you. - Original Message - From: "jason" <[EMAIL PROTECTED]> To: "Pedro n/a" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Monday, September 06, 2004 2:51 AM Subject: Re: MBR problem with FreeBSD 5.3 beta > Pedro n/a wrote: > > > In the first time I rebooted my computer, after I've finished the > > installation of this version, my motherboard started to beep and I > > didn't know what to do. > > After reseting the computer I realized that I could no longer "boot" > > my Windows. I did selected it from BootMng and it gave no response. > > Even though I tried to use FDISK /MBR to rewrite the MBR, all my > > effords were in vain and I couldn't start windows again. > > Recently I've reinstalled an old release version (trustworthy) but > > windows still unable to boot. > > Does anyone know anything that could be helpful? > > > > Thanks in advance, > > Pedro > > > > _ > > MSN Messenger: converse com os seus amigos online. > > http://messenger.msn.com.br > > > > ___ > > [EMAIL PROTECTED] mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > > To unsubscribe, send any mail to > > "[EMAIL PROTECTED]" > > Can you boot freebsd? What was the beep code, you mb manual will tell > what it means. Sounds like a hardware problem with the beeping. Try > looking for a boot disk image online and boot windows from that. I have > 5.3beta3 from yesterday, no problems. > ___ > [EMAIL PROTECTED] mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: MBR problem with FreeBSD 5.3 beta
On 06 Sep JJB wrote: > > I experienced the same thing w/ beta-2 > > Just *before* putting an image back I discovered that beta-2 had > > *changed* the LBA setting of my harddrive to another value. > > Putting this back (manualy forcing the bios into using LBA), my > > windows came back on.. Pfftt.. > > > > Def not a nice thing of beta-2 ;-( > > I have the same problem with 5.3 beta-2. > How about some details explaining how you reset the HD to LBA mode. > > This is a bug with 5.3 that needs to be reported back to the > development team so it gets fixed by next weekly beta release. I don't know what to report. Have no idea why this beta does this. I simply *forced* the drive back to LBA mode in the bios, that's it. (normally it's on 'automatic' ;-) FreeBSD-beta-2 had put the drive into 'LRG' (Large). It took me a while to see what happened. You are surprised because the drive just halts and you have no idea why. Now I know this sometimes can happen (even as a bug) it will not take me that long again to find out ;-) -- dick -- http://www.nagual.st/ -- PGP/GnuPG key: F86289CE ++ Running FreeBSD 4.10 ++ Debian GNU/Linux (Woody) + Nai tiruvantel ar vayuvantel i Valar tielyanna nu vilya ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: MBR problem with FreeBSD 5.3 beta
[EMAIL PROTECTED] wrote: > On 06 Sep Pedro n/a wrote: >> In the first time I rebooted my computer, after I've finished the >> installation of this version, my motherboard started to beep and I >> didn't know what to do. After reseting the computer I realized that >> I could no longer "boot" my Windows. I did selected it from BootMng >> and it gave no response. Even though I tried to use FDISK /MBR to >> rewrite the MBR, all my effords were in vain and I couldn't start >> windows again. >> Recently I've reinstalled an old release version (trustworthy) but >> windows still unable to boot. Does anyone know anything that could >> be helpful? > > I experienced the same thing w/ beta-2 > Just *before* putting an image back I discovered that beta-2 had > *changed* the LBA setting of my harddrive to another value. > Putting this back (manualy forcing the bios into using LBA), my > windows came back on.. Pfftt.. > > Def not a nice thing of beta-2 ;-( I have the same problem with 5.3 beta-2. How about some details explaining how you reset the HD to LBA mode. This is a bug with 5.3 that needs to be reported back to the development team so it gets fixed by next weekly beta release. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: MBR problem with FreeBSD 5.3 beta
On 06 Sep Pedro n/a wrote: > In the first time I rebooted my computer, after I've finished the > installation of this version, my motherboard started to beep and I didn't > know what to do. > After reseting the computer I realized that I could no longer "boot" my > Windows. I did selected it from BootMng and it gave no response. Even > though I tried to use FDISK /MBR to rewrite the MBR, all my effords were in > vain and I couldn't start windows again. > Recently I've reinstalled an old release version (trustworthy) but windows > still unable to boot. > Does anyone know anything that could be helpful? I experienced the same thing w/ beta-2 Just *before* putting an image back I discovered that beta-2 had *changed* the LBA setting of my harddrive to another value. Putting this back (manualy forcing the bios into using LBA), my windows came back on.. Pfftt.. Def not a nice thing of beta-2 ;-( -- dick -- http://www.nagual.st/ -- PGP/GnuPG key: F86289CE ++ Running FreeBSD 4.10 ++ Debian GNU/Linux (Woody) + Nai tiruvantel ar vayuvantel i Valar tielyanna nu vilya ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: MBR problem with FreeBSD 5.3 beta
Pedro n/a wrote: In the first time I rebooted my computer, after I've finished the installation of this version, my motherboard started to beep and I didn't know what to do. After reseting the computer I realized that I could no longer "boot" my Windows. I did selected it from BootMng and it gave no response. Even though I tried to use FDISK /MBR to rewrite the MBR, all my effords were in vain and I couldn't start windows again. Recently I've reinstalled an old release version (trustworthy) but windows still unable to boot. Does anyone know anything that could be helpful? Thanks in advance, Pedro _ MSN Messenger: converse com os seus amigos online. http://messenger.msn.com.br ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]" Can you boot freebsd? What was the beep code, you mb manual will tell what it means. Sounds like a hardware problem with the beeping. Try looking for a boot disk image online and boot windows from that. I have 5.3beta3 from yesterday, no problems. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: MBR
Am Dienstag, 11. Mai 2004 16:35 schrieb Olga Zenkova: > Hi! > How can I use FreeBSD MBR to load other OS? Can't find > needed doc. man (8) boot is a good point to start and of course, like always, the online handbook: (http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/index.html) -Harry > > Thanks, > Olga > > > > > __ > Do you Yahoo!? > Win a $20,000 Career Makeover at Yahoo! HotJobs > http://hotjobs.sweepstakes.yahoo.com/careermakeover > ___ > [EMAIL PROTECTED] mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to > "[EMAIL PROTECTED]" pgp0.pgp Description: signature
Re: MBR
How can I use FreeBSD MBR to load other OS? Can't find needed doc. man fdisk man boot0cfg _ STOP MORE SPAM with the new MSN 8 and get 2 months FREE* http://join.msn.com/?page=features/junkmail ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: MBR
On Tue, 27 Jan 2004 16:49:02 +0100 (?), Namik Dala wrote: >> > On Tue, Jan 27, 2004 at 09:10:51AM -0600, Brian H wrote: > > Currently I have the BSD boot loader running in my MBR, but since I only > > have BSD on my system I would like to replace it with the standard MBR. Is > > there a way with unix to safely reset the MBR? > > This > > dev=/dev/ad0 # change this > dd if=$dev of=/boot/mbr.backup bs=512 count=1 > dd if=/boot/mbr of=$dev bs=512 count=1 > > should to the trick. >> I suspect this would erase the MBR partition (aka "slice") table. Use the "fdisk" command "-B" option to install the bootstrap program from /boot/mbr. Be sure to set the desired "active" partition so that the bootstrap program knows which partition to boot. Dan Strick [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: MBR problem
Kjell B. wrote: Kjell B. wrote: I just installed FreeBSD 5.2-RELEASE (using the mini-install CD) on my laptop which already had Win XP Home + Win XP Pro on it. During partition definition I chose not to touch the MBR. (I wanted to make use of Windows boot.ini for booting into FreeBSD.) Nevertheless, whenever I boot I get directly to the FreeBSD boot menu where there's no option to boot Windows. disk layout: ad0s1: 31 MB DELL slice ad0s2: 8001 MB Windows XP Home slice ad0s3: 8510 MB extended DOS slice with three logical Win partitions (one of them Windows XP Professional) ad0s4: 2533 MB FreeBSD slice I tried to restore the MBR using fixmbr from Windows Recovery Console. It doesn't help. I claims it has overwritten the file, but I still get directly into FreeBSD at boot. I've tried setting ad0s2 and ad0s4 as bootable and then writing changes (W) in FDISK partition editor in sysinstall. At the following choice of MBR, I choose 'Install the FreeBSD Boot Manager'. I then get "ERROR: Unable to write data to disk ad0!" followed by "Disk partition write returned an error status!". The same result also if I choose 'Standard' or 'None' in the MBR choice menu. (Another weird thing in sysinstall -> fdisk: Positioning the cursor on any of the slices and hitting F1 yields "Sorry! The slice file is not provided on this particular floppy image". This indicates to me that something is wrong with my installation, but what?) Any hints on ways out of this? Another question: In 5.2 there are two sysinstalls - /stand/sysinstall and /usr/local/sbin/sysinstall whereas in 4.8 I only find /stand/sysinstall. Which one should I use with 5.2 and what's the difference between them? OK, I did find a hint Googling a little more. Apparently GEOM prevents me from using sysinstall on the installation for changing MBR. I need to use the install CD and run sysinstall from there. Then I could do the change of MBR and got the standard FreeBSD boot manager. I now can boot Win XP or FreeBSD using the standard FreeBSD boot manager. What remains is to get rid of that and use Windows boot.ini for choosing between Win XP and FreeBSD, i.e. overwrite the MBR using fixmbr. Hello, I have use to do this with win2k. The trick I used to boot into windows was to used fdisk -a from freebsd and switch the active partition to the one I wanted to boot. Then to get back to freebsd I would use the manage disk volumes(?) for win2k to set the freebsd partition active and reboot. -- -Ryan Merrick [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: MBR problem
Kjell B. wrote: > I just installed FreeBSD 5.2-RELEASE (using the mini-install CD) on my > laptop which already had Win XP Home + Win XP Pro on it. During > partition definition I chose not to touch the MBR. (I wanted to make > use of Windows boot.ini for booting into FreeBSD.) Nevertheless, > whenever I boot I get directly to the FreeBSD boot menu where there's > no option to boot Windows. > > disk layout: > ad0s1: 31 MB DELL slice > ad0s2: 8001 MB Windows XP Home slice > ad0s3: 8510 MB extended DOS slice with three logical Win partitions > (one of them Windows XP Professional) > ad0s4: 2533 MB FreeBSD slice > > I tried to restore the MBR using fixmbr from Windows Recovery > Console. It doesn't help. I claims it has overwritten the file, but I > still get directly into FreeBSD at boot. > > I've tried setting ad0s2 and ad0s4 as bootable and then writing > changes (W) in FDISK partition editor in sysinstall. At the following > choice of MBR, I choose 'Install the FreeBSD Boot Manager'. I then > get "ERROR: Unable to write data to disk ad0!" followed by "Disk > partition write returned an error status!". The same result also if I > choose 'Standard' or 'None' in the MBR choice menu. > > (Another weird thing in sysinstall -> fdisk: Positioning the cursor > on any of the slices and hitting F1 yields "Sorry! The slice file is > not provided on this particular floppy image". This indicates to me > that something is wrong with my installation, but what?) > > Any hints on ways out of this? > > Another question: In 5.2 there are two sysinstalls - > /stand/sysinstall and /usr/local/sbin/sysinstall whereas in 4.8 I > only find /stand/sysinstall. Which one should I use with 5.2 and > what's the difference between them? OK, I did find a hint Googling a little more. Apparently GEOM prevents me from using sysinstall on the installation for changing MBR. I need to use the install CD and run sysinstall from there. Then I could do the change of MBR and got the standard FreeBSD boot manager. I now can boot Win XP or FreeBSD using the standard FreeBSD boot manager. What remains is to get rid of that and use Windows boot.ini for choosing between Win XP and FreeBSD, i.e. overwrite the MBR using fixmbr. -- Kjell ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: MBR
On Tue, 27 Jan 2004 17:10:35 +0100 Ruben de Groot <[EMAIL PROTECTED]> wrote: > On Tue, Jan 27, 2004 at 04:49:02PM +0100, Namik Dala typed: > > On Tue, Jan 27, 2004 at 09:10:51AM -0600, Brian H wrote: > > > Currently I have the BSD boot loader running in my MBR, but since I only > > > have BSD on my system I would like to replace it with the standard MBR. Is > > > there a way with unix to safely reset the MBR? > > > > This > > > > dev=/dev/ad0 # change this > > dd if=$dev of=/boot/mbr.backup bs=512 count=1 > > dd if=/boot/mbr of=$dev bs=512 count=1 > > Don't do this. It'll overwrite your partition table. Use: > > fdisk -B [-b /boot/mbr] /dev/ad0 > > instead. > > Ruben Can't you accomplish the same thing (more modestly) with boot0cfg -b /boot/mbr /dev/ad0 ? -Chris ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: MBR
On Tue, Jan 27, 2004 at 04:49:02PM +0100, Namik Dala typed: > On Tue, Jan 27, 2004 at 09:10:51AM -0600, Brian H wrote: > > Currently I have the BSD boot loader running in my MBR, but since I only > > have BSD on my system I would like to replace it with the standard MBR. Is > > there a way with unix to safely reset the MBR? > > This > > dev=/dev/ad0 # change this > dd if=$dev of=/boot/mbr.backup bs=512 count=1 > dd if=/boot/mbr of=$dev bs=512 count=1 Don't do this. It'll overwrite your partition table. Use: fdisk -B [-b /boot/mbr] /dev/ad0 instead. Ruben > should to the trick. > > -Namik- > ___ > [EMAIL PROTECTED] mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: MBR
On Tue, Jan 27, 2004 at 09:10:51AM -0600, Brian H wrote: > Currently I have the BSD boot loader running in my MBR, but since I only > have BSD on my system I would like to replace it with the standard MBR. Is > there a way with unix to safely reset the MBR? This dev=/dev/ad0 # change this dd if=$dev of=/boot/mbr.backup bs=512 count=1 dd if=/boot/mbr of=$dev bs=512 count=1 should to the trick. -Namik- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: MBR
On Tuesday 27 January 2004 09:10 am, Brian H wrote: > Currently I have the BSD boot loader running in my MBR, but since I only > have BSD on my system I would like to replace it with the standard MBR. Is > there a way with unix to safely reset the MBR? I don't understand much about the MBR; but you might checkout fdisk. 'man fdisk' shows some options to initialize or reinitialize the MBR. I don't know if either of these options resets the MBR to a standard/default state. The man page also mentions that a default boot code is in /boot/mbr. Best of luck, Andrew Gould ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: MBR problem
On Sun, 2003-09-28 at 04:17, Dan Strick wrote: > On Sat, 27 Sep 2003, [EMAIL PROTECTED] wrote: > > There are 2 partitions on my hard drive, one for FreeBSD and the other > > one for XP. I had to reinstall Windows and of course it blew the MBR up. > > I've reinstalled FreeBSD's boot manager with: > > boot0cfg -B ad0 > > > > Now when I boot, the manager lists the 2 OS, but when I choose to boot > > FreeBSD, nothing happens. > > > > Any idea? > > > > #FreeBSD 5.1-CURRENT > > > > bash-2.05b# fdisk ad0 > > *** Working on device /dev/ad0 *** > > parameters extracted from in-core disklabel are: > > cylinders=232581 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=232581 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 7 (0x07),(OS/2 HPFS, NTFS, QNX-2 (16 bit) or Advanced UNIX) > > start 63, size 117210177 (57231 Meg), flag 0 > > beg: cyl 0/ head 1/ sector 1; > > end: cyl 1023/ head 254/ sector 63 > > The data for partition 2 is: > > sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) > > start 117210240, size 117226305 (57239 Meg), flag 80 (active) > > beg: cyl 1023/ head 0/ sector 1; > > end: cyl 1023/ head 254/ sector 63 > > I don't see any smoking guns. I know the basic concept, booting via > an MBR installed with boot0cfg on a FreeBSD 5.1 system with XP in the > first slice works, works. I did it just a couple of days ago. > > I do see a potential problem. The boot0 MBR will by default use the > legacy CHS int-13 BIOS services, even if the "extended" services are > available. (At least this is how I read the source code. This is > contrary to at least some of the boot0/boot0cfg documentation.) > > Your XP slice is just a teensy bit larger than 1024*255*63 sectors long, > pushing the bootstrap program in your FreeBSD slice just beyond the point > at which it could be successfully loaded with a legacy int-13 disk read. > > If possible, do "boot0cfg -v ad0" and see if the "packet" option is set. > If not, see if setting it with "boot0cfg -v -o packet ad0" fixes your > problem. I expect that you are using a modern motherboard whose BIOS > implements the modern "EDDS" int-13 disk functions, perhaps the Asus > P4P800 you just mentioned in a previous posting to freebsd-questions. > > Caveat: I have not yet tried the boot0cfg packet option and don't > know for sure that it works. I also wonder how the boot0 program worked > for you before you installed XP. I gather that it did and that suggests > your problem is something else. Still, it is worth a try. > > Dan Strick > [EMAIL PROTECTED] > Hi Dan! You were right, it works now with the 'packet' option. Thanks a lot! ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: MBR problem
On Sat, 27 Sep 2003, [EMAIL PROTECTED] wrote: > There are 2 partitions on my hard drive, one for FreeBSD and the other > one for XP. I had to reinstall Windows and of course it blew the MBR up. > I've reinstalled FreeBSD's boot manager with: > boot0cfg -B ad0 > > Now when I boot, the manager lists the 2 OS, but when I choose to boot > FreeBSD, nothing happens. > > Any idea? > > #FreeBSD 5.1-CURRENT > > bash-2.05b# fdisk ad0 > *** Working on device /dev/ad0 *** > parameters extracted from in-core disklabel are: > cylinders=232581 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=232581 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 7 (0x07),(OS/2 HPFS, NTFS, QNX-2 (16 bit) or Advanced UNIX) > start 63, size 117210177 (57231 Meg), flag 0 > beg: cyl 0/ head 1/ sector 1; > end: cyl 1023/ head 254/ sector 63 > The data for partition 2 is: > sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) > start 117210240, size 117226305 (57239 Meg), flag 80 (active) > beg: cyl 1023/ head 0/ sector 1; > end: cyl 1023/ head 254/ sector 63 I don't see any smoking guns. I know the basic concept, booting via an MBR installed with boot0cfg on a FreeBSD 5.1 system with XP in the first slice works, works. I did it just a couple of days ago. I do see a potential problem. The boot0 MBR will by default use the legacy CHS int-13 BIOS services, even if the "extended" services are available. (At least this is how I read the source code. This is contrary to at least some of the boot0/boot0cfg documentation.) Your XP slice is just a teensy bit larger than 1024*255*63 sectors long, pushing the bootstrap program in your FreeBSD slice just beyond the point at which it could be successfully loaded with a legacy int-13 disk read. If possible, do "boot0cfg -v ad0" and see if the "packet" option is set. If not, see if setting it with "boot0cfg -v -o packet ad0" fixes your problem. I expect that you are using a modern motherboard whose BIOS implements the modern "EDDS" int-13 disk functions, perhaps the Asus P4P800 you just mentioned in a previous posting to freebsd-questions. Caveat: I have not yet tried the boot0cfg packet option and don't know for sure that it works. I also wonder how the boot0 program worked for you before you installed XP. I gather that it did and that suggests your problem is something else. Still, it is worth a try. Dan Strick [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: MBR Corruption and Restore
On Sat, Aug 30, 2003 at 07:39:44PM -0400, yo _ typed: > Hello All! > > Unfortunatly, i was having a minor hard disk problem on my first FreeBSD > installation, and (so used to Debian) i thought i could fsck after > "shutdown now". Apparently this was not the case, as my file systems were > still mounted. After a quick re-install, with backups, it appears my MBR is > corrupted as it will not start the /boot/loader and my BIOS recognizes my > disk as a "non system disk" (FreeBSD has been re-installed, to get into the > system i use the boot2 from the bootable CD). > > Is there anyway i can manually install the FreeBSD boot loader while in the > system? I figured it is dd'ing the /boot files to the beginning of my hard > disk, but i don't know what location nor how safe this is. Thank to all of > you in advance! Try boot0cfg(8) ruben > -Rian Hunter > > _ > Get MSN 8 and enjoy automatic e-mail virus protection. > http://join.msn.com/?page=features/virus > > ___ > [EMAIL PROTECTED] mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: MBR screwed up
On Sun, 16 Mar 2003 10:30:02 -0500, Doug Reynolds <[EMAIL PROTECTED]> wrote: On Wed, 12 Mar 2003 20:29:26 +0100 (CET), Dirk-Willem van Gulik wrote: On Wed, 12 Mar 2003, dick hoogendijk wrote: master drive, but what do I do to get rid of the old fbsd loader on the second and get a good windows-xp one? On older windozes one would boot from floppy and do a format.exe c: /mbr I don't know if that will do it. I've always used 'fdisk /mbr'. afaik, you can only put a mbr on drive 0 Changing boot order in the bios will make whatever drive you like "drive 0" (or at any rate the first hard drive), I think. If you boot with the WinXP installer disk and choose to repair manually, you can get a list of repair commands (don't remember how, precisely - type "help," perhaps?), among which are a couple of relevant ones that allow you to put a "WinXP" MBR on the drive. Jud To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: MBR screwed up
On Wed, 12 Mar 2003 20:29:26 +0100 (CET), Dirk-Willem van Gulik wrote: >On Wed, 12 Mar 2003, dick hoogendijk wrote: > >> master drive, but what do I do to get rid of the old fbsd loader on the >> second and get a good windows-xp one? > >On older windozes one would boot from floppy and do a > > format.exe c: /mbr I don't know if that will do it. I've always used 'fdisk /mbr'. afaik, you can only put a mbr on drive 0 --- doug reynolds | the maverick | [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: MBR screwed up
On 12 Mar Dirk-Willem van Gulik wrote: > fixmbr > fixmbr \Device\HardDisk0 > > without a device name it will write to the boot device. See also the > man page for 'fixboot'. Oke, will look into it tomorrow. At the moment I get: F1 FreeBSD F5 Disk 1 And on disk1: F1 (= windows XP) F5 Disk 0 If I press F5 and then F1 windows XP does not start, but the system reboots (and that's weird..) I guess somewhere things were mixed up.. -- dick -- http://www.nagual.st/ -- PGP/GnuPG key: F86289CE ++ Running FreeBSD 4.7 ++ Debian GNU/Linux (Woody) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: MBR screwed up
On Wed, 12 Mar 2003, Dirk-Willem van Gulik wrote: > On older windozes one would boot from floppy and do a > > format.exe c: /mbr Actually - my memory is fading; that should be fdisk. And a quick man check on WinXP yeilds 'fixmbr' to be the equivalent: fixmbr fixmbr \Device\HardDisk0 without a device name it will write to the boot device. See also the man page for 'fixboot'. Dw To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: MBR screwed up
On Wed, 12 Mar 2003, dick hoogendijk wrote: > master drive, but what do I do to get rid of the old fbsd loader on the > second and get a good windows-xp one? On older windozes one would boot from floppy and do a format.exe c: /mbr Dw To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: MBR manipulated ???
not completely sure if it's ok to be giving windoze advice on a freebsd mailing list, but have you tried right clicking on My Computer, selecting "Manage" and checking whether or not the D: partition is still on the disk? -- kirt - Original Message - From: "Tim DeMonte" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, February 10, 2003 3:11 PM Subject: MBR manipulated ??? > Hi, > > If anyone can suggest a solution to my problem, it would be greatly > appreciated... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
