24 hours ago, I changed the location of my Kolibri Channels to an external SSD drive (SanDisk Extreme, NTFS formatted) and imported a number of large Channels (e.g. Khan Academy) into my Kolibri instance. Now, when attempting to view certain types of content (primarily video) in a Kolibri channel, I receive the following error:
“The media could not be loaded, either because the server or network failed or because the format is not supported”
In addition, the “preview images” associated with many of the “tiles” within the channel are not displayed.
There are certain channels which load and display content as expected (albeit smaller channels with non-video content), which gives me some confidence that the issue is not simply related to a failure during the process of changing the location of the Content Library.
In addition, I know that it is not an issue with the content type not being supported in my browser, as, prior to changing the location of the Content Library (and intermittently even after changing the location) I was able to view the video content successfully.
In various sections of the documentation, I saw reference to the fact that moving the location of the Content and incorporating large Channels into Kolibri can be a time consuming process.
Our team is now 72 hours away from departing for our project location, and I am at a point where I don’t know how to determine which of the following is true:
Everything is working as it should, it just requires more time to complete (however, I’ve been monitoring the Kolibri process in Task Manager on the Server device, and it is consistently at 2%)
Have we simply been too ambitious with the number and size of channels that we would like to deploy (Khan Academy, MIT Blossoms, and Career Girls being the 3 largest) and we need to eliminate content in order to address this issue?
Is there in fact a problem of some kind with my configuration that I failed to notice prior to now that is causing this behavior?
Did I simply make a poor choice with respect to the SSD we selected, and we should have gone with a different storage solution which would alleviate this problem?
Any assistance is greatly appreciated.
- Kolibri 0.14.7
- Raspbian GNU/Linux 10 (buster) on Raspberry Pi 400 (from Raspberry Pi Imager)
- Chromium Version 92.0.4515.98 (Official Build) Built on Raspbian , running on Raspbian 10 (32-bit)