consider this blind searching,
my findings are that the said recorfail=1 setting was in so called “grub enviroment block”. a date check in the actual file that contains the said environment block /boot/grub/grubenv says it has been this way since i installed manjaro.
you are only supposed to “unset” the grub-enviroment-var with;
$ sudo grub-editenv - unset recordfail
on unsetting “recorfail” i see that the /boot/grub/grubenv file is modified to current date. so i think recorfail=1 was set all this time, it only triggered the unncessary issues only after the recent changes triggered on it.
current grub enviroment block cocntents can be seen by command;
$ grub-editenv list
or by simply
$ sudo cat /boot/grub/grubenv
ADDENDUM:
so i started(booted) the nextday with no issues (after unsetting ‘recodfail’) things were as they were before. however after booting when i checked the contents of the grub-environment-block; recordfail=1 was back. and no, the date modified was untouched on the file `/boot/grub/grubenv’.
so something indeed is setting recordfail=1 since the recent update.
ADDENDUM #2;
in my case, commenting line #134 in /etc/grub.d/00_header
if [ -n "\${have_grubenv}" ]; then if [ -z "\${boot_once}" ]; then save_env recordfail; fi; fi
prevented setting of recordfail=1 on each successive boot.