[grub2] grub fails to load again (in Lucid)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
grub2 (Debian) |
Fix Released
|
Unknown
|
|||
grub2 (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Bug Description
Binary package hint: grub2
ORIGINAL BUG REPORT: https:/
Maybe the same problem in in Lucid Beta1. After booting Windows my system again was left with useless MBR.
The system message this time is not "GRUB LOADING" as it is in Karmic but:
"no module name found
Aborted. Press any key to exit."
After hitting "Enter" the message: "Non-system disk or disk error replace and strike any key when ready" appears.
The system is totally "unbootable" and there is a need to wipe out or re-install the "correct" (Windows-only) MBR after each boot of Windows (it does not matter if it is XP, Vista or 7, nor if an anti-virus application is used under Windows).
ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: grub-pc 1.98-1ubuntu2
ProcVersionSign
Uname: Linux 2.6.32-17-generic x86_64
Architecture: amd64
Date: Tue Mar 30 14:05:08 2010
LiveMediaBuild: Ubuntu 10.04 "Lucid Lynx" - Alpha amd64 (20100329)
ProcEnviron:
LANG=bg_BG.UTF-8
SHELL=/bin/bash
SourcePackage: grub2
Changed in grub2 (Ubuntu): | |
status: | New → Confirmed |
summary: |
- [grub2] grub fails to load again (in Lucid Beta1) + [grub2] grub fails to load again (in Lucid) |
tags: | added: i386 |
Changed in grub2 (Debian): | |
status: | Unknown → New |
Changed in grub2 (Debian): | |
status: | New → Confirmed |
Changed in grub2 (Debian): | |
status: | Confirmed → Fix Released |
This one just bit me in the ass :-( I'm running Lucid with latest updates as of 2 April 2010. I booted into Windows 7, and after shutting that down, I ended up with the same error as the OP for this bug.
Right now, I'm pulling down a new lucid iso to my other system, hoping I can boot that and restore grub.
This REALLY needs to be addressed somehow. This was never an issue with 9.10, and I've not had this issue at all with Lucid until after the last update... or whenever the last grub2 update was pushed to Lucid.
And if you see the bug listed in post #1, you'll see that this has been an issue with Grub2 intermingling with various things in Windows for dual booters since Ubuntu 9.10.
My hardware is an Alienware M15x (from Dell). I am thinking the offending program on the Windows side is probably going to be the Local Backup software, writing something weird to the first few blocks of the hard disk (It has a 6 block partition that it uses for something) which is interfering with Grub 2.
The older grub, with its smaller footprint at the beginning of the disk did not suffer from this issue... so something needs to be done.