Beta [Fork] Asuswrt-Merlin 374 LTS release 53D1

john9527

Part of the Furniture
BETA RELEASE: Update-53D1
13-January-2022
Merlin fork 374.43_53D1j9527
============================

BETA 53D1 Highlights
  • Updated iptables support for MIPS routers based on a patch set by @KMO
    This re-enables QoS IPv6 support on the MIPS based routers.
    Testing of QoS on all supported routers (including ARM based routers) is needed.
  • Updated OpenSSL to 1.1.1m
  • Updated OpenVPN to 2.5.5
  • Rolled back dnsmasq/getdns/stubby to previous release based on reported dnsmasq issues

Full ChangeLog: Changelog.txt in the download directory

Downloads:
https://1drv.ms/f/s!Ainhp1nBLzMJrEiyV5NOiKa8zDA3
Folder 'Development-Beta/Update-53D1'

Overview / Supported Routers / Installation:
or
LTS_OVERVIEW.pdf in the download directory

Previous release threads:
https://www.snbforums.com/threads/fork-asuswrt-merlin-374-lts-release-52e7.76314/
https://www.snbforums.com/threads/fork-asuswrt-merlin-374-lts-release-52e3.75496/
https://www.snbforums.com/threads/fork-asuswrt-merlin-374-lts-release-51e3.74513/
https://www.snbforums.com/threads/fork-asuswrt-merlin-374-lts-release-50e8.73798/
https://www.snbforums.com/threads/fork-asuswrt-merlin-374-lts-release-49E4.72269/
https://www.snbforums.com/threads/fork-asuswrt-merlin-374-lts-release-48e7.71000/
https://www.snbforums.com/threads/f...ease-47eb-rt-ac68u-v3-lets-encrypt-cli.70777/
https://www.snbforums.com/threads/fork-asuswrt-merlin-374-lts-release-46e9-dnspooq.69896/
https://www.snbforums.com/threads/fork-asuswrt-merlin-374-lts-release-46e8-superseded.68757/
https://www.snbforums.com/threads/fork-asuswrt-merlin-374-lts-release-45ec.67509

SHA256
(Default Build - All supported routers)
530e567a94affec82eba2dae224d3465fdf43442c03fd7079b67c5d3eab26403 RT-N16_374.43_53D1j9527.trx
f2a1b2f46897fd557932a3e55626466d8d041eeb42d30e0a13ab9cb4fbd7e755 RT-AC66U_374.43_53D1j9527.trx
f0c77e55c9bb9ab6326e3b69cdd453faea67731a01b3abe91e2da3d60c9172eb RT-N66U_374.43_53D1j9527.trx
4235ece310e117c399d3a32b6b7771f0e9c3cd8dac815e59920ea1f01bf803d3 RT-AC68U_374.43_53D1j9527.trx
172f4ac991a4e62d81b0d435c5c566f4f42b23b1622061a38e8117b368ee622e RT-AC56U_374.43_53D1j9527.trx
 

Jerom7

Occasional Visitor
I'll try and flash it to my N66U if I got some spare time... :p
Thanks4all,
 

octopus

Part of the Furniture
I have tried my RT-AC56U and most things work well. (53D1)

The latest software when I update usb is wiped with junk. (tomato_rstats_macadress.gz)
Some software is happening back then. Need to reformat it to make it work again

I'm using pre-mount script as this:
(Advanced script)

Thanks for new build(s)
 
Last edited:

john9527

Part of the Furniture
The latest software when I update usb is wiped with junk.
Really don't have a good idea here....The fork takes care of shutting down apps it knows about on the reboot, before it umounts the USB partitions.
The only thing I can think of is that something is holding on to the drive/partition preventing it from properly being unmounted. Does the syslog show that the USB drive/partition was successfully unmounted?

Are you running any addons?
 

octopus

Part of the Furniture
Really don't have a good idea here....The fork takes care of shutting down apps it knows about on the reboot, before it umounts the USB partitions.
The only thing I can think of is that something is holding on to the drive/partition preventing it from properly being unmounted. Does the syslog show that the USB drive/partition was successfully unmounted?

Are you running any addons?
Hi
No i don't run any addon. Only my gps clock updater.
I found this in log, som highligts < snip >

 

john9527

Part of the Furniture
I found this in log, som highligts < snip >
I was right, the router can't successfully umount the drive. But....

first thing I would take care of is
Jan 15 20:20:31 kernel: EXT2-fs (sda1): error: couldn't mount because of unsupported optional features (240)

this is usually due to formatting the drive on another, more modern kernel, which has default features not present on the older router kernel.
Reformat the drive on the router via cli or amtm and see if it helps things out.
 

octopus

Part of the Furniture
I was right, the router can't successfully umount the drive. But....

first thing I would take care of is
Jan 15 20:20:31 kernel: EXT2-fs (sda1): error: couldn't mount because of unsupported optional features (240)

this is usually due to formatting the drive on another, more modern kernel, which has default features not present on the older router kernel.
Reformat the drive on the router via cli or amtm and see if it helps things out.
I have my USB formatted as EXT4 with journal turned off.
When I unmount and mount again I have to "Create or reset data files" and after that it works until next time update Software.

Isn't this trying mount EXT2-3 but without success with use EXT4?
Code:
Jan 15 20:20:31 kernel: EXT2-fs (sda1): error: couldn't mount because of unsupported optional features (240)
Jan 15 20:20:31 kernel: EXT3-fs (sda1): error: couldn't mount because of unsupported optional features (240)
 

ColinTaylor

Part of the Furniture
I have my USB formatted as EXT4 with journal turned off.
When I unmount and mount again I have to "Create or reset data files" and after that it works until next time update Software.
Not having a journal is a really bad idea, especially with ext4, and probably part of your problem.

I suspect the root cause is likely to be that you're doing something that is preventing the USB device from being unmounted properly. What does your post-mount script do? Do you have a corresponding unmount script?

Isn't this trying mount EXT2-3 but without success with use EXT4?
Code:
Jan 15 20:20:31 kernel: EXT2-fs (sda1): error: couldn't mount because of unsupported optional features (240)
Jan 15 20:20:31 kernel: EXT3-fs (sda1): error: couldn't mount because of unsupported optional features (240)
I think this is the case. So that looks OK to me.
 

octopus

Part of the Furniture
Not having a journal is a really bad idea, especially with ext4, and probably part of your problem.

I suspect the root cause is likely to be that you're doing something that is preventing the USB device from being unmounted properly. What does your post-mount script do? Do you have a corresponding unmount script?


I think this is the case. So that looks OK to me.
OK, I can try to turn journaling on and test.
Im my post-mount I have this:
Code:
/bin/mount --bind /jffs /tmp/mnt/rt-ac56/jffs
 

ColinTaylor

Part of the Furniture
Im my post-mount I have this:
Code:
/bin/mount --bind /jffs /tmp/mnt/rt-ac56/jffs
What is the purpose of this?

You ought to have corresponding code in unmount otherwise you will get the errors seen in your log.
 

octopus

Part of the Furniture
What is the purpose of this?

You ought to have corresponding code in unmount otherwise you will get the errors seen in your log.
ok, I haven't...... purpose is to reach /jffs from /mnt when connected with Samba or FTP.
Hmm, maybe I always have this but discovered it now.

/bin/umount /jffs /tmp/mnt/rt-ac56/jffs
Don't know if I remeber it right?
 
Last edited:

john9527

Part of the Furniture
Thanks for the help @ColinTaylor
Just a remember that both post-mount and unmount custom scripts get passed the name of the mount point in case you have multiple USB partitions.....
 

octopus

Part of the Furniture
You can't unmount /jffs, you just need this:
Code:
umount /tmp/mnt/rt-ac56/jffs
Did I remember right to turn on "journaling" on existing device?

Code:
tune2fs -J device=/dev/sda1 /dev/ext4_fs
 

octopus

Part of the Furniture
Hmm, doesn't look right. Try Google.
I got it from here:

wiki
Code:
Use external journal to optimize performance

Tango-edit-clear.png
This article or section needs language, wiki syntax or style improvements. See Help:Style for reference.
Tango-edit-clear.png
Reason: Complicated to read, needs style fixing. (Discuss in Talk:Ext4)

For those with concerns about both data integrity and performance, the journaling can be significantly sped up with the journal_async_commit mount option. Note that it does not work with the balanced default of data=ordered, so this is only recommended when the filesystem is already cautiously using data=journal.

You can then format a dedicated device to journal to with mke2fs -O journal_dev /dev/journal_device. Use tune2fs -J device=/dev/journal_device /dev/ext4_fs to assign the journal to an existing device, or replace tune2fs with mkfs.ext4 if you are making a new filesystem.
 

ColinTaylor

Part of the Furniture
I got it from here:

wiki
Code:
Use external journal to optimize performance

Tango-edit-clear.png
This article or section needs language, wiki syntax or style improvements. See Help:Style for reference.
Tango-edit-clear.png
Reason: Complicated to read, needs style fixing. (Discuss in Talk:Ext4)

For those with concerns about both data integrity and performance, the journaling can be significantly sped up with the journal_async_commit mount option. Note that it does not work with the balanced default of data=ordered, so this is only recommended when the filesystem is already cautiously using data=journal.

You can then format a dedicated device to journal to with mke2fs -O journal_dev /dev/journal_device. Use tune2fs -J device=/dev/journal_device /dev/ext4_fs to assign the journal to an existing device, or replace tune2fs with mkfs.ext4 if you are making a new filesystem.
That's for an external journal. You just want a normal journal.
 

octopus

Part of the Furniture
That's for an external journal. You just want a normal journal.
seems I have journaling on:
[email protected]:/tmp/home/root# tune2fs -l /dev/sda1
tune2fs 1.45.6 (20-Mar-2020)
Filesystem volume name: rt-ac56
Last mounted on: /tmp/mnt/rt-ac56
Filesystem UUID: bdbcebea-a6f7-1c45-a667-7b27537f7243
Filesystem magic number: 0xEF53
Filesystem revision #: 1 (dynamic)
Filesystem features: ext_attr resize_inode dir_index filetype extent flex_bg sparse_super large_file huge_file uninit_bg dir_nlink extra_isize
Filesystem flags: signed_directory_hash
Default mount options: journal_data_writeback
Filesystem state: not clean
Errors behavior: Continue
Filesystem OS type: Linux
Inode count: 3924480
Block count: 7838464
Reserved block count: 391923
Free blocks: 4850939
Free inodes: 3919004
First block: 0
Block size: 4096
Fragment size: 4096
Reserved GDT blocks: 1022
Blocks per group: 32768
Fragments per group: 32768
Inodes per group: 16352
Inode blocks per group: 511
Flex block group size: 16
Filesystem created: Tue Jun 21 19:18:40 2016
Last mount time: Sat Jan 15 20:20:31 2022
Last write time: Wed Jan 19 08:58:21 2022
Mount count: 2
Maximum mount count: 20
Last checked: Wed Jan 1 01:00:17 2020
Check interval: 15552000 (6 months)
Next check after: Mon Jun 29 02:00:17 2020
Lifetime writes: 30 GB
Reserved blocks uid: 0 (user gollum)
Reserved blocks gid: 0 (group root)
First inode: 11
Inode size: 128
Default directory hash: half_md4
Directory Hash Seed: 7553dc82-d153-3c60-29f0-11225d2622ac
Journal backup: inode blocks
 

ColinTaylor

Part of the Furniture
seems I have journaling on:
I don't think so, that's something else. With journaling enabled you should see it under Filesystem features:
Rich (BB code):
# tune2fs -l /dev/sda1 | grep features
Filesystem features:      has_journal ext_attr resize_inode dir_index filetype needs_recovery extent flex_bg sparse_super large_file huge_file uninit_bg dir_nlink extra_isize

EDIT: Reading a bit more about journal_data_writeback I'd suggest that you remove that option as it defeats the purpose of having a journal in the first place. Or as Linus Torvalds apparently said: "...anybody who thinks that's a solution is just incompetent. We might as well go back to ext2 then".
Code:
tune2fs -o ^journal_data_writeback /dev/sda1
 
Last edited:

octopus

Part of the Furniture
I don't think so, that's something else. With journaling enabled you should see it under Filesystem features:
Rich (BB code):
# tune2fs -l /dev/sda1 | grep features
Filesystem features:      has_journal ext_attr resize_inode dir_index filetype needs_recovery extent flex_bg sparse_super large_file huge_file uninit_bg dir_nlink extra_isize

EDIT: Reading a bit more about journal_data_writeback I'd suggest that you remove that option as it defeats the purpose of having a journal in the first place. Or as Linus Torvalds apparently said: "...anybody who thinks that's a solution is just incompetent. We might as well go back to ext2 then".
Code:
tune2fs -o ^journal_data_writeback /dev/sda1
[email protected]:/tmp/home/root# tune2fs -l /dev/sda1 | grep features
Filesystem features: ext_attr resize_inode dir_index filetype extent flex_bg sparse_super large_file huge_file uninit_bg dir_nlink extra_isize

Ok seems missing.
 

Similar threads

Latest threads

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top