Gargoyle Forum

Hello everyone,

I am having some issues running some usb storage from the router (Archer c7 v2).
A little about my network:

I have two WD mybooks (1-3tb & 1 500 GB that are running great) and one 750gb hhd that is connected to a sata to usb cable. The HDD is receiving info from an ipcamera stream that is managed by Motioneyeos on a raspberry pi 3. It is mostly taking timelapses and then compiling the timelapse into a video every night with a rc.local. This setup has been running great on a 2.4 ghz only network until I turned on the 5 ghz after the 1.10.0 upgrade. (the 5ghz never worked for my router in gargoyle 1.9.2)

I have been trying to run a "logread" command using the cli to try and pinpoint any errors when the drive "drops" and loses connection to the camera stream. When this happens, I have to reboot motioneyeos on raspberry pi and then power cycle the drive. This "fix seems to work for about 1-5 days and then the connection "drops".

I was reading somewhere that the 5ghz and 2.4 ghz SSID names should be drastically different. If SSID names are similar, they could cause issues with connection. I have the names as "Home-gargoyle" for 2.4 ghz and HG-5ghz for 5 ghz. I dont see how this could cause my issue though..

Oh I also installed a murmur server on the router. Not sure is that could be causing any kind of troubles..

What more could I do to find this issue? Any help?

have you tried a failsafe reset (factory reset) yet?

or re-flash

ispyisail wrote:have you tried a failsafe reset (factory reset) yet?

or re-flash

No I have not done that yet. It was quot a pain to install gargoyle on the archer. Not saying it's a bad idea to do that but I'll spend a good chunk of time getting everything back to where I am now.

Factory reset will take me back to tp link firmware right?

I am getting this error from logread:

Wed Dec 20 06:23:27 2017 daemon.err uhttpd[3072]: sh: write error: Broken pipe
Wed Dec 20 06:23:51 2017 daemon.err uhttpd[3072]: sh: write error: Broken pipe
Wed Dec 20 06:23:51 2017 daemon.err uhttpd[3072]: sh: write error: Broken pipe
Wed Dec 20 06:23:51 2017 daemon.err uhttpd[3072]: sh: write error: Broken pipe
Wed Dec 20 06:23:51 2017 daemon.err uhttpd[3072]: sh: write error: Broken pipe
Wed Dec 20 06:23:51 2017 daemon.err uhttpd[3072]: sh: write error: Broken pipe
Wed Dec 20 06:23:51 2017 daemon.err uhttpd[3072]: sh: write error: Broken pipe
Wed Dec 20 06:23:51 2017 daemon.err uhttpd[3072]: sh: write error: Broken pipe
Wed Dec 20 06:23:51 2017 daemon.err uhttpd[3072]: sh: write error: Broken pipe
Wed Dec 20 06:24:05 2017 daemon.err uhttpd[3072]: sh: write error: Broken pipe
Wed Dec 20 06:24:12 2017 daemon.err uhttpd[3072]: sh: write error: Broken pipe
Wed Dec 20 06:24:12 2017 daemon.err uhttpd[3072]: sh: write error: Broken pipe
Wed Dec 20 06:24:12 2017 daemon.err uhttpd[3072]: sh: write error: Broken pipe
Wed Dec 20 06:24:12 2017 daemon.err uhttpd[3072]: sh: write error: Broken pipe
Wed Dec 20 06:24:12 2017 daemon.err uhttpd[3072]: sh: write error: Broken pipe
Wed Dec 20 06:24:12 2017 daemon.err uhttpd[3072]: sh: write error: Broken pipe
Wed Dec 20 06:24:12 2017 daemon.err uhttpd[3072]: sh: write error: Broken pipe
Wed Dec 20 06:24:12 2017 daemon.err uhttpd[3072]: sh: write error: Broken pipe
Wed Dec 20 06:24:12 2017 daemon.err uhttpd[3072]: sh: write error: Broken pipe
Wed Dec 20 06:24:12 2017 daemon.err uhttpd[3072]: sh: write error: Broken pipe
Wed Dec 20 06:24:12 2017 daemon.err uhttpd[3072]: sh: write error: Broken pipe
Wed Dec 20 06:24:12 2017 daemon.err uhttpd[3072]: sh: write error: Broken pipe
Wed Dec 20 06:24:12 2017 daemon.err uhttpd[3072]: sh: write error: Broken pipe
Wed Dec 20 06:24:12 2017 daemon.err uhttpd[3072]: sh: write error: Broken pipe
Wed Dec 20 06:24:12 2017 daemon.err uhttpd[3072]: sh: write error: Broken pipe
Wed Dec 20 06:24:13 2017 daemon.err uhttpd[3072]: sh: write error: Broken pipe

can be safely ignored.