Posts by LybsterKodi

    Is there some way that you can warn people that installing an upgrade from the nightlies will result in an addon being removed. I have very few addons - two skins, one visualisation and TVHEadend (version 4.2). As part of the upgrade process I was informed that TVHeadend had to be removed. I've installed 4.3 (Alpha) and that seems to work BUT I now have a lot of messing about to reconfigure everything.

    I think this post belongs here rather than in the PVR group. Using TVHeadend (4.2) I recorded an episode of Doc Martin with stream profile of "pass". Playing it back lip sync was out and it was "stuttering" sort of freeze of a 10th of a second to give jerky movements.

    I copied the .ts file to a memory stick, plugged it into one of the TVs USB ports and playback was perfect. I've recorded 3 other programs to test (different times, different channels) with the same result.

    Recordings are being saved onto the SSD that Kodi runs from so to eliminate that I copied the .ts file onto the 6TB HDD I store my films on. Still stuttering on playback.

    I'm guessing the issue is caused by ffmpeg so I'm going to try changing the stream profile to "matroska" and see if that helps. I'll report on that later today.

    I don't wish to be contentious but Windows & RPi3 LE 9.2.8 (I think) have worked fine since 2018. Switching to RPi4 & LE10 - not handling mp4 file correctly, moved to LE11 CEC problems & SAMBA problems. Or to put it another way I don't think its Windows fault.

    I have FileZilla (similar to WinSCP I assume) but, unfortunately, I didn't think to try it. But a simple disk copy should be no problem especially with oodles of space left.

    The 6TB disk is attached to the RPi4 by USB cable into one of the USB3 ports, the SSD holding LibreElec and Kodi is in the other. The filesystem is bog standard NTFS - again working perfectly since 2018 on the RPi3. The disk is the one that was corrupted several times but just worked happily when connected to the RPi3 for the last few weeks.

    I have no idea how to investigate. If you have any suggestions I can follow I'm interested.

    I'm having my latest attempt to switch to the RPi4. It seems to have gone all right (to early to really tell yet) apart from one weird phenomena. In music videos I have a (downloaded from YT) small clip from Medieval Babes. The title is Gaudete. When I tried to play it I couldn't and investigating I found the mp4 was missing (the jpg & nfo are there). When and why the mp4 isn't there I'm not sure - it is on my backup disk which was refreshed this morning whilst I was still on the RPi3 so I suspect importing the music videos did it (whatever it is).

    I thought - OK I'll copy it back - which is where I get the weird message that the file is to large - we're talking about a roughly 5MB file on a 6TB disk with a couple of TB spare!

    Even weirder if I change the name from Gaudete.mp4 to xxGaudete.mp4 it copies across just fine.

    I don't know if any other files are missing yet - I'm off to write a small program to check everything out.

    Anybody any ideas?

    I've just downloaded the latest nightly, burnt a clean SSD to try things out and so far I'm impressed. I did have a slightly weird thing happen. Normally I've been plugging the boot SSD into the bottom USB3 port. This time I plugged it into the top one and a 600GB spinner (I'll swop to my 6TB after I've tested for a while) into the bottom. I was asked to choose an OS and the RPi4 was going on-line to download my selection.

    Is there a specific order that the Pi looks for bootable media in and does it just stop looking as soon as it finds a drive connected OS installed or not? On the other hand is it just something weird I must have done?

    heitbaum

    Thanks. I guess all I can do is try things again and hope something works differently this time.

    One thing I did notice is that my synchronisation program (written in Delphi and using standard windows API calls (ShFileOperation) was running at very slow speeds on copying a file from the 6TB HDD to backup eg over 2 minutes for a .nfo file. With the RPi3 the same operation takes a few seconds.

    heitbaum

    Thanks for that.

    Before I install the latest nightly I do have one more question. My new 6TB powered Seagate Hub (2 USB ports) was corrupted 3 time whilst hooked onto the RPi4 - last time under LibreELEC-RPi4.arm-11.0-nightly-20220820-b2dced8. The same HDD is happy on my old RPi3 setup - absolutely no problems. The only thing I know would be writing to the HDD is samba.

    Long preamble - my question is what are the chances that it was the incomplete implementation of samba that caused the corruption? I do know that I forgot on several occasions to access via \\server\folder and received the can't find it message.

    petediscrete

    Thanks for the suggestion. I'm skilled with Windows not with Linux (4 Windows PCs to 1 Linux one) so I would have no idea what I'd be looking for apart from the disk becoming corrupt again and spending another 12 hours copying all the files back. The 6TB HDD was connected to a USB3 port on the RPi4 (and is currently plugged into a RPi3 USB2 port), only for population was if connected to the Windows PC.

    If you can expand on your suggestion I'm willing to give it a go.

    The story so far for the 6TB HDD:

    1. copy 4TB of files of backup

    2. run Windows app (homebrew written in Delphi) to modify 6TB HDD file names and .nfo to reflect name changes

    3. set up the RPi3s (LE 9.2.8, Kodi 18.9), removed sources and cleaned database

    4. plugged 6TB HDD in

    5. set up new sources and loaded database

    6. no last played information

    7. Exported database just in case nfo format was different

    8. was told I'd forgotten about advanced settings.xml

    9. use Windows via SAMBA to a) delete nfo files (c 7200 of them)

    10. use Windwos via SAMBA to copy nfos from backup to 6TB HDD

    11. removed sources, cleared databases, reset sources loaded database

    12. everything fine

    That pretty much confirms to me that the HDD is OK. I'm wondering if the incomplete implementation of SAMBA on the RPi4 could be responsible for the disk corruption. I can see no reason why Kodi should be writing to the sources unless I export the database and any file manipulation I do is via SAMBA so it will be writing to the disk.

    Any thoughts?

    I tried to connect it to the RPi4 again - not recognised. This time when I connected to my Windows PC it asked to scan and fix - FUBAR. I have for now given up on the RPi4. I do not know where the problem is but I suspect LibreElec. It may be the Pi but lack ability to test it. I'm going to swop the new 6TB HDD onto the old RPi3 system and see if it gives problems. If it does I'll apologise to LibreElec.

    Any suggestions on how to test the Pi welcome.

    System is setup on 128GB SSD.

    Chkdsk and other disk testing utilities run on Windows PC and no problems identified.

    The Seagate is set to spin down after 15 minutes same as the other Seagate 6TB HDD I had on the RPi3 setup which has run since 2018 with no problems.

    Configuration:

    LibreElec 20/08/2022 nightly, Amber skin loaded but not used, Shadertoy visualisation loaded, TVheadend server & client installed and running

    RPi4B 4GB, 128GB SSD (for boot etc), 6TB Seagate Backup Hub NTFS formatted (films etc) with Haupage tuner & wifi keyboard dongle plugged in, ethernet,

    I have posted about HDD corruption before but now I've lost a complete folder. I have three top level folders on the 6TB HDD - Films, MVids, Records. In Films I have folders A to Z with sub folders if there's a series (eg 'Allo 'Allo). This morning checking something I found I've lost the entire contents of Films/A. The folder is still there but there's nothing in it. Fortunately I do have backup but its more than a little disturbing.

    The RPi4 has been running since 20/8 but has been rebooted via the menu on occasions. I have pulled the HDD from the Pi and checked it out on Windows since I have better diagnostic tools there and can find nothing wrong apart from the fact that stuff has gone missing.

    Does anyone have a suggestion (or an explanation) that does not involve reformatting to Ext4 since that is not a viable option.

    Joe

    "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."

    WOW! To my Windows centric eyes that seems like a major design flaw.

    Hias

    "Or just use the "remove media" option from the context menu in the video files view."

    I knew it was there but assumed that I'd need to recreate the source and re-scan to the database. I've obviously misinterpreted as I did with EXPORT for videos.