Unable to ssh to Linux Redhat VM through putty
by Azureman from LinuxQuestions.org on (#4WCM5)
When I run this command: # "grub2-mkconfig -o /boot/grub2/grub.cfg" i can no longer ssh to Linux after reboot. My system is Bios based.
I followed these commands:
# grub2-mkconfig -o /boot/grub2/grub.cfg
Note: This command will overwrite the existing "initramfs" file.
# dracut -f
Modify the kernel command line of the current kernel in the "grub.cfg" file by adding the following option to the GRUB_CMDLINE_LINUX key in the "/etc/default/grub" file and then rebuild the "grub.cfg" file:
fips=1
Changes to "/etc/default/grub" require rebuilding the "grub.cfg" file as follows:
On BIOS-based machines, use the following command:
# grub2-mkconfig -o /boot/grub2/grub.cfg
I STOPPED HERE TO REBOOT, BECAUSE I WANTED TO FIND OUT WHAT COMMAND WAS CAUSING MY CONNECTION DISCONNECT. BEFORE I WOULD CONTINUE WITH THE REST OF THE COMMANDS BELOW, RESTART, SAME THING. THE COMMAND THAT WOULD CAUSE THE ISSUE IS THIS: # grub2-mkconfig -o /boot/grub2/grub.cfg
If /boot or /boot/efi reside on separate partitions, the kernel parameter boot=<partition of /boot or /boot/efi> must be added to the kernel command line. You can identify a partition by running the df /boot or df /boot/efi command:
# df /boot
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/sda1 495844 53780 416464 12% /boot
To ensure the "boot=" configuration option will work even if device naming changes occur between boots, identify the universally unique identifier (UUID) of the partition with the following command:
# blkid /dev/sda1
/dev/sda1: UUID="05c000f1-a213-759e-c7a2-f11b7424c797" TYPE="ext4"
For the example above, append the following string to the kernel command line:
boot=UUID=05c000f1-a213-759e-c7a2-f11b7424c797
Reboot the system for the changes to take effect.
I followed these commands:
# grub2-mkconfig -o /boot/grub2/grub.cfg
Note: This command will overwrite the existing "initramfs" file.
# dracut -f
Modify the kernel command line of the current kernel in the "grub.cfg" file by adding the following option to the GRUB_CMDLINE_LINUX key in the "/etc/default/grub" file and then rebuild the "grub.cfg" file:
fips=1
Changes to "/etc/default/grub" require rebuilding the "grub.cfg" file as follows:
On BIOS-based machines, use the following command:
# grub2-mkconfig -o /boot/grub2/grub.cfg
I STOPPED HERE TO REBOOT, BECAUSE I WANTED TO FIND OUT WHAT COMMAND WAS CAUSING MY CONNECTION DISCONNECT. BEFORE I WOULD CONTINUE WITH THE REST OF THE COMMANDS BELOW, RESTART, SAME THING. THE COMMAND THAT WOULD CAUSE THE ISSUE IS THIS: # grub2-mkconfig -o /boot/grub2/grub.cfg
If /boot or /boot/efi reside on separate partitions, the kernel parameter boot=<partition of /boot or /boot/efi> must be added to the kernel command line. You can identify a partition by running the df /boot or df /boot/efi command:
# df /boot
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/sda1 495844 53780 416464 12% /boot
To ensure the "boot=" configuration option will work even if device naming changes occur between boots, identify the universally unique identifier (UUID) of the partition with the following command:
# blkid /dev/sda1
/dev/sda1: UUID="05c000f1-a213-759e-c7a2-f11b7424c797" TYPE="ext4"
For the example above, append the following string to the kernel command line:
boot=UUID=05c000f1-a213-759e-c7a2-f11b7424c797
Reboot the system for the changes to take effect.