Grub not replacing boot sector backup when installing

[-JojoMan-]

To recreate i believe this would need to be done. I haven't tried but this is i believe how i got the problem.

SETUP:
HDA-
    -hda1 - winxp
    -hda2 - Ubuntu (breezy)
    -hda5 - swap

We want to ugrade to dapper RC1
Now when booting with the live cd we have to custom edit the partition table since the cd doesn't give you the option of just clean formatting hda2 (which it should, anywayz). we delete hda2, then we re-create it. everything gets installed then expresso-grub runs again.

Problem:
When booting into freshly installed dapper on new hda2 partition the following error comes up after checking filesystem.

dosfsck 2.11, 12 Mar 2005, FAT32, LFN
dosfsck 2.11, 12 Mar 2005, FAT32, LFN
There are differences between boot sector and its backup.
Differences: (offset:original/backup)
  71:57/4e, 72:49/4f, 73:4e/20, 74:58/4e, 75:50/41, 76:20/4d, 77:20/45
  , 430:4e/52, 431:54/65, 432:4c/6d, 433:44/6f, 434:52/76, 435:20/65
  , 436:69/20, 437:73/64, 438:20/69, 439:6d/73, 440:69/6b, 442:73/20
  , 443:69/6f, 444:6e/72, 445:67/20, 446:ff/6f, 447:0d/74, 448:0a/68
  , 449:44/65, 450:69/72, 451:73/20, 452:6b/6d, 453:20/65, 454:65/64
  , 455:72/69, 456:72/61, 457:6f/2e, 458:72/ff, 459:ff/0d, 460:0d/0a
  , 461:0a/44, 462:50/69, 463:72/73, 464:65/6b, 465:73/20, 466:73/65
  , 467:20/72, 468:61/72, 469:6e/6f, 470:79/72, 471:20/ff, 472:6b/0d
  , 473:65/0a, 474:79/50, 475:20/72, 476:74/65, 477:6f/73, 478:20/73
  , 479:72/20, 480:65/61, 481:73/6e, 482:74/79, 483:61/20, 484:72/6b
  , 485:74/65, 486:0d/79, 487:0a/20, 488:00/74, 489:00/6f, 490:00/20
  , 491:00/72, 492:00/65, 493:00/73, 494:00/74, 495:00/61, 496:00/72
  , 497:00/74, 498:00/0d, 499:00/0a, 506:bf/cb, 507:cc/d8

More Info:
what i think is happeneing here is perhaps a grub backup for older grub is not overwritten when new grub is installed, then when the system checks the disk it notices that the backup and original boot sector are different and hence the error.

Furthermore i searched through the ubuntu forums which took me to this page, http://www.ubuntuforums.org/showthread.php?p=1046158 , if you go to post #4 and #5 , it sorts of supports this idea & bug. so this is a confirmed bug.

Note: the original reporter indicated the bug was in package 'espresso-grub'; however, that package was not published in Ubuntu.

[Francisco Soster (kowal.flecha)]

Same here

[Pradeep (pradeep+-deactivatedaccount)]

Is this still an issue with the latest releases? If so, please tag it confirmed.

Thanks

[-JojoMan- (jojoman02)]

Dear Desi Guy,
yes, i installed edgy over dapper the other day and grub was reinstalled
(standard), but as soon as i booted after the ubuntu login screen it said
boot sector does not match backup. so either the backup should be deleted or
made to match the intalled grub bootloader when installing edgy boot loader,
please fix this in fiesty, so yes this problem still exists.

Hey desi people work for ubuntu yaay!!!

P.S. - Good work you guys on edgy, as far as binary driver by default (in
fiesty) bad choice, but it should be a choice upon installation. so both
users are happy, people who need nvidia/ati drivers and FOSS only users.

On 12/23/06, Pradeep Varadarajan <email address hidden> wrote:
>
> Is this still an issue with the latest releases? If so, please tag it
> confirmed.
>
> Thanks
>
> ** Changed in: Ubuntu
> Status: Unconfirmed => Needs Info
>
> --
> Grub not replacing boot sector backup when installing
> https://launchpad.net/bugs/47382
>

--
عباس

[-JojoMan- (jojoman02)]

the system boots normally after this but just gives the error before booting, it messes up the booting experience cuz you go from the boot screen to this black screen with text then a couple of seconds later a login screen (or bootup). this bug is really just an annoyance, but one that needs to be taken care of for users not knowing what's going on and might be concerned when this happens.

[saxnot (bringonthatjunk)]

This bug is still there in Feisty.

[reinhard6006 (reinhard-kathmann)]

Don't worry.
There is a simply soltion to solve this "error"message.

Subject the system ist bootable and you can have acces to your ubuntu, just do the following :

In Ubuntu open a terminal window. become either root by typing su + root password or type

sudo dosfsck -r /dev/hda1

Once you try to run fsck in recovery mode, nothing will happen, whatever option you choose.
Obviously dosfsck will be invoked by fsck and when the options choices appear on the screen dosfsck is already terminated.
And fsck has no glue how to handle the typed in figures ( 1, 2 oder 3 (no action).

On the first run of dosfsck the same errormessage will appear and it offers the 3 options (copy backup to original, origianl to backup, no action)
Choose "copy original to backup" and - after an while - confirm the "perform changes" with y for yes.
Thats it. For a test you may feel free to run fsck or dosfsck again.
The message "there are differeces bettween boot sector and his backup"has gone, as well as the also printed offsets and difference bytes.

Reboot and the message has been dessappeared to.

I had the same little problem under Feisty and solved it that way.

[John Vivirito (gnomefreak)]

Assiigned to package grub-installer as it seems to be the issue.
Is this still a problem for anyoen and what ubuntu version are you seeing this issue in?

[-JojoMan- (jojoman02)]

I believe this problem still exists in feisty fawn but not sure about gutsy.

On 7/15/07, John Vivirito <email address hidden> wrote:
> Assiigned to package grub-installer as it seems to be the issue.
> Is this still a problem for anyoen and what ubuntu version are you seeing this issue in?
>
> ** Changed in: grub-installer (Ubuntu)
> Sourcepackagename: None => grub-installer
>
> --
> Grub not replacing boot sector backup when installing
> https://bugs.launchpad.net/bugs/47382
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
عباس

[Phillip Susi (psusi)]

This was a bug in grub rather than grub-installer and grub legacy is no longer being maintained, so I am closing this bug. Karmic and later now use grub2. If this is still an issue there, please reopen this bug and reassign it to the grub2 package.