bugGNU GRUB - Bugs: bug #17472, grub install on hd(0,0)...

 
 

You are not allowed to post comments on this tracker with your current authentication level.

bug #17472: grub install on hd(0,0) permanently damages Windows bootloader

Submitted by:  Thomas K. <katzlbt>
Submitted on:  Sat 19 Aug 2006 07:40:29 AM UTC  
 
Category: BootingSeverity: Major
Priority: 5 - NormalItem Group: Software Error
Status: NonePrivacy: Public
Assigned to: NoneOriginator Name: Thomas
Open/Closed: ClosedRelease: 0.97-15
Release: NoneReproducibility: Every Time
Planned Release: None

Sat 15 Dec 2007 09:20:59 PM UTC, comment #2:

Unfortunately we do not currently have the resources to track down this kind of requests. Please reopen this bug if you can provide a patch, or if you're willing to work on this issue.

Thanks

Robert Millan <robertmh>
Project Administrator
Fri 19 Jan 2007 10:28:53 AM UTC, comment #1:

I got into the same problem and finally got to solved it. After so many hours of browsing for a solution I saw on a page that Win makes a backup of the boot record. So, what I did:
- i did a fixmbr/fixboot (although I was not expecting that the fixmbr would do anything, I was expecting that the fix boot would do something. Well, I don't know how one would expect that a M$ system tool (especially something that difficult as to copy one sector) would work. So I don;t know wht they ACTUALLY did thos two commands;
- I looked for a sector as close to sector 0 as possible (as close in terms of data (first) and in terms of location (second)); found sector 6 (if I remember well);
- I copied sector 6 to sector 0 USING A HEXEDITOR (I don't know if that was stupid or smart, but I couldn't rely on another stupid tool).
- PROBLEM SOLVED.
I hope that there will be at least one person to use this information, cause it took me some time to figure it.

corneliu <realn>
Sat 19 Aug 2006 07:40:29 AM UTC, original submission:

I have reproduced the behavior described in this article:
http://www.driverheaven.net/archive/index.php/t-36120.html

I made the mistake of installing GRUB in the boot sector of my Windows partition (C: grub-install /dev/hda1 or hd(0,0) -- can't remember exactly). At first, when trying to load Windows, GRUB would chainload GRUB. So I tried to reinstall the Windows boot system from the recovery console:

fixboot c:

--- BOOTING ---
rootnoverify hd(0,0)
chainloader +1

Disk Error.
Press any key to restart the system.
(this instantly reads GRUB again)

dosfsck reported mismatches in the bootsectors of hda1, so I replaced the originals with the backup ... but that showed no effect.

Mabe GRUB should at least show a warning that this may break Windows permanently.

References:
http://www.driverheaven.net/archive/index.php/t-36120.html

Thomas K. <katzlbt>

 

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -unavailable- added by robertmh (Posted a comment)
  • -unavailable- added by realn (Posted a comment)
  •  

    Do you think this task is very important?
    If so, you can click here to add your encouragement to it.
    This task has 0 encouragements so far.

    Only logged-in users can vote.

     

    Please enter the title of George Orwell's famous dystopian book (it's a date):

     

     

    Follows 1 latest change.

    Date Changed By Updated Field Previous Value => Replaced By
    Sat 15 Dec 2007 09:21:06 PM UTCrobertmhOpen/ClosedOpen=>Closed

    Back to the top


    Powered by Savane 3.1-cleanup1