Looks good?
[root@XenServer ~]# cat /proc/mdstat
Personalities : [raid10] [raid1]
md0 : active raid1 sdb[0] sdc[1]
976631360 blocks super 1.2 [2/2] [UU]
[=>...................] resync = 5.4% (52749312/976631360) finish=143.3min speed=107400K/sec
unused devices: <none>
[root@XenServer ~]#
Dell Warranty & Onsite Service (Exclusive Offer) (3 Year Dell ProSupport 4HR 7x24 Onsite: Non Mission Critical)
Server no drives ($10,156+/Each)
Why do you need such a costly warranty? Isn't the point of having 2 hosts that you only need 1 running at a given time?
Draw it out so we can better understand what you want to do.
So about once every 2 weeks, I logging to XenCenter, and all my VM's are off 
Is there a log or something I can read to find out what is happening?
@scottalanmiller 2 Days, but I can't remember if I rebooted it or not
@Danp Adding my server to the battery backup overloaded the battery backup, I have to get a larger one ASAP.
@Dashrender they have a desktop chat client! It's right on the front page on rocket.chat! 
Personally, I create a account for another reason. I like to use SSH keys, and SSH keys on a root account is bad form. Also, I disable root login via SSH - this just makes good security sense. If I need access I have to access via console.
@scottalanmiller said:
- It stops malware that gets to you as the end user from escalating to root. Click the wrong website link as root, and your system is pwned. Do it as an end user, you are completely safe (at a system level.) No Linux malware on the market can breach the root escalation point (today.)
I assume we are talking about servers here? I never browse websites on my servers
I find it very hard to do from the command line 
@scottalanmiller not trying to argue, just working it out in my head
At the end of the day my point is that you can't fix ignorance. If you don't know, you don't know. The key is know what your doing BEFORE you do it. And always have a backup just in case
To enable all yum operations to use a proxy server, specify the proxy server details in /etc/yum.conf. The proxy setting must specify the proxy server as a complete URL, including the TCP port number. If your proxy server requires a username and password, specify these by adding proxy_username and proxy_password settings.
The settings below enable yum to use the proxy server mycache.mydomain.com, connecting to port 3128, with the username yum-user and the password qwerty.
# The proxy server - proxy server:port number
proxy=http://mycache.mydomain.com:3128
# The account details for yum connections
proxy_username=yum-user
proxy_password=qwerty