Bug#580925: closed by maximilian attems <email@example.com> (Re: Bug#580925: This error is presenting while installing linux-image-2.6.32-5-686:)
- To: firstname.lastname@example.org
- Subject: Bug#580925: closed by maximilian attems <email@example.com> (Re: Bug#580925: This error is presenting while installing linux-image-2.6.32-5-686:)
- From: yanu <firstname.lastname@example.org>
- Date: Wed, 26 May 2010 16:48:27 +0200
- Message-id: <20100526144826.GA4963@kloon.u2>
- Reply-to: yanu <email@example.com>, firstname.lastname@example.org
- In-reply-to: <20100510202736.GC23921@kloon.u2>
- References: <20100509221848.GF13880@baikonur.stro.at> <email@example.com> <handler.580925.D580925.firstname.lastname@example.org> <20100510202736.GC23921@kloon.u2>
Op (10/05/10 22:27), yanu schreef:
> > On Sun, May 09, 2010 at 11:19:29PM +0200, yanu wrote:
> > > Running update-grub.
> > > Generating grub.cfg ...
> > > /usr/sbin/grub-probe: error: no mapping exists for `md5'.
> > fix your grub.cfg, if you don't know how to do this ask on
> > a debian userlist, not a linux-2.6 bug thus closing.
> Ok, thx, i solved it myself.
> I thought the 'md5'-part had something to do with enscryption ... but i was wrong.
> /dev/md5 is my root-device.
> So the problem was solved when i renamed the devices in /etc/fstab with the UUID's, as the installationproces of the kernel mentioned.
> After a reboot and an "apt-get install --reinstall linux-image-2.6.32-5-686" solved that one.
Just for others that have the same problem:
This problem appeared again when installing a new kernel.
After some searching, i found it was /boot/grub/device.map that was causing this trouble.
I renamed (then removed) that file and reinstalled the kernel.
Now everything is fine.
/boot/grub/device.map was made in the time grub couldn't boot a md-partition ... a long time ago ;)
Groeten Lieven Baes aka yanu