Hi @Bryan_Fisher
Firstly just a caution: In the “After Step 6 Output” (in the Google Doc that you shared privately), I can see that you are running with an empty database. You need to locate the original backup and ensure that you keep it safe for now.
Having now tried Kolibri with a blank DB confirms that the I/O error isn’t due to anything particular with your original DB. I observe that Kolibri installs correctly and starts, and that you have this I/O errors afterwards when using more than one tablet.
An additional test would be to try to load Kolibri with a completely fresh data directory:
# Stop kolibri
kolibri stop
# (ensure that you don't have any wild processes left)
ps aux | grep kolibri
# Move current ~/.kolibri to a safe location
mv ~/.kolibri ~/.kolibri_bak
# Start kolibri, notice that this is now a blank installation
kolibri start --foreground
# (Now test if the I/O error occurs)
# To restore:
# Stop kolibri
kolibri stop
# Remove the test home dir
rm -rf ~/.kolibri
# Move the backup back in place
mv ~/.kolibri_bak ~/.kolibri
If these problems persist, turn your attention to the I/O error again. Is your file system particular? Is it slow? Broken? Do you see other I/O errors, for instance in your syslog?
Here are some basic tests:
# Look at the sys log to see if you have other I/O errors. Press Q to quit.
less /varl/log/syslog
# Prints information about your partitions
sudo lsblk -f
# Benchmarks write speed
dd if=/dev/zero of=/tmp/output conv=fdatasync bs=384k count=1k; rm -f /tmp/output
# Checks your root partition /dev/sda2 for errors
fsck /dev/sda2
