Auto-detection of a filesystem of /dev/md0 failed.

Thanks. Michael Bienia also reported this on IRC; I'm in the middle of setting up a test harness so that I can debug it.

This bug was fixed in the package grub2 - 1.99~20101126-1ubuntu1

---------------
grub2 (1.99~20101126-1ubuntu1) natty; urgency=low

  * Resynchronise with Debian experimental. 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.
    - 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.
    - Don't generate /boot/grub/device.map during grub-install or
      grub-mkconfig by default.
    - Adjust upgrade version checks for Ubuntu.
    - 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.
    - Make sure GRUB_TIMEOUT isn't quoted unnecessarily.
    - Probe all devices in 'grub-probe --target=drive' if
      /boot/grub/device.map is missing.
    - Build-depend on qemu-kvm rather than qemu-system for grub-pc tests.
    - Use qemu rather than qemu-system-i386.
    - Program vesafb on BIOS systems rather than efifb.
    - Add a grub-rescue-efi-amd64 package containing a rescue CD-ROM image
      for EFI-AMD64.
    - On Wubi, don't ask for an install device, but just update wubildr
      using the diverted grub-install.
    - When embedding the core image in a post-MBR gap, check for and avoid
      sectors matching any of a list of known signatures.
    - Disable video_bochs and video_cirrus on PC BIOS systems, as probing
      PCI space seems to break on some systems.
    - Downgrade "ACPI shutdown failed" error to a debug message, sin...

Hm, this doesn't seem to have fixed my md0 booting problem in duplicate bug 681649

I've upgraded to 1.99~20101126-1ubuntu1, but update-grub2 and grub-install don't seem to fix the original problem (error: can't find device: 4dcb...)

The "grub-probe" line from above doesn't show any errors.

/boot/grub/device.map:
(hd0) /dev/disk/by-id/ata-Maxtor_.......
(hd1) /dev/disk/by-id/ata-Maxtor_.......
(hd2) /dev/disk/by-id/md-uuid-a42f........

The (hd2) line which should represent /dev/md0 doesn't seem to have the same UUID as the "search" line in /boot/grub/grub.cfg (the UUID there is 4dcb..., which is the same as the first entry in /etc/fstab).

I fixed this by:

1. mv /boot/grub/device.map /boot/grub/device.map.old
2. grub-mkdevicemap
3. update-grub2 && grub-install /dev/sda && grub-install /dev/sdb

Not sure how the device map/config were corrupted by 1.99~20101124-1ubuntu1.

More likely you ran into this from a while back:

grub2 (1.98+20100706-1) unstable; urgency=low

  * New Bazaar snapshot.
    - USB hub support.
    - Fix GRUB_BACKGROUND configuration ordering.
    - Fix corruption of first entry name in a reiserfs directory.
    - Don't include MD devices when generating device.map (if you're using
      RAID and upgraded through 1.98+20100702-1 or 1.98+20100705-1, you may
      need to fix this up manually).

 -- Colin Watson <email address hidden> Tue, 06 Jul 2010 18:06:40 +0100

bugb still present

/usr/sbin/grub-probe: error: no such disk.
Auto-detection of a filesystem of /dev/md0 failed.
Please report this together with the output of "/usr/sbin/grub-probe --device-map="/boot/grub/device.map" --target=fs -v /boot/grub" to <email address hidden>
root@adm:/boot/grub# blkid -o full
/dev/sda5: LABEL="Data" UUID="1AE4DF65E4DF41A5" TYPE="ntfs"
/dev/sda6: UUID="d54de081-0673-410d-890c-b7a6a7554a16" SEC_TYPE="ext2" TYPE="ext3"
/dev/sdc1: UUID="ef9699ec-c126-fdbb-2da8-6d69ce77be39" LABEL=":New RAID Array" TYPE="linux_raid_member"
/dev/sdb1: UUID="ef9699ec-c126-fdbb-2da8-6d69ce77be39" LABEL=":New RAID Array" TYPE="linux_raid_member"
/dev/sdb5: UUID="e13fdb16-eff8-423b-8418-5c0edc289de0" TYPE="ext4"
/dev/md0: LABEL="boot" UUID="407141b7-b828-430b-9941-9479d0636bde" TYPE="ext4"

(GRUB) 1.99~rc1-13ubuntu3

I'm still experiencing this bug in a fresh install using the ISO kubuntu-11.04-alternate-amd64.iso. The details are basically exactly the same as the original poster details.

Is there an updated ISO which contains the fixed GRUB package that I can use to install? I'm currently unable to use the PC which I've installed Kubuntu 11.04 on.

I can post any details required.

Same problem here (11.04 alternate on Sandy Bridge chipset).

/boot/grub/device.map doesn't exist
mkdevicemap creates a device.map, which contains the physical hard disks, instead of the md0
creating the device.map by hand (but pointing to the md0 device) and then running the above described
update-grub2 && grub-install /dev/sda && grub-install /dev/sdb
works without error message.
Otherwise update-grub2 fails with "No such device"

Nevertheless, system is not bootable with "no such device <uuid>", ls (hd0,1) gives "unknown filesystem"

I experience the same issue as Sam Banks and others. Here is my configuration (I used the alternate amd64 11.04 iso)

- Unencrypted /boot partition mounted on md0 RAID1, ext4 filesystem.
- Encrypted LVM partitions on top of md1 RAID1, ext4 filesystem (/, /opt, /home & swap).

Grub2 install fails with message: "Impossible to install GRUB on /dev/sda. This error is fatal."

I've tried chrooting (after mounting all required partitions and binding /proc, /dev, & /sys), but this way I obtain the same error as in the original post but instead of the "Auto-detection of a filesystem of /dev/md0 failed", I get "Auto-detection of a filesystem of /dev/mapper/vg--system-root1 failed.".

vg-system is the name of my LVM volume group and root1 is the '/' mount point.

The grub version present in the Fedora 15 distribution does not suffer this problem. I replicated the same partitionning without a problem (and it worked in the past, I think for the Ubuntu 10.04 alternate installer).

Not fixed in lucid!

See https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/733116
and https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/733116/comments/5

Reopen it, please.
It's still the major issue in the Natty LiveUSB, preventing me from installing Ubuntu on my netbook with two SSDs.

I'm still seeing this in natty / 11.04 -- with all updates installed.

Error message : usr/sbin/grub-probe: error: no such disk.
Auto-detection of a filesystem of /dev/md126 failed.
Please report this together with the output of "/usr/sbin/grub-probe --device-map="/boot/grub/device.map" --target=fs -v /boot/grub" to <email address hidden>
/usr/sbin/grub-probe: error: no such disk.

# dpkg -l | grep grub
ii grub-common 1.99~rc1-13ubuntu3 GRand Unified Bootloader, version 2 (common files)
ii grub-gfxpayload-lists 0.2 GRUB gfxpayload blacklist
iF grub-pc 1.99~rc1-13ubuntu3 GRand Unified Bootloader, version 2 (PC/BIOS version)
iU grub2 1.99~rc1-13ubuntu3 GRand Unified Bootloader, version 2 (dummy package)

Workaround: Install grub2 to from another distro, but then I run into problems every time i try to 'apt-get upgrade'. How can I tell apt / dpkg to leave the "foreign"version of grub2 alone? Or better yet, how do I tell it to use something from backports for this package only?

Please let me know if I can supply any more output or experiments for followup.

Same setup here as with #10 (except I believe to remember that it worked with my initial install and only broke after I changed the partitioning scheme afterwards in 'rescue mode').

The problem still exists in oneiric's version:

    # aptitude show grub-pc | grep Version
    Version: 1.99-11ubuntu1
    # grub-install --recheck /dev/sda
    /usr/sbin/grub-probe: error: no such disk.
    Auto-detection of a filesystem of /dev/mapper/crypt_part-root failed.
    Try with --recheck.
    If the problem persists please report this together with the output of "/usr/sbin/grub-probe --device-map="/boot/grub/device.map" --target=fs -v /boot/grub" to <email address hidden>

I am most certain this bug report needs to be reopened. tia.

Right now it doesn't work for me with

    # aptitude show grub-pc | grep Version
    Version: 1.98+20100804-5ubuntu3.3

either, though I only downgraded the dependencies that were formally required to install the package. Might be that the problem is in a dependency that is still in the higher version that (re-?)introduced the problem.

I get the same errors. I try to install grub in a chroot environment (dev,sys and proc is correctly mounted with rebind):

"""
$> grub-mkdevicemap
$> grub-install --no-floppy /dev/sda
/usr/sbin/grub-probe: error: no such disk.
Auto-detection of a filesystem of /dev/md1 failed.
Please report this together with the output of "/usr/sbin/grub-probe --device-map="/boot/grub/device.map" --target=fs -v /boot/grub" to <email address hidden>
"""

The boot partition is /dev/md1 (ext3).

I am using Ubuntu 11.04 (with all current updates installed) and I am using GPT on the hard disks (same partitioning scheme on sda and sdb):

"""
$> parted /dev/sda print
Disk /dev/sda: 3001GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt

Number Start End Size File system Name Flags
 4 1049kB 2097kB 1049kB bios_grub
 1 2097kB 2150MB 2147MB raid
 2 2150MB 2686MB 537MB raid
 3 2686MB 3001GB 2998GB raid
"""

I am using the following grub package version:

grub-common: 1.99~rc1-13ubuntu3
grub-pc: 1.99~rc1-13ubuntu3

I digged a little bit further into the issue. If I use a root partition with only 2000G (which gets used in a software raid-1) the grub installation works perfectly. It seems there is a problem when using high partition sizes. The filesystem is ext3.

It seems that the problem is when using big partitions and GPT. If I reduce my partition sizes and use a normal dos partition style grub installs without problems. When using GPT the error occures. I use a 1MB boot_grub partition for embedding the grub bootfiles. I use the following scheme (for example):

"""
$> parted /dev/sda print
Disk /dev/sda: 3001GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt

Number Start End Size File system Name Flags
 4 1049kB 3146kB 2097kB bios_grub
 1 3146kB 2151MB 2147MB raid
 2 2152MB 2688MB 536MB raid
 3 2689MB 45.6GB 42.9GB raid
"""

Does grub-2 from ubuntu not support GPT partition style?

Still broken in 11.10, this time with GPT and an EFI system (Intel Sandy Bridge).

Nevermind, my bug seems to be in Ubiquity.

does not work for me in either lucid or onoeric. No GPT here and only 8GB (virtual, test) harddrives. Please reopen!

This bug is not fixed for me. I'm using 11.04, raid 1, grub-pc 1.99~rc1-13ubuntu3.

# apt-get upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
3 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue [Y/n]? y
Setting up linux-image-2.6.38-13-generic (2.6.38-13.56) ...
Running depmod.
update-initramfs: Generating /boot/initrd.img-2.6.38-13-generic
Not updating initrd symbolic links since we are being updated/reinstalled
(2.6.38-13.53 was configured last, according to dpkg)
Not updating image symbolic links since we are being updated/reinstalled
(2.6.38-13.53 was configured last, according to dpkg)
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 2.6.38-13-generic /boot/vmlinuz-2.6.38-13-generic
run-parts: executing /etc/kernel/postinst.d/pm-utils 2.6.38-13-generic /boot/vmlinuz-2.6.38-13-generic
run-parts: executing /etc/kernel/postinst.d/update-notifier 2.6.38-13-generic /boot/vmlinuz-2.6.38-13-generic
run-parts: executing /etc/kernel/postinst.d/zz-update-grub 2.6.38-13-generic /boot/vmlinuz-2.6.38-13-generic
error: found two disks with the index 0 for RAID md/1.
error: found two disks with the index 0 for RAID md/0.
error: found two disks with the index 0 for RAID md/1.
error: found two disks with the index 0 for RAID md/0.
Generating grub.cfg ...
error: found two disks with the index 0 for RAID md/1.
error: found two disks with the index 0 for RAID md/0.
error: found two disks with the index 0 for RAID md/1.
error: found two disks with the index 0 for RAID md/0.
error: found two disks with the index 0 for RAID md/1.
error: found two disks with the index 0 for RAID md/0.
error: found two disks with the index 0 for RAID md/1.
error: found two disks with the index 0 for RAID md/0.
/usr/sbin/grub-probe: error: unknown filesystem.
run-parts: /etc/kernel/postinst.d/zz-update-grub exited with return code 1
Failed to process /etc/kernel/postinst.d at /var/lib/dpkg/info/linux-image-2.6.38-13-generic.postinst line 1010.
dpkg: error processing linux-image-2.6.38-13-generic (--configure):
 subprocess installed post-installation script returned error exit status 2
Setting up grub-pc (1.99~rc1-13ubuntu3) ...
Generating grub.cfg ...
/usr/sbin/grub-probe: error: no such disk.
dpkg: error processing grub-pc (--configure):
 subprocess installed post-installation script returned error exit status 1
dpkg: dependency problems prevent configuration of grub-gfxpayload-lists:
 grub-gfxpayload-lists depends on grub-pc (>= 1.99~20101210-1ubuntu2); however:
  Package grub-pc is not configured yet.
dpkg: error processing grub-gfxpayload-lists (--configure):
 dependency problems - leaving unconfigured
No apport report written because the error message indicates it's a follow-up error from a previous failure.
                                                                                                            Errors were encountered while processing:
 linux-image-2.6.38-13-generic
 grub-pc
 grub-gfxpayload-lists
E: Sub-process /usr/bin/d...

i'm using grub 1.99

i am using this setup:
GPT on sda and sdb (see parted paste below)
/dev/sda2 + /dev/sdb2 = /dev/md0
/dev/md0 is a pv (for lvm)

i installed my nixos system (yes no ubuntu) into /dev/myVolGrp/system and i'm not using an additional boot partition as /dev/sda1 or /dev/sdb2; they are only there so that i can put grub2 stuff there. my system is directly booted from lvm;

so why do i post this, because i had a similar error:
nixos-rebuild switch --fast
building the system configuration...
updating GRUB 2 menu...
installing the GRUB bootloader on /dev/sda...
/nix/store/iaypdz5mm1qk8izs9412cb28v9vwwcn4-grub-1.99/sbin/grub-probe: error: no such disk.
Auto-detection of a filesystem of /dev/mapper/myVolGrp-system failed.
Try with --recheck.
If the problem persists please report this together with the output of "/nix/store/iaypdz5mm1qk8izs9412cb28v9vwwcn4-grub-1.99/sbin/grub-probe --device-map="/boot/grub/device.map" --target=fs -v /boot/grub" to <email address hidden>

/nix/store/iaypdz5mm1qk8izs9412cb28v9vwwcn4-grub-1.99/sbin/grub-probe --device-map="/boot/grub/device.map" --target=fs -v /boot/grub
/nix/store/iaypdz5mm1qk8izs9412cb28v9vwwcn4-grub-1.99/sbin/grub-probe: info: Cannot stat `/dev/disk/by-id/scsi-35000c5003f556643', skipping.
/nix/store/iaypdz5mm1qk8izs9412cb28v9vwwcn4-grub-1.99/sbin/grub-probe: info: Cannot stat `/dev/disk/by-id/scsi-35000c5003f5363a6', skipping.
/nix/store/iaypdz5mm1qk8izs9412cb28v9vwwcn4-grub-1.99/sbin/grub-probe: info: changing current directory to /dev.
/nix/store/iaypdz5mm1qk8izs9412cb28v9vwwcn4-grub-1.99/sbin/grub-probe: info: changing current directory to pts.
/nix/store/iaypdz5mm1qk8izs9412cb28v9vwwcn4-grub-1.99/sbin/grub-probe: info: changing current directory to shm.
/nix/store/iaypdz5mm1qk8izs9412cb28v9vwwcn4-grub-1.99/sbin/grub-probe: info: changing current directory to myVolGrp.
/nix/store/iaypdz5mm1qk8izs9412cb28v9vwwcn4-grub-1.99/sbin/grub-probe: info: changing current directory to md.
/nix/store/iaypdz5mm1qk8izs9412cb28v9vwwcn4-grub-1.99/sbin/grub-probe: info: changing current directory to disk.
/nix/store/iaypdz5mm1qk8izs9412cb28v9vwwcn4-grub-1.99/sbin/grub-probe: info: changing current directory to by-label.
/nix/store/iaypdz5mm1qk8izs9412cb28v9vwwcn4-grub-1.99/sbin/grub-probe: info: changing current directory to by-uuid.
/nix/store/iaypdz5mm1qk8izs9412cb28v9vwwcn4-grub-1.99/sbin/grub-probe: info: changing current directory to by-partlabel.
/nix/store/iaypdz5mm1qk8izs9412cb28v9vwwcn4-grub-1.99/sbin/grub-probe: info: changing current directory to by-partuuid.
/nix/store/iaypdz5mm1qk8izs9412cb28v9vwwcn4-grub-1.99/sbin/grub-probe: info: changing current directory to by-path.
/nix/store/iaypdz5mm1qk8izs9412cb28v9vwwcn4-grub-1.99/sbin/grub-probe: info: changing current directory to by-id.
/nix/store/iaypdz5mm1qk8izs9412cb28v9vwwcn4-grub-1.99/sbin/grub-probe: info: changing current directory to snd.
/nix/store/iaypdz5mm1qk8izs9412cb28v9vwwcn4-grub-1.99/sbin/grub-p...

Any known workaround for the bug?
ubuntu precise (12.04 LTS) grub-pc 2.02~beta2-9ubuntu1

All I want is to have my root filesystem on /dev/md0 (RAID1 on two disks) and either disk to have correct MBR to boot from it..

Disregard my question, turned out I did not have mdadm installed, sorry.