Posts by chewitt

<blue>System.Exec("(/storage/LampsToggle.sh)&")</blue>

No idea if this ^ works, but in shell scripting (/path/to/command)& spawns a new shell process and backgrounds the task.

/dev/sdb1 on /var/media/Films type fuseblk (rw,nosuid,nodev,relatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=1024)

the only issue I can see is PEBKAC .. because /dev/sdb1 is mounted

[    3.003630] ata3.00: ATA-8: ST2000LM003 HN-M201RAD, 2BE10001, max UDMA/133
...
[    3.096836] scsi 2:0:0:0: Direct-Access     ATA      ST2000LM003 HN-M 0001 PQ: 0 ANSI: 5
[    3.097242] sd 2:0:0:0: Attached scsi generic sg2 type 0
[    3.097550] sd 2:0:0:0: [sdb] 3907029168 512-byte logical blocks: (2.00 TB/1.82 TiB)
[    3.097556] sd 2:0:0:0: [sdb] 4096-byte physical blocks
[    3.097602] sd 2:0:0:0: [sdb] Write Protect is off
[    3.097607] sd 2:0:0:0: [sdb] Mode Sense: 00 3a 00 00
[    3.097720] sd 2:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[    3.159969] sd 2:0:0:0: [sdb] Attached SCSI disk

^ definitely *not* a USB device

run "parted -s /dev/sdb unit s print | paste" then "blkid | paste" and "mount | paste" ..

You look for the very limited number of S8XX install thread in this section of the forums and hope that someone cobbled together a working image with a device tree that at least supports Ethernet (wifi is always a bonus). No need to type in codetext.

So add a DVB card to your setup and watch them legitimately on Belgium public TV .. in most cases VPN's are pain in the rear.

Always stop Kodi and rename or move folders out of the way first. If not you might end up with new (empty) versions of essential Kodi DB files and Kodi will not detect and automatically update/migrate your DB's to the latest schema version on first run.

The backup .tar covers /storage/.kodi (essential) and /storage/.config (essential if you modified anything there, otherwise not) and /storage/.cache (nothing essential, worst case you reconfigure a wireless password). Nothing else is included, so nothing else needs to be renamed/moved out of the way when manually restoring.

I'd boot from an Ubuntu live USB and use gdisk to analyse/repair the GPT tables. See Repairing GPT Disks

I'll also caution that corruption to the partition tables is often an early sign of the drive reaching end-of-life, so once things are repaired make a backup/duplicate of the data - while you still can.

If the drive will only be used with LibreELEC you can format as EXT3 or EXT4 and the filesystem drivers run in the kernel. If you need the drive to be compatible with macOS or Windows you need to use exFAT or NTFS and the filesystem drivers run in userspace which is considerably slower than running in-kernel. You can have compatibility *or* speed, not compatibility *and* speed.

dmesg shows 2x SATA controllers with 2x 6.0 Gb/sec and 1x 1.5Gb/sec channels in use with a 120GB (Sandisk SSD) as /dev/sda and 2.0TB (Seagate) drive as /dev/sdb and a BD player for optical media. The 2TB drive has some GPT partition header problems and Linux tends to err on the side of caution to avoid further damage to the filesystem; there's no log messages to suggest it mounted. Log entries are adjacent to some USB related messages but none of your drives show as connected to the USB bus.

[    3.158910] GPT:Primary header thinks Alt. header is not at the end of the disk.
[    3.158914] GPT:3907029163 != 3907029167
[    3.158916] GPT:Alternate GPT header not at the end of the disk.
[    3.158918] GPT:3907029163 != 3907029167
[    3.158919] GPT: Use GNU Parted to correct GPT errors.

^ fix the problem and the 2TB drive will mount.

That particular version requires DirectX so it cannot be compiled/used under Linux (and we don't have compile tools in the OS anyway).

Make a copy of the file and remove the Cyrillic tags and see what happens. I'm not sure that's the issue, but good to eliminate it.

Can you provide another logfile. Use the "cat /path/to/log | paste" service in LE instead of the Kodi uploader, as their paste service junks pastes rather quickly and it's no longer visible.

Latin or Cyrillic filename?

Over time we've seen an increase in TV screens which are capable of displaying things the HTPC device can't handle, but all Kodi sees is the list of resolutions from EDID on the HDMI connection, so it's become necessary to provide some better controls for how Kodi handles resolutions and refresh rates. Settings > System > Video > Whitelist; contains the whitelist of resolutions and refresh rates you need. If there are no entries Kodi will remain on ~1080p60 which is the default.

Synology.

Please provide "dmesg | paste" from a clean boot so we can see what the kernel logs.

Did you go through the process of whitelisting refresh rates (else Kodi will play everything at 60Hz)? .. and since it's an nVidia card the OOB modelines are not particularly accurate and it's possible to use a manual xorg.conf and tweak them to be more accurate.

The backup file is a standard .tar archive so it's nothing special and if required you can unpack it on the network share (whether Linux NAS or a Window box) and manually move files back over. The restore process is nothing magic, it's basically just stopping Kodi, removing 'new' folders that are auto-created on install, then moving old files/folder back to the right locations and then restarting Kodi again.