1 Temat przez Dyziek

  • Dyziek
  • Użytkownik
  • Nieaktywny
  • Skąd: Warszawa
  • Zarejestrowany: 2019-05-05
  • Posty: 269

Temat: LB-LINK AC1200 - dziwne (?) zapisy w logach po resecie

cześć,
Mam LB-LINK AC1200 (8/64, Mediatek), działał przez ok rok jako AP bez problemu. Ostatnio zostal wycofany z uzycia, zresetowany i postawiony od zera Twój (Cezary) najnowszy Openwrt (z Luci, dzis pobierany). Wgrane bez problemu.
Po ponownym uruchomieniu reset z poziomu aplikacji na wszelki wypadek (zawsze tak robie).
Popatrzylem w logi, nie wiem, czy bylo to wczesniej. Ponizej fragmenty, ktore mnie zaniepokoiły.
Jak mam je interpretowac? To nie jest moj pierwszy router z tym systemem (zaczynalem w czasach LEDE) i nie pierwszy Mediatek, ale takich wpisow nie widzialem.

Wed Nov 15 11:00:49 2023 kern.warn kernel: [    1.201853] spi spi0.0: force spi mode3
Wed Nov 15 11:00:49 2023 kern.info kernel: [    1.211241] spi-nor spi0.0: s25fl064k (8192 Kbytes)
Wed Nov 15 11:00:49 2023 kern.notice kernel: [    1.221186] 4 fixed-partitions partitions found on MTD device spi0.0
Wed Nov 15 11:00:49 2023 kern.err kernel: [    1.233948] OF: Bad cell count for /palmbus@10000000/spi@b00/flash@0/partitions
Wed Nov 15 11:00:49 2023 kern.err kernel: [    1.248579] OF: Bad cell count for /palmbus@10000000/spi@b00/flash@0/partitions
Wed Nov 15 11:00:49 2023 kern.err kernel: [    1.263631] OF: Bad cell count for /palmbus@10000000/spi@b00/flash@0/partitions
Wed Nov 15 11:00:49 2023 kern.err kernel: [    1.278292] OF: Bad cell count for /palmbus@10000000/spi@b00/flash@0/partitions
Wed Nov 15 11:00:49 2023 kern.notice kernel: [    1.293108] Creating 4 MTD partitions on "spi0.0":
Wed Nov 15 11:00:49 2023 kern.notice kernel: [    1.302707] 0x000000000000-0x000000030000 : "u-boot"
Wed Nov 15 11:00:49 2023 kern.notice kernel: [    1.316442] 0x000000030000-0x000000040000 : "config"
Wed Nov 15 11:00:49 2023 kern.notice kernel: [    1.327851] 0x000000040000-0x000000050000 : "factory"
Wed Nov 15 11:00:49 2023 kern.notice kernel: [    1.341493] 0x000000050000-0x000000800000 : "firmware"
Wed Nov 15 11:00:49 2023 kern.notice kernel: [    1.353379] 2 uimage-fw partitions found on MTD device firmware
Wed Nov 15 11:00:49 2023 kern.notice kernel: [    1.365294] Creating 2 MTD partitions on "firmware":
Wed Nov 15 11:00:49 2023 kern.notice kernel: [    1.375209] 0x000000000000-0x0000002304fd : "kernel"
Wed Nov 15 11:00:49 2023 kern.warn kernel: [    1.385110] mtd: partition "kernel" doesn't end on an erase/write block -- force read-only
Wed Nov 15 11:00:49 2023 kern.notice kernel: [    1.405042] 0x0000002304fd-0x0000007b0000 : "rootfs"
Wed Nov 15 11:00:49 2023 kern.warn kernel: [    1.415058] mtd: partition "rootfs" doesn't start on an erase/write block boundary -- force read-only
Wed Nov 15 11:00:49 2023 kern.info kernel: [    1.435813] mtd: setting mtd5 (rootfs) as root device
Wed Nov 15 11:00:49 2023 kern.notice kernel: [    1.446094] 1 squashfs-split partitions found on MTD device rootfs
Wed Nov 15 11:00:49 2023 kern.notice kernel: [    1.458465] 0x000000760000-0x0000007b0000 : "rootfs_data"





Wed Nov 15 11:00:49 2023 user.info kernel: [    5.715727] init: - preinit -
Wed Nov 15 11:00:49 2023 kern.notice kernel: [    7.264419] random: jshn: uninitialized urandom read (4 bytes read)
Wed Nov 15 11:00:49 2023 kern.notice kernel: [    7.467467] random: jshn: uninitialized urandom read (4 bytes read)
Wed Nov 15 11:00:49 2023 kern.notice kernel: [    7.727713] random: jshn: uninitialized urandom read (4 bytes read)
Wed Nov 15 11:00:49 2023 kern.info kernel: [    8.646613] mtk_soc_eth 10100000.ethernet eth0: port 5 link up (1000Mbps/Full duplex)
Wed Nov 15 11:00:49 2023 kern.info kernel: [    8.663069] 8021q: adding VLAN 0 to HW filter on device eth0
Wed Nov 15 11:00:49 2023 kern.info kernel: [    8.674808] IPv6: ADDRCONF(NETDEV_CHANGE): eth0.1: link becomes ready
Wed Nov 15 11:00:49 2023 kern.notice kernel: [    8.796990] random: procd: uninitialized urandom read (4 bytes read)
Wed Nov 15 11:00:49 2023 kern.info kernel: [    9.168183] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Wed Nov 15 11:00:49 2023 user.info kernel: [    9.761921] mount_root: loading kmods from internal overlay
Wed Nov 15 11:00:49 2023 user.info kernel: [    9.832027] kmodloader: loading kernel modules from //etc/modules-boot.d/*
Wed Nov 15 11:00:49 2023 user.info kernel: [    9.854293] kmodloader: done loading kernel modules from //etc/modules-boot.d/*
Wed Nov 15 11:00:49 2023 kern.warn kernel: [   10.697223] jffs2: warning: (376) jffs2_sum_scan_sumnode: Summary node crc error, skipping summary information.
Wed Nov 15 11:00:49 2023 kern.notice kernel: [   10.720053] jffs2: jffs2_scan_inode_node(): CRC failed on node at 0x00010fec: Read 0x1080e8fa, calculated 0x300914dc
Wed Nov 15 11:00:49 2023 kern.notice kernel: [   10.743566] jffs2: jffs2_scan_inode_node(): CRC failed on node at 0x00011ff4: Read 0x4f7f19d5, calculated 0x4622eb5c
Wed Nov 15 11:00:49 2023 kern.notice kernel: [   10.767151] jffs2: jffs2_scan_dirent_node(): Name CRC failed on node at 0x00012fd8: Read 0x5feaff7f, calculated 0xbc15280b
Wed Nov 15 11:00:49 2023 kern.notice kernel: [   10.789225] jffs2: jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00013004: 0x0004 instead
Wed Nov 15 11:00:49 2023 kern.notice kernel: [   10.808422] jffs2: jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00013008: 0x0091 instead
Wed Nov 15 11:00:49 2023 kern.notice kernel: [   10.827381] jffs2: jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x0001300c: 0xb557 instead
Wed Nov 15 11:00:49 2023 kern.notice kernel: [   10.846364] jffs2: jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00013010: 0x001b instead
Wed Nov 15 11:00:49 2023 kern.notice kernel: [   10.865295] jffs2: jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00013014: 0x0002 instead
Wed Nov 15 11:00:49 2023 kern.notice kernel: [   10.884210] jffs2: jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00013018: 0x81a4 instead
Wed Nov 15 11:00:49 2023 kern.notice kernel: [   10.903117] jffs2: jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00013020: 0x00c5 instead
Wed Nov 15 11:00:49 2023 kern.notice kernel: [   10.922024] jffs2: jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00013024: 0x000d instead
Wed Nov 15 11:00:49 2023 kern.notice kernel: [   10.940933] jffs2: jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00013028: 0x000d instead
Wed Nov 15 11:00:49 2023 kern.notice kernel: [   10.959848] jffs2: jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x0001302c: 0x000d instead
Wed Nov 15 11:00:49 2023 kern.notice kernel: [   10.978755] jffs2: Further such events for this erase block will not be printed
Wed Nov 15 11:00:49 2023 kern.notice kernel: [   11.005538] jffs2: jffs2_scan_dirent_node(): Node CRC failed on node at 0x00017ff4: Read 0xebc4a963, calculated 0xfa571778
Wed Nov 15 11:00:49 2023 kern.notice kernel: [   11.037511] jffs2: jffs2_scan_dirent_node(): Node CRC failed on node at 0x0001bfe0: Read 0x20021100, calculated 0x2392f540
Wed Nov 15 11:00:49 2023 kern.warn kernel: [   11.067316] jffs2: Empty flash at 0x00040510 ends at 0x00041000
Wed Nov 15 11:00:49 2023 kern.notice kernel: [   11.079149] jffs2: CLEANMARKER node found at 0x00041000, not first node in block (0x00040000)
Wed Nov 15 11:00:49 2023 kern.warn kernel: [   11.098367] jffs2: Empty flash at 0x0004100c ends at 0x00042000
Wed Nov 15 11:00:49 2023 kern.notice kernel: [   11.110186] jffs2: CLEANMARKER node found at 0x00042000, not first node in block (0x00040000)
Wed Nov 15 11:00:49 2023 kern.warn kernel: [   11.131550] jffs2: Empty flash at 0x0004200c ends at 0x00043000
Wed Nov 15 11:00:49 2023 kern.notice kernel: [   11.143374] jffs2: CLEANMARKER node found at 0x00043000, not first node in block (0x00040000)
Wed Nov 15 11:00:49 2023 kern.warn kernel: [   11.162662] jffs2: Empty flash at 0x0004300c ends at 0x00044000
Wed Nov 15 11:00:49 2023 kern.notice kernel: [   11.174509] jffs2: CLEANMARKER node found at 0x00044000, not first node in block (0x00040000)
Wed Nov 15 11:00:49 2023 kern.warn kernel: [   11.195866] jffs2: Empty flash at 0x0004400c ends at 0x00045000
Wed Nov 15 11:00:49 2023 kern.notice kernel: [   11.207695] jffs2: CLEANMARKER node found at 0x00045000, not first node in block (0x00040000)
Wed Nov 15 11:00:49 2023 kern.warn kernel: [   11.226907] jffs2: Empty flash at 0x0004500c ends at 0x00046000
Wed Nov 15 11:00:49 2023 kern.notice kernel: [   11.238722] jffs2: CLEANMARKER node found at 0x00046000, not first node in block (0x00040000)
Wed Nov 15 11:00:49 2023 kern.warn kernel: [   11.260496] jffs2: Empty flash at 0x000466a0 ends at 0x00047000
Wed Nov 15 11:00:49 2023 kern.notice kernel: [   11.272340] jffs2: CLEANMARKER node found at 0x00047000, not first node in block (0x00040000)
Wed Nov 15 11:00:49 2023 kern.notice kernel: [   11.291620] jffs2: CLEANMARKER node found at 0x00048000, not first node in block (0x00040000)
Wed Nov 15 11:00:49 2023 kern.notice kernel: [   11.310936] jffs2: CLEANMARKER node found at 0x00049000, not first node in block (0x00040000)
Wed Nov 15 11:00:49 2023 kern.notice kernel: [   11.330332] jffs2: CLEANMARKER node found at 0x0004a000, not first node in block (0x00040000)
Wed Nov 15 11:00:49 2023 kern.notice kernel: [   11.349706] jffs2: CLEANMARKER node found at 0x0004b000, not first node in block (0x00040000)
Wed Nov 15 11:00:49 2023 kern.notice kernel: [   11.369189] jffs2: CLEANMARKER node found at 0x0004c000, not first node in block (0x00040000)
Wed Nov 15 11:00:49 2023 kern.notice kernel: [   11.388644] jffs2: CLEANMARKER node found at 0x0004d000, not first node in block (0x00040000)
Wed Nov 15 11:00:49 2023 kern.notice kernel: [   11.408005] jffs2: CLEANMARKER node found at 0x0004e000, not first node in block (0x00040000)
Wed Nov 15 11:00:49 2023 kern.notice kernel: [   11.427419] jffs2: CLEANMARKER node found at 0x0004f000, not first node in block (0x00040000)
Wed Nov 15 11:00:49 2023 kern.notice kernel: [   11.447510] jffs2: notice: (376) jffs2_build_xattr_subsystem: complete building xattr subsystem, 19 of xdatum (0 unchecked, 19 orphan) and 29 of xref (2 dead, 27 orphan) found.
Wed Nov 15 11:00:49 2023 user.info kernel: [   11.479890] block: attempting to load /tmp/jffs_cfg/upper/etc/config/fstab
Wed Nov 15 11:00:49 2023 user.err kernel: [   11.494182] block: unable to load configuration (fstab: Entry not found)
Wed Nov 15 11:00:49 2023 user.info kernel: [   11.508076] block: attempting to load /tmp/jffs_cfg/etc/config/fstab
Wed Nov 15 11:00:49 2023 user.err kernel: [   11.521348] block: unable to load configuration (fstab: Entry not found)
Wed Nov 15 11:00:49 2023 user.info kernel: [   11.535233] block: attempting to load /etc/config/fstab
Wed Nov 15 11:00:49 2023 user.err kernel: [   11.559519] block: unable to load configuration (fstab: Entry not found)
Wed Nov 15 11:00:49 2023 user.err kernel: [   11.573416] block: no usable configuration
Wed Nov 15 11:00:49 2023 kern.warn kernel: [   11.593747] jffs2: warning: (374) jffs2_sum_scan_sumnode: Summary node crc error, skipping summary information.
Wed Nov 15 11:00:49 2023 kern.notice kernel: [   11.616553] jffs2: jffs2_scan_inode_node(): CRC failed on node at 0x00010fec: Read 0x1080e8fa, calculated 0x300914dc
Wed Nov 15 11:00:49 2023 kern.notice kernel: [   11.639987] jffs2: jffs2_scan_inode_node(): CRC failed on node at 0x00011ff4: Read 0x4f7f19d5, calculated 0x4622eb5c
Wed Nov 15 11:00:49 2023 kern.notice kernel: [   11.663515] jffs2: jffs2_scan_dirent_node(): Name CRC failed on node at 0x00012fd8: Read 0x5feaff7f, calculated 0xbc15280b
Wed Nov 15 11:00:49 2023 kern.notice kernel: [   11.685594] jffs2: jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00013004: 0x0004 instead
Wed Nov 15 11:00:49 2023 kern.notice kernel: [   11.704500] jffs2: jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00013008: 0x0091 instead
Wed Nov 15 11:00:49 2023 kern.notice kernel: [   11.723411] jffs2: jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x0001300c: 0xb557 instead
Wed Nov 15 11:00:49 2023 kern.notice kernel: [   11.742320] jffs2: jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00013010: 0x001b instead
Wed Nov 15 11:00:49 2023 kern.notice kernel: [   11.761232] jffs2: jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00013014: 0x0002 instead
Wed Nov 15 11:00:49 2023 kern.notice kernel: [   11.780431] jffs2: jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00013018: 0x81a4 instead
Wed Nov 15 11:00:49 2023 kern.notice kernel: [   11.799404] jffs2: jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00013020: 0x00c5 instead
Wed Nov 15 11:00:49 2023 kern.notice kernel: [   11.818311] jffs2: jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00013024: 0x000d instead
Wed Nov 15 11:00:49 2023 kern.notice kernel: [   11.837638] jffs2: jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00013028: 0x000d instead
Wed Nov 15 11:00:49 2023 kern.notice kernel: [   11.856825] jffs2: jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x0001302c: 0x000d instead
Wed Nov 15 11:00:49 2023 kern.notice kernel: [   11.875749] jffs2: Further such events for this erase block will not be printed
Wed Nov 15 11:00:49 2023 kern.notice kernel: [   11.902550] jffs2: jffs2_scan_dirent_node(): Node CRC failed on node at 0x00017ff4: Read 0xebc4a963, calculated 0xfa571778
Wed Nov 15 11:00:49 2023 kern.notice kernel: [   11.934525] jffs2: jffs2_scan_dirent_node(): Node CRC failed on node at 0x0001bfe0: Read 0x20021100, calculated 0x2392f540
Wed Nov 15 11:00:49 2023 kern.warn kernel: [   11.964262] jffs2: Empty flash at 0x00040510 ends at 0x00041000
Wed Nov 15 11:00:49 2023 kern.notice kernel: [   11.976109] jffs2: CLEANMARKER node found at 0x00041000, not first node in block (0x00040000)
Wed Nov 15 11:00:49 2023 kern.warn kernel: [   11.995304] jffs2: Empty flash at 0x0004100c ends at 0x00042000
Wed Nov 15 11:00:49 2023 kern.notice kernel: [   12.007140] jffs2: CLEANMARKER node found at 0x00042000, not first node in block (0x00040000)
Wed Nov 15 11:00:49 2023 kern.warn kernel: [   12.028525] jffs2: Empty flash at 0x0004200c ends at 0x00043000
Wed Nov 15 11:00:49 2023 kern.notice kernel: [   12.040343] jffs2: CLEANMARKER node found at 0x00043000, not first node in block (0x00040000)
Wed Nov 15 11:00:49 2023 kern.warn kernel: [   12.059539] jffs2: Empty flash at 0x0004300c ends at 0x00044000
Wed Nov 15 11:00:49 2023 kern.notice kernel: [   12.071359] jffs2: CLEANMARKER node found at 0x00044000, not first node in block (0x00040000)
Wed Nov 15 11:00:49 2023 kern.warn kernel: [   12.093070] jffs2: Empty flash at 0x0004400c ends at 0x00045000
Wed Nov 15 11:00:49 2023 kern.notice kernel: [   12.104941] jffs2: CLEANMARKER node found at 0x00045000, not first node in block (0x00040000)
Wed Nov 15 11:00:49 2023 kern.warn kernel: [   12.124153] jffs2: Empty flash at 0x0004500c ends at 0x00046000
Wed Nov 15 11:00:49 2023 kern.notice kernel: [   12.135977] jffs2: CLEANMARKER node found at 0x00046000, not first node in block (0x00040000)
Wed Nov 15 11:00:49 2023 kern.warn kernel: [   12.157431] jffs2: Empty flash at 0x000466a0 ends at 0x00047000
Wed Nov 15 11:00:49 2023 kern.notice kernel: [   12.169251] jffs2: CLEANMARKER node found at 0x00047000, not first node in block (0x00040000)
Wed Nov 15 11:00:49 2023 kern.notice kernel: [   12.188554] jffs2: CLEANMARKER node found at 0x00048000, not first node in block (0x00040000)
Wed Nov 15 11:00:49 2023 kern.notice kernel: [   12.207894] jffs2: CLEANMARKER node found at 0x00049000, not first node in block (0x00040000)
Wed Nov 15 11:00:49 2023 kern.notice kernel: [   12.227256] jffs2: CLEANMARKER node found at 0x0004a000, not first node in block (0x00040000)
Wed Nov 15 11:00:49 2023 kern.notice kernel: [   12.246628] jffs2: CLEANMARKER node found at 0x0004b000, not first node in block (0x00040000)
Wed Nov 15 11:00:49 2023 kern.notice kernel: [   12.265935] jffs2: CLEANMARKER node found at 0x0004c000, not first node in block (0x00040000)
Wed Nov 15 11:00:49 2023 kern.notice kernel: [   12.285234] jffs2: CLEANMARKER node found at 0x0004d000, not first node in block (0x00040000)
Wed Nov 15 11:00:49 2023 kern.notice kernel: [   12.304578] jffs2: CLEANMARKER node found at 0x0004e000, not first node in block (0x00040000)
Wed Nov 15 11:00:49 2023 kern.notice kernel: [   12.323894] jffs2: CLEANMARKER node found at 0x0004f000, not first node in block (0x00040000)
Wed Nov 15 11:00:49 2023 kern.notice kernel: [   12.343831] jffs2: notice: (374) jffs2_build_xattr_subsystem: complete building xattr subsystem, 19 of xdatum (0 unchecked, 19 orphan) and 29 of xref (2 dead, 27 orphan) found.
Wed Nov 15 11:00:49 2023 user.info kernel: [   12.843081] block: attempting to load /tmp/jffs_cfg/upper/etc/config/fstab
Wed Nov 15 11:00:49 2023 user.err kernel: [   12.857628] block: unable to load configuration (fstab: Entry not found)
Wed Nov 15 11:00:49 2023 user.info kernel: [   12.871559] block: attempting to load /tmp/jffs_cfg/etc/config/fstab
Wed Nov 15 11:00:49 2023 user.err kernel: [   12.885143] block: unable to load configuration (fstab: Entry not found)
Wed Nov 15 11:00:49 2023 user.info kernel: [   12.899040] block: attempting to load /etc/config/fstab
Wed Nov 15 11:00:49 2023 user.err kernel: [   12.910039] block: unable to load configuration (fstab: Entry not found)
Wed Nov 15 11:00:49 2023 user.err kernel: [   12.923905] block: no usable configuration
Wed Nov 15 11:00:49 2023 user.info kernel: [   12.934333] mount_root: overlay filesystem has not been fully initialized yet
Wed Nov 15 11:00:49 2023 user.info kernel: [   12.950387] mount_root: switching to jffs2 overlay
Wed Nov 15 11:00:49 2023 kern.warn kernel: [   12.967568] overlayfs: upper fs does not support tmpfile.
Wed Nov 15 11:00:49 2023 user.warn kernel: [   12.984051] urandom-seed: Seed file not found (/etc/urandom.seed)

2 Odpowiedź przez Cezary

  • Skąd: Warszawa
  • Zarejestrowany: 2006-02-25
  • Posty: 115,840

Odp: LB-LINK AC1200 - dziwne (?) zapisy w logach po resecie

To pierwsze jest normalnie - zawsze występuje.

To drugie - skasuj rootfs_data bo cos ci się jffs nie zrobił.

Masz niepotrzebny router, uszkodzony czy nie - chętnie przygarnę go.

Cezary's Strona

3 Odpowiedź przez Dyziek

  • Dyziek
  • Użytkownik
  • Nieaktywny
  • Skąd: Warszawa
  • Zarejestrowany: 2019-05-05
  • Posty: 269

Odp: LB-LINK AC1200 - dziwne (?) zapisy w logach po resecie

cześć
jest na to jakas komenda, czy tez przeinstalowac nowy obraz?

4 Odpowiedź przez Cezary

  • Skąd: Warszawa
  • Zarejestrowany: 2006-02-25
  • Posty: 115,840

Odp: LB-LINK AC1200 - dziwne (?) zapisy w logach po resecie

mtd erase rootfs_data

w trybie failsafe

Masz niepotrzebny router, uszkodzony czy nie - chętnie przygarnę go.

Cezary's Strona

5 Odpowiedź przez Dyziek

  • Dyziek
  • Użytkownik
  • Nieaktywny
  • Skąd: Warszawa
  • Zarejestrowany: 2019-05-05
  • Posty: 269

Odp: LB-LINK AC1200 - dziwne (?) zapisy w logach po resecie

dzięki, ruszyło.
Niemniej nadal mam jeden dziwny zapis.
W luci, menu Overview mam:
Storage >>> Disk Space: 244.00 KiB /320 KiB
Temp Space: 88 KiB / 27.97 MiB

jest to o tyle dziwne, ze dla WR841 V13 (8/64, Mediatek) mam:
Storage >>> Disk Space: 128.00 KiB /27.96 MiB
Temp Space: 144 KiB / 27.96 MiB

Ten Disk Space dla LB-LINK'a powinien tak wygladac? Obawiam sie, ze nie

6 Odpowiedź przez Cezary

  • Skąd: Warszawa
  • Zarejestrowany: 2006-02-25
  • Posty: 115,840

Odp: LB-LINK AC1200 - dziwne (?) zapisy w logach po resecie

Czemu nie? Jeżeli zainstalowałeś obraz luci który jest naładowany rzeczami a masz mało flash to właśnie tyle zostaje wolnego miejsca.

Masz niepotrzebny router, uszkodzony czy nie - chętnie przygarnę go.

Cezary's Strona

7 Odpowiedź przez Dyziek

  • Dyziek
  • Użytkownik
  • Nieaktywny
  • Skąd: Warszawa
  • Zarejestrowany: 2019-05-05
  • Posty: 269

Odp: LB-LINK AC1200 - dziwne (?) zapisy w logach po resecie

czyli normalne jest, ze sprzet moze miec maksymalny (nie pisze o zajętym) diskspace na poziomie 320 KB?

8 Odpowiedź przez Cezary

  • Skąd: Warszawa
  • Zarejestrowany: 2006-02-25
  • Posty: 115,840

Odp: LB-LINK AC1200 - dziwne (?) zapisy w logach po resecie

Tak. Zwłaszcza jeżeli masz 8MB i używasz mojego obrazu luci który i wsparcie do usb i ma inne rzeczy. 23.05 to najprawdopodobniej w ogóle ostatnie wydanie które będzie wspierało routery z 8MB flash.

Masz niepotrzebny router, uszkodzony czy nie - chętnie przygarnę go.

Cezary's Strona

9 Odpowiedź przez Dyziek

  • Dyziek
  • Użytkownik
  • Nieaktywny
  • Skąd: Warszawa
  • Zarejestrowany: 2019-05-05
  • Posty: 269

Odp: LB-LINK AC1200 - dziwne (?) zapisy w logach po resecie

Wielkie dzięki za wyjaśnienie.
Co do kilowania edycji 8MB, całkowicie rozumiem starzenie się produktu. One i tak dostały drugie życie.
Jeśli wersja konsolowa nie bedzie sie miescic (Luci i tak ledwo weszlo), to nie ma co, trzeba ciąć.

10 Odpowiedź przez Cezary

  • Skąd: Warszawa
  • Zarejestrowany: 2006-02-25
  • Posty: 115,840

Odp: LB-LINK AC1200 - dziwne (?) zapisy w logach po resecie

Konsolowa jeszcze wchodzi, tyle że ona jest golasem bez niczego. Ale możesz zrobić extroota i możesz instalować co chcesz.

Masz niepotrzebny router, uszkodzony czy nie - chętnie przygarnę go.

Cezary's Strona

11 Odpowiedź przez kofec

  • kofec
  • Użytkownik
  • Nieaktywny
  • Zarejestrowany: 2011-01-05
  • Posty: 243

Odp: LB-LINK AC1200 - dziwne (?) zapisy w logach po resecie

Witam,
Mam podobne błędy: "Bad cell count for /palmbus@10000000/spi@b00/flash@0/partitions"
wiec już nie zakładałem nowego wątku. Czy one są niepokojące na przyszłość ?:

[    0.000000] Linux version 6.6.57 (MojeBuild@OnServer) (mipsel-openwrt-linux-musl-gcc (OpenWrt GCC 13.3.0 r27892-1306885968) 13.3.0, GNU ld (GNU Binutils) 2.42) #0 Tue Oct 22 19:13:26 2024
[    0.000000] Board has DDR2
[    0.000000] Analog PMU set to hw control
[    0.000000] Digital PMU set to hw control
[    0.000000] SoC Type: MediaTek MT7620A ver:2 eco:6
[    0.000000] printk: bootconsole [early0] enabled
[    0.000000] CPU0 revision is: 00019650 (MIPS 24KEc)
[    0.000000] MIPS: machine is Xiaomi MiWiFi Mini
......................
[    0.790425] printk: bootconsole [early0] disabled
[    0.819966] spi spi0.0: force spi mode3
[    0.824739] spi-nor spi0.0: w25q128 (16384 Kbytes)
[    0.829782] 7 fixed-partitions partitions found on MTD device spi0.0
[    0.836374] OF: Bad cell count for /palmbus@10000000/spi@b00/flash@0/partitions
[    0.843883] OF: Bad cell count for /palmbus@10000000/spi@b00/flash@0/partitions
[    0.851663] Creating 7 MTD partitions on "spi0.0":
[    0.856633] 0x000000000000-0x000000030000 : "u-boot"
[    0.865896] 0x000000030000-0x000000040000 : "u-boot-env"
[    0.874061] 0x000000040000-0x000000050000 : "factory"
[    0.881884] OF: Bad cell count for /palmbus@10000000/spi@b00/flash@0/partitions
[    0.889809] 0x000000050000-0x000000fd0000 : "firmware"
[    0.898298] 2 uimage-fw partitions found on MTD device firmware
[    0.904446] Creating 2 MTD partitions on "firmware":
[    0.909524] 0x000000000000-0x00000027420b : "kernel"
[    0.914603] mtd: partition "kernel" doesn't end on an erase/write block -- force read-only
[    0.925788] 0x00000027420b-0x000000f80000 : "rootfs"
[    0.930897] mtd: partition "rootfs" doesn't start on an erase/write block boundary -- force read-only
[    0.942838] mtd: setting mtd5 (rootfs) as root device
[    0.948183] 1 squashfs-split partitions found on MTD device rootfs
[    0.954525] 0x000000810000-0x000000f80000 : "rootfs_data"
[    0.962619] 0x000000fd0000-0x000000fe0000 : "crash"
[    0.970347] 0x000000fe0000-0x000000ff0000 : "reserved"
[    0.978367] 0x000000ff0000-0x000001000000 : "Bdata"
[    1.024299] gsw: setting port4 to ephy mode
[    1.028850] mtk_soc_eth 10100000.ethernet: mdio-bus disabled
[    1.034963] mtk_soc_eth 10100000.ethernet: loaded mt7620 driver
[    1.041889] mtk_soc_eth 10100000.ethernet eth0: mediatek frame engine at 0xb0100000, irq 5

12 Odpowiedź przez Cezary

  • Skąd: Warszawa
  • Zarejestrowany: 2006-02-25
  • Posty: 115,840

Odp: LB-LINK AC1200 - dziwne (?) zapisy w logach po resecie

Nie, to normalnie zachowanie firmware, zignoruj to.

Masz niepotrzebny router, uszkodzony czy nie - chętnie przygarnę go.

Cezary's Strona