-
Notifications
You must be signed in to change notification settings - Fork 111
troubleshooting/upgrade: describe "previous installation not detected" cases #418
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
|
|
||
| :::note | ||
| This section details how to deal with the most frequent causes for the installer not detecting your current installation. There can be other, rarer cases which are not detailed here. | ||
| This section details how to deal with the most frequent causes for the installer not detecting your current installation. There can be other, rarer cases which are not detailed here. In all cases the detailed reason for an inability to upgrade will always be possible to find in the installer log file.See [During installation or upgrade](#during-installation-or-upgrade) to access the log file. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| This section details how to deal with the most frequent causes for the installer not detecting your current installation. There can be other, rarer cases which are not detailed here. In all cases the detailed reason for an inability to upgrade will always be possible to find in the installer log file.See [During installation or upgrade](#during-installation-or-upgrade) to access the log file. | |
| This section details how to deal with the most frequent causes for the installer not detecting your current installation. There can be other, rarer cases which are not detailed here. In all cases the detailed reason for an inability to upgrade will always be possible to find in the installer log file. See [During installation or upgrade](#during-installation-or-upgrade) to access the log file. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
fixed
|
|
||
| #### Disk partitionning not recognized | ||
|
|
||
| XCP-ng is quite strict about the partition table layout, partition labels, partition types. If anything has modified it, it can prevent proper identification of the previous install. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| XCP-ng is quite strict about the partition table layout, partition labels, partition types. If anything has modified it, it can prevent proper identification of the previous install. | |
| XCP-ng is quite strict about the partition table layout, partition labels, partition types. If anything has modified it, it can prevent proper identification of the previous install. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
fixed
|
|
||
| XCP-ng is quite strict about the partition table layout, partition labels, partition types. If anything has modified it, it can prevent proper identification of the previous install. | ||
|
|
||
| Log lines like the one below (taken from an upgrade of a sane 8.3 install) will give an idea whether something is wrng in this area. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| Log lines like the one below (taken from an upgrade of a sane 8.3 install) will give an idea whether something is wrng in this area. | |
| Log lines like the one below (taken from an upgrade of a healthy 8.3 install) will give an idea whether something is wrong in this area. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
fixed
|
|
||
| #### Inconsistent inventory file | ||
|
|
||
| The `/etc/xensource-inventory` file is critical to the upgrade process. This is one case where a log entry reading "A problem occurred whilst scanning for existing installations:" followed by more details. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The last sentence seems off, like it's not complete.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
fixed
| ### Previous installation detected but not upgradable | ||
|
|
||
| For the installer to detect your current install (XCP-ng or XenServer), the ISO must be booted in the same firmware context. | ||
| In some cases the installer will detect a current install (XCP-ng or XenServer), but report "Only product installations that cannot be upgraded have been detected". The most common causes are listed below. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Since we're moving to a new section immediately after, we can replace "below" with an actual link to the relevant section/subsection.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
that's actually not a cross-section link but "in the following subsections", and I felt it's lighter to the reader than "in the following subsections".
|
|
||
| ### Previous installation not detected | ||
|
|
||
| In other cases the installer will fail to detect a current install and only propose fresh installations. Some causes are listed below. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| In other cases the installer will fail to detect a current install and only propose fresh installations. Some causes are listed below. | |
| In other cases, the installer may fail to detect an existing installation, and default to offering only a clean install. Some causes are listed below. |
Also, replace "Below" with a link to the actual subsection in the page
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
same as above
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"default to offering only a clean install." would be wrong, there is no other option. Changing to "only offer".
I'm not sure "clean" is a good idea here (could be perceived as "cleaning", which "fresh" cannot convey)
Signed-off-by: Yann Dirson <[email protected]>
f09b8f8 to
e2678b9
Compare
No description provided.