OpenWrt Forum Archive

Topic: mount_root: No jffs2 marker was found

The content of this topic has been archived on 31 Mar 2018. There are no obvious gaps in this topic, but there may still be some posts missing at the end.

I tried this FW today:

59d7390ff8d8a572d8a490b33b765a82  openwrt-ar71xx-generic-tl-mr3220-v2-squashfs-factory.bin

after flashing, the router reboots in infinite loop. Led starts flashing then reboot. I can still enter safe mode and login with telnet, but I am unable to debrick it. What is wrong?

Dropbear does not start so I cannot scp another firmware sad

any idea?

root@(none):/# mount_root
mount_root: No jffs2 marker was found
mount_root: mount failed: Invalid argument

root@(none):/# mount
rootfs on / type rootfs (rw)
/dev/root on /rom/rom type squashfs (ro,relatime)
proc on /proc type proc (rw,noatime)
sysfs on /sys type sysfs (rw,noatime)
tmpfs on /tmp type tmpfs (rw,nosuid,nodev,noatime)
tmpfs on /dev type tmpfs (rw,noatime,size=512k,mode=755)
devpts on /dev/pts type devpts (rw,noatime,mode=600)
tmpfs on /tmp/root type tmpfs (rw,noatime,mode=755)
overlayfs:/tmp/root on /rom type overlayfs (rw,noatime,lowerdir=/,upperdir=/tmp/root)
tmpfs on /tmp/root type tmpfs (rw,noatime,mode=755)
overlayfs:/tmp/root on / type overlayfs (rw,noatime,lowerdir=/,upperdir=/tmp/root)
tmpfs on /tmp/root type tmpfs (rw,noatime,mode=755)


root@(none):/# df
Filesystem           1K-blocks      Used Available Use% Mounted on
rootfs                   14496         0     14496   0% /
/dev/root                 1792      1792         0 100% /rom/rom
tmpfs                    14496        12     14484   0% /tmp
tmpfs                      512         0       512   0% /dev
tmpfs                    14496         0     14496   0% /tmp/root
overlayfs:/tmp/root      14496         0     14496   0% /rom
tmpfs                    14496         0     14496   0% /tmp/root
overlayfs:/tmp/root      14496         0     14496   0% /
tmpfs                    14496         0     14496   0% /tmp/root

root@(none):/# ps
  PID USER       VSZ STAT COMMAND
    1 root      1248 S    /sbin/init
    2 root         0 SW   [kthreadd]
    3 root         0 SW   [ksoftirqd/0]
    4 root         0 SW   [kworker/0:0]
    5 root         0 SW<  [kworker/0:0H]
    6 root         0 SW   [kworker/u:0]
    7 root         0 SW<  [kworker/u:0H]
    8 root         0 SW<  [khelper]
    9 root         0 SW   [kworker/u:1]
   63 root         0 SW   [bdi-default]
   65 root         0 SW<  [kblockd]
   95 root         0 SW   [kswapd0]
  141 root         0 SW   [fsnotify_mark]
  169 root         0 SW<  [ath79-spi]
  245 root         0 SW<  [deferwq]
  247 root         0 SW   [kworker/0:2]
  257 root         0 SW   [khubd]
  285 root      1620 S    /bin/sh /etc/preinit
  350 root      1492 R    telnetd -l /bin/login.sh
  354 root      1484 S    lock /tmp/.failsafe
  355 root      1496 S    ash --login
  362 root      1508 S    /bin/ash --login
  396 root      1492 R    ps

root@(none):/# dropbear -F -E
[400] Jan 01 00:07:26 Premature exit: Bad buf_getptr

I think this is the cause of the problem (from dmsg) - but why it happend and what went wrong??

[    0.700000] 0x000000000000-0x000000020000 : "u-boot"
[    0.710000] 0x000000020000-0x00000011eb80 : "kernel"
[    0.710000] mtd: partition "kernel" must either start or end on erase block boundary or be smaller than an erase block -- forcing read-only
[    0.730000] 0x00000011eb80-0x0000003f0000 : "rootfs"
[    0.730000] mtd: partition "rootfs" must either start or end on erase block boundary or be smaller than an erase block -- forcing read-only
[    0.740000] mtd: partition "rootfs" set to be root filesystem
[    0.750000] mtd: partition "rootfs_data" created automatically, ofs=2D0000, len=120000
[    0.760000] 0x0000002d0000-0x0000003f0000 : "rootfs_data"
[    0.760000] 0x0000003f0000-0x000000400000 : "art"
[    0.770000] 0x000000020000-0x0000003f0000 : "firmware"

I also had this problem with the 13 July build for the TL-WR720N.  I could put a working firmware on it with the netcat / indirect method described on <http://wiki.openwrt.org/doc/howto/generic.sysupgrade>.  This will probably work for you, too.

yeah I debricked it using netcat.... however do not find the reason why it bricked. Seems to me the Jul 13 images are broken... just wait few days.

Same here, jul 13 built, TP-3220 v2.1 . And netcat (indirect method as recommended) does not solve the issue. Are the snapshots weekly?

kurczaq wrote:

yeah I debricked it using netcat....

tell me steps that you've done, please

velsi wrote:
kurczaq wrote:

yeah I debricked it using netcat....

tell me steps that you've done, please

you basically do on the host (replace firmwareXXXX with the correct filename ):

cat firmwareXXXX | netcat -l 3333

and on the router:

nc 192.168.1.X 3333 >fw.bin

you must be able to login into router in safe mode. X is the IP of the host.

then on the router you do "sysupgrade fw.bin" and you are done.

thanks

my problem was in win7 firewall

The discussion might have continued from here.