Above is the output from
### BEGIN /etc/grub.d/06_OVHkernel ###
menuentry "GNU/Linux with OVH Kernel, OVH kernel 4.9.87-xxxx-std-ipv6-64" {
load_video
set gfxpayload=keep
insmod part_gpt
insmod part_gpt
insmod diskfilter
insmod mdraid09
insmod ext2
set root='mduuid/2fbcdcf2f2dde0c4a4d2adc226fd5302'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint='mduuid/2fbcdcf2f2dde0c4a4d2adc226fd5302' 09c4dbce-15
65-42ce-a0b2-2a1179a74bdc
else
search --no-floppy --fs-uuid --set=root 09c4dbce-1565-42ce-a0b2-2a1179a74bdc
fi
linux /bzImage-4.9.87-xxxx-std-ipv6-64 root=/dev/md3 ro crashkernel=auto rhgb quiet rootdelay=10
}
### END /etc/grub.d/06_OVHkernel ###
### BEGIN /etc/grub.d/10_linux ###
menuentry 'CentOS Linux (0-rescue-1e98a4cc1263468b9f9a12e365316b95) 7 (Core)' --class centos --class gnu-linux
--class gnu --class os --unrestricted $menuentry_id_option 'gnulinux-0-rescue-1e98a4cc1263468b9f9a12e365316b95-
advanced-c84d3726-95a0-477e-a4a8-a1fdf71b90c1' {
load_video
insmod gzio
insmod part_gpt
insmod part_gpt
insmod diskfilter
insmod mdraid09
insmod ext2
set root='mduuid/2fbcdcf2f2dde0c4a4d2adc226fd5302'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint='mduuid/2fbcdcf2f2dde0c4a4d2adc226fd5302' 09c4dbce-15
65-42ce-a0b2-2a1179a74bdc
else
search --no-floppy --fs-uuid --set=root 09c4dbce-1565-42ce-a0b2-2a1179a74bdc
fi
linuxefi /vmlinuz-0-rescue-1e98a4cc1263468b9f9a12e365316b95 root=/dev/md3 ro crashkernel=auto rhgb quie
t rootdelay=10
initrdefi /initramfs-0-rescue-1e98a4cc1263468b9f9a12e365316b95.img
}so i looked at /etc/grub.d/06_OVHkernel
if [ "x{$GRUB_GFXPAYLOAD_LINUX}" != xtext ]; then
echo -e "\tload_video"
fi
echo -e "\tset gfxpayload=\"${GRUB_GFXPAYLOAD_LINUX}\""
fi
fi
prepare_grub_to_access_device ${GRUB_DEVICE_BOOT} | sed -e "s/^/\t/"
cat << EOF
linux ${rel_dirname}/${basename} root=${linux_root_device_thisversion} ro ${GRUB_CMDLINE_LINUX} ${GRU
B_CMDLINE_LINUX_DEFAULT} ${IXGBE_BOOT_PARAM}
EOF
initrd=""
for i in "initrd.img-${version}" "initrd-${version}.img" \
"initrd-${version}" "initramfs-${version}.img" \
"initrd.img-${alt_version}" "initrd-${alt_version}.img" \
"initrd-${alt_version}" "initramfs-${alt_version}.img" \
"initramfs-genkernel-${version}" \
"initramfs-genkernel-${alt_version}" \
"initramfs-linux.img" \
"initrd-ovh-generic-amd64.img"
do
if test -f "${dirname}/${i}" ; then
initrd="${i}"
break
fi
done
if test -f "${dirname}/${initrd}" ; then
echo "Found initrd image: ${rel_dirname}/${initrd}" >&2
cat << EOF
initrd ${rel_dirname}/${initrd}
EOF
fi
cat << EOF
}
EOFi dont have to select (on reboot ovh dashboard) device for hdd boot, only on netboot where i manually fill /dev/md3 after choosing the kernel i want (its the current state of my server ).
# grep vmlinuz /boot/efi/EFI/centos/grub.cfg
linuxefi /vmlinuz-4.4.169-1.el7.elrepo.x86_64 root=/dev/md3 ro crashkernel=auto rhgb quiet vga=normal nomodeset rd.auto=1 rd.md.uuid=55fba025:dcfa45b1:a4d2adc2:26fd5302 rd.md.uuid=4f2ff053:53ba30e8:a4d2adc2:26fd5302 rootdelay=10 rootdelay=10 noquiet nosplash net.ifnames=0 biosdevname=0
linuxefi /vmlinuz-4.4.166-1.el7.elrepo.x86_64 root=/dev/md3 ro crashkernel=auto rhgb quiet vga=normal nomodeset rd.auto=1 rd.md.uuid=55fba025:dcfa45b1:a4d2adc2:26fd5302 rd.md.uuid=4f2ff053:53ba30e8:a4d2adc2:26fd5302 rootdelay=10 rootdelay=10 noquiet nosplash net.ifnames=0 biosdevname=0
linuxefi /vmlinuz-0-rescue-c1a63cb41f3a079c801badf65b464d62 root=/dev/md3 ro crashkernel=auto rhgb quiet vga=normal nomodeset rd.auto=1 rd.md.uuid=55fba025:dcfa45b1:a4d2adc2:26fd5302 rd.md.uuid=4f2ff053:53ba30e8:a4d2adc2:26fd5302 rootdelay=10 rootdelay=10 noquiet nosplash net.ifnames=0 biosdevname=0linux ${rel_dirname}/${basename} root=${linux_root_device_thisversion} ro ${GRUB_CMDLINE_LINUX} ${GRU
B_CMDLINE_LINUX_DEFAULT} ${IXGBE_BOOT_PARAM}linuxefi ${rel_dirname}/${basename} root=${linux_root_device_thisversion} ro ${GRUB_CMDLINE_LINUX} ${GRU
B_CMDLINE_LINUX_DEFAULT} ${IXGBE_BOOT_PARAM}initrd ${rel_dirname}/${initrd}initrdefi ${rel_dirname}/${initrd}[[email protected] ~]# uname -a
Linux ns3616484.ip-151-80-24.eu 4.9.87-xxxx-std-ipv6-64 #1 SMP Tue Mar 13 18:41:47 CET 2018 x86_64 x86_64 x86_64 GNU/Linux[[email protected] ~]# grep vmlinuz /boot/efi/EFI/centos/grub.cfg
linuxefi /vmlinuz-0-rescue-1e98a4cc1263468b9f9a12e365316b95 root=/dev/md3 ro crashkernel=auto rhgb quiet rootdelay=10Thanks, but I cannot afford to lose any more clients, I lost way too many last year when I spent DAYS upgrading to CentOS 7. If I could go back in time and I knew there would be that many issues, I would have stayed the hell away from it and I would have stayed on CentOS 6 like it has been for years before, and which ran PERFECTLY fine. I'm way too afraid to even attempt to reboot the server now. The next time any machine will be rebooted is when I migrate to another server. The last WHM update back in december BRICKED my production server without any warning. It got back up using netboot thanks to a generous OVH employee who investiguated it for 15 mins. Now that it's back in operation, it's gonna stay EXACTLY like it is now for a year, then I'll migrate to another server with an already installed CentOS 7.6. A simple minor WHM update should NEVER, EVER brick a production server, especially when you're on the STABLE "branch"... like WTF?! I'm paying $$ every month for a WHM/cPanel licence and I cannot believe that's what my money is buying lately; Is this dashboard even tested prior to be released under a "production stable" tier? There USED TO BE a difference between LTS, STABLE, RELEASE and CURRENT but over the last year or so, I don't remember seeing much of a difference between the four tiers.
yum updateyum update