Yes, device.map is only used by grub to figure out the relationship between linux kernel device names and bios device numbers. Grub uses the notation (hd0) to name the first hard disk in the system, (hd1) for the second, and so on. To the bios the first hard disk is identified as device 80h to the int13 disk service interrupts. When installing though, grub has to open the device and go through the kernel to access the disk so it needs to know the correct device name to open that corresponds to hd0. That is where device.map comes in. The fakeraid bios handles requests for bios disk 80h correctly to provide access to the raid as if it were just one big hard disk.
When you say update-grub would fail if specifying the raid device, do you mean editing device.map to point hd0 to the /dev/mapper device? Also could you be more specific about it failing? Such as any error message it gives? If device.map is set up to correctly map the device to hd0 everything should work. -- grub should support dmraid fakeraids https://bugs.launchpad.net/bugs/73141 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
