We (more specifically jc) are already looking into it. Yes, something got broken.
so long,
Hias
We (more specifically jc) are already looking into it. Yes, something got broken.
so long,
Hias
In general it's a bad idea to trim on each block free (i.e. using the discard mount option) as that leads to write amplification and will wear out SSDs quickly.
It's better to regularly run "fstrim -a", typically once a week, via a systemd timer.
LE doesn't ship fstrim.service/fstrim.timer systemd files but you can easily add them to /storage/.config/systemd/ and then enable it with "systemctl enable fstrim.timer".
Untested as I don't have any SSDs on my LE devices here, but these should work:
fstrim.service
[Unit]
Description=Discard unused blocks on filesystems
[Service]
Type=oneshot
ExecStart=/usr/sbin/fstrim --all --verbose --quiet-unsupported
fstrim.timer:
[Unit]
Description=Discard unused blocks once a week
[Timer]
OnCalendar=weekly
AccuracySec=1h
Persistent=true
RandomizedDelaySec=6000
[Install]
WantedBy=timers.target
Display More
so long,
Hias
What's the exact model of your remote and receiver?
IR remotes using the standard MCE (RC6) protocol will give you repeated button presses so you can just hold the button (eg to change volume up/down or to scroll through a list).
There are lots of other remotes though which are commonly (but somewhat incorrecrtly) referred to as "MCE" remotes which use proprietary protocols and receivers. A very common one is the Gmyle / Ortek / Hama VRC-1100 - and guess what, it only sends repeats with up/down/left/right buttons (and maybe a few others) but not volume up/down.
So if you have one of these there's not much you can do.
so long,
Hias
The log files are quite old and show you are/were using an old inputstream.adaptive version (20.3.7).
Make sure you have the latest version (20.3.8) installed - that fixes a memory leak which sounds a lot like the issue you are having.
Please report back if the issue is fixed or not - in the latter case please post new logs.
so long,
Hias
NFS over UDP is disabled in LE (like in most other distributions as well), so just use TCP instead.
See the kernel config for background info why UDP isn't supported anymore:
default y
help
Choose Y here to disable the use of NFS over UDP. NFS over UDP
on modern networks (1Gb+) can lead to data corruption caused by
fragmentation during high loads.
so long,
Hias
Can I go back to 11 if I need to?
Only with a clean install and restoring the backup.
Best to test it by booting from a USB pendrive in live or run mode.
so long,
Hias
I've added the fix to LE11 and LE12, it'll be in the next nightly builds.
so long,
Hias
On LE11 and before use "vcdbg log msg" - vclog is only available in LE12.
so long,
Hias
I'm no expert in kodi caching details but quite likely it had cached more audio data than video so audio could continue for a while.
As for the USB drive: might be worth to just ditch the case, there are tons of reports of cheap USB-SATA/NVMe adapters/cases being crap.
so long,
Hias
The log shows that your USB (SSD?) drive frequently stops responding and the kernel needs to reset it (after the 30 second timeout elapsed) so no wonders you have issues playing media from it.
May 07 07:49:49.601266 RPi4 kernel: usb 2-2: reset SuperSpeed USB device number 2 using xhci_hcd
May 07 07:49:49.617935 RPi4 kernel: sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x03 driverbyte=DRIVER_OK cmd_age=30s
May 07 07:49:49.618535 RPi4 kernel: sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x28 28 00 03 3b 5d e2 00 01 00 00
May 07 07:49:49.618913 RPi4 kernel: I/O error, dev sda, sector 54222306 op 0x0:(READ) flags 0x80700 phys_seg 6 prio class 2
Insufficient power and broken cables/connectors/... are very often causing such errors, so first try to look into that and connect via a powered USB3 hub.
Lots of USB devices, especially the cheap no-name ones, have broken USB implementations and sometimes it's possible to work around those with usb-storage.quirks - in your case it's not the rather frequent UAS issue though, it's already using the usb-storage driver.
Quick search for the USB IDs (idVendor=13fd, idProduct=3456) didn't show up anything useful, searching for "sage 3639S" did neither so not sure what device you actually have.
so long,
Hias
Using a btrfs filesystem as /storage is not supported, the btrfs kernel driver is built as a module (so not available during initramfs stage) and also the initramfs doesn't contain fsck.btrfs - this is only available via the btrfs-progs addon (so in case anything goes wrong you won't be able to fix the issue on LE).
Stick to ext4 for /storage - you can use btrfs on additional drives though.
so long,
Hias
You need to add "dtoverlay=cma,cma-256" to the end of config.txt, otherwise LE won't boot on devices with 512MB RAM.
so long,
Hias
Do you have a space in your password? It looks like LE will trip over that (and maybe other special characters, too) - so avoid them.
so long,
Hias
Mario77 most RPi2s are 32bit SOCs (Cortex A7) - only the very latest RPi2 production runs used the same (64bit capable, Cortex-A53) SOC as RPi3.
so long,
Hias
Thanks for checking, you have plenty of space free so we can tick that idea off the list.
so long,
Hias
Is your storage partition full? That would explain why copying the database doesn't work.
ssh in, run "df -h" and post the output
so long,
Hias