no entry for device-mapper found

Bug #526045 reported by Gary Trakhman
34
This bug affects 7 people
Affects Status Importance Assigned to Milestone
grub2 (Ubuntu)
Fix Released
Low
Unassigned

Bug Description

Binary package hint: grub

in lucid, during update-grub, I get a bunch of:

/proc/devices: No entry for device-mapper found
/proc/devices: No entry for device-mapper found
/proc/devices: No entry for device-mapper found
/proc/devices: No entry for device-mapper found
/proc/devices: No entry for device-mapper found
/proc/devices: No entry for device-mapper found
/proc/devices: No entry for device-mapper found
/proc/devices: No entry for device-mapper found
/proc/devices: No entry for device-mapper found
/proc/devices: No entry for device-mapper found
/proc/devices: No entry for device-mapper found
/proc/devices: No entry for device-mapper found
/proc/devices: No entry for device-mapper found
/proc/devices: No entry for device-mapper found
/proc/devices: No entry for device-mapper found
/proc/devices: No entry for device-mapper found
/proc/devices: No entry for device-mapper found
/proc/devices: No entry for device-mapper found
/proc/devices: No entry for device-mapper found
/proc/devices: No entry for device-mapper found
/proc/devices: No entry for device-mapper found
/proc/devices: No entry for device-mapper found
/proc/devices: No entry for device-mapper found
/proc/devices: No entry for device-mapper found
/proc/devices: No entry for device-mapper found
/proc/devices: No entry for device-mapper found
/proc/devices: No entry for device-mapper found
/proc/devices: No entry for device-mapper found
/proc/devices: No entry for device-mapper found
/proc/devices: No entry for device-mapper found
/proc/devices: No entry for device-mapper found
/proc/devices: No entry for device-mapper found
/proc/devices: No entry for device-mapper found
/proc/devices: No entry for device-mapper found
/proc/devices: No entry for device-mapper found

Steve Langasek (vorlon)
affects: grub (Ubuntu) → grub2 (Ubuntu)
Revision history for this message
Colin Watson (cjwatson) wrote :

This is harmless but noisy; it's a bug in the dmraid patch we're currently carrying - the libdm functions always issue this complaint if the device-mapper modules aren't loaded. We should clean this up a bit more quietly.

Changed in grub2 (Ubuntu):
status: New → Triaged
importance: Undecided → Low
Revision history for this message
emas (emas80spam) wrote :

Hi, I got a solution!

This problem appeared suddenly after I recompiled with Lucid RC the Ubuntu kernel which ships with this version, 2.6.32.
I copied the configuration from my "old" 2.6.33 Vanilla (which I actually can't make working, I really don't understand what's wrong with it, but after I upgraded to RC from Beta 2 the same kernel doesn't work anymore).

I tried to recompile my kernel adding one more module, MD and BLK_DEV_DM, Device Driver>Multiple Devices driver Support> Device Mapper Support.
After I added that as module, all is fine again, and when I run an "update-grub" no more messages stating /proc/devices ecc. are printed.

I really don't know why grub (or Ubuntu?) suddenly started to behave like this.

Revision history for this message
Launchpad Janitor (janitor) wrote :
Download full text (10.5 KiB)

This bug was fixed in the package grub2 - 1.98+20100614-1ubuntu1

---------------
grub2 (1.98+20100614-1ubuntu1) maverick; urgency=low

  * Resynchronise with Debian:
    - Add btrfs probing support, currently only in the single-device case
      (LP: #450260).
    - Insert partmap module in prepare_grub_to_access_device to handle
      cross-partmap setups (LP: #451585).
    - Fix verbose error output when device-mapper isn't supported by the
      running kernel (LP: #526045).
    Remaining changes:
    - Adjust for default Ubuntu boot options ("quiet splash").
    - Default to hiding the menu; holding down Shift at boot will show it.
    - Set a monochromatic theme for Ubuntu.
    - Apply Ubuntu GRUB Legacy changes to legacy update-grub script: title,
      recovery mode, quiet option, tweak how memtest86+ is displayed, and
      use UUIDs where appropriate.
    - Fix backslash-escaping in merge_debconf_into_conf.
    - Remove "GNU/Linux" from default distributor string.
    - Add crashkernel= options if kdump and makedumpfile are available.
    - If other operating systems are installed, then automatically unhide
      the menu. Otherwise, if GRUB_HIDDEN_TIMEOUT is 0, then use keystatus
      if available to check whether Shift is pressed. If it is, show the
      menu, otherwise boot immediately. If keystatus is not available, then
      fall back to a short delay interruptible with Escape.
    - Allow Shift to interrupt 'sleep --interruptible'.
    - Don't display introductory message about line editing unless we're
      actually offering a shell prompt. Don't clear the screen just before
      booting if we never drew the menu in the first place.
    - Remove some verbose messages printed before reading the configuration
      file.
    - Suppress progress messages as the kernel and initrd load for
      non-recovery kernel menu entries.
    - Keep the loopback file open so that subsequent changes to the "root"
      environment variable don't affect it.
    - Change prepare_grub_to_access_device to handle filesystems
      loop-mounted on file images.
    - Ignore devices loop-mounted from files in 10_linux.
    - Show the boot menu if the previous boot failed, that is if it failed
      to get to the end of one of the normal runlevels.
    - Handle RAID devices containing virtio components.
    - Don't generate /boot/grub/device.map during grub-install or
      grub-mkconfig by default.
    - Store grub-pc/install_devices as persistent device names under
      /dev/disk/by-id/.
    - Change priority to optional to match the priority of grub.
    - Don't display "GRUB loading" unless Shift is held down.
    - Adjust versions of grub-doc and grub-legacy-doc conflicts to tolerate
      our backport of the grub-doc split.
    - Fix LVM/RAID probing in the absence of /boot/grub/device.map.
    - Look for .mo files in /usr/share/locale-langpack as well, in
      preference.
    - Don't run /etc/grub.d/README, even if it somehow ended up being
      executable.
    - Make sure GRUB_TIMEOUT isn't quoted unnecessarily.
    - Probe all devices in 'grub-probe --target=drive' if
      /boot/grub/device.map is missing.
    - Adjust hostdisk id f...

Changed in grub2 (Ubuntu):
status: Triaged → Fix Released
Revision history for this message
Lorenzo Bettini (bettini) wrote :

as for me, setting CONFIG_BLK_DEV_DM=m was not enough: I had to set it as CONFIG_BLK_DEV_DM=y

Revision history for this message
Juan Simón (simonbcn) wrote :

Same problem that comment #4.
I have updated the grub packages in Lucid to Maverick versions to solve this. The worst thing is that Lucid is supposedly a LTS version but Canonical only solves the bugs in newer versions! :-(

Revision history for this message
Ken Chappell (ken-chappell) wrote :

I too would like to see a fix for this bug backported to Lucid. I am using the grub packages from 10.10, but that is an inelegant solution.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.