SQUASHFS errors on GT-BE98 Pro

[tcv21212121]

Hi all, 

My log file on my main router is filled with this:

Sep 29 12:36:31 kernel: SQUASHFS error: Unable to read fragment cache entry [13b3965]
Sep 29 12:36:31 kernel: SQUASHFS error: Unable to read page, block 13b3965, size a7cc

I have 2 Mesh extenders that are also GT-BE98 Pro's that are hardwired back to the main device. The only change that I have made was to update  the 2 extenders with the latest firmware 2 days ago however I have yet to update the main unit after a very ugly firmware upgrade project about a year and a half ago that required me to reset the devices and reinstall the older version of firmware to get the unit to obtain a DHCP address from my ISP.  I'm not as well versed in troubleshooting these devices as I would like to be so, any assistance would be greatly appreciated!

[Saltgrass]

I see mentions of the Linux compressor (squashfs) but only in the reboot process and no errors related to it.

I would not be running the primary router with an older version of the firmware.  If you continue to have problems, the instructions do ask folks to reset their routers after the update.  Unless you are making many changes to your firmware settings, it is not that hard to redo the system.

I am currently running a 98 Pro as primary and a 98 Pro as the Mesh unit.  Mine are running as MLO wireless backhaul.

[tcv21212121]

The issue that I had previously was when I updated the router with updated firmware, the device would not get an IP from my ISP and had to take the firmware back to what came from the factory. Not looking forward to having to that again but more importantly, concerned about the error in the log file.

[jzchen]

Is there special requirements/settings from your ISP?  Which ISP?  What was the previous/current primary router firmware version?

[tcv21212121]

I tried putting the one after this (the only one available at the time) and it would not get a DHCP from Cox, my ISP. After reading many articles, it seems that this has been an ongoing issue with ASUS and firmware updates but I havent been able to find out anything about the current firmware. I really dont want to do a firmware upgrade and have it brick the device. 

[jzchen]

If you are adamant about not updating the primary router, then I suggest you revert the two nodes back to the prior firmware.  From experience when a node firmware is updated this can affect any other router in the mesh function....

Cox is fiber or cable modem?  (Modem model if cable)?

[tcv21212121]

Im running Fiber and the Asus is the "modem" hooked directly to the ONT. Its not that I'm adamant about updating the primary node, its just that the last time that I did it, it wouldn't get an IP from the ISP. When speaking to Cox, they said that there was nothing wrong on their end so, the firmware was the only thing to change. Have you had any issues when updating firmware and not being able to get back online? Im hoping that the newer firmware has fixed this issue. I guess I wont know until I try.. uhggg.

[jzchen]

Since you have more than one...  You can replace the primary router with one of the updated nodes, try to set it up and see if you can get it running.  If not just swap the non-updated one back in...

Yes I have had trouble, but with the GT-BE98 Pro I've been running mine in AP mode so it is getting a static IP that I assigned manually....

[Saltgrass]

If you are not using the COX gateway, is there a MAC address on the ONT?

You might go to the bottom of the WAN page and see if clicking the MAC Clone button will enter a MAC address.  If it is the same, it may work.  If it isn't, then try the number you got from the ONT.

EDIT:  You may not be allowed to duplicate the MAC address from the ONT on another device.

[jzchen]

Not sure if that works, to be honest...  Typically the cloning takes a LAN side MAC address not WAN side.  There may be some time, I guesstimate up to 30 minutes, where the DHCP lease from the ISP is tied to the current primary router.  If it is then taking the current router's MAC and cloning that should allow the replacement router to run...