RT-AC86U Strange Behavior

[JT Strickland]

I set my dns filter in the LAN "on" and "router", and since I haven't been able to reboot it. It may be a coincidence, but it is weird. I reboot through the GUI, and it goes through the motions, and the LED's never go off, and they always go off two or three times during the reboot process (sometimes they don't come back on, but that's a different story). I haven't had a system entry in the log barely since, either, and I tried to restart syslog-ng in scribe, and it failed to shut syslog-ng down to restart it. Twice. I tried rebooting the router twice throug the GUI and once through scmerlin by amtm, same thing. It bailed out of scmerlin, and nothing appeared to happened.

Anybody got any ideas? Next step is to pull the plug, although I don't like to do that. That should at least reboot it.
tia,
jts

 

[bbunge]

Check to see if the /jffs is mounted. If not look in the post for the 384.18 release for your fix.

 

[JT Strickland]

It's mounted, I reckon, but I've never saw this many orphaned inodes in the disk check log file.
I hope it's not an indication that about to crash. BTW, I pulled the plug and it's back ~ normal.
Also, thanks for the help, I appreciate it.
Sun Sep 20 04:02:29 CDT 2020 Probing 'ext4' on device /dev/sda1 Running disk check v2.9, with command 'e2fsck -p' on /dev/sda1 sandisk32: recovering journal sandisk32: Clearing orphaned inode 1309456 (uid=0, gid=0, mode=0100600, size=144749) sandisk32: Clearing orphaned inode 1308228 (uid=0, gid=0, mode=0100755, size=10136) sandisk32: Clearing orphaned inode 1308241 (uid=0, gid=0, mode=0100755, size=31032) sandisk32: Clearing orphaned inode 1308189 (uid=0, gid=0, mode=0100644, size=83960) sandisk32: Clearing orphaned inode 1309085 (uid=0, gid=0, mode=0100755, size=736712) sandisk32: Clearing orphaned inode 1308479 (uid=0, gid=0, mode=0100755, size=251848) sandisk32: Clearing orphaned inode 1309074 (uid=0, gid=0, mode=0100644, size=30888) sandisk32: Clearing orphaned inode 1308792 (uid=0, gid=0, mode=0100755, size=5960) sandisk32: Clearing orphaned inode 1308786 (uid=0, gid=0, mode=0100755, size=14224) sandisk32: Clearing orphaned inode 1308783 (uid=0, gid=0, mode=0100755, size=1261064) sandisk32: Clearing orphaned inode 1308234 (uid=0, gid=0, mode=0100755, size=105168) sandisk32: Clearing orphaned inode 1308218 (uid=0, gid=0, mode=0100755, size=84160) sandisk32: Clearing orphaned inode 1308215 (uid=0, gid=0, mode=0100755, size=51176) sandisk32: Clearing orphaned inode 1308213 (uid=0, gid=0, mode=0100755, size=22504) sandisk32: Clearing orphaned inode 1308208 (uid=0, gid=0, mode=0100755, size=735216) sandisk32: Clearing orphaned inode 1308206 (uid=0, gid=0, mode=0100755, size=14312) sandisk32: Clearing orphaned inode 1308200 (uid=0, gid=0, mode=0100755, size=1431816) sandisk32: Clearing orphaned inode 1308196 (uid=0, gid=0, mode=0100755, size=136952) sandisk32: Clearing orphaned inode 1308900 (uid=0, gid=0, mode=0100755, size=15200) sandisk32: Clearing orphaned inode 1308887 (uid=0, gid=0, mode=0100755, size=47216) sandisk32: Clearing orphaned inode 1308864 (uid=0, gid=0, mode=0100755, size=155888) sandisk32: Clearing orphaned inode 1308862 (uid=0, gid=0, mode=0100755, size=125736) sandisk32: Clearing orphaned inode 1308858 (uid=0, gid=0, mode=0100755, size=968480) sandisk32: Clearing orphaned inode 1308856 (uid=0, gid=0, mode=0100755, size=14176) sandisk32: Clearing orphaned inode 1308846 (uid=0, gid=0, mode=0100755, size=18248) sandisk32: clean, 1380/1880480 files, 750224/7511036 blocks Sun Sep 20 04:02:29 CDT 2020 Disk check done on /dev/sda1 Sun Sep 20 07:03:13 CDT 2020 Waited 2s for NTP to sync date Sun Sep 20 07:03:13 CDT 2020 Probing 'ext4' on device /dev/sda1 Running disk check v2.9, with command 'e2fsck -p' on /dev/sda1 sandisk32: recovering journal sandisk32: clean, 1380/1880480 files, 750704/7511036 blocks Sun Sep 20 07:03:15 CDT 2020 Disk check done on /dev/sda1 --------------------------------------------------- END FILE

 

[JT Strickland]

It looks like the first reboot happened, but none after that until I pulled the plug.

A search didn't turn up much here for orphaned inodes, duck-duck-go turned up a few pages. I have seen it before in the disk, but not before 384.19, which may be another coincidence. But I have never seen so many as the 4 am reboot.

Can anybody point me toward the cause?