Well, life was going great till this past week.  I am hoping the issue is nothing, but thought before I went crazy rebooting, I would ask.

 

The log was too big for pastebine, so I put just a section of it, hopefully it is enough since the same thing is repeated over and over.

http://pastebin.com/N9weizCZ

 

edit:

looking at the array operation and it appears the mover is running, which it shouldnt be it should run at its default time

 

edit2: the mymain view on unmenu is not showing the cache disk, but the unraid main page, under cache devices does show the drive and it is green, so not sure if this could be the source of the issue

syslog-2015-04-15.zip

My initial thought was going to be to run reiserfsck on your drives, but all of your drives appear to be marked as read only, so I would think that something else is going on.

 

Also, what ever drive is hooked up to ata1 is tossing errors that are consistent with loose / bad sata cables and/or power issues.

 

With all of the drives showing read-only, I would find a way to post up the entire syslog.  Zip if necessary so that we can see what's happening at the beginning when emhttp is trying to mount the drives.

How can I get the entire log?  I did post the 4MB syslog in the zip there.

 

The strange thing with the sata cable issue is the system hasnt moved in months, so nothing would be jarred loose.  but I would be on bored with power as that could likely result from a PSU going bad I suppose.

 

Would it be a bad idea to reboot at this point, just to see if the issue clears?

 

Is there an easy way to figure out what is actually plugged into ata1? 

Looks like your syslog rotated. You probably have older syslogs in /var/log with names like syslog1.

 

It looks like ata1 may be your cache drive. Most of the log is just attempts to create files on cache. For some reason, those files are on a user share name "Video Video". Is this really what you intend for that user share to be named, or is some app misconfigured?

How can I get the entire log?  I did post the 4MB syslog in the zip there.

 

The strange thing with the sata cable issue is the system hasnt moved in months, so nothing would be jarred loose.  but I would be on bored with power as that could likely result from a PSU going bad I suppose.

 

Would it be a bad idea to reboot at this point, just to see if the issue clears?

 

Is there an easy way to figure out what is actually plugged into ata1?

A reboot certainly won't hurt, and the benefit would be that there is going to be a clean syslog from the beginning to work from and it'll be easier to figure out whats in ata1.

 

There are command lines you can enter to determine whats attached to ata1, but not at work right now and can't remember off the top of my head.  But the clean syslog from a reboot will also show it.

 

Most of the log is just attempts to create files on cache.

 

I suppose thats also possible, but there is a reference to each and every drive in the same log entry, which is what I was looking at.  Assuming its only the cache drive set to read only its going to be alot easier to fix.  A reboot will tell us everything we need to know.

here it is...

syslog-2015-04-16.zip

as a follow-up, I wanted to post a syslog for after removing the cache drive, it would seem as though it may have been my issue...but I really have no idea, but some things do appear functioning with it gone, so maybe.  Plus, my log isn't stupid big now that it is gone

syslog-2015-04-16_1.txt

It certainly appears that the cache drive was the problem.  The new syslog doesn't have any errors in it.  It also looks like the system at one point gave up trying to mount it on the first one and then just error after error after error

OK, hopefully, thats all it is.  I will stick it on another system and see what it does, run a preclear against it and stuff to work the drive a bit to see if it still acts crazy.

So, I ran a preclear on the said cache drive, here are the results.

 

preclear_finish_WD-WMAP42311958_2015-04-17.txt