WebUI on EAP225 not accessible after power outage - squashfs error
After short power outage EAP225 working quite unstable, rebooting every 1.5-2 hours, moreover WebUI is not accessible any but ssh. Wifi still working, so clients can connect.
I have been able to loogin via ssh and check processes and log, there is no http active process and nothing listening on port 80 or 443 additionaly to that, dmesg shows alot of error like "squashfs error: unable to read page, block ...".
So, how it could be fixed ? it it any chance to re-image ?
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Goosey-George wrote
After short power outage EAP225 working quite unstable, rebooting every 1.5-2 hours, moreover WebUI is not accessible any but ssh. Wifi still working, so clients can connect.
I have been able to loogin via ssh and check processes and log, there is no http active process and nothing listening on port 80 or 443 additionaly to that, dmesg shows alot of error like "squashfs error: unable to read page, block ...".
So, how it could be fixed ? it it any chance to re-image ?
Please upload the page of the error in the SSH, so that we can know more information about this.
If it is ok for you, you can reset the EAP to have a try. We are not sure if the hardware or software has something wrong. Sometimes when we reset the AP, some issues will be fixed automatically.
- Copy Link
- Report Inappropriate Content
unfortunately it's remote location, but will try to do a reset next time BusyBox v1.01 (2018.06.28-06:58+0000) Built-in shell (ash) Enter 'help' for a list of built-in commands. $ dmesg UASHFS error: Unable to read fragment cache entry [54e35c] [ 1285.910000] SQUASHFS error: Unable to read page, block 54e35c, size 765c [ 1285.920000] SQUASHFS error: Unable to read fragment cache entry [54e35c] [ 1285.920000] SQUASHFS error: Unable to read page, block 54e35c, size 765c [ 1285.930000] SQUASHFS error: Unable to read fragment cache entry [54e35c] [ 1285.940000] SQUASHFS error: Unable to read page, block 54e35c, size 765c [ 1285.950000] SQUASHFS error: Unable to read fragment cache entry [54e35c] [ 1285.950000] SQUASHFS error: Unable to read page, block 54e35c, size 765c [ 1285.960000] SQUASHFS error: Unable to read fragment cache entry [54e35c] [ 1285.970000] SQUASHFS error: Unable to read page, block 54e35c, size 765c [ 1285.970000] SQUASHFS error: Unable to read fragment cache entry [54e35c] [ 1285.980000] SQUASHFS error: Unable to read page, block 54e35c, size 765c $ cat /proc/partitions major minor #blocks name 31 0 128 mtdblock0 31 1 64 mtdblock1 31 2 64 mtdblock2 31 3 1536 mtdblock3 31 4 14336 mtdblock4 31 5 192 mtdblock5 31 6 64 mtdblock6 $ mount /dev/mtdblock4 on / type squashfs (ro,relatime) /proc on /proc type proc (rw,relatime) devpts on /dev/pts type devpts (rw,relatime,mode=622) none on /tmp type ramfs (rw,relatime) none on /var type ramfs (rw,relatime) sysfs on /sys type sysfs (rw,relatime) $ netstat -ln Active Internet connections (only servers) Proto Recv-Q Send-Q Local Address Foreign Address State tcp 0 0 0.0.0.0:51237 0.0.0.0:* LISTEN tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN udp 0 0 0.0.0.0:1040 0.0.0.0:* udp 0 0 127.0.0.1:4000 0.0.0.0:* raw 0 0 0.0.0.0:255 0.0.0.0:* 0 Active UNIX domain sockets (only servers) Proto RefCnt Flags Type State I-Node Path
$ ps ax
PID Uid VmSize Stat Command
1 root 408 S init
2 root SW [kthreadd]
3 root SW [ksoftirqd/0]
4 root SW [kworker/0:0]
6 root SW< [khelper]
7 root SW [kworker/u:1]
19 root SW [irq/10-ath79-gp]
57 root SW [sync_supers]
59 root SW [bdi-default]
61 root SW< [kblockd]
91 root SW [kswapd0]
141 root SW [fsnotify_mark]
150 root SW< [ath79-spi]
161 root SW [mtdblock0]
166 root SW [mtdblock1]
171 root SW [mtdblock2]
176 root SW [mtdblock3]
181 root SW [mtdblock4]
186 root SW [mtdblock5]
191 root SW [mtdblock6]
205 root SW [kworker/0:1]
214 root 320 S /sbin/hotplug2 --override --persistent --set-rules-file /etc/hotplug2.rules --set-coldplug-cmd /sbin/udevtrigger --max-children 1
287 root 7316 S /usr/bin/uclited
289 root 416 S /bin/sh /etc/rc.d/rc.eapcs
291 root 368 S /sbin/getty ttyS0 115200
292 root 336 R cat /usr/bin/eap-cs
293 root 7316 S /usr/bin/uclited
294 root 7316 S /usr/bin/uclited
295 root 7316 S /usr/bin/uclited
296 root 7316 S /usr/bin/uclited
297 root 7316 S /usr/bin/uclited
298 root 7316 S /usr/bin/uclited
299 root 7316 S /usr/bin/uclited
346 root 4316 S /usr/bin/uclited
356 root 372 S syslogd -C -l 7
368 root 340 S klogd
371 root 7316 S /usr/bin/uclited
485 root 4316 S /usr/bin/uclited
486 root 4316 S /usr/bin/uclited
511 root 4160 S /usr/bin/uclited
528 root 7316 S /usr/bin/uclited
529 root 7316 S /usr/bin/uclited
536 root 7316 S /usr/bin/uclited
539 root 7316 S /usr/bin/uclited
540 root 7316 S /usr/bin/uclited
568 root 7316 S /usr/bin/uclited
585 root SW [kworker/u:2]
597 root 364 S /sbin/udhcpc -h EAP225-D8-0D-17-10-C6-E0 -i br0 -p /tmp/udhcpc.pid -s /etc/udhcpc.script
598 root 212 S /sbin/udhcpc -h EAP225-D8-0D-17-10-C6-E0 -i br0 -p /tmp/udhcpc.pid -s /etc/udhcpc.script
610 root 356 S /usr/local/sbin/dropbear -p 22 -r /tmp/dropbear_rsa_host_key -d /tmp/dropbear_dss_host_key -L
917 root 592 S hostapd /tmp/topology1.conf
1108 root 592 S hostapd /tmp/topology2.conf
1260 root 7316 S /usr/bin/uclited
1290 root 7316 S /usr/bin/uclited
1291 root 7316 S /usr/bin/uclited
1292 root 7316 S /usr/bin/uclited
1309 root 7316 S /usr/bin/uclited
1310 root 7316 S /usr/bin/uclited
10792 root 620 R /usr/local/sbin/dropbear -p 22 -r /tmp/dropbear_rsa_host_key -d /tmp/dropbear_dss_host_key -L
10865 guest 492 S -sh
11444 guest 396 R ps ax
- Copy Link
- Report Inappropriate Content
so, factory reset doesn't help, even became worse :) I could see a default SSID of AP but can't connect.
Also I have tryed with lan cable, nmap shows me that only ssh port is open but login via ssh doesn't work anymore.
Is it any possibility of tftp recovery or any other method ?
- Copy Link
- Report Inappropriate Content
Goosey-George wrote
Is it any possibility of tftp recovery or any other method ?
If the flash chip is defective, usually no recovery method will help. I suggest to RMA the EAP, as a business-class device it has lifetime warranty (lifetime being the active support time of the product).
- Copy Link
- Report Inappropriate Content
Goosey-George wrote
so, factory reset doesn't help, even became worse :) I could see a default SSID of AP but can't connect.
Also I have tryed with lan cable, nmap shows me that only ssh port is open but login via ssh doesn't work anymore.
Is it any possibility of tftp recovery or any other method ?
We want to check if the flash of your devcie defective, and I have sent you a message about that. If possible, I think we can have a check together.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 1322
Replies: 5
Voters 0
No one has voted for it yet.