RT-AC86U Watchdog & mtd9 scan

  • ATTENTION! As of November 1, 2020, you are not able to reply to threads 6 months after the thread is opened if there are more than 500 posts in the thread.
    Threads will not be locked, so posts may still be edited by their authors.
    Just start a new thread on the topic to post if you get an error message when trying to reply to a thread.

CaptnDanLKW

Regular Contributor
I noticed this in my logs yesterday. Never seen it before. RT-AC86U with 384.18_beta1

It seems that something went wrong and the watchdog daemon caught it, but I'm bewildered by the actions taken. Perhaps a listing of the function <> partition mapping can shed some light?

Is mtd9 really the nvram partition, that was seemingly mounted as a file system, checked, and then dismounted and released back to the OS?

Hardware fluke, software bug? Thoughts?


Jun 27 16:51:23 RTAC86U check_watchdog: [check_watchdog] restart watchdog for no heartbeat
Jun 27 16:51:23 RTAC86U rc_service: check_watchdog 1312:notify_rc restart_watchdog
Jun 27 16:51:23 RTAC86U custom_script: Running /jffs/scripts/service-event (args: restart watchdog)
Jun 27 16:51:24 RTAC86U kernel: ubi1: attaching mtd9
Jun 27 16:51:24 RTAC86U kernel: ubi1: scanning is finished
Jun 27 16:51:24 RTAC86U kernel: ubi1: attached mtd9 (name "misc1", size 8 MiB)
Jun 27 16:51:24 RTAC86U kernel: ubi1: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
Jun 27 16:51:24 RTAC86U kernel: ubi1: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
Jun 27 16:51:24 RTAC86U kernel: ubi1: VID header offset: 2048 (aligned 2048), data offset: 4096
Jun 27 16:51:24 RTAC86U kernel: ubi1: good PEBs: 64, bad PEBs: 0, corrupted PEBs: 0
Jun 27 16:51:24 RTAC86U kernel: ubi1: user volume: 1, internal volumes: 1, max. volumes count: 128
Jun 27 16:51:24 RTAC86U kernel: ubi1: max/mean erase counter: 9/5, WL threshold: 4096, image sequence number: 113886647
Jun 27 16:51:24 RTAC86U kernel: ubi1: available PEBs: 0, total reserved PEBs: 64, PEBs reserved for bad PEB handling: 4
Jun 27 16:51:24 RTAC86U kernel: ubi1: background thread "ubi_bgt1d" started, PID 10686
Jun 27 16:51:25 RTAC86U kernel: UBIFS (ubi1:0): UBIFS: mounted UBI device 1, volume 0, name "nvram", R/O mode
Jun 27 16:51:25 RTAC86U kernel: UBIFS (ubi1:0): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
Jun 27 16:51:25 RTAC86U kernel: UBIFS (ubi1:0): FS size: 5840896 bytes (5 MiB, 46 LEBs), journal size 1015809 bytes (0 MiB, 6 LEBs)
Jun 27 16:51:25 RTAC86U kernel: UBIFS (ubi1:0): reserved for root: 275879 bytes (269 KiB)
Jun 27 16:51:25 RTAC86U kernel: UBIFS (ubi1:0): media format: w4/r0 (latest is w4/r0), UUID DA02FFC9-330C-43B0-884B-CD262F788227, small LPT model
Jun 27 16:51:25 RTAC86U kernel: UBIFS (ubi1:0): un-mount UBI device 1
Jun 27 16:51:25 RTAC86U kernel: ubi1: detaching mtd9
Jun 27 16:51:25 RTAC86U kernel: ubi1: mtd9 is detached​
 

ColinTaylor

Part of the Furniture
Searching the forum those UBI messages appear to be pretty normal. So unless you're seeing a lot of them I'd ignore it.
 

Similar threads

Sign Up For SNBForums Daily Digest

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