Forums

Resolved
0 votes
Will these instructions work?

https://linuxconfig.org/installation-of-memtest-ram-memory-test-tool-on-redhat-7-linux

Red Hat Enterprise Linux ships a memory test tool called memtest86+. It is a bootable utility that tests physical memory by writing various patterns to it and reading them back. Since memtest86+ runs directly off the hardware it does not require any operating system support for execution.

This tool is available as an RPM package from Red Hat Network (RHN) as well as a boot option from the Red Hat Enterprise Linux rescue disk.

To boot memtest86+ from the rescue disk, you will need to boot your system from CD 1 of the Red Hat Enterprise Linux installation media, and type the following at the boot prompt (before the Linux kernel is started):

boot: memtest86

If you would rather install memtest86+ on the system, here is an example of how to do it on a Red Hat Enterprise Linux 5 machine registered to RHN:

# yum install memtest86+

For the Red Hat Enterprise Linux version 4, perform the following command to install memtest86+. Make sure current system has been registered to RHN:

# up2date -i memtest86+

Then you will have to configure it to run on next reboot:

# memtest-setup

After reboot, the GRUB menu will list memtest. Select this item and it will start testing the memory.
Please note that once memtest86+ is running it will never stop unless you interrupt it by pressing the Esc key. It is usually a good idea to let it run for a few hours so it has time to test each block of memory several times.

# grub2-mkconfig -o /boot/grub2/grub.cfg
...
Found memtest image: /boot/elf-memtest86+-4.20
done
Monday, January 10 2022, 02:56 AM
Share this post:
Responses (3)
  • Accepted Answer

    Monday, January 10 2022, 10:05 AM - #Permalink
    Resolved
    0 votes
    It should work but there are some caveats.

    1 - you may need a command to update grub on an EFI system "grub2-mkconfig -o /boot/efi/EFI/clearos/grub.cfg". Check if the first command updates /boot/efi/EFI/clearos/grub.cfg as well.
    2 - on one of my systems updating grub does not write to the file at all and I have no idea why. I have to redirect the output to file, so either:
    "grub2-mkconfig -o /boot/efi/EFI/clearos/grub.cfg > /boot/efi/EFI/clearos/grub.cfg"
    or
    "grub2-mkconfig -o /boot/grub2/grub.cfg > /boot/grub2/grub.cfg"

    It may be easier just to run it from something like the Ultimate Boot CD.
    The reply is currently minimized Show
  • Accepted Answer

    Monday, January 10 2022, 02:37 PM - #Permalink
    Resolved
    0 votes
    Nick Howitt wrote:

    It should work but there are some caveats.

    1 - you may need a command to update grub on an EFI system "grub2-mkconfig -o /boot/efi/EFI/clearos/grub.cfg". Check if the first command updates /boot/efi/EFI/clearos/grub.cfg as well.
    2 - on one of my systems updating grub does not write to the file at all and I have no idea why. I have to redirect the output to file, so either:
    "grub2-mkconfig -o /boot/efi/EFI/clearos/grub.cfg > /boot/efi/EFI/clearos/grub.cfg"
    or
    "grub2-mkconfig -o /boot/grub2/grub.cfg > /boot/grub2/grub.cfg"

    It may be easier just to run it from something like the Ultimate Boot CD.


    How do you know if its /boot/grub2/grub.cfg or /boot/efi/EFI/clearos/grub.cfg
    The reply is currently minimized Show
  • Accepted Answer

    Monday, January 10 2022, 03:55 PM - #Permalink
    Resolved
    0 votes
    Have a look in /boot/efi/EFI/clearos. Mine is:
    [root@microserver support]# ls -l /boot/efi/EFI/clearos
    total 6908
    -rwx------ 1 root root 114 Apr 13 2019 BOOT.CSV
    -rwx------ 1 root root 114 Apr 13 2019 BOOTX64.CSV
    drwx------ 2 root root 4096 Jul 1 2021 fonts
    -rwx------ 1 root root 8582 Dec 15 03:53 grub.cfg
    -rwx------ 1 root root 1024 Dec 15 03:53 grubenv
    -rwx------ 1 root root 1122848 Jul 1 2021 grubx64.efi
    -rwx------ 1 root root 1152232 Apr 13 2019 mmx64.efi
    -rwx------ 1 root root 1152232 Apr 13 2019 MokManager.efi
    -rwx------ 1 root root 1202952 Apr 13 2019 shim.efi
    -rwx------ 1 root root 1199352 Apr 13 2019 shimx64-clearos.efi
    -rwx------ 1 root root 1202952 Apr 13 2019 shimx64.efi
    If yours is empty or missing then you don't have EFI. I did see somewhere else a better way of checking, but this should do.
    The reply is currently minimized Show
Your Reply