[blue68f100]

Sorry for the delay, I have been out of pocket with limited access.

I get an error on the file, but was able to read it. With the logs save as HTML.

The error accours every time you boot the server by the log. This error is normally an indication that you may have a HD failing. My suggestion is to make sure you have a current backup of your files. I would then mark position and jumper settings, remove the HD's and see if you can make a copy of the SnapOS Boot trackes with Digital Dolly. In most cases you do not need it if your running raid1, but recommended. If Maxtors HD's I have seen these fail with in days of each other.

Do not let Windows see the HD's or you will loose everything. Both Spinrite (CD) or Linux OS will not modify the HD's. Neither can read it, so only use the Boot CD for Spinrite or Linux OS to run DD from terminal mode.

Then I would run SpinRite (in maintance mode) on the HD's to see if you are experiencing media problems. Spinrite works at the HW level and does not attempt to inturpit the file structure. Do this on both HD's. If SpinRite has a problems in the 4-5% area, the HD is failing. If you have Maxtors HD's, your on borrowed time, go ahead and replace the HD's with something good. Use the guide in the FAQ's. We normally recommed the WD Raid Edition (RE) drives.

I do not recommend start and stopping the Snaps on a daily bases. This puts a lot of stress on the power supply. And this load increases as the HD get old and start failing. Use a UPS and run it 24/7. If you want auto shutdown you need to a APC Smart-UPS with a network card.