How to troubleshoot router crash during file transfer?

My device is connected to wired ethernet port of GL-MT3000, which connects to corporate LAN via WiFi.
I am transferring files from device to another PC on LAN using scp or rsync.
I may either run scp/rsync on the device - pushing files out
or I can run scp/rsync on outside PC - pulling files from the device.
In either case the router appears to crash or reset itself intermittently - sometimes after a couple of files, sometimes after few dozen, but it always crashes sooner or later.
During the crash the router becomes inaccessible - I cannot connect to router via ssh or HTTP browser for few dozen of seconds,
after that System Log and Kerne Log shows that the system rebooted, but Crash log is empty.

What should I do?
Thank you

I would assume you should set up some log server to push the logs there.
Reboots are often because of faulty power management. Maybe something what could lead the router to draw more power?

Logs are normally stored in memory inside the /tmp directory, but on restart emptied.

You could try this command in a ssh window:

logread -f, and then check what it does.

If its too fast, im afraid there is not really a option than opening the case, and search for a UART header/pins, and then read out the serial connection.

Though ive no experience on gl-inet products, only on my Mochabin i have been using this, which used a usb c connector for it, but normally you need leds or clips for the default traditional uart to serial. :wink:

Though before you continue are you sure its software issue?, not hardware defect?

Cus opening may void your warranty.

When problem happens, all connections to GL-MT3000 fail immediately (including ssh and HTTP), so cannot read any logs before the reset.
Modern CPUs normally have a boot cause register, which indicate whether device booted because of power up or brown out or hardware reset or software reset or crash. Do you know how to access that register on GL-MT3000? Also, is there some indication of input voltage?

Guess using a syslog server would be the way to go here.
Or you could insert a USB stick and symlink the log files to this directory.

No, nothing from the network logger (I tried ncat).
If you are right and this is a sudden power failure, then nothing should come from the log.