One minor problem - doesn't seem to cause any harm but now when I turn the Pi on I get
remote communications server failed to start
I've made sure wait for network is enabled and increased it to 30 seconds. Any thoughts / suggestions?
One minor problem - doesn't seem to cause any harm but now when I turn the Pi on I get
remote communications server failed to start
I've made sure wait for network is enabled and increased it to 30 seconds. Any thoughts / suggestions?
Thanks - I shall experiment later on today.
Its later on, and I've tested and its looking good. Using the cables supplied with the BT powerline adaptor I tried pinging - about 50% of packets lost. Typed in the magic command "ethtool -s eth0 speed 100 duplex full autoneg off" and no packets lost, plugged the TV in to the adaptor ping that and the RPi4 and ..... no packets lost.
Now to add to autostart.sh and figure out how to remind myself to do it again if I have to reinstall.
Is it possible to slow down the ethernet port on the RPi4?
I know it sounds a bit daft but I'm using powerline ethernet and my laptops / desktops have a 100MB port, most of my powerline adaptors are 100MB. My current setup with 2 RPi3s has a 100MB powerline adaptor with a 5 port 10/100 minihub. The RPi3s are about to be replaced with an RPi4 and I want to replace the 100MB adaptor & minihub with a 2 port 1GB adaptor. 1 port for the Pi and 1 port for the TV.
With both TV & RPi4 plugged in the Pi (or possibly adaptor, router or mains wiring) doesn't play well at 1GB, lots of lost packets. So if I can slow the Pi down to the same speed as everything else the network may be good.
I have a 6TB HDD plugged into the Pi so I'm happy with 100MB as network speed for the occasions I need to transfer files.
For some unknown reason I decided to try altering the resolution & refresh rate to 1920x1080p @ 60Hz andtrying my test of Homes Under The Hammer with its teleporting man it seems to have worked. Ineed to dismantle the RPi3 setup again and replace with the RPi4 and do some more testing but its looking good.
Thanks for the post, if nothing else it helps to know that others have had problems.:)
Id have a "solution" by just leaving my current setup alone(and making very sure it doesn't update anything).
I'm posting here rather than the PVR group because I think the problem is with Kodi playback not TVHeadend. Since I don't know just where the split occurs I'm not sure if it should be here or the Kodi forum. On with the sad story.
Point 1: My dual RPi3 setup with one RPi3 used for TVHeadend server and the other for the client and playing films works solidly and has for several years. The move to RPi4 was to consolidate onto one box and remove some of the rats nest behind the TV.
Setup: RPi4 4GB with latest updates, LibreELEC-RPi4.arm-11.0-nightly-20221121, TVHeadend 4.3 server, TVHeadend client
Problem: "juddering", maybe skipping frames occasionally (my interpretation of the teleporting)
I've just tried TVHeadend again on the RPi4 and whilst it seems a bit better the problem of juddering is still there. At its worst on one of the things I tried to record (homes under the hammer) a person walking towards a house "teleported" about 5 feet. Very difficult to describe properly but on Laura Kuenssberg one of the people on a panel looked as though their hands weren't really part of their body almost the effect you get by waving your fingers in front of your eyes.
The effect is more pronounced on the main TV (Panasonic TX40CX680B) than on the 24" second hand one (Technika something or other) I bought for testing.
I've tried using matroska rather than pass for recording and it made a fractional difference. I also tried setting the URL from 127.0.0.1 to the router URL for th3 Pi - again a fractional difference.
Way back I had someone suggest altering the deinterlacing but I can't find anywhere to do that, either on Kodi/TVHeadend or my TV.
Thinking it might be the recording rather than playback I copied the clips over to a memory stick.plugged it into the TV - plays smooth as silk, the man walked rather than teleporting. I plugged the same memory stick into the RPi4 and played the file directly from Videos| Files and had the man teleporting again.
Its now been over a year and a couple of hundred quid since I started trying to switch over to a single RPi4 rather than two RPI3s. I'm happy to try almost anything suggested (please give simple instructions) before I resort to introducing the RPi4 to a nice large hammer.
EDIT
Just had another thought - not a solution but it may help to identify one - I handbraked the Homes Under The Hammer clip and played that on the RPi4 - its fine as an mp4 but not as recorded as mkv.
As you've spotted I don't think the problem I had and your's are the same. My first suggestion would be to try the latest nightly and see if things work with that. There have been a lot of changes (including my favourite of samba now works).
As Da Flex says it could be a bug in netinstall or it could be the port - I have one of the USB3 ports on my Windows PC that will not read anything over 1TB - the other two are fine. So next suggestion would be to try all four ports.
I'm using a 128GB SSD to boot the Pi and have a 6TB HDD for storage but I'm going to switch back to a 128GB MicroSD for LibreElec - seems to be neater, lower power needs and strangely enough faster than SSD or HDD. So final suggestion (if Da Flex's suggestion doesn't work) would be to use the 2TB for storage but put LibreElec on a MIcroSD.
Just tested with the 6TB disk and write caching is still not supported with exFAT but the good news is that the disk isn't corrupted. I can only think its to do with the journaling in NTFS / Ext4.
BUT, since I now have something that works, I don't care - Yippee
I agree with pretty much all you posted. Most of the time with the Pi3 I've transferred videos and just left things running. Generally I don't just turn things off, I've done it with the Pi4 partly to try and find out what's happening and what's safe.
I do have a 120GB SSD which is used for boot and recording. I found with the Pi3 that it was best to write to the boot device. Most of the stuff recorded from TV never makes it to the HDD, mainly because its rubbish - difficult to pick only the good films from the descriptions
I'd love an SSD for main storage as well, its only the price that stops me.
Intriguing. The 600GB exFAT drive has write-caching enabled, the 6TB NTFS drive has
/dev/sda1:
write-caching = not supported
Checked on the Pi3 and the 6TB drive on that also has write-caching = not supported
Any thoughts?
Yeah, that will do it. Not surprised to be honest.
...
the other thing to consider is disk-side write caching
Neither would I be if stuff was still being written to disk but for one test I left it overnight. I thought about disk side caching, especially since you can hear it "chuntering" which is why I did the leave it overnight thing.
Thanks for that, especially hdparm I'll be checking both NTFS & ExFAT formatted disks. You never know if I keep learning Linux at this rate I'll be an expert by the year 3000!
I'll just be happy if I've found a solution.
It could be hardware, it could be how your shutting down
Its definitely how I'm shutting down - just flip the power switch. Having said that I do the same with the Pi3s and no problem. I pull USB drives out of the port on Windows (you know the OS everyone loves to slag <G>) without safely ejecting and no problem . In addition I live in the Scottish Highlands where power cuts or voltage drops are not unknown.
As far as not having the problem when taking a usb drive on holiday - how often have you written to the usb drive whilst its connected to the Pi4? If I leave it connected and do not change anything it works perfectly.
However, I do have some good news
Did you tried another format type or only NTFS and Ext4?
ExFAT looks like the answer, at least with my experiments with a 600GB USB drive.
I didn't try it because all my USB drives have been formatted to NTFS and all of the research I did said ExFAT is less stable. Stage 2 testing will commence after formatting the 6TB HDD.
another way: keep /storage on the SD, mount the hdd normal (e.g. as /var/media/storage2), delete the data directories (tvshows, videos, etc.) and make softlinks to the directories on your hdd under /storage
I'm not sure what this is meant to achieve.
I assume you are seeing these messages at boot time only.
Yup - as to Linux capability - very limited. Ignoring the PIs I have one Linux Mint PC ultralight notebook used whilst watching films to look things up. Never explored further than getting WINE running for a couple of homebrew apps.
Content of /storage/.kodi/userdata/advancedsettings.xml should be:
It was - I just quoted the cache bit.
<buffermode>3</buffermode>
is no buffering so removing it should have no effect but I'll try next week.
I'm using an ExFAT partition for data what I want to be accessible in the both OS. I you have some spare small disks, maybe is worth to try it.
I've only tried NTFS and Ext4 so far. ExFAT is supposed to be less robust than NTFS but I'll have a go. The thing that's really baffling me is why I get this on the RPi4 setup but not the RPi3.
Whilst investigating my HDD corruption I have noticed that, occasionally, that a number of messages are displayed on the monitor. These wizz by a bit to quickly for me to read
Is there a setting I can use to capture them? I hope there's something in the Event Log that will permit me to record these but does not involve massive amounts for me to wade through and I'm hoping someone can point me to the right settings rather than just have to try all of them.
I've tried various SD card formatting tools on my windows PC
I've had success with MiniTool Partition Wizard (https://www.partitionwizard.com/) and DiskGenius (https://www.diskgenius.com/). Free editions of both.
What's the result of <memorysize>0</memorysize> on advancedsettings.xml? That will write all the cache onto disk.
It was worth a try so I tried it
<cache>
<memorysize>0</memorysize>
<buffermode>3</buffermode>
</cache>
but it has no effect, and reading the info about it I wouldn't expect it to because this is for streams not file operations.
I've now tried with a couple of different disks, even formatted the smaller (600GB) one to Ext4 but still the same problem. Also tried plugging into the USB 2 port rather than the USB 3 - no difference.
Looks like I'll be sticking with the RPi3 setup.