Problem with 1900ac V2 build r40672 (won't accept flash)

Post new topic   Reply to topic    DD-WRT Forum Forum Index -> Marvell MVEBU based Hardware (WRT1900AC etc.)
Author Message
Surphr33k
DD-WRT Novice


Joined: 19 Aug 2019
Posts: 2

PostPosted: Mon Aug 19, 2019 3:00    Post subject: Problem with 1900ac V2 build r40672 (won't accept flash) Reply with quote
Hi all,

I have a problem with the r40672 build for the WRT 1900ac V2. Struggling to get the router to accept the build I eventually hard bricked it.

I purchased a serial cable and ran the procedure to "run update_both_images" (with the factory firmware). I am assuming this updates both partitions?

Worked like a charm. Came back up on factory image just fine.

After it came up, I tried to flash the factory-to-ddwrt.bin again. This time I had the serial cable attached and logged the session.

The router tried to come-up on the newly flashed partition 3 times before reverting back to the first one.

Below is the kernal panic from the console. It panicked in the same place all three times. Again, this happened _after_ I had already successfully done "run update_both_images" and _then_ tried to flash to the factory-to-ddwrt.bin .

[ 1.472160] Waiting 1 sec before mounting root device...
[ 2.561883] squashfs: SQUASHFS error: unable to read id index table
[ 2.568239] List of all partitions:
[ 2.571755] 1f00 2048 mtdblock0 [ 2.575777] (driver?)
[ 2.578147] 1f01 256 mtdblock1 [ 2.582174] (driver?)
[ 2.584543] 1f02 256 mtdblock2 [ 2.588565] (driver?)
[ 2.590933] 1f03 1024 mtdblock3 [ 2.594961] (driver?)
[ 2.597330] 1f04 40960 mtdblock4 [ 2.601353] (driver?)
[ 2.603726] 1f05 37888 mtdblock5 [ 2.607747] (driver?)
[ 2.610116] 1f06 39936 mtdblock6 [ 2.614142] (driver?)
[ 2.616510] 1f07 36864 mtdblock7 [ 2.620532] (driver?)
[ 2.622905] 1f08 256 mtdblock8 [ 2.626928] (driver?)
[ 2.629296] 1f09 37888 mtdblock9 [ 2.633326] (driver?)
[ 2.635695] 1f0a 6656 mtdblock10 [ 2.639804] (driver?)
[ 2.642178] fe00 35092 ubiblock0_0 [ 2.646375] (driver?)
[ 2.648741] No filesystem could mount root, tried: [ 2.653467] squashfs
[ 2.655746]
[ 2.657242] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(254,0)
[ 2.665714] CPU1: stopping
[ 2.668434] CPU: 1 PID: 0 Comm: swapper/1 Not tainted 4.9.189 #1227
[ 2.674725] Hardware name: Marvell Armada 380/385 (Device Tree)
[ 2.680683] [<c010e7d4>] (unwind_backtrace) from [<c010a770>] (show_stack+0x10/0x14)
[ 2.688462] [<c010a770>] (show_stack) from [<c02b86c4>] (dump_stack+0x84/0x98)
[ 2.695715] [<c02b86c4>] (dump_stack) from [<c010d3f8>] (handle_IPI+0xe4/0x190)
[ 2.703056] [<c010d3f8>] (handle_IPI) from [<c01014a8>] (gic_handle_irq+0x70/0x74)
[ 2.710657] [<c01014a8>] (gic_handle_irq) from [<c010b14c>] (__irq_svc+0x6c/0x90)
[ 2.718168] Exception stack(0xdf473f98 to 0xdf473fe0)
[ 2.723240] 3f80: dfbdd 2a8 00000000
[ 2.731452] 3fa0: 00000b5e c0114220 00000001 c0912839 c090447c df472000 c090442c c0683f58
[ 2.739663] 3fc0: 00000000 00000000 00000000 df473fe8 c0107ce8 c0107cec 60000013 ffffffff
[ 2.747876] [<c010b14c>] (__irq_svc) from [<c0107cec>] (arch_cpu_idle+0x34/0x38)
[ 2.755306] [<c0107cec>] (arch_cpu_idle) from [<c0158358>] (cpu_startup_entry+0xc8/0x128)
[ 2.763518] [<c0158358>] (cpu_startup_entry) from [<00101608>] (0x101608)
[ 2.770334] Rebooting in 5 seconds..

Is it possible that the factory-to-ddwrt.bin is trying to do some magic to ensure that it gets installed on partition 1 instead of partition 2? And, if this is the case, then is it possible this mechanism is not working?
Sponsor
WENED
DD-WRT User


Joined: 30 May 2017
Posts: 329
Location: Rural Manitoba

PostPosted: Mon Aug 19, 2019 4:05    Post subject: Re: Problem with 1900ac V2 build r40672 (won't accept flash) Reply with quote
Surphr33k wrote:
Hi all,

I have a problem with the r40672 build for the WRT 1900ac V2. Struggling to get the router to accept the build I eventually hard bricked it.

I purchased a serial cable and ran the procedure to "run update_both_images" (with the factory firmware). I am assuming this updates both partitions?

Worked like a charm. Came back up on factory image just fine.

After it came up, I tried to flash the factory-to-ddwrt.bin again. This time I had the serial cable attached and logged the session.

The router tried to come-up on the newly flashed partition 3 times before reverting back to the first one.

Below is the kernal panic from the console. It panicked in the same place all three times. Again, this happened _after_ I had already successfully done "run update_both_images" and _then_ tried to flash to the factory-to-ddwrt.bin .

[ 1.472160] Waiting 1 sec before mounting root device...
[ 2.561883] squashfs: SQUASHFS error: unable to read id index table
[ 2.568239] List of all partitions:
[ 2.571755] 1f00 2048 mtdblock0 [ 2.575777] (driver?)
[ 2.578147] 1f01 256 mtdblock1 [ 2.582174] (driver?)
[ 2.584543] 1f02 256 mtdblock2 [ 2.588565] (driver?)
[ 2.590933] 1f03 1024 mtdblock3 [ 2.594961] (driver?)
[ 2.597330] 1f04 40960 mtdblock4 [ 2.601353] (driver?)
[ 2.603726] 1f05 37888 mtdblock5 [ 2.607747] (driver?)
[ 2.610116] 1f06 39936 mtdblock6 [ 2.614142] (driver?)
[ 2.616510] 1f07 36864 mtdblock7 [ 2.620532] (driver?)
[ 2.622905] 1f08 256 mtdblock8 [ 2.626928] (driver?)
[ 2.629296] 1f09 37888 mtdblock9 [ 2.633326] (driver?)
[ 2.635695] 1f0a 6656 mtdblock10 [ 2.639804] (driver?)
[ 2.642178] fe00 35092 ubiblock0_0 [ 2.646375] (driver?)
[ 2.648741] No filesystem could mount root, tried: [ 2.653467] squashfs
[ 2.655746]
[ 2.657242] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(254,0)
[ 2.665714] CPU1: stopping
[ 2.668434] CPU: 1 PID: 0 Comm: swapper/1 Not tainted 4.9.189 #1227
[ 2.674725] Hardware name: Marvell Armada 380/385 (Device Tree)
[ 2.680683] [<c010e7d4>] (unwind_backtrace) from [<c010a770>] (show_stack+0x10/0x14)
[ 2.688462] [<c010a770>] (show_stack) from [<c02b86c4>] (dump_stack+0x84/0x98)
[ 2.695715] [<c02b86c4>] (dump_stack) from [<c010d3f8>] (handle_IPI+0xe4/0x190)
[ 2.703056] [<c010d3f8>] (handle_IPI) from [<c01014a8>] (gic_handle_irq+0x70/0x74)
[ 2.710657] [<c01014a8>] (gic_handle_irq) from [<c010b14c>] (__irq_svc+0x6c/0x90)
[ 2.718168] Exception stack(0xdf473f98 to 0xdf473fe0)
[ 2.723240] 3f80: dfbdd 2a8 00000000
[ 2.731452] 3fa0: 00000b5e c0114220 00000001 c0912839 c090447c df472000 c090442c c0683f58
[ 2.739663] 3fc0: 00000000 00000000 00000000 df473fe8 c0107ce8 c0107cec 60000013 ffffffff
[ 2.747876] [<c010b14c>] (__irq_svc) from [<c0107cec>] (arch_cpu_idle+0x34/0x38)
[ 2.755306] [<c0107cec>] (arch_cpu_idle) from [<c0158358>] (cpu_startup_entry+0xc8/0x128)
[ 2.763518] [<c0158358>] (cpu_startup_entry) from [<00101608>] (0x101608)
[ 2.770334] Rebooting in 5 seconds..

Is it possible that the factory-to-ddwrt.bin is trying to do some magic to ensure that it gets installed on partition 1 instead of partition 2? And, if this is the case, then is it possible this mechanism is not working?


Refer to the stikies at the top of the forum and various posts regarding newer builds.
Newer builds are too large to install on partition 2 for 1900's and 1200's.
You must force install to partition 1 on these newer builds.If you are going from stock it is best to first install a factory to dd-wrt build that is old (pre-2019) first then upgrade to the newer build first by forcing partition 1 install with the command "ubootenv set boot_part 2" then doing the upgrade.
There are other ways that work also and are explained in the stickies.

_________________
WRT3200acm Master WDS 5GHz 80Mhz r41491
WRT3200acm WDS Station r41491
WRT1900Ac V1 WDS AP 5Ghz r41491 (Defective, no 2.4Ghz but 5Ghz works great)
WRT1900AC V1 WDS Station r41491
WRT1900AC V1 SPARE r41418
WRT1200AC V1 Client-Bridge r35898
WRT54G DD-WRT v3.0-r37305 micro Client-Bridged for 1 IP Camera
EX6200 DD-WRT r38535 - Spare
EX7000 Stock Firmware Spare
Devices and Cameras and Sensors
15 WiFi cameras, 4 desktops, 2 laptop, 12 Sonoff Basic/TH16, Artisan 700 Printer, Ongoing testing of other devices.
Surphr33k
DD-WRT Novice


Joined: 19 Aug 2019
Posts: 2

PostPosted: Mon Aug 19, 2019 12:07    Post subject: Reply with quote
Thanks @wened. Will I need to go back and redo the serial "run update_both_images" to repair partition 2 or is there an easier way?
WENED
DD-WRT User


Joined: 30 May 2017
Posts: 329
Location: Rural Manitoba

PostPosted: Mon Aug 19, 2019 14:41    Post subject: Reply with quote
Surphr33k wrote:
Thanks @wened. Will I need to go back and redo the serial "run update_both_images" to repair partition 2 or is there an easier way?


It is my guess that partition 2 is likely in tact with stock firmware, so don't worry about it. You can upgrade via GUI by simply flashing "factory to dd-wrt" with an older build such as r35898 which will install on partition 2 (assuming you are on 1 now, although it doesn't matter).
Once updated to r35898 or so, don't enter any parameters just Administration->Command-> ubootenv set boot_part 2 Run Commands
Administration->Firmware Upgrade Select webflash file desired and execute.
This puts the desired build on partition 1
Unless the size of the new builds is decreased you will never be running on partition 2, it is just a failsafe if for some reason Partition 1 gets bricked. I have never had to serial any 1900, have done so with some other single partition routers

_________________
WRT3200acm Master WDS 5GHz 80Mhz r41491
WRT3200acm WDS Station r41491
WRT1900Ac V1 WDS AP 5Ghz r41491 (Defective, no 2.4Ghz but 5Ghz works great)
WRT1900AC V1 WDS Station r41491
WRT1900AC V1 SPARE r41418
WRT1200AC V1 Client-Bridge r35898
WRT54G DD-WRT v3.0-r37305 micro Client-Bridged for 1 IP Camera
EX6200 DD-WRT r38535 - Spare
EX7000 Stock Firmware Spare
Devices and Cameras and Sensors
15 WiFi cameras, 4 desktops, 2 laptop, 12 Sonoff Basic/TH16, Artisan 700 Printer, Ongoing testing of other devices.
kernel-panic69
DD-WRT Guru


Joined: 08 May 2018
Posts: 2683
Location: Texas, USA

PostPosted: Mon Aug 19, 2019 15:20    Post subject: Reply with quote
I would probably opt to return both partitions to stock and start over, but that's just me. Because it's been trying to flash the smaller partition Wink
Display posts from previous:    Page 1 of 1
Post new topic   Reply to topic    DD-WRT Forum Forum Index -> Marvell MVEBU based Hardware (WRT1900AC etc.) All times are GMT

Navigation

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You cannot download files in this forum