Those messages are 17 days old, still occurring? Anything in /var/log/messages for those times...
To check your harddisk use smartctl from the smartmontools package :-
If you do not know how to use it refer to web-pages such as http://www.linuxtechi.com/smartctl-monitoring-analysis-tool-hard-drive/
I suspect the errors are reported by LVM, LVM installed? Look for references such as this http://docstore.mik.ua/manuals/hp-ux/en/5992-4589/ch04s03.html
There are probably better ones, search. I have to go to the chemist so must rush out...
It was only a week or two ago I complained about missing documentation for ClearOS 6.x. Yes after all the time ClearOS 6.x has been offered the doc is still not finished and some links from webconfig result in no help pages available... Shame...
I just did a partial check on this site. It is still littered with bad or broken links i.e. bad hosts where ClearOS references an external site that no longer exists, and of course the inevitable '404' broken links.
Another example of bad source from the ClearOS site
Mistakes like this are easy to do, I have done similar myself. However, there are tools available to find problems like this as well as 404s bad host references etc. The questions is why the maintainers aren't using tools to ensure a clean site and some pride in their workmanship. Outsourced to a company who couldn't care less trying to get away with the minimum work possible? Poorly written contact? Who knows...
Great - In most cases you are better off looking for an rpm suited for your distribution than installing a tar file.
It is also much easier to remove an rpm. Use the yum list or search options with all the repos enabled in the command line for a first check to find what may be available. Then make a decision whether to install or not, for instance you might not want something in a "testing" or "test" repo etc.
"won't work" doesn't tell us much :-(
What exactly did you install? an rpm using yum, a tar file? What version?
What errors? What's in the log files? etc
What dynamic dns provider? What's your configuration file for it?
How are you starting it?
It is also possible the readme hasn't been updated with instructions for a "systemd" distribution like CleaOS 7.x
Logging into ssh being slow is probably as a result of reverse lookup failing, then timing out - a typical issue when you have DNS problems.
Most likely you can speed it up by adding "UseDNS" to no in /etc/ssh/sshd_config. It will then look something like this :-
Revert when your DNS issues are fixed.
Sorry I cannot help with the dnsmasq problem. Isn't in use here, but bind and ISC dhcpd instead.
The "Apr 21 18:29:00 home systemd: Starting Session 730 of user root." messages are just noise, Probably cron tasks run by root?
Just to follow up with the kind of information Nick is requesting. It so happens I added a USB NIC yesterday to a ClearOS 7.2 system. I was lucky in that the base system includes the required driver. This is the sort of information to be looking for:-
and the output from lsusb
In my case the USB-id is "0bda:8150"