Posted: Fri Aug 06, 2021 16:19 Post subject: [SOLVED] Issues upgrading TP-Link WDR4900
TP-Link WDR4900 V1.3
Bootloop
According to the boot log the root fs could not be mounted. Something about device 31.3 that was not found.
Tried dd-wrt V44715 and V47086 earlier, also bootloops.
Last known stable version to me is V42366 which was mentioned in a different topic about WDR4900 bootloop.
I haven't tried the versions between V47117 and V42366 to find another stable release. There are too many to try.
Joined: 08 May 2018 Posts: 14246 Location: Texas, USA
Posted: Fri Aug 06, 2021 16:33 Post subject:
@urkel: Please provide boot log from this version or first known bad firmware image so that we can forward the information to the developer. In other words, try each new version from 42366 forward until you find the build that breaks it. This is likely what he will ask you to do.
EDIT: Found two threads regarding this, am forwarding the information to BrainSlayer now. Seems that
- started from build r40559 dd 20190806 => ok
- webflash to build r41269 dd 20191010 => ok
- webflash to build r41686 dd 20191210 => ok
- webflash to build r42366 dd 20200214 => ok
- webflash to build r42910 dd 20200415 = not ok ! (boot loop with flashing lan/wan leds)
- revert with tftp r42366 dd 20200214 => ok
- webflash to build r42681 dd 20200313 = not ok ! (boot loop with flashing lan/wan leds)
- revert with tftp r42366 dd 20200214 => ok
- webflash to build r42542 dd 20200227 = not ok ! (boot stuck with only power led on and connected LAN light blinking)
Here is where I got V42366 from as working and it seems the issue arose before V42366 according to the tests from koen.vdvelde. Probably between V42366 and V42910!?
Joined: 08 May 2018 Posts: 14246 Location: Texas, USA
Posted: Fri Aug 06, 2021 17:17 Post subject:
I guess my edits didn't hit your radar. I found the thread, and noted that two builds were not tested. It would be great to compare the first build that broke to the current one as far as bootlogs, considering the number of releases between 42366 and 47117. _________________ "Life is but a fleeting moment, a vapor that vanishes quickly; All is vanity"
Contribute To DD-WRT Pogo - A minimal level of ability is expected and needed... DD-WRT Releases 2023 (PolitePol)
DD-WRT Releases 2023 (RSS Everything)
----------------------
Linux User #377467 counter.li.org / linuxcounter.net
About testing builds. To make sure that I am not going to test builds that are not helpfull, could you give me the build number where you want me to start testing!?
Already tried V42410 -> bootloop
[ 2.285767] No filesystem could mount root, tried: squashfs
[ 2.291426] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(31,3)
Joined: 08 May 2018 Posts: 14246 Location: Texas, USA
Posted: Fri Aug 06, 2021 18:49 Post subject:
I knew I forgot a build in there, and yes, I meant test 42410, 42460, and 42514 in order and report the first build that failed; which we now know is 42410. Thanks for the feedback! I will update the developer. _________________ "Life is but a fleeting moment, a vapor that vanishes quickly; All is vanity"
Contribute To DD-WRT Pogo - A minimal level of ability is expected and needed... DD-WRT Releases 2023 (PolitePol)
DD-WRT Releases 2023 (RSS Everything)
----------------------
Linux User #377467 counter.li.org / linuxcounter.net
Joined: 08 May 2018 Posts: 14246 Location: Texas, USA
Posted: Sat Aug 07, 2021 12:06 Post subject:
urkel wrote:
Already tried V42410 -> bootloop
[ 2.285767] No filesystem could mount root, tried: squashfs
[ 2.291426] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(31,3)
The bootloop is gone, but the unit doesn't work well.
I did an upgrade without resetting to factory defaults.
Both radio's were not working. ip a s didn't show ath0 and ath1. The Wireless tab in the webinterface was missing.
Performed a factory default. Unit did a reboot and cannot be reached after the reboot. Both radio's are down and the unit doesn't respond on the 192.168.1.1 address using a cable. No ping, no webpage.
Is a boot log required? What else do the devs need? _________________
1x TP-Link Archer C7 V2.0 r48432 (Primary router at primary location. Former Ziggo repeater)
1x TP-Link Archer C7 V2.0 OpenWrt 21.02.3 (Testing at primary location. Former Ziggo repeater)
1x TP-Link Archer C7 V5.0 r48540 (Secondary router at primary location)
1x TP-Link Archer C7 V5.0 OpenWrt 21.02.3 (Testing at primary location)
1x TP-Link WR1043ND V4.0 OpenWrt 21.02.3 (Testing at primary location)
1x TP-Link WDR4900 V1.3 (green leds) r48646 (Primary router at secondary location)
1x TP-Link WDR4900 V1.3 (blue leds) OpenWrt 21.02.3 (Testing at primary location)
1x TP-Link WDR4900 V1.3 (green leds) OpenWrt 21.02.3 (Testing at primary location)
1x TP-Link WDR4900 V1.3 (green leds) OpenWrt 21.02.3 (Testing at primary location)
1x TP-Link WDR4900 V1.3 (blue leds) r47925 (Testing at secondary location)
1x Linksys WRT160NL r48494 (Guest network with QoS at secondary location)
1x Linksys WRT54G V2.0 r14929 (Switched off at secondary location)
1x Linksys WRT54GL V1.1 r14929
