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