I have my Blue Iris system set to save to a Cache'd unRaid location. However, I have noticed that disk never spins down. I have been periodically checking streams, and the only thing going is my Blue Iris stuff. If I shut down this VM, the disk will eventually spin down and stay down.

 

Thoughts, or a method for looking in to this? not really sure where to even start from here.

 

EDIT: To clarify, my cache drive is an SSD. I mean the array disk I have set to exclusively have my Blue Iris share use, never spins down.

I noticed in another thread that you also have Plex on your system?  Plex is known for continually accessing the drive it is hosted on, typically the cache drive.

I noticed in another thread that you also have Plex on your system?  Plex is known for continually accessing the drive it is hosted on, typically the cache drive.

 

I do have Plex, run in a docker, which is off of an unassigned device now. I had thought about Plex being the culprit before, and shut it down for a day trying to diagnose. Thanks for the thought though!

 

I also now realize that I was not very clear in my initial post. Edited for clarification.

I have my Blue Iris system set to save to a Cache'd unRaid location. However, I have noticed that disk never spins down. I have been periodically checking streams, and the only thing going is my Blue Iris stuff. If I shut down this VM, the disk will eventually spin down and stay down.

 

Thoughts, or a method for looking in to this? not really sure where to even start from here.

 

EDIT: To clarify, my cache drive is an SSD. I mean the array disk I have set to exclusively have my Blue Iris share use, never spins down.

 

 

I'm not sure I understand the question. Blue Iris is keeping the disk busy.

But I set that share to use cache... so shouldnt it write it all to cache then move it over to the disk I specified at night?

 

Attached share settings.

So once Blue Iris writes a file it never has to access that file again?

So once Blue Iris writes a file it never has to access that file again?

 

It maintains access, for reviewing alerts and archived snaps. I think I see your point, it is constantly looking at the drive apparently, even though I am not necessarily calling up the archives etc. I will have to have a look at the Blue Iris forums to see if I can stop this. I really only check the alerts as they happen(when they would be on the cache drive), have yet to have to go back and review.

I know this is a very old post, but just wondering if you found a solution to this ?i have similar situation where BI is running on a Windows VM and its keeping the disk busy. if I shutdown the VM, the disk will spin down eventually and stay.