Posts by mglae

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:

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.

There are two major issues in the log.

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.

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.

Good catch. Seem to be the issue (including NFSv4 not affected). Are you able to build an image with the patches?

With your remount finding and the mount-storage.sh feature here you can try to create this file in your boot= mount point to work around the issue:

# Warning: if using "overlay" the target directory is not created

# Use default command to mount storage
mount_part "$disk" "/storage" "rw,noatime"
# force rw to work around kernel issue, see https://lore.kernel.org/lkml/[email protected]/T/
mount -o remount,rw /storage

The other thread is about NFSv4. vers=3 is still the default for kernel mounts.

Quote from DavidGA

and then did mount -o remount,rw /storage, which worked fine

Boot code in initramfs is using busybox mount while LE user mode is having util-linux mount + nfs-utils mount.nfs. There may be differences in behavior, but the tools are identical in the bisected versions.

Remain the kernel changes. For NFS (only) they are;

> git --no-pager log --oneline v6.6.63...v6.6.66 -- fs/*nfs*
37dfc81266d3 nfsd: fix nfs4_openowner leak when concurrent nfsd4_open occur
1cecfdbc6bfc nfsd: make sure exp active before svc_export_show
065902117a5b nfs: ignore SB_RDONLY when mounting nfs
229a30ed42bb NFSv4.0: Fix a use-after-free problem in the asynchronous open()
dde654cad08f NFSD: Prevent a potential integer overflow
1dfc79bfc544 NFSD: Fix nfsd4_shutdown_copy()
bd8524148dd8 nfsd: release svc_expkey/svc_export with rcu_work
028417543535 NFSD: Cap the number of bytes copied by nfs4_reset_recoverydir()
eb51733ae5fc NFSD: Prevent NULL dereference in nfsd4_process_cb_update()

But I do see nothing obvious.

Did you read this thread?

Quote from osflake

Code

[...]
HDMI:EDID monitor name is SyncMaster
[...]

SyncMaster is a Samsung brand. You very likely do use a custom EDID on RPI OS.n Something similar may be required for LE.

Use THREADCOUNT=X CONCURRENCY_MAKE_LEVEL=Y to reduce (memory) resources while building.

The PR was never back ported to LE12 ...

Timzone is usually working but there is already a similar LE13 report of not writing the file. It is odd that the C++ code of LE12 cause the same issue as Python of LE13 but I cannot reproduce the issue.

PeteAklNZ Easiest work around is echo TIMEZONE=Pacific/Auckland >/storage/.cache/timezone and reboot.

The undefined symbol: _ZTI7SidTune unfortunately is a LE linking error.

Pushed a PR

The bash extension "<<<" is not available in busybox ash - even with enabled bash extensions. Use

while read line; do
 echo $line
done <<EOF
$var
EOF

Driver for pci 0000:02:00.0: [14c3:0608] type 00 class 0x028000 is only enabled in LE13.

LE13 Generic-legacy does not work anymore because support for kernel "radeon" driver was removed.

But you can try to switch to "amdgpu" driver for your Kabini GPU on both Generic and Generic-legacy, see AMD Kabini - no hardware acceleration?

On Generic (GBM) you have to use Settings/System/Input to configure Kodi's HW keyboard layout.

That is different to Generic-legacy (X11) where the system wide setting of LE Settings Addon is used.

Then post the link to a log so that we at least know the USB ID and the see the recation of the system.

Start with linuxtv.org

Quote from MatteN

On LE13 Generic nightlies in Timezones Europe/Stockholm is missing, its present in Pi images.

Unlikely, for the selection they both do use identical /usr/share/zoneinfo/tzdata.zi