you could search for the name, in this case the date-time string.
or for size (see the man page)
find / -size +2G | more
searches under "/" for files greater then 2G and will maybe output a long list.
the command stops each page, cause of "| more";
further/next page with the space key
I got it right, you're searching for a ~vanished~ backup made with the buildin backup tool ?
if you haven't changed it (if doable at all) backup's usually contain a date-time-string in it's name.
A full name is "20220819222924.tar" and this one was made at date 19.08.2022 and time 22:29:24
after ssh'ed into the box the command
find /storage -name '*20220819*'
will search under "/storage" (other location would be "/var/media" where external disks are usually mounted OR "/" to search the whole disk including mounted disk)
and
will find all files containing "20220819" in it's name, if existing
alternative:
find /storage -name '*.tar'
will find all files under "/storage" ending on ".tar"
you know when you made the ~vanished~ backup, so please adjust the date or use the alternative find command ?
you're able to ssh into the box ?
more to read/learn ? :
I tried that but kodi still crashes.
sometime it helps to setup/install from ground of (on ?) new to remove old cruft what maybe has been collected over years
- if doable ... -
Or just use the "remove media" option from the context menu in the video files view.
didn't know it since now !
thanks
I completely overread it's an RPi....
Your's and Joe's comments pretty much destroy my theory. ...
well, not complete, if the main question was: what causes FS corruption !
why "not complete" ?
cause of this:
During bootup LE will then scan for all USB devices and mount all partitions (except boot/flash and storage, which are already mounted) in /var/media so you can access them - here your 6TB HDD will get mounted.
so to prevent FS corruption you need to do either
- shutdown the RPi (system shutdown will unmount all mounted disks for you)
or
- in an terminal run "umount /var/media/*" or better "sync && sync && umount /var/media/*"
before unplugging the disk.
to iterate:
a FS gets corrupt when a disk gets unplugged or a power cut, while the FS/disk is in use.
and "being mounted" translates to being "in use", here.
what was the reason switching back to LE10.
LE11 has newer components (kernel, etc).
I'm running LE11 nightly with DRMPrime OFF and without errors since month.
You're right, I didn't realize this thread had a different goal
me too (or too late)
let's build a club 
your thought/theory are unlikely
the most against your thinking was declared in the other thread (closed cause of "layer 8 problem" on both ends).
again:
mostly a filesystem gets corrupt when the drive is disconnected while being in use/mounted (e.g. hard power cut).
against the "boot theory" and for the "dear Pi don't boot my external drive":
usually LE is configured where to boot from during LE installation.
with the UUID's form the disk what is attached during installation.
in an LE terminal the command
dmesg|grep "Kernel command line:"
will show what UUID's are involved.
there are usually two entries (from my sata ssd):
- boot=UUID=...
and
- disk=UUID=...
what UUID belongs to what partition/disk is shown by the command "blkid"
long story short:
I'm not aware off by only attaching an external disk would change the above entries where to boot from !
- that changes need more work -
therefore I'm - for the main part - NOT convinced that the external disk is bootable at all and if it would somehow, with the lack of needed boot files you would see an error message only (unable to boot from ... or such ), but it wouldn't corrupt the filesystem.
===
to boot from a disk you additional need the disk marked as bootable (don't know if that is still true with EFI !)
if you only partitioned and formated your external disk this bootable flag is usually NOT set (unsure).
there are some tools (fdisk, parted, etc.) out there to see and change the boot flag.
!!! playing with those tools could damage partitions !!!
parted is available on LE.
please read the help files/manuals for parted, e.g. "man parted" => internet
there the "print" command and how to find out if a external disk IS bootable or NOT
my LE internal and bootable sata ssd:
...
1 4194kB 541MB 537MB fat16 System boot, legacy_boot, esp
...
3. Am I safe to just delete storage\.kodi\userdata\Thumbnails\
yes.
and you need to delete:
/storage/.kodi/userdata/Database/Textures13.db
too
next time the box boots or when you open pictures in you picture folder the thumbnails are generated again
to me there seem to be problems with your video:
2022-08-19 22:06:50.228 T:891
and
2022-08-19 22:06:50.387 T:891
care to try another one from maybe here:
P.S.
did you realize that you put comment/issue in a thread dealing with special images from smp what are different from LE11 nightlies you're running ?
TL,DR, don't know what these special images *exactly* are for ...
running nightly and SAT-TV on an NUC8 [*] and all is fine here (apart when thunderstorm).
my shots into the dark:
1. what does "Continuity" counter show ?
login to the web-IF from TVH required => Tab "Status" (usually http://<the TVH-server-IP-addr-here>:9981/)
explanation: same Web-IF => menu bar => help
2 . does this also happen switching between two recorded TV streams or two movies with same codecs as the tv stream ?
P.S.
try to run the lastest nightly
[*]
assuming nuc's buildin media devices haven't changed much NUC8 => NUC11
your log isn't accessable without ubuntu pastebin log in !
is the NUC11 a new device (cause talking about an NUC5 first) ?
if so:
recheck your bios setting regarding audio.
on my nuc8 with audio jack I've two bios entries (HDMI and DSP something; the last is off) seems not the case for an NUC11TNHi3 (not audio jack)
running audio via hdmi through the headphone jack on the monitor (maybe a test scenario for you too, before running CEC stuff ?)
recheck if new bios available what maybe fixes a media device related bug
to me your journal looks sane.
It would be best to switch debug ON and provide a kodicrash.log after the crash occurred.
you need a reboot after switching debug on !
Log files
more to read:
https://wiki.libreelec.tv/support/log-files
I would be also good to know if
- all addon's are up to date ?
- the crash always happens with the same video ?
- you're running a local video or does it come from remote box (via LAN ? ) ?
P.S.
in one off the elder LE releases is was recommended NOT to only update the box.
A new install was prefered...
somebody ran out of patience and attacked original poster.
I'm convinced the "somebody" doesn't "attack original poster", but "attacks" the OPs wrong attitude what prevents to find the answer for his question(s) himself.
please learn to read the differences in the sentences ! 
Both NTFS and exFAT are not native filesystems for Linux and NTFS implementation is older and more mature.
sure ?
both are in-kernel FS's
the exfat implementation is -AFAIK- from Samsung, where M$ exfat was thrown away last (?) year.
The New Microsoft exFAT File-System Driver Has Landed In Linux 5.7 - Phoronix
IIRC, a similar story happend with ntfs...
Wikipedia have a very detailed entry if I was interested in technical specs. I'm not.
okay, next time please mention in your questions that your're not really interesting in answers, safes some time here ...
doesn't come to any reaction
english isn't your native language, right ?
anyway:
what "reaction" is expected or what doesn't work after ghtester recommendation, e.g. is "tvhe-4.2-server gets stuck to sat2ip-stream" afterwards still a problem and only fixable via reboot ?
with ghtester recommendation you' ll just see - IIRC - that the button flip from "disable" to "enable and vice versa.
but in the background the services get restarted without any popup or such.
How can I reload tvhe-server & -client - preferable by remote control just for my wife....
as long as the issue isn't cleared, what's about: train your wife to reboot the box via remote (if that helps here)
...
* Use OneDrive as a source. (=> read only ?)
...
