No Previous Installations Found
pros81
8 Posts
May 2, 2020, 1:05 amQuote from pros81 on May 2, 2020, 1:05 amHello,
I am trying to upgrade from 2.2.0 to 2.3.0, and am running into the issue of the installer looking for previous installations and not being able to find the previous (currently installed) version of 2.2.0. The installer then appears to go through the process of a clean install.
What needs to be done so that the installer can recognize version 2.2.0 and upgrade accordingly?
Hello,
I am trying to upgrade from 2.2.0 to 2.3.0, and am running into the issue of the installer looking for previous installations and not being able to find the previous (currently installed) version of 2.2.0. The installer then appears to go through the process of a clean install.
What needs to be done so that the installer can recognize version 2.2.0 and upgrade accordingly?
admin
2,930 Posts
May 2, 2020, 12:52 pmQuote from admin on May 2, 2020, 12:52 pmI am not sure the exact details but we mark/tag the install partition, so we can detect if a prev install is present. It would be strange the installer was not able to detected them.
Are you using the 2.3.0 installer ?
Is the OS disk seen by the installer (maybe it could not detect the disk for whatever reason) ?
Has the OS disk been modified in any way, cloned..etc anything than would lead to deletion of partition tag ?
I am not sure the exact details but we mark/tag the install partition, so we can detect if a prev install is present. It would be strange the installer was not able to detected them.
Are you using the 2.3.0 installer ?
Is the OS disk seen by the installer (maybe it could not detect the disk for whatever reason) ?
Has the OS disk been modified in any way, cloned..etc anything than would lead to deletion of partition tag ?
Last edited on May 2, 2020, 12:53 pm by admin · #2
pros81
8 Posts
May 3, 2020, 9:29 amQuote from pros81 on May 3, 2020, 9:29 amHi,
Yes, we are using the 2.3.0 installer. The interesting thing is when we try using the 2.5.0 installer, it is able to detect the previous (2.2.0) installation!
To answer your question, nothing has been that would delete the partition tag in any way.
Hi,
Yes, we are using the 2.3.0 installer. The interesting thing is when we try using the 2.5.0 installer, it is able to detect the previous (2.2.0) installation!
To answer your question, nothing has been that would delete the partition tag in any way.
admin
2,930 Posts
May 3, 2020, 12:33 pmQuote from admin on May 3, 2020, 12:33 pmThis is very strange, beside our own testing we have thousands of users who did this.
Does the 2.3.0 installer goes straight for a fresh install, or does it say there was a previous version but cannot upgrade from ?
Have you installed any software manually ?
What is output of
blkid -lt LABEL=PetaSANSystem -o device
dpkg -s petasan | grep -i Version | tr -s ' ' | cut -d ' ' -f2
dpkg -l petasan | grep ii | tr -s ' ' | cut -d ' ' -f3
This is very strange, beside our own testing we have thousands of users who did this.
Does the 2.3.0 installer goes straight for a fresh install, or does it say there was a previous version but cannot upgrade from ?
Have you installed any software manually ?
What is output of
blkid -lt LABEL=PetaSANSystem -o device
dpkg -s petasan | grep -i Version | tr -s ' ' | cut -d ' ' -f2
dpkg -l petasan | grep ii | tr -s ' ' | cut -d ' ' -f3
Last edited on May 3, 2020, 12:34 pm by admin · #4
pros81
8 Posts
May 3, 2020, 5:24 pmQuote from pros81 on May 3, 2020, 5:24 pmHi,
The 2.3.0 installer first scans for previous installations before saying that none were found.
No software has been installed manually.
Output of commands as requested:
root@ps-node-01:~# blkid -lt LABEL=PetaSANSystem -o device
/dev/sdb2
root@ps-node-01:~# dpkg -s petasan | grep -i Version | tr -s ' ' | cut -d ' ' -f2
2.2.0
root@ps-node-01:~# dpkg -l petasan | grep ii | tr -s ' ' | cut -d ' ' -f3
2.2.0
Hi,
The 2.3.0 installer first scans for previous installations before saying that none were found.
No software has been installed manually.
Output of commands as requested:
root@ps-node-01:~# blkid -lt LABEL=PetaSANSystem -o device
/dev/sdb2
root@ps-node-01:~# dpkg -s petasan | grep -i Version | tr -s ' ' | cut -d ' ' -f2
2.2.0
root@ps-node-01:~# dpkg -l petasan | grep ii | tr -s ' ' | cut -d ' ' -f3
2.2.0
admin
2,930 Posts
May 3, 2020, 7:29 pmQuote from admin on May 3, 2020, 7:29 pmi just downloaded 2.3 and upgraded a 2.2 installation for test and it works. i am not sure why you are see-ing this. If you wish for us to look into this, please do look into our support services.
i just downloaded 2.3 and upgraded a 2.2 installation for test and it works. i am not sure why you are see-ing this. If you wish for us to look into this, please do look into our support services.
pros81
8 Posts
May 5, 2020, 9:17 pmQuote from pros81 on May 5, 2020, 9:17 pmHello admin,
One of my colleagues has reached out to you guys regarding your support services.
Can you please have a look and get back to us? Thanks!
Hello admin,
One of my colleagues has reached out to you guys regarding your support services.
Can you please have a look and get back to us? Thanks!
No Previous Installations Found
pros81
8 Posts
Quote from pros81 on May 2, 2020, 1:05 amHello,
I am trying to upgrade from 2.2.0 to 2.3.0, and am running into the issue of the installer looking for previous installations and not being able to find the previous (currently installed) version of 2.2.0. The installer then appears to go through the process of a clean install.
What needs to be done so that the installer can recognize version 2.2.0 and upgrade accordingly?
Hello,
I am trying to upgrade from 2.2.0 to 2.3.0, and am running into the issue of the installer looking for previous installations and not being able to find the previous (currently installed) version of 2.2.0. The installer then appears to go through the process of a clean install.
What needs to be done so that the installer can recognize version 2.2.0 and upgrade accordingly?
admin
2,930 Posts
Quote from admin on May 2, 2020, 12:52 pmI am not sure the exact details but we mark/tag the install partition, so we can detect if a prev install is present. It would be strange the installer was not able to detected them.
Are you using the 2.3.0 installer ?
Is the OS disk seen by the installer (maybe it could not detect the disk for whatever reason) ?
Has the OS disk been modified in any way, cloned..etc anything than would lead to deletion of partition tag ?
I am not sure the exact details but we mark/tag the install partition, so we can detect if a prev install is present. It would be strange the installer was not able to detected them.
Are you using the 2.3.0 installer ?
Is the OS disk seen by the installer (maybe it could not detect the disk for whatever reason) ?
Has the OS disk been modified in any way, cloned..etc anything than would lead to deletion of partition tag ?
pros81
8 Posts
Quote from pros81 on May 3, 2020, 9:29 amHi,
Yes, we are using the 2.3.0 installer. The interesting thing is when we try using the 2.5.0 installer, it is able to detect the previous (2.2.0) installation!
To answer your question, nothing has been that would delete the partition tag in any way.
Hi,
Yes, we are using the 2.3.0 installer. The interesting thing is when we try using the 2.5.0 installer, it is able to detect the previous (2.2.0) installation!
To answer your question, nothing has been that would delete the partition tag in any way.
admin
2,930 Posts
Quote from admin on May 3, 2020, 12:33 pmThis is very strange, beside our own testing we have thousands of users who did this.
Does the 2.3.0 installer goes straight for a fresh install, or does it say there was a previous version but cannot upgrade from ?
Have you installed any software manually ?
What is output of
blkid -lt LABEL=PetaSANSystem -o device
dpkg -s petasan | grep -i Version | tr -s ' ' | cut -d ' ' -f2
dpkg -l petasan | grep ii | tr -s ' ' | cut -d ' ' -f3
This is very strange, beside our own testing we have thousands of users who did this.
Does the 2.3.0 installer goes straight for a fresh install, or does it say there was a previous version but cannot upgrade from ?
Have you installed any software manually ?
What is output of
blkid -lt LABEL=PetaSANSystem -o device
dpkg -s petasan | grep -i Version | tr -s ' ' | cut -d ' ' -f2
dpkg -l petasan | grep ii | tr -s ' ' | cut -d ' ' -f3
pros81
8 Posts
Quote from pros81 on May 3, 2020, 5:24 pmHi,
The 2.3.0 installer first scans for previous installations before saying that none were found.
No software has been installed manually.
Output of commands as requested:
root@ps-node-01:~# blkid -lt LABEL=PetaSANSystem -o device
/dev/sdb2
root@ps-node-01:~# dpkg -s petasan | grep -i Version | tr -s ' ' | cut -d ' ' -f2
2.2.0
root@ps-node-01:~# dpkg -l petasan | grep ii | tr -s ' ' | cut -d ' ' -f3
2.2.0
Hi,
The 2.3.0 installer first scans for previous installations before saying that none were found.
No software has been installed manually.
Output of commands as requested:
root@ps-node-01:~# blkid -lt LABEL=PetaSANSystem -o device
/dev/sdb2
root@ps-node-01:~# dpkg -s petasan | grep -i Version | tr -s ' ' | cut -d ' ' -f2
2.2.0
root@ps-node-01:~# dpkg -l petasan | grep ii | tr -s ' ' | cut -d ' ' -f3
2.2.0
admin
2,930 Posts
Quote from admin on May 3, 2020, 7:29 pmi just downloaded 2.3 and upgraded a 2.2 installation for test and it works. i am not sure why you are see-ing this. If you wish for us to look into this, please do look into our support services.
i just downloaded 2.3 and upgraded a 2.2 installation for test and it works. i am not sure why you are see-ing this. If you wish for us to look into this, please do look into our support services.
pros81
8 Posts
Quote from pros81 on May 5, 2020, 9:17 pmHello admin,
One of my colleagues has reached out to you guys regarding your support services.
Can you please have a look and get back to us? Thanks!
Hello admin,
One of my colleagues has reached out to you guys regarding your support services.
Can you please have a look and get back to us? Thanks!