Opened 14 months ago
Closed 14 months ago
#2446 closed (invalid)
Build 18770: esr-9752 sqashfs error
| Reported by: | Ric03 | Owned by: | |
|---|---|---|---|
| Keywords: | Cc: |
Description (last modified by Ric03)
This is on my esr9752 router with lates BS's 18770 build (test build, not posted on the ftp site). I don't know what the system was trying to read, but there's this error in the dmesg:
<3>SQUASHFS error: lzma returned unexpected result 0x1 <3>SQUASHFS error: Unable to read fragment cache block [157d50] <3>SQUASHFS error: Unable to read page, block 157d50, size 892f <3>SQUASHFS error: lzma returned unexpected result 0x1 <3>SQUASHFS error: Unable to read fragment cache block [157d50] <3>SQUASHFS error: Unable to read page, block 157d50, size 892f <3>SQUASHFS error: lzma returned unexpected result 0x1 <3>SQUASHFS error: Unable to read fragment cache block [157d50] <3>SQUASHFS error: Unable to read page, block 157d50, size 892f <3>SQUASHFS error: lzma returned unexpected result 0x1 <3>SQUASHFS error: Unable to read fragment cache block [157d50] <3>SQUASHFS error: Unable to read page, block 157d50, size 892f
Change History (6)
comment:1 Changed 14 months ago by Ric03
- Description modified (diff)
comment:2 Changed 14 months ago by Ric03
- Description modified (diff)
- Summary changed from Build 18770: sqashfs error to Build 18770: esr-9752 sqashfs error
comment:3 Changed 14 months ago by BrainSlayer
comment:4 Changed 14 months ago by Ric03
Ok I reflashed back to 16214 but the error was still there .. had issues flashing I had to try flashing two times. After flashing 16214 for the second time, the system looked good but I could not login .. I could see from the remote syslogd (redirected syslog to my PC some days ago) that the sqashfs errors were still there: the system was degradating quickly. I had an illumination so I decided to unplug the power cable and re-plug .. that's a power OFF/ON .. after this, the squashfs error disappeared. Can it be something to do with the fact that the problem was with something related to the status of the hardware? I have then reflashed 18770 and the error did not reappear. But in the dmesg there's another message that's strange:
<5>0x00000012f000-0x0000003e0000 : "rootfs" <4>mtd: partition "rootfs" must either start or end on erase block boundary or be smaller than an erase block -- forcing read-only
comment:5 Changed 14 months ago by Ric03
Closing this as the hard reboot and double re-flashing seems to have cured it. I'll open a ticket just for the rootfs warning message.
comment:6 Changed 14 months ago by Ric03
- Resolution set to invalid
- Status changed from new to closed

looks like its not flashed correct