Bug#545675: grub-pc --configure fails on linux-image-2.6.30-1-686

Felix Zielcke fzielcke at z-51.de
Wed Sep 9 10:09:28 UTC 2009


Am Mittwoch, den 09.09.2009, 11:57 +0200 schrieb Jan Rasche:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> 
> Hi  Grub-pc Maintainers,
> 
> I had found  Felix Zielcke's post here:
> 
> http://www.mail-archive.com/debian-bugs-dist@lists.debian.org/msg686387.html
> 
> <cite>
> 
> Check with `ls -l /dev/mapper/' if the files there are real devices or
> symlinks to /dev/dm-?
> If they're symlinks then this is #542435 which is actually caused by an
> upstream dmsetup change: #542422
> Though that has been fixed now but it seems like for some people just
> upgrading the package and rebooting doestn't solve the problem.
> In that case run `echo change > /sys/block/dm-?/uevent'
> Replace the ? with every /dev/dm-* device you have.
> 
> </cite>
> 
> But the issue is not solved this way (unstable is freshest - I did
> what above suggested) or maybe not related to dmsetup.
> 
> l /dev/mapper/
> insgesamt 0
> crw-rw----  1 root root  10, 60  9. Sep 11:36 control
> lrwxrwxrwx  1 root root       7  9. Sep 11:36 vg-lv--root -> ../dm-0
> brw-rw----  1 root disk 253,  2  9. Sep 11:36 vg-lv--swap
> drwxr-xr-x  2 root root     120  9. Sep 11:36 ./
> brw-rw----  1 root disk 253,  1  9. Sep 11:36 vg-lv--tmp
> drwxr-xr-x 16 root root    5300  9. Sep 11:37 ../
> 
> vg-lv--root -> ../dm-0
> 
> is still linked this way, but only under 2.6.30 not under 2.6.29, so
> it seems somehow Kernel related.
> 
> Best regard, Jan

Oh that gives me an idea I totally didn't think about with the other
reports.
Your initrd maybe was created with that buggy dmsetup udev rule instead
of the fixed one.
`update-initramfs -c -t -k all' and a reboot should fix this if that's
the case.


-- 
Felix Zielcke
Proud Debian Maintainer






More information about the Pkg-grub-devel mailing list