| 1 |
On 25/11/2020 23:03, Neil Bothwick wrote: |
| 2 |
> On Wed, 25 Nov 2020 19:37:32 -0000 (UTC), Grant Edwards wrote: |
| 3 |
> |
| 4 |
>>>>> I'm not sure chainloading would work as that requires a drive |
| 5 |
>>>>> definition from which to load the boot sector. |
| 6 |
>>>> |
| 7 |
>>>> I thought that's what LVM provided was a drive definition. |
| 8 |
>>> |
| 9 |
>>> It's more like a partition definition, GRUB requires the boot |
| 10 |
>>> sector/MBR of a whole drive. |
| 11 |
>> |
| 12 |
>> I'm asking about chainloading. Grub has already been loaded via MBR |
| 13 |
>> and grub's partition (which can be a normal physical partition if |
| 14 |
>> needed). Grub is now running and displaying its menu. Each of the menu |
| 15 |
>> entries instructs grub to load the first sector of a specified |
| 16 |
>> partition into RAM and execute it. That sector can contain grub, LILO, |
| 17 |
>> windows boot manager, whatever. If grub understands LVM volumes, then |
| 18 |
>> can it read that first sector from an LVM volume instead of a physical |
| 19 |
>> partition? |
| 20 |
> |
| 21 |
> I think the only way to find out is to try it, but my gut feeling about |
| 22 |
> this is not good. However, I'd be happy for my gut to be proved wrong. |
| 23 |
> |
| 24 |
> |
| 25 |
Well, it should be able to do it with raid (you can partition an md-raid |
| 26 |
volume), so maybe the same with LVM? |
| 27 |
|
| 28 |
Cheers, |
| 29 |
Wol |
Archives