Merlins 380.68_4 HELP

[Laserpaddy]

For the last 2 or 3 days I have been eating up drives like they are popcorn- the below is happening all the bloddy time no matter what package:

also I just noticed , since I was digging out my shovel to help me trouble shoot the issue- that this was in my log

ul 31 20:00:23 kernel: ohci_hcd 0000:00:0b.0: irq 111, io mem 0x18022000
Jul 31 20:00:23 kernel: hub 3-0:1.0: USB hub found
Jul 31 20:00:23 kernel: hub 3-0:1.0: 2 ports detected
Jul 31 20:00:23 kernel: usbcore: registered new interface driver usblp
Jul 31 20:00:23 kernel: usbcore: registered new interface driver asix
Jul 31 20:00:23 kernel: usbcore: registered new interface driver cdc_ether
Jul 31 20:00:23 kernel: usbcore: registered new interface driver rndis_host
Jul 31 20:00:23 kernel: cdc_ncm: 14-Mar-2012
Jul 31 20:00:23 kernel: usbcore: registered new interface driver cdc_ncm
Jul 31 20:00:23 kernel: usbcore: registered new interface driver cdc_wdm
Jul 31 20:00:23 kernel: usbcore: registered new interface dri

that's when the shovel started to bang loudly against my head- rather than the computer-ya see I have been having all kinds of strange issues-

I guess the jokes on my sorry but- after many hundreds of dollars, hours etc- I have had a USB driver that is an internet usb driver and has somehow turned everything into an erection for the internet--

What am I missing here? there isn't a normal driver? I mean I respect everyones level of experience as its light years ahead of mine- but I will take you on in lasers etc..

SOeverytime I got on the internet and I would have deletions and file corruptions on my drives etc.. no virus or malware I have a mess and don't know where to start

 

[ColinTaylor]

I have no idea what you are talking about. It would help if you cut out the hyperbole and simply stated your problem.

BTW The usbcore messages you posted are normal and nothing to be concerned about.

 

[thelonelycoder]

Bloody hell. Shovels full of popcorn were dug up, holes pierced through them by an erect laser-spewing internet.

 

[Vexira]

issue with a usb modem

 

[jim769]

issue with a usb modem

Let him finish his popcorn and erection on the internet....

 

[ColinTaylor]

issue with a usb modem

There is no USB modem.

 

[Vexira]

There is no USB modem.

I was guessing it was that or he's talking about a usb wifi adapter.

 

[Vexira]

Let him finish his popcorn and erection on the internet....

Firstly eww that's disgusting, second I was trying to translate his articulate mess.

 

[Laserpaddy]

had a family emergency and had to stop...so I am back-sort of I can send someone a bunch of text only based files.

No modem NO USB MODEM-- essentially I have some very strange IMO log files etc--

actually sometimes a mans gotta have a sense of humor and I had one for a moment--didn't mean to waste anyone's time-i apologize Collin
and just so ya know mr lonely coder- I thought the internet had an extremely erect laser focused box of holes for me...

Now that I know for sure I'm not a crazy paranoid person- I can explain.

For a least a year I have had weird drive failures- always having to enter my password 2 times- usb drives die keyboards etc and the list goes on- these types of things happening over and over again when the kind that the only thing you did was use CAD a few times- and on the internet less than 10 hours in a few weeks- with your machine off and not being idlely open to the web.- Can really get on your nerve- ya I had 1 left.

SO being a retired engineer and disabled vet I am home bound most of the time so I started investigating- and it wasn't till the last severa weeks that I started to use the entware and put it on my rt-88u since I was redoing my untangle and pfsense boxes- and I actually did have drives die as I watched etc.
actually sometimes a mans gotta have a sense of humor and I had one for a moment--didn't mean to waste anyones time-i apologize Collin
and just so ya know mr lonely coder- I thought the internet had an extremely erect laser focused box of holes for me...

Now that I know for sure I'm not a crazy paranoid person- I can explain.

For a least a year I have had weird drive failures- always having to enter my password 2 times- usb drives die keyboards etc and the list goes on- these types of things happening over and over again when the kind that the only thing you did was use CAD a few times- and on the internet less than 10 hours in a few weeks- with your machine off and not being idlely open to the web.- Can really get on your nerve- ya I had 1 left.

SO being a retired engineer and disabled vet I am home bound most of the time so I started investigating- and it wasn't till the last severa weeks that I started to use the entware and put it on my rt-88u since I was redoing my untangle and pfsense boxes- and I actually did have drives die as I watched etc.​

ul 31 19:00:15 kernel: Found a Zentel/Esmt NAND flash:
_______________________________
J
ul 31 19:00:15 kernel: <3>SQUASHFS error: Unable to read fragment cacheï¾Uªry [9d3f0]
Jul 31 19:00:15 kernel: <3>SQUASHFS error: Unable to read page, block 9d3f0, size 9584
Jul 31 19:00:15 kernel: <3>SQUASHFS error: Unable to read fragment cache entry [9d3f0]
Jul 31 19:00:15 kernel: <3>SQUASHFS error: Unable to read page, block 9d3f0, size 9584
Jul 31 19:00:15 kernel: <4>dhd_detach(): thread:dhd_watchdog_thread:7d terminated OK
Jul 31 19:00:15 kernel: <4>dhd_detach(): thread:dhd_watchdog_thread:79 terminated OK
Jul 31 19:00:15 kernel: ____________________________________________________________________________
Jul 31 19:00:15 sd-idle-2.6[451]: IDLETIME set too small which is bad for disks: 60; setting to minimum 300
Jul 31 19:00:16 WAN_Connection: ISP's DHCP did not function properly.
Jul 31 19:00:16 WAN_Connection: Ethernet link down.
Jul 31 19:00:16 dropbear[526]: Failed listening on '23': Error listening: Address already in use

Jul 31 19:00:25 kernel: usb usb1: No SuperSpeed endpoint companion for config 1 interface 0 altsetting 0 ep 129: using minimum values


- this is but a small sample and what occurs when I notices it: JUST STARTED POPING UP

N=br0 OUT=eth0 SRC=192.168.1.228 DST=199.85.126.10 LEN=118 TOS=0x00 PREC=0x00 TTL=127 ID=21982 PROTO=UDP SPT=65354 DPT=53 LEN=98
Oct 12 15:59:48 kernel: ACCEPT IN=br0 OUT=eth0 SRC=192.168.1.228 DST=199.85.126.10 LEN=72 TOS=0x00 PREC=0x00 TTL=127 ID=22007 PROTO=UDP SPT=51532 DPT=53 LEN=52
Oct 12 15:59:48 kernel: ACCEPT IN=br0 OUT=eth0 SRC=192.168.1.228 DST=199.85.126.10 LEN=72 TOS=0x00 PREC=0x00 TTL=127 ID=22008 PROTO=UDP SPT=51532 DPT=53 LEN=52
Oct 12 15:59:51 kernel: ACCEPT IN=br0 OUT=eth0 SRC=192.168.1.219 DST=199.85.126.10 LEN=75 TOS=0x00 PREC=0x00 TTL=63 ID=25716 DF PROTO=UDP SPT=16084 DPT=53 LEN=55
Oct 12 15:59:51 kernel: ACCEPT IN=br0 OUT=eth0 SRC=192.168.1.219 DST=172.217.12.99 LEN=60 TOS=0x00 PREC=0x00 TTL=63 ID=64154 DF PROTO=TCP SPT=37851 DPT=443 SEQ=344721332 ACK=0 WINDOW=65535 RES=0x00 SYN URGP=0 OPT (020405B40402080A02D2FD2E0000000001030306)
Oct 12 16:00:06 kernel: EXT2-fs (sda1): error: ext2_lookup: deleted inode referenced: 12
Oct 12 16:00:06 kernel: EXT2-fs (sda1): error: ext2_lookup: deleted inode referenced: 12
Oct 12 16:00:06 kernel: EXT2-fs (sda1): error: ext2_lookup: deleted inode referenced: 12
Oct 12 16:00:06 kernel: EXT2-fs (sda1): error: ext2_lookup: deleted inode referenced: 12
Oct 12 16:00:06 kernel: EXT2-fs (sda1): error: ext2_lookup: deleted inode referenced: 12
Oct 12 16:00:06 kernel: EXT2-fs (sda1): error: ext2_lookup: deleted inode referenced: 12
Oct 12 16:00:06 kernel: EXT2-fs (sda1): error: ext2_lookup: deleted inode referenced: 12
Oct 12 16:00:06 kernel: EXT2-fs (sda1): error: ext2_lookup: deleted inode referenced: 12
Oct 12 16:00:06 kernel: EXT2-fs (sda1): error: ext2_lookup: deleted inode referenced: 12
Oct 12 16:00:06 kernel: EXT2-fs (sda1): error: ext2_lookup: deleted inode referenced: 12
Oct 12 16:00:06 kernel: EXT2-fs (sda1): error: ext2_lookup: deleted inode referenced: 12
Oct 12 16:00:06 kernel: EXT2-fs (sda1): error: ext2_lookup: deleted inode referenced: 12
Oct 12 16:00:06 kernel: EXT2-fs (sda1): error: ext2_lookup: deleted inode referenced: 12
Oct 12 16:00:06 kernel: EXT2-fs (sda1): error: ext2_lookup: deleted inode referenced: 12
Oct 12 16:00:06 kernel: EXT2-fs (sda1): error: ext2_lookup: deleted inode referenced: 12
Oct 12 16:00:06 kernel: EXT2-fs (sda1): error: ext2_lookup: deleted inode referenced: 12
Oct 12 16:00:27 kernel: DROP IN=eth0 OUT= MAC=1c:b7:2c:74:82:40:d4:2c:44:7c:30:19:08:00 SRC=220.184.46.6 DST=50.82.238.138
SEQ=844295818 ACK=0 WINDOW=37008 RES=0x00 SYN URGP=0 OPT (020405B4)
Oct 12 16:00:30 kernel: DROP IN=eth0 OUT= MAC=1c:b7:2c:74:82:40:d4:2c:44:7c:30:19:08:00 SRC=5.188.86.20 DST=50.82.238.138 LEN=44 TOS=0x00 PREC=0x00 TTL=243 ID=54217 PROTO=TCP SPT=50650 DPT=3478 SEQ=255144149 ACK=0 WINDOW=1024 RES=0x00 SYN URGP=0 OPT (020405B4)
Oct 12 16:00:37 kernel: EXT2-fs (sda1): error: ext2_lookup: deleted inode referenced: 12
Oct 12 16:00:37 kernel: EXT2-fs (sda1): error: ext2_lookup: deleted inode referenced: 12
Oct 12 16:00:37 kernel: EXT2-fs (sda1): error: ext2_lookup: deleted inode referenced: 12
Oct 12 16:00:37 kernel: EXT2-fs (sda1): error: ext2_lookup: deleted inode referenced: 12
Oct 12 16:00:37 kernel: EXT2-fs (sda1): error: ext2_lookup: deleted inode referenced: 12
Oct 12 16:00:37 kernel: EXT2-fs (sda1): error: ext2_lookup: deleted inode referenced: 12
Oct 12 16:00:37 kernel: EXT2-fs (sda1): error: ext2_lookup: deleted inode referenced: 12
Oct 12 16:00:37 kernel: EXT2-fs (sda1): error: ext2_lookup: deleted inode referenced: 12
Oct 12 16:00:37 kernel: EXT2-fs (sda1): error: ext2_lookup: deleted inode referenced: 12
Oct 12 16:00:37 kernel: EXT2-fs (sda1): error: ext2_lookup: deleted inode referenced: 12
Oct 12 16:00:37 kernel: EXT2-fs (sda1): error: ext2_lookup: deleted inode referenced: 12
Oct 12 16:00:37 kernel: EXT2-fs (sda1): error: ext2_lookup: deleted inode referenced: 12
Oct 12 16:00:37 kernel: EXT2-fs (sda1): error: ext2_lookup: deleted inode referenced: 12
Oct 12 16:00:37 kernel: EXT2-fs (sda1): error: ext2_lookup: deleted inode referenced: 12
Oct 12 16:00:37 kernel: EXT2-fs (sda1): error: ext2_lookup: deleted inode referenced: 12
Oct 12 16:00:37 kernel: EXT2-fs (sda1): error: ext2_lookup: deleted inode referenced: 12

 

[Vexira]

and here I was questioning my mental sanity

 

[Laserpaddy]

and here I was questioning my mental sanity

Ya I know- Sometimes I should just keep my mouth shut.

 

[thelonelycoder]

Jul 31 19:00:15 kernel: <3>SQUASHFS error: Unable to read fragment cache

I am just guessing here but maybe your router has corrupted firmware file(s).
What version of Asuswrt-Merlin are you running and when did you last update?
A reinstall might solve this and possibly more errors.

Since your device is attached via USB3, have you tried enabling Wireless/Professional (2.4GHZ) "Reducing USB 3.0 interference"?
What device is this anyway? USB stick or SSD/HDD?
If not as stick, could it be that it powers down and causes write errors when AB-Solution writes to the dnsmasq.log file, assuming logging is enabled?

Have you tried to running the Health Scanner on the device?

 

[Laserpaddy]

newest software

updated 3 days ago with a full NVRAM back up- reset to factory and a fresh load of firmware- and the first thing I noticed was the date and time issue during loading. I also had a usb die and I think that where I needed to do a full reset.

SO since I am king of the NOOBs- I would beg for some guidance on have to wipe this sucker clean and get back to having Skynet, AB to start with- cause apparently I cannot get it done correctly.

I had it format the jff and rebooted with out jff custom scripts on-
scan file the reboot file:
WRG was not cleanly unmounted, check forced.
1843 inodes used (0.10%, out of 1912832)
16 non-contiguous files (0.9%)
6 non-contiguous directories (0.3%)
# of inodes with ind/dind/tind blocks: 272/31/1
1352081 blocks used (8.84%, out of 15296512)
0 bad blocks
0 large files
1692 regular files
93 directories
0 character device files
0 block device files
0 fifos
0 links
49 symbolic links (49 fast symbolic links)
0 sockets
------------
1834 files




Jul 31 19:00:16 kernel: CPU: ARMv7 Processor [413fc090] revision 0 (ARMv7), cr=10c53c7f
Jul 31 19:00:16 kernel: CPU: VIPT nonaliasing data cache, VIPT nonaliasing instruction cache
Jul 31 19:00:16 kernel: Machine: Northstar Prototype
Jul 31 19:00:16 kernel: Ignoring unrecognised tag 0x00000000
Jul 31 19:00:16 kernel: Memory policy: ECC disabled, Data cache writealloc
Jul 31 19:00:16 kernel: Built 1 zonelists in Zone order, mobility grouping on. Total pages: 130048
Jul 31 19:00:16 kernel: External imprecise Data abort at addr=0x0, fsr=0x1c06, pc=0x8000f9d8 lr=0x8000f9cc ignored.
Jul 31 19:00:16 kernel: Mount-cache hash table entries: 512
Jul 31 19:00:16 kernel: CPU1: Booted secondary processor
Jul 31 19:00:16 kernel: Found a Zentel/Esmt NAND flash:
Jul 31 19:00:16 kernel: Total size: 128MB
Jul 31 19:00:16 kernel: Block size: 128KB
Jul 31 19:00:16 kernel: Page Size: 2048B
Jul 31 19:00:16 kernel: OOB Size: 64B
Jul 31 19:00:16 kernel: Sector size: 512B
Jul 31 19:00:16 kernel: Spare size: 16B
Jul 31 19:00:16 kernel: ECC level: 8 (8-bit)
Jul 31 19:00:16 kernel: Device ID: 0xc8 0xd1 0x80 0x95 0x42 0x7f
Jul 31 19:00:16 kernel: bio: create slab <bio-0> at 0
Jul 31 19:00:16 kernel: PCI: no core
Jul 31 19:00:16 kernel: PCI: no core
Jul 31 19:00:16 kernel: PCI: Fixing up bus 0
Jul 31 19:00:16 kernel: PCI: Fixing up bus 0
Jul 31 19:00:16 kernel: PCI: Fixing up bus 1
Jul 31 19:00:16 kernel: PCI: Fixing up bus 0
Jul 31 19:00:16 kernel: PCI: Fixing up bus 1
Jul 31 19:00:16 kernel: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
Jul 31 19:00:16 kernel: pflash: found no supported devices
Jul 31 19:00:16 kernel: bcmsflash: found no supported devices
Jul 31 19:00:16 kernel: Boot partition size = 524288(0x80000)
Jul 31 19:00:16 kernel: lookup_nflash_rootfs_offset: offset = 0x200000
Jul 31 19:00:16 kernel: === PPTP init ===
Jul 31 19:00:16 kernel: Spare area=64 eccbytes 56, ecc bytes located at:
Jul 31 19:00:16 kernel: 2 3 4 5 6 7 8 9 10 11 12 13 14 15 18 19 20 21 22 23 24 25 26 27 28 29 30 31 34 35 36 37 38 39 40 41 42 43 44 45 46 47 50 51 52 53 54 55 56 57 58 59 60 61 62 63
Jul 31 19:00:16 kernel: Available 7 bytes at (off,len):
Jul 31 19:00:16 kernel: (1,1) (16,2) (32,2) (48,2) (0,0) (0,0) (0,0) (0,0)
Jul 31 19:00:16 kernel: Bad eraseblock 119 at 0x000000ee0000
Jul 31 19:00:16 kernel: Bad eraseblock 220 at 0x000001b80000
Jul 31 19:00:16 kernel: Bad eraseblock 451 at 0x000003860000
Jul 31 19:00:16 kernel: Options: NO_AUTOINCR,NO_READRDY,
Jul 31 19:00:16 kernel: VFS: Mounted root (squashfs filesystem) readonly on device 31:3.
Jul 31 19:00:16 kernel: rtl8365mb: module license 'Proprietary' taints kernel.
Jul 31 19:00:16 kernel: Disabling lock debugging due to kernel taint
Jul 31 19:00:16 kernel: rtl8365mbrtl8365mb initialized(0)(retry:1)
Jul 31 19:00:16 kernel: rtk port_phyEnableAll ok
Jul 31 19:00:16 kernel: register rtl8365mb done (link down at first)
Jul 31 19:00:16 kernel: et_module_init: passivemode set to 0x0
Jul 31 19:00:16 kernel: et_module_init: txworkq set to 0x0
Jul 31 19:00:16 kernel: et_module_init: et_txq_thresh set to 0xce4
Jul 31 19:00:16 kernel: et_module_init: et_rxlazy_timeout set to 0x3e8
Jul 31 19:00:16 kernel: et_module_init: et_rxlazy_framecnt set to 0x20
Jul 31 19:00:16 kernel: et_module_init: et_rxlazy_dyn_thresh set to 0
Jul 31 19:00:16 kernel: fwd0: Broadcom BCM47XX 10/100/1000 Mbps Ethernet Controller 7.14.131.56 (r641653)
Jul 31 19:00:16 kernel: fwd1: Broadcom BCM47XX 10/100/1000 Mbps Ethernet Controller 7.14.131.56 (r641653)
Jul 31 19:00:16 kernel: eth0: Broadcom BCM47XX 10/100/1000 Mbps Ethernet Controller 7.14.131.56 (r641653)
Jul 31 19:00:16 kernel: PCI_PROBE: bus 1, slot 0,vendor 14E4, device 4365(good PCI location)
Jul 31 19:00:16 kernel: PCI: Enabling device 0001:01:00.0 (0140 -> 0142)
Jul 31 19:00:16 kernel: dhd_attach(): thread:dhd_watchdog_thread:190 started
Jul 31 19:00:16 kernel: Dongle Host Driver, version 1.363.45.58013 (r651509)
Jul 31 19:00:16 kernel: Compiled in drivers/net/wireless/bcmdhd on Jun 21 2017 at 10:36:36
Jul 31 19:00:16 kernel: Register interface [eth1] MAC: 1c:b7:2c:74:82:40
Jul 31 19:00:16 kernel: PCI_PROBE: bus 1, slot 0,vendor 14E4, device 4365(good PCI location)
Jul 31 19:00:16 kernel: PCI: Enabling device 0002:01:00.0 (0140 -> 0142)
Jul 31 19:00:16 kernel: dhd_attach(): thread:dhd_watchdog_thread:196 started
Jul 31 19:00:16 kernel: Dongle Host Driver, version 1.363.45.58013 (r651509)
Jul 31 19:00:16 kernel: Compiled in drivers/net/wireless/bcmdhd on Jun 21 2017 at 10:36:36
Jul 31 19:00:16 kernel: Register interface [eth2] MAC: 1c:b7:2c:74:82:44
Jul 31 19:00:16 sd-idle-2.6[451]: IDLETIME set too small which is bad for disks: 3; setting to minimum 300
Jul 31 19:00:18 kernel: rtk port_phyEnableAll (on) ok
Jul 31 19:00:21 dnsmasq[540]: failed to send packet: Network is unreachable
Jul 31 19:00:21 dnsmasq[540]: failed to send packet: Network is unreachable
Jul 31 19:00:21 dnsmasq[540]: failed to send packet: Network is unreachable
Jul 31 19:00:24 syslog: module ledtrig-usbdev not found in modules.dep
Jul 31 19:00:24 syslog: module leds-usb not found in modules.dep
Jul 31 19:00:25 kernel: csw_retry 100
Jul 31 19:00:27 kernel: xhci_hcd 0000:00:0c.0: Failed to enable MSI-X
Jul 31 19:00:27 kernel: xhci_hcd 0000:00:0c.0: failed to allocate MSI entry
Jul 31 19:00:27 kernel: usb usb1: No SuperSpeed endpoint companion for config 1 interface 0 altsetting 0 ep 129: using minimum values
Jul 31 19:00:29 kernel: sd 0:0:0:0: [sda] Assuming drive cache: write through
Jul 31 19:00:29 kernel: sd 0:0:0:0: [sda] Assuming drive cache: write through
Jul 31 19:00:29 kernel: sd 0:0:0:0: [sda] Assuming drive cache: write through
Jul 31 19:00:34 kernel: EXT2-fs (sda1): warning: mounting unchecked fs, running e2fsck is recommended
Jul 31 19:00:41 kernel: gro disabled
Oct 13 15:49:33 kernel: * Make sure sizeof(struct sw_struct)=160 is consistent
Oct 13 15:49:34 kernel: gro enabled with interval 2
Oct 13 15:49:34 kernel: sizeof forward param = 160
Oct 13 15:49:52 crond[548]: time disparity of 1159069 minutes detected
Oct 13 15:56:40 kernel: gro enabled with interval 2
Oct 13 15:56:42 smbd[2656]: [2017/10/13 15:56:42.058163, 0] lib/pidfile.c:146(pidfile_create)
Oct 13 15:56:42 smbd[2656]: ERROR: smbd is already running. File /var/run/samba/smbd.pid exists and process id 1019 is running.

 

[R1-Limited]

Soooo
If this has been going on for 2 years
If this has been going on for 2 years
Why are you concerned with the recent build
Why are you concerned with the recent build
Seems to me you need to scrub yoru PC
Seems to me you need to scrub yoru PC

 

[Laserpaddy]

Soooo
If this has been going on for 2 years
If this has been going on for 2 years
Why are you concerned with the recent build
Why are you concerned with the recent build
Seems to me you need to scrub yoru PC
Seems to me you need to scrub yoru PC

The router hasn't been in service consistently over the last 2 years- had a untangle and pfsense in service- whist this was in AP wireless 5ghz only mode. This is in service while I hardware upgrade.

I should've presented this better and owe the community an apology- I am sorry- - all systems have been "scrubbed" - is there a specific reason you mention this? Since day one I had a time issue-

Suggestions? please...

 

[Vexira]

No it's ok

Ya I know- Sometimes I should just keep my mouth shut.

You just need to be more direct with your request, that's all.

 

[Laserpaddy]

No it's ok

You just need to be more direct with your request, that's all.

Thank you- and it wont happen again

I will have specific info soon

Sent from my SM-G955U using Tapatalk

 

[Laserpaddy]

Burned the midnight oil- and it was very corrupted- everything seems to be working great-

I will be sending Merlin some donations soon- and mr AB Solution

 

[ColinTaylor]

Since day one I had a time issue-

If you are referring to the time discrepancy in the logs when the router boots up then that's normal. The router doesn't have a battery-backed clock, so when it is powered on the date and time are set to a default value. Once the router has established a connection to the internet it corrects the time from NTP servers. Also, as far as I'm aware, if it's configured as an access point it will never correct its date and time (because it doesn't know how to get to the internet).

 

[Laserpaddy]

No for some reason central time zone is 1 hour earlier than it should be I have to mess with Microsoft by turning it off- even a centos install, beginning to wonder if the modem is lying as well...
That's my next battle, time and dns and radius servers, in a vm baremetal, nas perhaps.....

Sent from my SM-G955U using Tapatalk