Disregard my question, turned out I did not have mdadm installed, sorry.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/681535
Title:
Auto-detection of a filesystem of /dev/md0 failed.
To manage not
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..
--
You received this bug notification because you are a member of Ubuntu
Bugs,
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 a
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.
Afte
does not work for me in either lucid or onoeric. No GPT here and only
8GB (virtual, test) harddrives. Please reopen!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/681535
Title:
Auto-detection of a
Nevermind, my bug seems to be in Ubiquity.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/681535
Title:
Auto-detection of a filesystem of /dev/md0 failed.
To manage notifications about this bug go t
Still broken in 11.10, this time with GPT and an EFI system (Intel Sandy
Bridge).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/681535
Title:
Auto-detection of a filesystem of /dev/md0 failed.
To m
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 exa
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.
--
You received this bug notification because
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 to
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 ver
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-11ubunt
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=f
Reopen it, please.
It's still the major issue in the Natty LiveUSB, preventing me from installing
Ubuntu on my netbook with two SSDs.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/681535
Title:
Aut
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
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net
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 w
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
upda
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
(GRUB) 1.99~rc1-13ubuntu3
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/681535
Title:
Auto-detection of a filesystem of /dev/md0 failed.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
ht
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
root@adm:/boot/grub# blkid -o full
/dev/sda5:
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 ge
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.
--
Auto-detection of a filesystem of /dev/md0 failed.
https:/
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.
/boo
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; holdi
** Branch linked: lp:~ubuntu-core-dev/ubuntu/natty/grub2/natty
--
Auto-detection of a filesystem of /dev/md0 failed.
https://bugs.launchpad.net/bugs/681535
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubun
** Changed in: grub2 (Ubuntu)
Status: Triaged => Fix Committed
--
Auto-detection of a filesystem of /dev/md0 failed.
https://bugs.launchpad.net/bugs/681535
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing li
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.
** Changed in: grub2 (Ubuntu)
Importance: Undecided => High
** Changed in: grub2 (Ubuntu)
Status: New => Triaged
** Changed in: grub2 (Ubuntu)
Assignee: (unass
27 matches
Mail list logo
