please search the thread for "ENABLEDSERVICES" and "/etc/packagesinstall.txt" and "AUTORESTOREAPPLY" if you are upgrading with the luci traditonal menu...
while it always good to see bug reports ( I keep them in mind in my travels and a second report could turn out to be a major issue ) I suspect in this case you've either been caught up in some of the *-20 issues or are doing something that's not recommended (logging in too soon after upgrade?)...
worst case scenario you should probably start with a fresh factory image (-30) but please do let me know if this issue persists ( and what were the circumstances around it's triggering )
the log you posted is something 'inode' related... so the general assumption is that something got messed up with your filesystem... which is a first... / has not been reported by others so i'm pretty lost as to what may have been the underlying reason for this... ( faulty card? )
I think i got the issues since *-20 but ignored it then upgraded to -30. My file system after flashing the sdcard 16GB. Add 2 more partition ntfs and ext4 for more disk usually i call it exroot then setting the overlay in mount disk. Is it recommended to add overlay with same sdcard?
while mounts on the same disk are technically not unsupported... ( and are different from 'overlay' mounts )... they are something i'd only advise for seriously skilled users...
primarily due to the behavior of sysupgrade when additional partitions are present...
for more space... the advised option is to use a usb drive and a non-overlay mount in /etc/config/fstab...
this is what I have (can be done graphically in luci)
thankyou... I will move that notice to a clearer place... it got buried next to less important comments...
(and if I get a chance I will also run some tests with additional partitions during sysupgrade so I can provide better advice/info in the future)
good question... it's a bit of a balancing act depending on what I'm planning / features I support in the build... (and how many people are willing to actively participate in testing these features or need them)
can you explain in a bit more detail;
why you think this would be good?
in what way this would be used?
this will really help me to translate 'operational requirements' into practical implementations...
@anon50098793 is this the reason for my pi4 not giving internet and installing packages after fresh upgrade?
I have removed the dns 127.0.0.1 from my WAN interface.
Yes ofc it's will be good, everyone can do anything or trying something in openwrt, rn available space you're set like 700MB it's good enough but isn't 8GB sdcard can be set more than that. Sometimes i messed around in openwrt instead Using linux running on virtual in windows.
Here the log Everytime login to terminal, should ignored it?
SatJul1006:52:222021 plugin: cu_rrd_create_file (/tmp/rrd/OpenWRT/dns/dns_rcode-SERVFAIL.rrd) failed.
SatJul1006:52:222021 subsystem: Built-in target `write': Dispatching value to all write plugins failed with sta
SatJul1006:52:222021 subsystem: Built-in target `write': Some write plugin is back to normal operation. `write'
And This is kog from system log
Sat Jul 10 06:47:52 2021 daemon.err collectd[11181]: rrdtool plugin: rrd_update_r failed: /tmp/rrd/OpenWRT/dns/dns_rcode-SERVFAIL.rrd: opening '/tmp/rrd/OpenWRT/dns/dns_rcode-SERVFAIL.rrd': No such file or directory
Sat Jul 10 06:48:22 2021 daemon.err collectd[11181]: rrdtool plugin: srrd_create: rrd_create (/tmp/rrd/OpenWRT/dns/dns_rcode-SERVFAIL.rrd) failed: can't parse argument '-s'
Sat Jul 10 06:48:22 2021 daemon.err collectd[11181]: rrdtool plugin: cu_rrd_create_file: srrd_create (/tmp/rrd/OpenWRT/dns/dns_rcode-SERVFAIL.rrd) returned status -1.
Sat Jul 10 06:48:22 2021 daemon.err collectd[11181]: rrdtool plugin: rrd_update_r failed: /tmp/rrd/OpenWRT/disk-mmcblk0p1/disk_ops.rrd: can't parse argument '-s'
Sat Jul 10 06:48:22 2021 daemon.err collectd[11181]: rrdtool plugin: cu_rrd_create_file (/tmp/rrd/OpenWRT/dns/dns_rcode-SERVFAIL.rrd) failed.
Sat Jul 10 06:48:22 2021 daemon.err collectd[11181]: Filter subsystem: Built-in target `write': Dispatching value to all write plugins failed with status -1.
Sat Jul 10 06:48:22 2021 daemon.err collectd[11181]: Filter subsystem: Built-in target `write': Some write plugin is back to normal operation. `write' succeeded.
Sat Jul 10 06:48:52 2021 daemon.err collectd[11181]: rrdtool plugin: rrd_update_r failed: /tmp/rrd/OpenWRT/dns/dns_rcode-SERVFAIL.rrd: opening '/tmp/rrd/OpenWRT/dns/dns_rcode-SERVFAIL.rrd': No such file or directory
Sat Jul 10 06:49:22 2021 daemon.err collectd[11181]: rrdtool plugin: rrd_update_r failed: /tmp/rrd/OpenWRT/dns/dns_rcode-SERVFAIL.rrd: opening '/tmp/rrd/OpenWRT/dns/dns_rcode-SERVFAIL.rrd': No such file or directory
Sat Jul 10 06:49:52 2021 daemon.err collectd[11181]: rrdtool plugin: rrd_update_r failed: /tmp/rrd/OpenWRT/dns/dns_rcode-SERVFAIL.rrd: opening '/tmp/rrd/OpenWRT/dns/dns_rcode-SERVFAIL.rrd': No such file or directory
Sat Jul 10 06:50:22 2021 daemon.err collectd[11181]: rrdtool plugin: rrd_update_r failed: /tmp/rrd/OpenWRT/dns/dns_rcode-SERVFAIL.rrd: opening '/tmp/rrd/OpenWRT/dns/dns_rcode-SERVFAIL.rrd': No such file or directory
Sat Jul 10 06:50:52 2021 daemon.err collectd[11181]: rrdtool plugin: rrd_update_r failed: /tmp/rrd/OpenWRT/dns/dns_rcode-SERVFAIL.rrd: opening '/tmp/rrd/OpenWRT/dns/dns_rcode-SERVFAIL.rrd': No such file or directory
Sat Jul 10 06:51:22 2021 daemon.err collectd[11181]: rrdtool plugin: rrd_update_r failed: /tmp/rrd/OpenWRT/dns/dns_rcode-SERVFAIL.rrd: opening '/tmp/rrd/OpenWRT/dns/dns_rcode-SERVFAIL.rrd': No such file or directory
Sat Jul 10 06:51:52 2021 daemon.err collectd[11181]: rrdtool plugin: srrd_create: rrd_create (/tmp/rrd/OpenWRT/dns/dns_rcode-SERVFAIL.rrd) failed: can't parse argument '-s'
Sat Jul 10 06:51:52 2021 daemon.err collectd[11181]: rrdtool plugin: cu_rrd_create_file: srrd_create (/tmp/rrd/OpenWRT/dns/dns_rcode-SERVFAIL.rrd) returned status -1.
Sat Jul 10 06:51:52 2021 daemon.err collectd[11181]: rrdtool plugin: rrd_update_r failed: /tmp/rrd/OpenWRT/dns/dns_qtype-NAPTR.rrd: can't parse argument '-s'
Sat Jul 10 06:51:52 2021 daemon.err collectd[11181]: rrdtool plugin: cu_rrd_create_file (/tmp/rrd/OpenWRT/dns/dns_rcode-SERVFAIL.rrd) failed.
Sat Jul 10 06:51:52 2021 daemon.err collectd[11181]: Filter subsystem: Built-in target `write': Dispatching value to all write plugins failed with status -1.
Sat Jul 10 06:51:52 2021 daemon.err collectd[11181]: Filter subsystem: Built-in target `write': Some write plugin is back to normal operation. `write' succeeded.
Sat Jul 10 06:52:22 2021 daemon.err collectd[11181]: rrdtool plugin: srrd_create: rrd_create (/tmp/rrd/OpenWRT/dns/dns_rcode-SERVFAIL.rrd) failed: can't parse argument '-s'
Sat Jul 10 06:52:22 2021 daemon.err collectd[11181]: rrdtool plugin: cu_rrd_create_file: srrd_create (/tmp/rrd/OpenWRT/dns/dns_rcode-SERVFAIL.rrd) returned status -1.
Sat Jul 10 06:52:22 2021 daemon.err collectd[11181]: rrdtool plugin: rrd_update_r failed: /tmp/rrd/OpenWRT/dns/dns_octets.rrd: can't parse argument '-s'
Sat Jul 10 06:52:22 2021 daemon.err collectd[11181]: rrdtool plugin: cu_rrd_create_file (/tmp/rrd/OpenWRT/dns/dns_rcode-SERVFAIL.rrd) failed.
Sat Jul 10 06:52:22 2021 daemon.err collectd[11181]: Filter subsystem: Built-in target `write': Dispatching value to all write plugins failed with status -1.
Sat Jul 10 06:52:22 2021 daemon.err collectd[11181]: Filter subsystem: Built-in target `write': Some write plugin is back to normal operation. `write' succeeded.
that plugin has a low benefit<>load/resource ratio, if it causes problems for others (or they think its a good idea to remove it) i'm ok with dropping it...
then you should update your config to reflect this...
(the recommended/default setup is wan on eth1)
search the thread for this...
I try to provide a typical config for most people
and... it's impossible to accommodate for
every custom setup...
(removing this will disadvantage 96% of build users)
some level of user configuration is required in
these cases...
uci set luci_statistics.collectd_exec_input.cmdline='/usr/libexec/collectd/sqm_collectd.sh eth0'
uci commit luci_statistics
/etc/init,d/luci_statistics restart
( or luci > statistics > setup > general > exec [configure] )
wifi firmware txt file needed (think I may have patched for this)
see manufacturer page re: dwc host config.txt for enabling usb
happy to take your advice on those if they need to be setup by default or whatnot...
(carp... I have a bunch of logic that tests for '4-model-b' for boardname to automate stuff... it will take longer to add some fixes for additional boards... consider that build a 'tester' (driver function only... and i'll let you know when a proper build is ready -> 90% done...)
pm me a;
dmesg | grep -E '(4-model-b|4-compute-module)'
after firstboot...
one other query / concern I have about these boards is how they present any onboard storage(if present) vs sdcard...
is it just a jumper that uses one or the other
do both present as /dev/mmcblk0 or is it possible to have both with a second /dev/mmcblk1
etc. etc. (disregard if your cm4 has no onboard storage)
sidenote: limited rpi-400 fixes were also implemented as above... so if there are any 400 users you will need to also do a little run testing to polish off support...