2015-10-10, 04:37
Hi there,
Just wondering if someone can shed any light on this error message and exactly what it means and how to troubleshoot it?
(I am getting it on an OpenElec install but I think it's a Kodi error message - can anyone confirm that?)
Context:
- My setup consists of a Synology NAS using NFS shares that are accessed by a chromebox running openelec, along with a windows PC, android tablet and ipad all running the latest official Kodi Builds with standard skins and the base addons.
- I've been using this setup with no problems for about a year. The last update to the synology firmware/DSM was more than a month ago and there have been no changes to my router, cabling setup or file sharing settings on any of my devices.
- Last night all of a sudden the chromebox (openelec) drops whatever video it's playing after almost exactly 8 minutes and throws the above error message a bunch of times before dropping back to the GUI.
- Until the next reboot it can't access anything on that specific share but it can access things on other shares (where it then throws the same error after another 8 minutes of video playing).
- When it throws the error, I can still access and control kodi on the chromebox itself using Yatse, putty or windows explorer (via the SMB share)... it literally just drops the NFS share it was accessing and nothing else.
Troubleshooting:
1. I have confirmed that the other devices (win 7, ipad, android tablet) can all still access and play files from the Synology shares with no issues.
2. I tried the same files from ipad, windows & android (more than 20 different files tested) - all fine so not an issue with a specific file or folder.
3. I don't know what I was trying to rule out but I also queued up a 30minute youtube video on the chromebox... which played all the way through so I guess not a networking or rendering/hardware error?
4. I ruled out cabling issues by replacing the relevant patch leads and also by swapping the chromebox to wireless instead of wired... same errors.
5. At that point I assumed it was an issue with the chromebox and I swapped from NFS to SMB... it still drops the video, just with a different error message "read - error (-1, 22, invalid argument)"
6. I setup an SMB share on my windows 7 machine and accessed that from the chromebox - videos played all the way through without problems.
7. I completely purged my Kodi USERDATA files to make sure it wasn't anything in there that had corrupted... I then setup an entirely new NFS share on the synology with a single video in it... same issue.
Conclusion:
I am totally lost and don't know how to resolve the issue... I know the Synology must be partially responsible (given 5 & 6 above) but those same shares work fine from 3 other different devices so all I can think of is that something in the chromebox has gone corrupt and is now clashing with something in the synology. If that's the case I don't know how it started or how to resolve it. If anyone can offer any advice, suggestions or guidance I would be extremely grateful.
Edit:
I have added a debug log to post #2
Cheers,
TC
Just wondering if someone can shed any light on this error message and exactly what it means and how to troubleshoot it?
(I am getting it on an OpenElec install but I think it's a Kodi error message - can anyone confirm that?)
Context:
- My setup consists of a Synology NAS using NFS shares that are accessed by a chromebox running openelec, along with a windows PC, android tablet and ipad all running the latest official Kodi Builds with standard skins and the base addons.
- I've been using this setup with no problems for about a year. The last update to the synology firmware/DSM was more than a month ago and there have been no changes to my router, cabling setup or file sharing settings on any of my devices.
- Last night all of a sudden the chromebox (openelec) drops whatever video it's playing after almost exactly 8 minutes and throws the above error message a bunch of times before dropping back to the GUI.
- Until the next reboot it can't access anything on that specific share but it can access things on other shares (where it then throws the same error after another 8 minutes of video playing).
- When it throws the error, I can still access and control kodi on the chromebox itself using Yatse, putty or windows explorer (via the SMB share)... it literally just drops the NFS share it was accessing and nothing else.
Troubleshooting:
1. I have confirmed that the other devices (win 7, ipad, android tablet) can all still access and play files from the Synology shares with no issues.
2. I tried the same files from ipad, windows & android (more than 20 different files tested) - all fine so not an issue with a specific file or folder.
3. I don't know what I was trying to rule out but I also queued up a 30minute youtube video on the chromebox... which played all the way through so I guess not a networking or rendering/hardware error?
4. I ruled out cabling issues by replacing the relevant patch leads and also by swapping the chromebox to wireless instead of wired... same errors.
5. At that point I assumed it was an issue with the chromebox and I swapped from NFS to SMB... it still drops the video, just with a different error message "read - error (-1, 22, invalid argument)"
6. I setup an SMB share on my windows 7 machine and accessed that from the chromebox - videos played all the way through without problems.
7. I completely purged my Kodi USERDATA files to make sure it wasn't anything in there that had corrupted... I then setup an entirely new NFS share on the synology with a single video in it... same issue.
Conclusion:
I am totally lost and don't know how to resolve the issue... I know the Synology must be partially responsible (given 5 & 6 above) but those same shares work fine from 3 other different devices so all I can think of is that something in the chromebox has gone corrupt and is now clashing with something in the synology. If that's the case I don't know how it started or how to resolve it. If anyone can offer any advice, suggestions or guidance I would be extremely grateful.
Edit:
I have added a debug log to post #2
Cheers,
TC