Use the following command to update to the latest rpm
yum -y install https://download.postgresql.org/pub/repos/yum/reporpms/EL-7-x86_64/pgdg-redhat-repo-latest.noarch.rpm
This happens when a user selects strict mode under settings for tracking prevention.
Change this to balanced.
mirrorlist.centos.org is no longer active.
Use
vi /etc/yum.repos.d/CentOS-Base.repo
to update your repos as follows:
# CentOS-Base.repo
#
# The mirror system uses the connecting IP address of the client and the
# update status of each mirror to pick mirrors that are updated to and
# geographically close to the client. You should use this for CentOS updates
# unless you are manually picking other mirrors.
#
# If the mirrorlist= does not work for you, as a fall back you can try the
# remarked out baseurl= line instead.
#
#
[base]
name=CentOS-$releasever - Base
#mirrorlist=http://mirrorlist.centos.org/?release=$releasever&arch=$basearch&repo=os&infra=$infra
baseurl=http://vault.centos.org/centos/$releasever/os/$basearch/
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-7
#released updates
[updates]
name=CentOS-$releasever - Updates
#mirrorlist=http://mirrorlist.centos.org/?release=$releasever&arch=$basearch&repo=updates&infra=$infra
baseurl=http://vault.centos.org/centos/$releasever/updates/$basearch/
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-7
#additional packages that may be useful
[extras]
name=CentOS-$releasever - Extras
#mirrorlist=http://mirrorlist.centos.org/?release=$releasever&arch=$basearch&repo=extras&infra=$infra
baseurl=http://vault.centos.org/centos/$releasever/extras/$basearch/
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-7
#additional packages that extend functionality of existing packages
[centosplus]
name=CentOS-$releasever - Plus
#mirrorlist=http://mirrorlist.centos.org/?release=$releasever&arch=$basearch&repo=centosplus&infra=$infra
baseurl=http://vault.centos.org/centos/$releasever/centosplus/$basearch/
gpgcheck=1
enabled=0
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-7
Now updates and installs should work normally again.
This is caused because the 3dM2 app is using a very outdated TLS 1.0 protocol.
To solve this you need to enable TLS 1.0 while accessing the local 3DM2 web GUI. You should change this back as it presents a large security risk as TLS 1.0 is easily exploited.
To enable TLS 1.0 while using 3DM2 go to "Internet Options" (Internet Properties on newer Windows OS), under advanced check the box for "Use TLS 1.0" then click apply. It's advisable to keep this window open so you remember to disable TLS 1.0 after you are done.
With Use TLS 1.0 checked you should now be able to access the 3DM2 web GUI for your 3ware raid cards using Internet Explorer mode in edge.
Then click more information and go on to the webpage
That's it, you're done.
Don't forget to turn off TLS 1.0 when you're done.
Quick Tip: if you've just installed 3DM2 and don't know your password it's 3ware, be sure to change it.
You can do this with a registry change,
Whenever making registry changes be sure to do a full backup first, I am not responsible for your mistakes.
Open your registry editor (regedit)
goto
Computer\HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\Advanced
right click on advanced and add new DWORD value "JumpListItems_Maximum" and assign the desired value in decimal format.
In most cases you do not need to restart anything, if you would like you can restart explorer using the task manager.
open task manager: Ctrl+Alt+DEL select task manager and under the processes tab right click on "Windows Explorer" and choose restart.
That's it, your done.