Solved GT-AX6000 Write Protected aka Borked

[Tech9]

It has never been resolved.

I didn't know the issue goes so far back. And I'm sure you have tried everything suggested in the previous thread.

 

[ColinTaylor]

It has never been resolved.

Sorry, I'm confused. Are you just repeating your post from October or is this a new problem with a different router?

 

[Tech9]

Seems like the same issue on the same router and after all fixing attempts failed it was replaced with a new router.

 

[Clark Griswald]

Thank You for trying to un-Griswald my 6000.
I just completed Asus Firmware Restoration four times (twice with Asus fw and twice with RMerlin's Latest), and issue still persist. Unless a resolution miraculously appears, then I am forced to demote this 60000 to AP status, and hoping AP mode will work.

 

[L&LD]

After doing said Firmware Restoration processes, did you also perform a full reset (or multiple resets)?

 

[Tech9]

Thank You for trying to un-Griswald my 6000.

Reading the previous thread with similar issue and knowing you have tried everything described there - currently I have no more ideas except calling your daughter and giving her the router to play with. I remember she was the one who built the Pi-holes for you from scratch. I'm sure she'll return the router fixed to you at some point.

 

[Viktor Jaep]

Is that AX-6000 for sale, @Clark Griswald? If so, @Tech9 and I will probably go halfsies because we're going to need another RTRHTR test unit for his newest aircraft acquisition.

 

[RMerlin]

You need to determine first which volume is read-only. UBIFS will switch to read-only to protect itself when an issue is discovered. Check the volume status:

ubinfo -a

If it's the JFFS2 volume as most likely, then it's recoverable, although not simple. You would basically need to reformat that volume (or possibly recreate it which is what someone did in that other thread). The opration carries a high risk of bricking the router, so that might be considered only as a last ressort option.

There is a ubiformat command included in the firmware, but since I have never used it myself, I'm not ready to blindly tell you to run it and possibly brick everything. Let's start first by confirming that it's a UBI volume that's in a non-OK state, and which one.

 

[Clark Griswald]

Thank You RMerlin for replying!
I will attempt later today, and update.

@Viktor Jaep if I can't get this 6000 to work, then I will sell to you and @Tech9 Shall I cut in half vertically or horizontally?

 

[Clark Griswald]

Other than volumes 7,8,9,12 are not present, the other volumes state OK.
Result:

UBI version: 1
Count of UBI devices: 1
UBI control device major/minor: 10:59
Present UBI devices: ubi0

ubi0
Volumes count: 9
Logical eraseblock size: 126976 bytes, 124.0 KiB
Total amount of logical eraseblocks: 2016 (255983616 bytes, 244.1 MiB)
Amount of available logical eraseblocks: 260 (33013760 bytes, 31.4 MiB)
Maximum count of volumes 128
Count of bad physical eraseblocks: 0
Count of reserved physical eraseblocks: 40
Current maximum erase counter value: 2610
Minimum input/output unit size: 2048 bytes
Character device major/minor: 249:0
Present volumes: 1, 2, 3, 4, 5, 6, 10, 11, 13

Volume ID: 1 (on ubi0)
Type: static
Alignment: 1
Size: 1 LEBs (126976 bytes, 124.0 KiB)
Data bytes: 272 bytes
State: OK
Name: metadata1
Character device major/minor: 249:2
-----------------------------------
Volume ID: 2 (on ubi0)
Type: static
Alignment: 1
Size: 1 LEBs (126976 bytes, 124.0 KiB)
Data bytes: 272 bytes
State: OK
Name: metadata2
Character device major/minor: 249:3
-----------------------------------
Volume ID: 3 (on ubi0)
Type: static
Alignment: 1
Size: 92 LEBs (11681792 bytes, 11.1 MiB)
Data bytes: 10622396 bytes (10.1 MiB)
State: OK
Name: bootfs1
Character device major/minor: 249:4
-----------------------------------
Volume ID: 4 (on ubi0)
Type: dynamic
Alignment: 1
Size: 452 LEBs (57393152 bytes, 54.7 MiB)
State: OK
Name: rootfs1
Character device major/minor: 249:5
-----------------------------------
Volume ID: 5 (on ubi0)
Type: static
Alignment: 1
Size: 93 LEBs (11808768 bytes, 11.2 MiB)
Data bytes: 10688752 bytes (10.1 MiB)
State: OK
Name: bootfs2
Character device major/minor: 249:6
-----------------------------------
Volume ID: 6 (on ubi0)
Type: dynamic
Alignment: 1
Size: 427 LEBs (54218752 bytes, 51.7 MiB)
State: OK
Name: rootfs2
Character device major/minor: 249:7
-----------------------------------
-----------------------------------
-----------------------------------
-----------------------------------
Volume ID: 10 (on ubi0)
Type: dynamic
Alignment: 1
Size: 166 LEBs (21078016 bytes, 20.1 MiB)
State: OK
Name: data
Character device major/minor: 249:11
-----------------------------------
Volume ID: 11 (on ubi0)
Type: dynamic
Alignment: 1
Size: 67 LEBs (8507392 bytes, 8.1 MiB)
State: OK
Name: defaults
Character device major/minor: 249:12
-----------------------------------
-----------------------------------
Volume ID: 13 (on ubi0)
Type: dynamic
Alignment: 1
Size: 413 LEBs (52441088 bytes, 50.0 MiB)
State: OK
Name: jffs2
Character device major/minor: 249:14

 

[RMerlin]

They all seem in an OK state.

Next, try to write to the JFFS volume:

touch /jffs/test.txt

See if it returns an error message.

 

[Clark Griswald]

touch: /jffs/test.txt: Read-only file system

 

[Viktor Jaep]

touch: /jffs/test.txt: Read-only file system

Time for step 2: BURN IT ALL DOWN

 

[Clark Griswald]

Time for step 2: BURN IT ALL DOWN
View attachment 58884

"I'm baby stepping, see Dr. Marvin. I'm doing The Work."
Bob from What about Bob?

 

[RMerlin]

touch: /jffs/test.txt: Read-only file system

Ok. Let me see if I can poke at someone and get a solution.

 

[Tech9]

@Viktor Jaep if I can't get this 6000 to work, then I will sell to you and @Tech9 Shall I cut in half vertically or horizontally?

Don't worry about @Viktor Jaep. He already has one GT-AX6000 and with his scripting obsession it's just a question of time to achieve your results for free.

 

[Clark Griswald]

Thank You RMerlin for your assistance!!!

EDIT: Used The Wife's PayPal account, and sent you something for your effort!!

 

[sfx2000]

Ok. Let me see if I can poke at someone and get a solution.

I think the best solution would be to RMA the device...

I don't think this is a common issue, and likely not a bug in UBI/UBIFS..

 

[John Fitzgerald]

@Clark Griswald

I was talking to Cousin Eddy and he thought you should try the new stock firmware that just dropped as a last ditch effort before you hear back from RMerlin.

Good luck!

Release - ASUS GT-AX6000 Firmware version 3.0.0.6.102_34791

ASUS GT-AX6000 Firmware version 3.0.0.6.102_34791 61.73 MB 2024/05/22 Bug Fixes and Enhancements: - Added new iptv profile NowTV. - Resolved AiMesh-related issues to provide stable backhaul connection. - Resolved GUI issues to ensure that the user interface is even more user-friendly. -...

www.snbforums.com

 

[RMerlin]

@Clark Griswald

Here are two methods they suggest you try. Keep in mind these will erase part of the router configuration (like DHCP reservations).

Try the following first:

  nvram set ubifs_clean_fs=1
  nvram commit
  reboot

Once it comes back, try again with touch /jffs/test.txt. If it still fails, follow these instructions to recreate the JFFS2 volume:

killall syslogd
killall ahs
umount /jffs
ubirmvol /dev/ubi0 --vol_id=13
ubimkvol /dev/ubi0 --vol_id=13 -s 50MiB -N jffs2
reboot

Try again the touch test.

Let me know how it works out.