You built the raid array using the entire underlying disk drive so grub
can not be installed on them. You must partition the drive and use a
partition as the raid component.
I did use the entire underlying disk drive, as this seemed to be the way
palimpsest wanted it to be done.
This was my
On 6 December 2013 02:12, Phillip Susi ps...@ubuntu.com wrote:
It has been possible in the past since they were managed by dmraid and
grub had hooks to recognize that and understand that the bios recgonizes
the array as a single drive. I started some discussion upstream maybe a
year ago about
** Summary changed:
- Ubuntu installer unable to install GRUB to software raid
+ Ubuntu installer unable to install GRUB to software raid (entire disk)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
You need to install the system to the raid array built on a partition,
and install grub to the whole disk, since that is what the bios knows
about and boots.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Ubuntu installer popped up a window with the following message:
Unable to install GRUB in /dev/sda
Executing 'grub-install /dev/sda' failed.
This is a fatal error.
I attempted to run this command manually at this point, with the following
result:
$ sudo grub-install /dev/sda
Path `/boot/grub'
You built the raid array using the entire underlying disk drive so grub
can not be installed on them. You must partition the drive and use a
partition as the raid component.
** Changed in: grub-installer (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you
On 5 December 2013 23:20, Phillip Susi ps...@ubuntu.com wrote:
You built the raid array using the entire underlying disk drive so grub
can not be installed on them. You must partition the drive and use a
partition as the raid component.
But that would always be the case with container type
It has been possible in the past since they were managed by dmraid and
grub had hooks to recognize that and understand that the bios recgonizes
the array as a single drive. I started some discussion upstream maybe a
year ago about how to proceed with the mdadm transition and being able
to detect
