On Fri, Feb 10, 2012 at 08:01:23PM +0100, Vladimir 'φ-coder/phcoder' Serbinenko
wrote:
I agree that it should be fixed but the question is how.
I can't think of a way that would work if the disks were in fact using
different setups, which they could be.
No
OK, fair enough if the below worked then.
Currently it only
tries to include partition table support for grub_device, which being
an md raid returns nothing.
This is a problem. It should return the partmap of underlying device
and we have code for that. What does grub-probe -t partmap -d
/dev/mdX is?
address@hidden:~# grub-probe -t partmap -d /dev/md0
address@hidden:~#
So that would be a problem of course.
address@hidden:~# cat /proc/mdstat
Personalities : [raid1] [raid6] [raid5] [raid4]
md1 : active raid5 sda3[0] sdb3[1]
284773376 blocks super 1.2 level 5, 512k chunk, algorithm 2 [3/2] [UU_]
md0 : active raid1 sda2[0] sdb2[1]
976884 blocks super 1.2 [2/2] [UU]
unused devices:<none>
md0 is /boot
md1 is /
When I do the final install I will probably but lvm on md1 and put /
and swap and other things on that.