You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: support/azure/virtual-machines/linux/troubleshoot-vm-boot-error.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -151,7 +151,7 @@ This error might be associated with one of the following issues:
151
151
152
152
* GRUB boot loader points to an invalid disk or partition.
153
153
154
-
To resolve this issue, [reinstall GRUB and regenerate the GRUB configuration file-manually](#reinstall-grub-regenerate-the-grub-configuration-file-manually).
154
+
To resolve this issue, [reinstall GRUB and regenerate the GRUB configuration file-manually](#reinstall-grub-regenerate-grub-configuration-file).
155
155
156
156
* OS disk partition table issues caused by human error.
157
157
@@ -179,7 +179,7 @@ To resolve this issue, follow these steps:
179
179
180
180
2. Inspect the `/boot` file system contents and determine what's missing.
181
181
182
-
3. If the GRUB configuration file is missing, [reinstall GRUB and regenerate the GRUB configuration file manually](#reinstall-grub-regenerate-the-grub-configuration-file-manually).
182
+
3. If the GRUB configuration file is missing, [reinstall GRUB and regenerate the GRUB configuration file manually](#reinstall-grub-regenerate-grub-configuration-file).
183
183
184
184
4. Verify that the file permissions in the `/boot` file system are OK. You can compare the permissions by using another VM that's running the same Linux version.
185
185
@@ -265,7 +265,7 @@ If the `/boot` partition is missing, re-create it by following these steps:
265
265
266
266
3. If the partition table has **dos** as the partition table type, [re-create /boot partition in dos systems](#re-create-boot-partition-in-dos-systems). If the partition table has **GPT** as the partition table type, [re-create /boot partition in GPT systems](#re-create-boot-partition-in-gpt-systems).
267
267
268
-
4. Make sure that the GRUB boot loader is installed by using the proper disk. You can follow the steps in [Reinstall GRUB and regenerate the GRUB configuration file manually](#reinstall-grub-regenerate-the-grub-configuration-file-manually) to get it installed and configured.
268
+
4. Make sure that the GRUB boot loader is installed by using the proper disk. You can follow the steps in [Reinstall GRUB and regenerate the GRUB configuration file manually](#reinstall-grub-regenerate-grub-configuration-file) to get it installed and configured.
269
269
270
270
5. Proceed with step 3 in [Troubleshoot GRUB rescue issue offline](#offline-troubleshooting) to swap the OS disk.
271
271
@@ -467,7 +467,7 @@ To resolve this error, follow these steps:
467
467
*[GRUB access in SUSE SLES](serial-console-grub-single-user-mode.md#grub-access-in-suse-sles)
468
468
*[GRUB access in Oracle Linux](serial-console-grub-single-user-mode.md#grub-access-in-oracle-linux)
469
469
470
-
3.[Reinstall GRUB and regenerate the GRUB configuration file manually](#reinstall-grub-regenerate-the-grub-configuration-file-manually).
470
+
3.[Reinstall GRUB and regenerate the GRUB configuration file manually](#reinstall-grub-regenerate-grub-configuration-file).
471
471
472
472
> [!NOTE]
473
473
> If the missing file is `/boot/grub/menu.lst`, this error is for older OS versions (RHEL 6.x, Centos 6.x and Ubuntu 14.04). The commands will differ because GRUB version 1 is used in those systems instead. GRUB version 1 isn't covered in this article.
0 commit comments