On 11/02/12 12:02, John Hughes wrote:
On 11/02/12 11:29, Vladimir 'φ-coder/phcoder' Serbinenko wrote:
This looks like fakeraid rather than a honest software raid. You need to
manually add it to device.map.
The difference is rather blurred now that it's mdadm that's handling
it rather than the old dm-raid.
I'll try adding it to the map by hand.
Ok, adding
(hd2) /dev/md126
to target/boot/grub/device.map then re-running the grub-install works
(it didn't find the windows install, but doing an update-grub from the
running system fixed that).
Like you I get the feeling that the source of the problem is that it's a
mdadm raid using intel container format (aka fake raid). grub looks
like it's trying to cope with either the old dmraid, or linux raid being
handled by mdadm, but this case is beyond it's abilities.
Would you like me to try debugging this further?
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
