thanks, but this is one of hundreds of constellations i already checked out
from my listing above you would know, that
(hd3) /dev/mapper/via_jehhchjje
^
would be correct in my case.
anyway -- NO chance .... seems not being possible to workaround this
bug.
my current device.map fyi:
(fd0) /dev/fd0
(hd0) /dev/disk/by-id/ata-ST31000528AS_6VP9JJJG
(hd1) /dev/disk/by-id/ata-ST1000DL002-9TT153_W1V09RY5
(hd2) /dev/disk/by-id/ata-ST1000DL002-9TT153_W1V09HRJ
(hd3) /dev/mapper/via_jehhchjje
(hd3,1) /dev/mapper/via_jehhchjje1
(hd3,2) /dev/mapper/via_jehhchjje2
(hd3,5) /dev/mapper/via_jehhchjje5
(hd3,7) /dev/disk/by-uuid/90ac6970-5f11-442d-8b51-c336f9e4149c
(hd3,8) /dev/disk/by-uuid/f5768a22-a5a9-4ee2-93fa-c2396573dbcf
it makes no difference for the line with hd3,7 and hd3,8 if it written
with UUID or like this:
(hd3,7) /dev/dev/mapper/via_jehhchjje7
(hd3,8) /dev/dev/mapper/via_jehhchjje8
or even
(hd3,7) /dev/dm-6
(hd3,8) /dev/dm-7
absolutly no change in error message when update-grub:
josef@josef-maxtor-quad:~$ sudo update-grub
Generating grub.cfg ...
Found linux image: /boot/vmlinuz-3.2.0-35-generic
Found initrd image: /boot/initrd.img-3.2.0-35-generic
umount: /var/lib/os-prober/mount ist nicht eingehängt
rmdir: konnte »/var/lib/os-prober/mount“ nicht entfernen: Das Gerät oder die
Ressource ist belegt
rmdir: konnte »/var/lib/os-prober/mount“ nicht entfernen: Das Gerät oder die
Ressource ist belegt
rmdir: konnte »/var/lib/os-prober/mount“ nicht entfernen: Das Gerät oder die
Ressource ist belegt
rmdir: konnte »/var/lib/os-prober/mount“ nicht entfernen: Das Gerät oder die
Ressource ist belegt
rmdir: konnte »/var/lib/os-prober/mount“ nicht entfernen: Das Gerät oder die
Ressource ist belegt
grub-probe: Fehler: cannot find a GRUB drive for /dev/mapper/via_jehhchjje7.
Check your device.map.
grub-probe: Fehler: cannot find a GRUB drive for /dev/mapper/via_jehhchjje8.
Check your device.map.
Found Windows 7 (loader) on /dev/mapper/via_jehhchjje1
Found Windows Vista (loader) on /dev/mapper/via_jehhchjje2
done
even same error message without any device.map file
.
could someone have a look to the code in grub-probe please ??!!??!!
or are we just discussing (talking in a circle without any outcome?!) here?
.
as far as i remember there was similar situation in the past when upgrading
from 10.04 to 10.10
.
issue was solved in the past, but same error popped back
.
maybe someone in the past forgot to feed back the code changes in grub to
http://www.gnu.org/ for root of any code changes in grub ??!!??
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1093918
Title:
grub-probe auto-detection fails on raid
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1093918/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
