It takes about 1-3 days to finally get to the reimage process (which itself only takes a couple of minutes), but i don't care about that. It's only a Testserver, nothing "Mission Critical".
I wouldn't use a cac server for anything important anyway - i have my own private servers for that
Tony I am running "ClearOS Community release 6.7.0 (Final)" The results of yum repolist shown below
[code type="markup"repo id repo name status
clearos ClearOS Community 6 - x86_64 - OS 1,976
clearos-addons ClearOS Community 6 - x86_64 - Addons 72
clearos-extras ClearOS Community 6 - x86_64 - Extras 172
clearos-fast-updates ClearOS 6 - x86_64 - Fast Updates 0
clearos-updates ClearOS Community 6 - x86_64 - Updates 311
contribs contribs 116
private-clearcenter-backuppc private-clearcenter-backuppc 16
private-clearcenter-dyndns private-clearcenter-dyndns 2
private-clearcenter-plex private-clearcenter-plex 3
private-clearcenter-smart-monitor private-clearcenter-smart-monitor 2
private-clearcenter-zarafa-community private-clearcenter-zarafa-community 29
zabbix Zabbix Official Repository - x86_64 193
zabbix-non-supported Zabbix Official Repository non-supported - 15
I f I look through the mirror I can see the 7.7 versions in "Test" but as I dont have that enabled I will just wait for it to end up in updates.
Hi Tony, Can you run tell us what the patched version is so I can confirm if I am patched? I have just manually run a yum update followed by a yum upgrade and didnt get a new version of glibc I did have an update beginning of January is that the patched version?
I have the almost same error in my system log (md0 rather than md1) so your not alone. I wouldnt of known without seeing your post and checking my log. if you run "parted -l" to list your disk partitions you can see the error there too. I ran "mdadm --detail /dev/md0" and it shows me that my array is clean and in sync. My storage seems to be working fine so I will just keep an eye on it unless someone posts here it is a problem that needs fixing.