2015-12-12, 16:55
Hi TychoCaine,
Firstly, thank you for your detailed post. It was the closest I could find to my own problem, and I very much hope my suggested solution works for you too.
I am using the most recent version of OpenElec on a Raspberry Pi 2 and streaming files from my home-made server via Samba, running on Ubuntu server version. Between the server and the Raspberry Pi 2 is a gigabit switch. I have been getting the same read errors for several weeks, and tried the following solutions, based on ideas from this and other forums:
1. Powering the Raspberry Pi 2 from the USB port on my TV.
2. Changing the lan cable.
3. Using another port on the switch.
4. Switching to OSMC.
5. Switching back to OpenElec after a few weeks, just in case anything had been updated :-)
6. Switching to NFS
7. Setting up buffering using the advancedsettings.xml file in /storage/.kodi/userdata (this extended the successful play time, but did not remove the problem.)
8. Checking the test files using VLC on my old Dell Studio Hybrid with Windows 7, also via Samba from the server (they played correctly)
For completeness, I should probably have tested Kodi on the WIndows 7 machine, but I skipped that, because the following setting seems to have solved the problem and also seems very plausible to me. I found this looking around some old linux forum posts relating to Samba issues. The fix is to add "keep alive=10" or "keepalive=10" to the [global] section of the Samba smb.conf file (on the server side). The "10" is the number of seconds between keep-alive packets sent from the server to check the client is still awake. In the post I found, the author had set it to 5; I guess this is not critical. I found different suggestions as to the correct syntax, so just included both versions in my smb.conf, the top section of which now looks like this:
#======================= Global Settings =======================
[global]
keep alive=10
keepalive=10
...
...
...
I then ran testparm to check the file, and restarted Samba.
My two test files, a 2GB .VOB file and a 40GB 3D .mkv file both played perfectly all the way through, which has never happened for any file up to now.
As I say, I very much hope this solves your problem too, and would appreciate any feedback.
Kind regards,
RD
Firstly, thank you for your detailed post. It was the closest I could find to my own problem, and I very much hope my suggested solution works for you too.
I am using the most recent version of OpenElec on a Raspberry Pi 2 and streaming files from my home-made server via Samba, running on Ubuntu server version. Between the server and the Raspberry Pi 2 is a gigabit switch. I have been getting the same read errors for several weeks, and tried the following solutions, based on ideas from this and other forums:
1. Powering the Raspberry Pi 2 from the USB port on my TV.
2. Changing the lan cable.
3. Using another port on the switch.
4. Switching to OSMC.
5. Switching back to OpenElec after a few weeks, just in case anything had been updated :-)
6. Switching to NFS
7. Setting up buffering using the advancedsettings.xml file in /storage/.kodi/userdata (this extended the successful play time, but did not remove the problem.)
8. Checking the test files using VLC on my old Dell Studio Hybrid with Windows 7, also via Samba from the server (they played correctly)
For completeness, I should probably have tested Kodi on the WIndows 7 machine, but I skipped that, because the following setting seems to have solved the problem and also seems very plausible to me. I found this looking around some old linux forum posts relating to Samba issues. The fix is to add "keep alive=10" or "keepalive=10" to the [global] section of the Samba smb.conf file (on the server side). The "10" is the number of seconds between keep-alive packets sent from the server to check the client is still awake. In the post I found, the author had set it to 5; I guess this is not critical. I found different suggestions as to the correct syntax, so just included both versions in my smb.conf, the top section of which now looks like this:
#======================= Global Settings =======================
[global]
keep alive=10
keepalive=10
...
...
...
I then ran testparm to check the file, and restarted Samba.
My two test files, a 2GB .VOB file and a 40GB 3D .mkv file both played perfectly all the way through, which has never happened for any file up to now.
As I say, I very much hope this solves your problem too, and would appreciate any feedback.
Kind regards,
RD
