So I've had this problem for a while now but at this point, I really like to know why this happens. This problem usually occurs when I'm copying files (probably) larger than 50MB. My setup is very basic, with one parity drive and two as storage. For whatever reason, the existing parity drive sometimes loses 'memory' (for a lack of a better word to use) and I would have to start the parity-sync. I see others have posted a log file, but I wouldn't know where to find it at the moment. The server is used mostly as storage, so it's usually turned off unless I want to ensure my files are safely stored on my unraid server. This problem happens quite often to me, for someone that doesn't use it all that often.

 

The version of unraid being used is 4.7

 

The obvious question is by what means do you power off your server?  It must be shut down correctly (normally via the web interface) to avoid forcing a parity check at the next start up.  If you always do that then it suggests a problem perhaps with your USB flash stick or other hardware.

I always use the web interface to shut down the server. The hard drive was replaced a while ago but still experience this problem.  I haven't looked into the usb memory stick as a problem. It's made by Kingston but quite old. Could the age or perhaps maybe even the write/read speeds of the stick cause this sort of problem? How would I go about transferring the contents from this Kingston stick to another and maintain the server as it is?

I assume your using only a Basic licence (since only three drives).  In that case, you should be able to create another stick (make it bootable), and copy across your files.  However, there is a possibility that something in your current settings is behind this in which case copying the files might simply mean that the problem remains. 

Run check disk on the flash in a PC.

I'm using 4.7, have the very same problem with my parity drive and my drive happens to be a seagate..  If I have to shutdown or reboot for some reason parity drive comes up as new with blue dot.  Is this the expected behavior?  Bug?  Or coincidence?  I'm replacing my parity drive as soon as it it's delivered.

 

 

None of these behaviors are normal nor are they bugs. There is something wrong with these systems. As a test, prepare a new flash (or backup the existing one) with a clean install and see if the behavior persists on a clean install.

I'm using 4.7, have the very same problem with my parity drive and my drive happens to be a seagate..  If I have to shutdown or reboot for some reason parity drive comes up as new with blue dot.  Is this the expected behavior?  Bug?  Or coincidence?  I'm replacing my parity drive as soon as it it's delivered.

If it shows up as "new" (blue) it usually indicates it was not detected at all on the prior boot.  I'd suspect the cabling first, drive trays, etc.

Thanks for the advice.

I'm not sure if this fixed it as I've only had the server back up for a day. I'm using another flash drive and upgraded to one of the betas.

I've followed this thread and checked everything out. Cleaned all the connection points, changed loose connections, cables and tried different flash drives.

 

What device in any system will cause this behavior? 

What device in any system will cause this behavior?

Anything with an intermittent fault in any system will cause that behavior.

It did not cause a problem in 4.7. What turned out to be a problem is a bug. The beta 5.0-beta14 code does not support my controller and caused some odd behavior. I look forward to the next 5.0 GA version and hope it supports my controller.