Readonly filesystem usually means there is a problem with your system disk. Maybe the filesystem got damaged, or, in the worse case, the eMMC memory cells have died.
Thanks both.
7.1.4 is the one it is running. Had auto update on always.
Lucky I dont use the eMMC, the system is running on mSATA SSD in the internal PCIe port.
Ok, I will research how to fresh / re- install the system.
root@turris:~# mount
/dev/sda1 on / type btrfs (ro,noatime,ssd,space_cache,commit=5,subvolid=256,subvol=/@)
devtmpfs on /dev type devtmpfs (rw,relatime,size=1031232k,nr_inodes=187936,mode=755)
proc on /proc type proc (rw,nosuid,nodev,noexec,noatime)
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,noatime)
cgroup2 on /sys/fs/cgroup type cgroup2 (rw,nosuid,nodev,noexec,relatime,nsdelegate)
tmpfs on /tmp type tmpfs (rw,nosuid,nodev,noatime)
tmpfs on /dev type tmpfs (rw,nosuid,noexec,noatime,size=512k,mode=755)
devpts on /dev/pts type devpts (rw,nosuid,noexec,noatime,mode=600,ptmxmode=000)
debugfs on /sys/kernel/debug type debugfs (rw,noatime)
bpffs on /sys/fs/bpf type bpf (rw,nosuid,nodev,noexec,noatime,mode=700)
none on /srv type tmpfs (rw,relatime,size=51200k)
Thanks for the help
I could remount read-write with " mount -o remount,rw /dev/sda1 / " command
and now the pkgupdate is running
upd. and it has finished successfully. Thanks for all the help.
Second Omnia updated. No reboot required and using new notification system. Thanks
I am not sure if I understand your comment - you want to say that Thread Detection works fine despite the fact Overview screen says it is Disabled? I observe the same on my Turris after upgrade to 7.2.0, so I am also curious why it says suddenly Disabled. Or does it mean that this feature was deprecated by Turris team?
Personally I see it as bug and Turris team should at least react in terms - yes, we know about it and working on fix or no, ignore it or we are investigating. Otherwise it leaves people in doubt what is happening.
Yes - the reForis-Overview function indication is negative, active in the Sentinel-Overview option, and the result shows that Sentinel is working.
Iâm curious to learn how well Transmission is working on this release. My Omnia is still on 6.5.2, because I was reading newer versions had issues with Transmission. (High CPU usage.)
i found this to be the case on every release since ~7.2.0 and continues from there over the releases on HBT onto 8.0 on HBL where i am now
None of the new âNetwork Settingsâ panels seem to work for me. I guess I have a pretty complex non-standard setup so I can understand that, but the new sections have errors:
LAN:
An unknown API error occurred.
DNS:
An unknown API error occurred.
Guest Network (which I donât really use):
An unknown API error occurred.
Port Forwarding:
An error occurred while fetching data.
This doesnât really affect me since I do almost all of this management in LuCI anyway.
Under Administration, there are repeated entries.
When I selected one (Diagnostics in this case):
This seems to be merely cosmetic.
I guess your reforis needs a Ctrl+F5.
Hello,
I run pkgupdate :
WARN:There is a newer version available, but update is scheduled after another 1 6.2 hours. If you want the latest and greatest all the time, switch to one of th e development branches.
So I wonât get anything for now.
But if I reset in â4 LEDâ mode
i.e. a USB flash with version 7.2.0 loaded, this version will last for a while. And after about 10 minutes, it will downgrade to 7.1.4
Why did the downgrade take place ?
7.1.4 â 7.2.0 update okay except the dynamic firewall issue reported above. Restart was not needed.
Turris Omnia 2017, 1 GB RAM, dead eMMC, system running from mSATA SSD, original wifi cards, UBoot 2022.10. Storage plugin enabled, LXC containers, tor relay, USB HDD shared over samba4 and minidlna, Syncthing, SQM, Hardwario gateway + MQTT IoT bridge, OpenVPN, PPtP VPN, Strongswan IKEv2 VPN, morce.
I have already updated everything to 7.2.0
I have âHaasâ set up correctly including the token set up, why is âthreat detectionâ in the off state?
It seems to be a bug on the reForis Overview page. Iâve created an issue for it and it will be solved.
@ljelinek also report my previous post to your devs:
Also minor reforis bug
I am running on this issue:
I have exactly the same observation. After 10/24 the number of incidents went almost to zero. Is the whole thing working? All services seem up and running.
Same issue here with threat detection disabled
Additionally for Reforis port forwarding, Iâm missing field for option src_ip
[needs to allow to enter a range, not only a single IP]
Whereas the destination port should not be required, as mentioned Turris OS 7.2 is out! - #7 by xsys
Turris Omnia 2020. 2GB, 2x WiFi, 1TB SSD, VLAN, Wireguard, AdBlock, MiniDlna, Samba.
Update went smooth without any errors but IPv6 stopped working, interface seems down and cant bring up. Everything else seems working fine. Nothing specific in logs.
root@turris:~# ifstatus wan6
{
"up": false,
"pending": true,
"available": true,
"autostart": true,
"dynamic": false,
"proto": "dhcpv6",
"device": "eth2",
"data": {
}
}