Hi Felix! On Fri, 28 Aug 2009 16:13:46 +0200, Felix Zielcke wrote: > Am Freitag, den 28.08.2009, 15:36 +0200 schrieb Luca Capello: >> BTW, I do not have two hard disks on my machine, but only /dev/sda. > > Just remove it from device.map if you want or run grub-mkdevicemap.
I do not remember since which version both /dev/sda and /dev/sdb are there, but I consider this as a bug. Re-running grub-mkdevicemap produced: # cat /boot/grub/device.map (hd0) /dev/sda (hd1) /dev/mmcblk0 And indeed I have a microSD in my SD reader, thus everything is OK. >> -- Package-specific info: >> >> *********************** BEGIN /proc/mounts >> /dev/mapper/vggismo-lvroot / ext3 rw,relatime,errors=remount-ro,data=ordered >> 0 0 >> /dev/dm-3 /home ext3 rw,relatime,errors=continue,data=ordered 0 0 > > Seems like the dmsetup upgrade went a bit wrong for you. Note that while /proc/mounts contains the above, `mount` correctly reports / being /dev/dm-2. > Check with `ls -l /dev/mapper/' if the files there are real devices or > symlinks to /dev/dm-? Yes, they are symlinks. > If they're symlinks then this is #542435 which is actually caused by an > upstream dmsetup change: #542422 BTW, in my case everything but /boot is on an encrypted LUKS, then LVM. FWIW, the very same LVM bug caused cryptsetup to break: #544773. > Though that has been fixed now but it seems like for some people just > upgrading the package and rebooting doestn't solve the problem. I do not reboot so often (thanks to my ThinkPad X60 correctly handling ACPI suspend and hibernate), thus I guess that the LVM change was not taken into consideration. > In that case run `echo change > /sys/block/dm-?/uevent' > Replace the ? with every /dev/dm-* device you have. Done, and everything worked as expected. I am not sure how to proceed here: it seems the bug was unrelated to grub-pc, thus feel free to close or reassign it. Thx, bye, Gismo / Luca
pgpJm80G1NvDp.pgp
Description: PGP signature
