| 1 |
2016-09-06 21:45 GMT+03:00 Willie M <matthews.willie80@×××××.com>: |
| 2 |
> On 09/06/2016 11:38 AM, gevisz wrote: |
| 3 |
>> 2016-09-06 21:21 GMT+03:00 Neil Bothwick <neil@××××××××××.uk>: |
| 4 |
>>> On Tue, 6 Sep 2016 21:16:12 +0300, gevisz wrote: |
| 5 |
>>> |
| 6 |
>>>> I had one IDE hard drive for / |
| 7 |
>>>> and one SATA hard drive for /home |
| 8 |
>>>> |
| 9 |
>>>> After adding another (yet non-formatted) SATA hard drive |
| 10 |
>>>> the system panics and complains that it cannot find kernel |
| 11 |
>>>> (if I understood it correctly :). |
| 12 |
>>>> |
| 13 |
>>>> As it happens after the GRUB(2) menu, I suspect GRUB(2). |
| 14 |
>>>> |
| 15 |
>>>> Just executed |
| 16 |
>>>> # grub-mkconfig -o /boot/grub/grub.cfg |
| 17 |
>>>> but have not tried to reboot yet. |
| 18 |
>>>> |
| 19 |
>>>> After disconnecting a new hard drive, the system boot normally. |
| 20 |
>>> |
| 21 |
>>> It sounds like you are specifying the root device by device node and |
| 22 |
>>> those have changed with the addition of a new drive. Using UUID or LABEL |
| 23 |
>>> will avoid this problem. |
| 24 |
>> |
| 25 |
>> Thank you for the prompt reply! |
| 26 |
>> |
| 27 |
>> In my fstab, all the old drives are specified by UUID. |
| 28 |
>> And the new one does not have UUID yet. |
| 29 |
>> |
| 30 |
>> But it seems that GRUB does not read fstab... :( |
| 31 |
>> |
| 32 |
>> Where else should I specify them? |
| 33 |
>> |
| 34 |
>> Do you think that running |
| 35 |
>> # grub-mkconfig -o /boot/grub/grub.cfg |
| 36 |
>> with a new drive connected will be enough? |
| 37 |
>> |
| 38 |
> I edit the /etc/default/grub. |
| 39 |
|
| 40 |
I have already looked into this file but did not find where to set the |
| 41 |
UUID of the root partion. |
Archives