What's new

Release Asuswrt-Merlin 3006.102.7 is now available

AXE-16000. Have reverted back to 3006.102.6. Losing devices, both wired and wireless. Reboot brings them back and then they disappear around two hours later. Might have something to do with IPV6. Don't see anything in the logs that pops out at me.
 
7 days and counting with 3006.102.7 on my BE88U with stock AImesh nodes.... thanks again @RMerlin.
 
7 days and counting with 3006.102.7 on my BE88U with stock AImesh nodes.... thanks again @RMerlin.
Same here, but no nodes
1000050416.png
 
Thank you as always!
If anyone installs this on their (ROG) GT-AX11000 Pro, would appreciate andy follow ups/comments. Both the August and November releases displayed quirks, was awating this to see how it goes. Good weekend to all, S.
the only weird behavior i've noticed since my 102.7 update was with the usb 3.0 health scanner panel. when doing a rescan of my nas attached usb.30 ssd, at ~50% i get logged out! after logging back in, the scan shows completion. this behavior is new with 102.7 as that 860 evo ssd has been solid on several asus devices over the years.
 
the only weird behavior i've noticed since my 102.7 update was with the usb 3.0 health scanner panel. when doing a rescan of my nas attached usb.30 ssd, at ~50% i get logged out! after logging back in, the scan shows completion. this behavior is new with 102.7 as that 860 evo ssd has been solid on several asus devices over the years.
Check the system log. The most likely reason I can think of would be your router runs out of memory while doing the scan, causing service crashes. In the past running a fs check on a large disk has always been a problem due to the amount of RAM required for it.
 
Check the system log. The most likely reason I can think of would be your router runs out of memory while doing the scan, causing service crashes. In the past running a fs check on a large disk has always been a problem due to the amount of RAM required for it.
not seeing anything specific re ram/memory in the syslog.
>>> >> >
Mar 2 11:14:39 disk_monitor: re-mount partition
Mar 2 11:14:39 kernel: tntfs info (device sda1, pid 18165): ntfs_fill_super(): fail_safe is enabled.
Mar 2 11:14:39 kernel: tntfs info (device sda1, pid 18165): load_system_files(): NTFS volume name 'gpdNAS-1t', version 3.1 (cluster_size 4096, PAGE_SIZE 4096).
Mar 2 11:14:39 disk_monitor: USB ntfs fs at /dev/sda1 mounted on /tmp/mnt/ssdNAS-1t
Mar 2 11:14:39 usb: USB ntfs fs at /dev/sda1 mounted on /tmp/mnt/gpdNAS-1t.
Mar 2 11:14:39 rc_service: disk_monitor 4555:notify_rc stop_httpd
Mar 2 11:14:39 rc_service: disk_monitor 4555:notify_rc start_httpd
Mar 2 11:14:39 rc_service: waitting "stop_httpd"(last_rc:stop_httpd) via disk_monitor ...
Mar 2 11:14:40 rc_service: disk_monitor 4555:notify_rc start_samba
Mar 2 11:14:40 rc_service: waitting "start_httpd"(last_rc:start_httpd) via disk_monitor ...
< << <<<
on the system status panel, ram typically shows ~47% but i'm not sure how that may change during the scan. shortly after the remount msg is when i get logged out. this is just a snippet but no other messages re ram/memory show on a fresh log.
 
Mar 2 11:14:39 rc_service: disk_monitor 4555:notify_rc stop_httpd
Mar 2 11:14:39 rc_service: disk_monitor 4555:notify_rc start_httpd
Mar 2 11:14:39 rc_service: waitting "stop_httpd"(last_rc:stop_httpd) via disk_monitor ...
Mar 2 11:14:40 rc_service: disk_monitor 4555:notify_rc start_samba
Mar 2 11:14:40 rc_service: waitting "start_httpd"(last_rc:start_httpd) via disk_monitor ...
I suppose it’s this part of disk_monitor that stops the httpd daemon. Perhaps this isn’t meant to be there:
 

Similar threads

Latest threads

Support SNBForums w/ Amazon

If you'd like to support SNBForums, just use this link and buy anything on Amazon. Thanks!

Sign Up For SNBForums Daily Digest

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