kodi.log: kodi.log - Pastebin.com
history.log: Start-Date: 2015-11-24 08:50:58Install: perl-modules:armhf (5.20.2-3+deb8u1 - Pastebin.com
term.log: term.log - Pastebin.com
all I can manage from journalctl: journalctl - Pastebin.com
Don’t think I’ve ever had a seemless update unfortunately 
I had an identical issue to this last update (Oct.) resolved it myself with a new image install.
Was hoping to not have to do that this time.
From what I can see sd card or usb install is somehow now read only mode?
I guessed perhaps sd card corruption after Oct. update, so bought a new class 10 sd card and reimaged. Now has happened again with Nov. update.
Can the USB stick corrupt and affect updates?
(those are my two kids wondering why daddy can’t play them their cartoons lol)
Yes, you have a read only file system due to corruption - if this keeps happening to you you have an underlying hardware issue causing it. Updates failing is a symptom of this underlying problem, not any issue with the updates themselves or the update process.
USB installs are more prone to this happening than SD installs (IMHO) because USB devices can “disconnect” and reconnect spontaneously if the voltage level drops too low during periods of high CPU usage if the power adaptor is not adequate or there is some other power related issue.
This is equivalent to you yanking out the USB stick while the device is running and plugging it quickly back in again - file system corruption is inevitable when this happens. Over time this corruption builds up until the point where the system can’t boot properly and the file system is put into read only mode, once that happens Kodi and most other things will not run properly.
The good news is that this months update introduces an initramfs which does automated fsck during boot - this will help to catch any minor cases of corruption and keep the file system as clean as possible, which may have prevented this particular instance.
The bad news is that relying on fsck to keep repairing the file system when something is causing regular corruption is only a band aid solution, so you really need to get to the bottom of the cause of the corruption.
You could try running:
sudo fsck /
reboot
As a quick fix then rerun updates.
ok ,fsck and reboot got me up and running and re applying updates finished the install off. Bit late on a school night here in Australia to give it a full test run, but looks to be in working order.
Thanks for your help Mandrake.
(might have to look into getting an RPi approved power supply, mine says it’s 2A but who knows)
No problem. Now that you have updated keep your eye out for some text just before the blue OSMC splash screen during boot - it should say something about waiting for device and then very briefly fsck. If you see this you know you have the new kernel that will be doing an automatic fsck on every boot.
If no problems are found it usually completes in under a second but if repairs are needed it may take a lot longer.
