2016-09-06 22:54 GMT+03:00 Neil Bothwick <n...@digimed.co.uk>:
> On Tue, 6 Sep 2016 21:38:07 +0300, gevisz wrote:
>
>> > It sounds like you are specifying the root device by device node and
>> > those have changed with the addition of a new drive. Using UUID or
>> > LABEL will avoid this problem.
>>
>> Thank you for the prompt reply!
>>
>> In my fstab, all the old drives are specified by UUID.
>> And the new one does not have UUID yet.
>>
>> But it seems that GRUB does not read fstab... :(
>
> It does not, because it has not loaded the kernel yet, so it cannot do
> anything on the system.
Oh, poor little Grand Unified Boot Loader!
It cannot do anything! Even to read fstab by its grub-mkconfig script!
P.S. I usually run grub-mkconfig when kernel is already loaded!
And in my fstab all the disks are refered by UUID!
>> Where else should I specify them?
>
> grub.cfg in the kernel options.
>
>> Do you think that running
>> # grub-mkconfig -o /boot/grub/grub.cfg
>> with a new drive connected will be enough?
>
> grub-mkconfig should use UUIDs by default, unless you have uncommented
>
> #GRUB_DISABLE_LINUX_UUID=true
I did not. So, it is a bug in a almighty Grand Unified Boot Loader!
> in /etc/default/grub
>
>
> --
> Neil Bothwick
>
> Top Oxymorons Number 8: Tight slacks
