random crashing and rebooting into safe mode.

    these are the 2 errors i get. i googled them but didn't find a solution:

    If you read the code you'll find that in lots of scenarios Kodi tests for capabilities and makes code-path decisions based on whether something succeeds (is supported) or fails (is not supported). Both 'errors' are normal and harmless.

    Quote from chewitt

    If you read the code you'll find that in lots of scenarios Kodi tests for capabilities and makes code-path decisions based on whether something succeeds (is supported) or fails (is not supported). Both 'errors' are normal and harmless.

    i understand. that's why i'm posting this issue for help.

    If you want support from experienced users or from experts like chewitt , you shouldn't skim with information. Snippets of logs are in 99.99 percent are pointless and and results into same as if you post "something is going wrong" - nothing more, no helpful content. Please provide a full debug log like described above.

    Quote from HarryH

    If you want support from experienced users or from experts like chewitt , you shouldn't skim with information. Snippets of logs are in 99.99 percent are pointless and and results into same as if you post "something is going wrong" - nothing more, no helpful content. Please provide a full debug log like described above.

    i understand. i thought i was posting the required log. here is per the instructions. but it didn't give me an ix.io link. it gave me this url: https://paste.libreelec.tv/discrete-stallion.log

    I'd suggest updating to an LE13 nightly before doing anything else. If there's a bug/issue related to UPnP the issue is with Kodi not the OS layer (LE) and all Kodi development moved onto K22 more than a year ago. See if anything changes with the update.

    There are two major issues in the log.

    Code
    Thread 1 (Thread 0x7f0a06ea86c0 (LWP 5007)):
#0  0x00007f0a62182aaa in free () from /usr/lib/libc.so.6
#1  0x0000000000ee2952 in dbiplus::SqliteDataset::close() ()
#2  0x0000000000c56ff3 in CVideoDatabase::GetEpisodesByWhere(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, CDatabase::Filter const&, CFileItemList&, bool, SortDescription const&, int) ()
#3  0x0000000000c57e9f in CVideoDatabase::GetItems(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, CFileItemList&, CDatabase::Filter const&, SortDescription const&) ()
#4  0x00000000014c6a22 in XFILE::CSmartPlaylistDirectory::GetDirectory(CSmartPlaylist const&, CFileItemList&, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, bool) ()
#5  0x00000000014c7bfb in XFILE::CSmartPlaylistDirectory::GetDirectory(CURL const&, CFileItemList&) ()
#6  0x00000000014a44a7 in XFILE::CDirectory::GetDirectory(CURL const&, std::shared_ptr<XFILE::IDirectory> const&, CFileItemList&, XFILE::CDirectory::CHints const&) ()
[...]

    1. Kodi is crashing when closing the video database. May be a broken sqlite DB file.

    Code
    Apr 18 01:49:06.662671 KodiServer kernel: EXT4-fs (sdc1): warning: mounting fs with errors, running e2fsck is recommended

Apr 18 01:49:06.665733 KodiServer kernel: EXT4-fs (sda): warning: mounting fs with errors, running e2fsck is recommended

Apr 18 01:49:06.679060 KodiServer kernel: EXT4-fs (sdb): warning: mounting fs with errors, running e2fsck is recommended

    2. The file systems on your HDs (except the NVME) are broken.

    I do recommend a system backup (via LE settings) to an external media first, then fixing the errors before trying any larger updates.

    Quote from mglae

    There are two major issues in the log.

    1. Kodi is crashing when closing the video database. May be a broken sqlite DB file.

    2. The file systems on your HDs (except the NVME) are broken.

    I do recommend a system backup (via LE settings) to an external media first, then fixing the errors before trying any larger updates.

    okay. can you recommend a good way to prepare the drives? i used ubuntu to do a fresh format in ext4 on all drives. i do have minitool partition wizard i can use. i just figured doing through an actual linux distro would be better. they were all brand new drives and all were formatted back to back in ubuntu. do you think i may have done something incorrectly or with the wrong setting? or could the filesystems have just become corrupted this quick from crashing (3 months)? this is my first time using ext4. previously i've only used ntfs. i do have backups of all drives, i just hate to wipe and copy everything back over. not the end of the world just takes days. i see it says "running e2fsck is recommended". is there a tool to repair the filesystem to avoid formatting? i have Parted Magic and UBCD. would those help me at all?

    Quote from chewitt

    I'd suggest updating to an LE13 nightly before doing anything else. If there's a bug/issue related to UPnP the issue is with Kodi not the OS layer (LE) and all Kodi development moved onto K22 more than a year ago. See if anything changes with the update.

    i will update today. i fresh installed 11 after having issues with 12 to see if it fixed anything but i had same issues so i reinstalled 12. then again, i guess the crashing and database issues can be completely separate and i never noticed one because of the other? do you think the database errors could be caused by the corrupted filesystems? and i don't mind leaving upnp disabled. it doesn't affect access on the network in the house anyway. and nothing ever gets plugged into it.

    just an update. i got this on screen today. first time i got to see in real time what just happened. i can see all the ext4 errors you're talking about.

    EXT4 is considered reliable and Ubuntu defaults will have formatted the drives appropriately for normal use like LE, and while Kodi crashes can corrupt files in the filesystem, esp. databases which Kodi is responsible for managing, they should not cause corruption to the filesystem itself. This means filesystem errors in the system log are more likely to be the result of power issues, i.e. sudden power loss, or issues with the physical disk media.

    If you are lucky it's minor corruption and running fsck against unmounted drives will fix things. If you're less lucky the physical drives are okay but the filesystem is properly messed up and needs a total rebuild. If you're properly unlucky there's physical media damage to the drives. These days physical media damage is rare unless some form of physical shock is also involved, but it's not completely impossible. Failures also follow a bell curve: if the drive is going to fail it's more likely to be when the drive is still very new, or years later when it's very old. Failure rates often correlate to the manufacturing batch of the drives too, so the ideal scenario when purchasing a set of disks is to acquire disks from a variety of different batches not all drives from the same batch.

    The only way to find out is trying to fsck, or trying to reformat and rebuild. Beware that if formatting, the default quick format done by most tools may not find physical media issues. That kind of thing is normally only found by trying to 'zero' the drive by writing to all sectors (also rather long and boring).

    Reinstallation does not change the state of the disks but start with an empty database.

    You can do disk setup and maintenance from LE using SSH. Enable SSH in LE settings and use a SSH client to connect.

    To e.g. check your sda file system stop Kodi to avoid any disk access, unmount the fs and perform the fsck:

    Code
    systemctl stop kodi

udevil umount /dev/sda
fsck -f /dev/sda

    After successful check use udevil umount /dev/sda to get access again.

    When done with /dev/sdb and /dev/sdc1 too start kodi with  systemctl restart kodi again.

    To get healt_h information about the disk install System Tools Addon from LE Repo and use e.g. smartctl -a /dev/sda|paste and post the URL.