From f723b7551664f2440fa776153ab577930a0074d5 Mon Sep 17 00:00:00 2001
From: Mark David <44349634+markd69@users.noreply.github.com>
Date: Sat, 29 Jan 2022 17:58:56 -0500
Subject: [PATCH 1/4] Information about resolving sysroot error

---
 migrate2rocky/README.md | 16 ++++++++++++++++
 1 file changed, 16 insertions(+)

diff --git a/migrate2rocky/README.md b/migrate2rocky/README.md
index 3cfdef9..02a6a11 100644
--- a/migrate2rocky/README.md
+++ b/migrate2rocky/README.md
@@ -118,6 +118,22 @@ package for the repo that you need):
 rpm2cpio <(curl http://mirror.centos.org/centos/8/extras/x86_64/os/Packages/centos-release-gluster9-1.0-1.el8.noarch.rpm) | cpio -iD/ \*.repo
 ```
 
+#### Error "specified switch root path /sysroot does not seem to be an os tree"
+
+This issue is caused by a GRUB issue after installation. Has been seen on Hetzner Dedicated Server upgrades from CentOS 8.4 -> Rocky 8.X
+In order to resolve this issue, boot your dedicated server into a rescue system (for example, hetzner rescue system)
+From here, you need to locate your partitions via `fdisk -l` and mount your `/` partition into a directory of your choosing (or `/mnt`).
+
+Run the following commands (be sure to change the "mnt" to the directory of your mounted drives).
+```
+mount --rbind /dev  /mnt/dev
+mount --rbind /proc /mnt/proc
+mount --rbind /sys  /mnt/sys
+chroot /mnt
+
+grub2-mkconfig -o /boot/grub2/grub.cfg
+```
+
 ### Latest Version
 
 The latest version of this script can be found [here](https://github.com/rocky-linux/rocky-tools/).

From f37efa6b413d01993dfaf23981dd8146d7e25bd2 Mon Sep 17 00:00:00 2001
From: Mark David <44349634+markd69@users.noreply.github.com>
Date: Sat, 29 Jan 2022 18:15:10 -0500
Subject: [PATCH 2/4] Update README.md

---
 migrate2rocky/README.md | 1 +
 1 file changed, 1 insertion(+)

diff --git a/migrate2rocky/README.md b/migrate2rocky/README.md
index 02a6a11..7166f84 100644
--- a/migrate2rocky/README.md
+++ b/migrate2rocky/README.md
@@ -125,6 +125,7 @@ In order to resolve this issue, boot your dedicated server into a rescue system
 From here, you need to locate your partitions via `fdisk -l` and mount your `/` partition into a directory of your choosing (or `/mnt`).
 
 Run the following commands (be sure to change the "mnt" to the directory of your mounted drives).
+> Note: You may need to mount your `/boot` directory if your `/` and `/boot` directories are different. You can do this by doing `mnt /dev/XXX /mnt/dev`
 ```
 mount --rbind /dev  /mnt/dev
 mount --rbind /proc /mnt/proc

From 6e001745797bfde01a4f5adbfe3f210dec3aed04 Mon Sep 17 00:00:00 2001
From: Mark David <44349634+markd69@users.noreply.github.com>
Date: Sat, 29 Jan 2022 18:15:58 -0500
Subject: [PATCH 3/4] Typo in note

---
 migrate2rocky/README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/migrate2rocky/README.md b/migrate2rocky/README.md
index 7166f84..51af938 100644
--- a/migrate2rocky/README.md
+++ b/migrate2rocky/README.md
@@ -125,7 +125,7 @@ In order to resolve this issue, boot your dedicated server into a rescue system
 From here, you need to locate your partitions via `fdisk -l` and mount your `/` partition into a directory of your choosing (or `/mnt`).
 
 Run the following commands (be sure to change the "mnt" to the directory of your mounted drives).
-> Note: You may need to mount your `/boot` directory if your `/` and `/boot` directories are different. You can do this by doing `mnt /dev/XXX /mnt/dev`
+> Note: You may need to mount your `/boot` directory if your `/` and `/boot` directories are different. You can do this by doing `mount /dev/XXX /mnt/dev`
 ```
 mount --rbind /dev  /mnt/dev
 mount --rbind /proc /mnt/proc

From c1d26d2d542b018bae680b56dddf8fa705116e15 Mon Sep 17 00:00:00 2001
From: Mark David <44349634+markd69@users.noreply.github.com>
Date: Sat, 29 Jan 2022 18:23:32 -0500
Subject: [PATCH 4/4] Fix typo in note

---
 migrate2rocky/README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/migrate2rocky/README.md b/migrate2rocky/README.md
index 51af938..6578401 100644
--- a/migrate2rocky/README.md
+++ b/migrate2rocky/README.md
@@ -125,7 +125,7 @@ In order to resolve this issue, boot your dedicated server into a rescue system
 From here, you need to locate your partitions via `fdisk -l` and mount your `/` partition into a directory of your choosing (or `/mnt`).
 
 Run the following commands (be sure to change the "mnt" to the directory of your mounted drives).
-> Note: You may need to mount your `/boot` directory if your `/` and `/boot` directories are different. You can do this by doing `mount /dev/XXX /mnt/dev`
+> Note: You may need to mount your `/boot` directory if your `/` and `/boot` directories are different. You can do this by doing `mount /dev/XXX /mnt/boot`
 ```
 mount --rbind /dev  /mnt/dev
 mount --rbind /proc /mnt/proc