Looking for a little guidance on troubleshooting something. I'd rate myself a noob.
I have an N66U with an attached 4 TB drive. When I remux a video file on a Windows 8.1 PC from a local drive to a folder on the 4TB drive, the process will error out every time, and while the N66U continues to route, SSH and the Webgui are no longer available. I have to power reset.
Specifically, I use a program called Videoredo for this, and remuxing errors with the message: "FFmpeg muxer: error writing packet". Videoredo keeps a log, but there doesn't seem to be more on the error. If I SSH into the router, and run top while executing the remux, around 73% CPU is /user/sbin/smbd -D -s /etc/smb.conf and 17% is [usb-storage]. Memory usage is around 73%. When the error occurs, top freezes. When I power reset the syslog starts over, so I don't have anything there.
This happens with the .53 firmware, and for a lark I tried .55 alpha (because of the reference to the updated ffmpeg). Same thing.
If I remux back to the local drive, and then copy the result to the 4TB drive, everything is fine. In all other respects everything is working as expected. I am running minidlna 1.1.4-2 on entware off a flash drive, adblocking with dnsmasq using the combined hosts setup, and two VPN servers (with nothing connected).
I have an N66U with an attached 4 TB drive. When I remux a video file on a Windows 8.1 PC from a local drive to a folder on the 4TB drive, the process will error out every time, and while the N66U continues to route, SSH and the Webgui are no longer available. I have to power reset.
Specifically, I use a program called Videoredo for this, and remuxing errors with the message: "FFmpeg muxer: error writing packet". Videoredo keeps a log, but there doesn't seem to be more on the error. If I SSH into the router, and run top while executing the remux, around 73% CPU is /user/sbin/smbd -D -s /etc/smb.conf and 17% is [usb-storage]. Memory usage is around 73%. When the error occurs, top freezes. When I power reset the syslog starts over, so I don't have anything there.
This happens with the .53 firmware, and for a lark I tried .55 alpha (because of the reference to the updated ffmpeg). Same thing.
If I remux back to the local drive, and then copy the result to the 4TB drive, everything is fine. In all other respects everything is working as expected. I am running minidlna 1.1.4-2 on entware off a flash drive, adblocking with dnsmasq using the combined hosts setup, and two VPN servers (with nothing connected).
