* John Crispin <blo...@openwrt.org> [24.02.2015 21:50]:

today i started to sysupgrade a r44751 router and the log (in another terminal) 
showed this:

Wed Mar 18 22:46:05 2015 daemon.notice netifd: Network device 'wlan0' link is 
down
Wed Mar 18 22:46:05 2015 daemon.notice netifd: Interface 'wlanadhocRADIO1' has 
link connectivity loss
Wed Mar 18 22:46:06 2015 daemon.notice netifd: Interface 'wlanadhocRADIO1' is 
now down
Wed Mar 18 22:46:06 2015 daemon.notice netifd: Interface 'wlanadhocRADIO1' is 
disabled
Wed Mar 18 22:46:06 2015 daemon.err procd: Rebooting as procd has crashed
Wed Mar 18 22:46:06 2015 daemon.info procd: reboot
Wed Mar 18 22:46:06 2015 daemon.notice netifd: Interface 'wlanRADIO1' is now 
down
Wed Mar 18 22:46:06 2015 daemon.notice netifd: Interface 'wlanRADIO1' is 
disabled
Wed Mar 18 22:46:06 2015 daemon.notice netifd: Interface 'wlanRADIO1' has link 
connectivity loss
Wed Mar 18 22:46:08 2015 kern.notice kernel: [42464.060000] Removing MTD device 
#3 (rootfs_data) with use count 1
Wed Mar 18 22:46:08 2015 kern.err kernel: [42464.080000] m25p80 spi0.0: error 
-143 reading 5
Wed Mar 18 22:46:08 2015 kern.err kernel: [42464.080000] error -143 reading SR
Wed Mar 18 22:46:08 2015 kern.err kernel: [42464.090000] blk_update_request: 
I/O error, dev mtdblock2, sector 5936
Write failed: Broken pipe

after that, the 'TP-LINK TL-WR1043ND' rebootet and the log was full of:
[  623.110000] jffs2: iget() failed for ino #131
[  632.960000] jffs2: warning: (361) jffs2_get_inode_nodes: Eep. No valid nodes 
for ino #131.
[  632.970000] jffs2: warning: (361) jffs2_do_read_inode_internal: no data 
nodes found for ino #131

and some files (e.g. netifd) could'nt be loaded anymore, so the only
possible solution to bootup somehow was failsafe, but 'firstboot' hangs
forever.

should a do more tests before reflashing via serial console?

bye, bastian
_______________________________________________
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Reply via email to