| 1 |
On Sunday 20 Oct 2013 13:57:34 Michael Hampicke wrote: |
| 2 |
> Am 20.10.2013 11:54, schrieb Mick: |
| 3 |
> > Any ideas why the Ubuntu installation won't boot? |
| 4 |
> |
| 5 |
> My guess would be, you cannot boot, because if you install grub in |
| 6 |
> /dev/md0. |
| 7 |
> |
| 8 |
> Upon boot the bios cannot find stage1 of the bootloader, which normally |
| 9 |
> lies in the MBR (which also houses the partition table). |
| 10 |
|
| 11 |
I see ... so installing the MBR code in the /dev/md0 block device is further |
| 12 |
down the disk than where BIOS is looking for it and that's why it errors out? |
| 13 |
|
| 14 |
Meanwhile, there is no MBR or partition table on /dev/sda or /dev/sdb for BIOS |
| 15 |
to jump to. Hmm ... |
| 16 |
|
| 17 |
It seems to me then that I *have* to create normal partitions on /dev/sda & |
| 18 |
/dev/sdb, or I would need a different boot drive. Is there another way to |
| 19 |
overcome this problem. |
| 20 |
|
| 21 |
|
| 22 |
> Is a setup as you wish - sda and sdb as raid1, and partitions only on |
| 23 |
> md0 - bootable in general? |
| 24 |
|
| 25 |
Yes, in this case. It makes easy to set a faulty drive in failed state and |
| 26 |
remove it from RAID in a single step, rather than the alternative which would |
| 27 |
involve removing multiple /dev/mdX, one for each partition. I could I guess |
| 28 |
install LVM on top of RAID, but this adds complexity for a functionality |
| 29 |
(increasing LV sizes) which will not be used in this implementation. |
| 30 |
|
| 31 |
Any suggestions welcome. |
| 32 |
-- |
| 33 |
Regards, |
| 34 |
Mick |
Archives