Hi Tony,
It took me some time to arrange all backups but finally found time to do so. I followed the instructions but still update does give the same error as before.
Now I am downloading the latest iso, wil try to reinstall the server while maintaining the raid1 and shares.
Thanks for all the support!
Kees

Sure you can reinstall to just one drive, but you must be careful that the other two are not touched. Always use the custom install here so can have control over exactly what the install is going to do... but - you need the skill to do this...

Another way is to disconnect them for the install. Maybe use the "Configuration Backup and Restore" to make things easier - just make sure you have copied the latest backup "backup--------.tgx" file (and maybe the one before) someplace where you can retrieve it. Never used it, but doc seems to indicate it should put things back they as they were - however, cannot speak from experience here...

If you don't use that app (or even if you do) and disconnect the drives, understand how they were setup so you can access them again, both the raid configuration and the shares. If you were using flexshares cannot help as they are never used here... A backup copy of /etc/mdadm.conf could become useful for the raid setup...

Hi Tony, thansk for your elaborate response!
I'll give it a try ater this weekend and let you know the outcome.
In case it fails, I assume should just instell the latest version from scratch, correct? In that case, can I keep my shares which are on separate drives (2 drives in raid 1 configuration)? (ie, I have one drive with the OS, and two drives for the shares).

6.4.0 - way behind - at some point in the past ClearOS radically changed the repository organization for 6.x - but cannot remember now if it was before or after 6.4. Regardless it is best to keep up to date - for two reasons. 1) Very important - Security and 2) Updates sometimes create an issue - the fix for which is normally swiftly forthcoming at that time. You will have a large number of updates. If you have an issue with one, if an old update, trying to discover the solution from a few years ago - maybe a lot of searching of old posts - could be time-consuming and tedious.. Better to encounter these when they are currently discussed. Hopefully you will have a clean upgrade...

There used to be an option whereby you downloaded the latest iso and used the "Upgrade an existing system" to bring the machine up to the level of that on the disc which should be reasonably recent, then complete using the market-place. No idea if this is still available or works... have not used in years. Don't have an old system to try - my systems are more up-to-date than any iso available.

If you wan to up-date your repo files... I am assuming here that your diagnosis is correct. What follows is a suggestion - again don't have an installation that old to test... The rpms can be downloaded manually by specifying the url location and package...
"/etc/yum.repos.d/clearos.repo" is supplied by the clearos-release-community package - so files from this package will provide the latest available repo files...

First copy your repo directory so you can go back if necessary...

# cp -r /etc/yum.repos.d /etc/yum.repos.d.saved

to download...
# wget http://mirror2-frankfurt.clearos.com/clearos/community/6/updates/x86_64/RPMS/clearos-release-community-6-6.8.0.3.v6.noarch.rpm

now extract the repo information only
# rpm2cpio clearos-release-community-6-6.8.0.3.v6.noarch.rpm | cpio -ivd ./etc/yum.repos.d/centos-unverified.repo
# rpm2cpio clearos-release-community-6-6.8.0.3.v6.noarch.rpm | cpio -ivd ./etc/yum.repos.d/clearos-centos.repo
# rpm2cpio clearos-release-community-6-6.8.0.3.v6.noarch.rpm | cpio -ivd ./etc/yum.repos.d/clearos.repo

now move them to their proper directory (y to overwrite - we saved your originals)
# mv ./etc/yum.repos.d/* /etc/yum.repos.d/

That will give you the latest clearos repo files...

I am not sure whether this is enough to get you going, or if it will barf on something like the os level in the /etc/*release* or market-place files... Installing the whole rpm you downloaded will update the *release* files, and several other besides - but would be more difficult to back-out of... I temporarily edited my /etc/clearos-release file to "ClearOS Community release 6.4.0 (Final)" - the other *release* files are symlinks so they also changed automatically. Yum didn't seem to care, and in fact, a yum update installed the latest ntp and ntpdate packages that have just been released...

So up to you - your system - your responsibility

I am running ClearOS Community release 6.4.0 (Final)

Please tell us the Version of ClearOS you are using (6.x or 7.x) and the Edition (Home, Pro, Community, Business)