1 |
2016-09-06 22:48 GMT+03:00 Daniel Frey <djqfrey@×××××.com>: |
2 |
> On 09/06/2016 12:39 PM, gevisz wrote: |
3 |
>> 2016-09-06 22:08 GMT+03:00 Rich Freeman <rich0@g.o>: |
4 |
>>> On Tue, Sep 6, 2016 at 3:01 PM, gevisz <gevisz@×××××.com> wrote: |
5 |
>>>> |
6 |
>>>> I have already looked into this file but did not find where to set the |
7 |
>>>> UUID of the root partion. |
8 |
>>>> |
9 |
>>> |
10 |
>>> It depends. :) |
11 |
>>> |
12 |
>>> Usually you end up with root=UUID=abc on your kernel command line. It |
13 |
>>> looks like grub-mkconfig is supposed to do this automatically. |
14 |
>> |
15 |
>> I do agree and suspect that it is a bug in grub-mkconfig. |
16 |
>> |
17 |
>> Why otherwise adding a new unformatted disk to the system |
18 |
>> should prevent grub from finding a root (and boot :) partition |
19 |
>> if it already been set in fstab? |
20 |
> |
21 |
> Because either the BIOS (or the kernel itself) is rearranging your |
22 |
> device names when you plug the new device in. |
23 |
|
24 |
After the GRUB menu, it should be GRUB. |
25 |
|
26 |
But why, on earth, it does not use UUID that has been set in fstab |
27 |
and was available for grub-mkconfig? |
28 |
|
29 |
It seems that now I should edit /boot/grub/grub.cfg directly |
30 |
without even knowing its commands. |
31 |
|
32 |
>>> Your initramfs tool may also do something here (I know dracut sticks a |
33 |
>>> copy of your fstab in the initramfs and uses it to help find the root |
34 |
>>> partition, assuming you have root in your fstab (if not it will |
35 |
>>> probably yell at you at some point)). |
36 |
>>> |
37 |
>>> You have to use an initramfs to use a UUID to mount your root. |
38 |
> |
39 |
> I ran into this myself and I don't remember having to use an initramfs |
40 |
> to fix it. In my case I believe it was USB devices mucking it up and I |
41 |
> was able to fix it by building sata into the kernel and USB as modules |
42 |
> so it wouldn't mess up my boot order. I don't think this will work in |
43 |
> your case though. |
44 |
> |
45 |
> I see you are still using IDE drives, so perhaps the kernel is loading |
46 |
> the sata and ide order differently when adding a new drive. |
47 |
> |
48 |
> |
49 |
> Dan |
50 |
> |