February 7, 20215 yr HI All, I've installed Unraid yesterday, so pretty new to all of this. I tried searching the forums but could not find an answer to my question. The unraid server is installed for media playing and file sharing, thats it for now. But even when i'm not accessing the files or watching a movie, the disk seems busy and making a sound in a pattern. See the video in the following link: https://photos.app.goo.gl/bWBroD7MMDjMA19y7 It's not the ticking of a broken disk (its brand new), it really sounds as if it doing something but i can't find out what and find i strange that is keeps busy. Its been doing this all night. I started with just one disk, ones i have moved over files from my old server I will add the disk from that server to Unraid as well.
February 7, 20215 yr Community Expert You are likely to get better informed feedback if you attach your systems diagnostics zip file (obtained via Tools->Diagnostics) to your NEXT post.
February 7, 20215 yr Author 2 minutes ago, itimpi said: You are likely to get better informed feedback if you attach your systems diagnostics zip file (obtained via Tools->Diagnostics) to your NEXT post. Should have known that, thanks. Here it is! unraid-diagnostics-20210207-1133.zip
February 7, 20215 yr Community Expert Looking at your diagnostics I would thing the activity is caused by your docker containers? Is the 'active' drive 'disk1' at the Unraid level as I see that both your docker image file and your appdata folder are currently on that drive. There are also lots of messages in the syslog relating to the 'paperless' container not connecting. You could check by stopping the docker service and seeing if that stops this disk activity.
February 7, 20215 yr Author 2 minutes ago, itimpi said: Looking at your diagnostics I would thing the activity is caused by your docker containers? Is the 'active' drive 'disk1' at the Unraid level as I see that both your docker image file and your appdata folder are currently on that drive as well. There are also lots of messages in the syslog relating to the 'paperless' container not connecting. You could check by stopping the docker service and seeing if that stops this disk activity. Yes, Disk 1 is the one and only disk for now. I've stopped the paperless container and that indeed helped a bit. Just to be sure i have to correct log, is below the error you are mentioning? Feb 6 20:36:15 Unraid nginx: 2021/02/06 20:36:15 [error] 26535#26535: *45970 connect() to unix:/var/tmp/Paperless-ng.sock failed (111: Connection refused) while connecting to upstream, client: 192.168.1.48, server: , request: "GET /dockerterminal/Paperless-ng/token HTTP/1.1", upstream: "http://unix:/var/tmp/Paperless-ng.sock:/token", host: "192.168.1.11", referrer: "http://192.168.1.11/dockerterminal/Paperless-ng/" Feb 6 20:36:15 Unraid nginx: 2021/02/06 20:36:15 [error] 26535#26535: *46126 connect() to unix:/var/tmp/Paperless-ng.sock failed (111: Connection refused) while connecting to upstream, client: 192.168.1.48, server: , request: "GET /dockerterminal/Paperless-ng/ws HTTP/1.1", upstream: "http://unix:/var/tmp/Paperless-ng.sock:/ws", host: "192.168.1.11"
February 7, 20215 yr Community Expert 3 minutes ago, Michelangelo said: Yes, Disk 1 is the one and only disk for now. I've stopped the paperless container and that indeed helped a bit. Note I said try disabling the docker service - not just the container to make sure. Do you lave other containers running - this is not something that can be seen from the diagnostics. Also it is possible that the docker service itself is doing something periodically even when idle. 5 minutes ago, Michelangelo said: Yes, Disk 1 is the one and only disk for now. I've stopped the paperless container and that indeed helped a bit. Just to be sure i have to correct log, is below the error you are mentioning? Feb 6 20:36:15 Unraid nginx: 2021/02/06 20:36:15 [error] 26535#26535: *45970 connect() to unix:/var/tmp/Paperless-ng.sock failed (111: Connection refused) while connecting to upstream, client: 192.168.1.48, server: , request: "GET /dockerterminal/Paperless-ng/token HTTP/1.1", upstream: "http://unix:/var/tmp/Paperless-ng.sock:/token", host: "192.168.1.11", referrer: "http://192.168.1.11/dockerterminal/Paperless-ng/" Feb 6 20:36:15 Unraid nginx: 2021/02/06 20:36:15 [error] 26535#26535: *46126 connect() to unix:/var/tmp/Paperless-ng.sock failed (111: Connection refused) while connecting to upstream, client: 192.168.1.48, server: , request: "GET /dockerterminal/Paperless-ng/ws HTTP/1.1", upstream: "http://unix:/var/tmp/Paperless-ng.sock:/ws", host: "192.168.1.11" Yes. That was what made me immediately suggest docker (and containers) as the possible causes of the disk activity. BTW: I have no experience of that container so have no idea why you are getting that message logged. It makes me think something may not be set up ideally.
February 7, 20215 yr Author 1 minute ago, itimpi said: Note I said try disabling the docker service - not just the container to make sure. Do you lave other containers running - this is not something that can be seen from the diagnostics. Also it is possible that the docker service itself is doing something periodically even when idle. Yes. That was what made me immediately suggest docker (and containers) as the possible causes of the disk activity. BTW: I have no experience of that container so have no idea why you are getting that message logged. It makes me think something may not be set up ideally. The paperless-ng docker works as expexted, but i will post the error in the paperloss topic. For now, just the paperless docker is stopped. All others are still working and the disk is quiet. It stopped doing anything. The error interval in the logs corrensponds with the "pattern" of sound that the disk made. So im pretty sure it has something to do with that error. I will investigate a bit more. Thanks. Allready love the community for such quick responses and the software is just great.
Archived
This topic is now archived and is closed to further replies.