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