2016-09-06 22:48 GMT+03:00 Daniel Frey <djqf...@gmail.com>: > On 09/06/2016 12:39 PM, gevisz wrote: >> 2016-09-06 22:08 GMT+03:00 Rich Freeman <ri...@gentoo.org>: >>> On Tue, Sep 6, 2016 at 3:01 PM, gevisz <gev...@gmail.com> wrote: >>>> >>>> I have already looked into this file but did not find where to set the >>>> UUID of the root partion. >>>> >>> >>> It depends. :) >>> >>> Usually you end up with root=UUID=abc on your kernel command line. It >>> looks like grub-mkconfig is supposed to do this automatically. >> >> I do agree and suspect that it is a bug in grub-mkconfig. >> >> Why otherwise adding a new unformatted disk to the system >> should prevent grub from finding a root (and boot :) partition >> if it already been set in fstab? > > Because either the BIOS (or the kernel itself) is rearranging your > device names when you plug the new device in.
After the GRUB menu, it should be GRUB. But why, on earth, it does not use UUID that has been set in fstab and was available for grub-mkconfig? It seems that now I should edit /boot/grub/grub.cfg directly without even knowing its commands. >>> Your initramfs tool may also do something here (I know dracut sticks a >>> copy of your fstab in the initramfs and uses it to help find the root >>> partition, assuming you have root in your fstab (if not it will >>> probably yell at you at some point)). >>> >>> You have to use an initramfs to use a UUID to mount your root. > > I ran into this myself and I don't remember having to use an initramfs > to fix it. In my case I believe it was USB devices mucking it up and I > was able to fix it by building sata into the kernel and USB as modules > so it wouldn't mess up my boot order. I don't think this will work in > your case though. > > I see you are still using IDE drives, so perhaps the kernel is loading > the sata and ide order differently when adding a new drive. > > > Dan >
