Just as I saw your email as grep found it.
[root@hxx grub2]# cat /etc/default/grub
GRUB_TIMEOUT=5
GRUB_DISTRIBUTOR="$(sed 's, release .*$,,g' /etc/system-release)"
GRUB_DEFAULT=saved
GRUB_DISABLE_SUBMENU=true
GRUB_TERMINAL_OUTPUT="console"
GRUB_CMDLINE_LINUX="crashkernel=auto rd.lvm.lv=centos/root
Steffan A. Cline wrote:
> I’ve looked and looked and can’t seem to find anything which would
> explain why grub.cfg would have been rewritten with a whole new volume
> group name.
>
> Suggestions?
>
C6 or C7? In either case, have you looked in /etc/default/grub?
mark
_
I’ve looked and looked and can’t seem to find anything which would explain why
grub.cfg would have been rewritten with a whole new volume group name.
Suggestions?
Steffan A. Cline
stef...@hldns.com
602-793-0014
> On Aug 21, 2018, at 11:27 PM, Steffan A. Cline wrote:
>
> I ran into somethi
I ran into something with a recent batch of updates on CentOS 7. It seems that
possibly one of the kernel updates running dracut changed all of the volume
groups in the grub.cfg file making the system unable to boot until I manually
edited each line putting it back to the way it was originally.
4 matches
Mail list logo