MBR problem.
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]
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
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
[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 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
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
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
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
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]
MBR problem with FreeBSD 5.3 beta
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]
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]
MBR problem
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? -- Kjell ___ [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 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
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]
MBR problem
Hello, 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 The data for partition 3 is: UNUSED The data for partition 4 is: UNUSED ___ [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]
