Re: [gentoo-amd64] possible MBR corruption?

Re: [gentoo-amd64] possible MBR corruption?

[Saifi Khan]

On Fri, 24 Aug 2007, Marc Joliet wrote:

> Date: Fri, 24 Aug 2007 19:45:38 +0200
> From: Marc Joliet <marcec@gmx.de>
> Reply-To:  <gentoo-amd64@lists.gentoo.org>
> To: Gentoo-User ML <gentoo-user@lists.gentoo.org>
> Cc: Gentoo-AMD64 ML <gentoo-amd64@lists.gentoo.org>
> Subject: [gentoo-amd64] possible MBR corruption?
> 
> Hi,
> 
> After the reboot following my daily upgrade from yesterday - during
> which a revised kernel was installed - GRUB just wouldn't finish
> starting. It's attempt to start looked like this:
> 
> GRUB _
> 
> with the underscore blinking. Ctrl-alt-del (reboot) worked.
> 
> Now, to make it clear, I solved that: after finding out that I could
> make a bootable GRUB CD, I made one from within a live-CD (c't
> Knoppicillin 5.2). I was then able to boot into Gentoo with it and
> reinstalled GRUB into the MBR. Don't you just love GRUB ;-)?
> 
> What I *do* want to know, however, is how the hell the MBR could have
> been wrecked in the first place. All I did was install the new
> kernel/initramfs via
> 
> $ genkernel --lvm2 --symlink --install all [1]
> 
> , edit grub.conf appropriately and reboot. It worked flawlessly until
> now. Is Genkernel known to cause anything like this?
> 
> For the record: I have a Windows partition, but never use it[3]. So I
> can't imagine how that might be related. In the event that it helps,
> here's a list of the packages that were updated to yesterday:
> 
> =net-misc/rsync-2.6.9-r3
> =media-sound/madplay-0.15.2b-r1
> =media-libs/libdvdcss-1.2.9-r1
> =sys-kernel/gentoo-sources-2.6.22-r5
> =app-misc/beagle-0.2.17
> =app-arch/tar-1.18-r2
> 
> Also, just to understand the issue better, am I correct in assuming that
> GRUB *always* installs its stage1 into the MBR or a boot sector (unless
> you install it onto a floppy or CD)? I know it's a stupid question, but
> I want to be sure that it was in the MBR in the first place, in the
> event that there was a completely different cause. If it helps, this was
> originally a Sabayon 3.20 install. A lot has changed since the initial
> install, though ;-).
> 
> Of course, it could just be random disk corruption, but I sure hope not.
> 
> - SATA drive: Seagate ST3320620AS
> - Motherboard: Asus M2N-E
> 

Surprising !

I am using Seagate ST3320620AS 16Mb,NCQ with Asus M2N-MX.
No issues what so ever.

In fact as part of your grub installation on MBR,
could use the verbose option to see how things are going.

thanks
Saifi.

-------------------------------------------------------
TWINCLING Society            http://www.twincling.org/
freedom of innovation        Hyderabad AP, India.
-------------------------------------------------------

-- 
gentoo-amd64@gentoo.org mailing list