Renamed an external drive to try to resolve some other issues and now when I rescan the movies back into library, it only makes it 3-5 items in each time and crashes.
Also happens with tv shows. 100% reproducible.
I’m also getting Embuary Info Helper errors though no idea why or if it’s related.
Logs uploaded
Https://paste.osmc.tv/vetekayeli
Your internal storage is very close to full and that might be the issue. Likely this is due to a buildup of old cached artwork. Although not the only option, the easiest fix is to just ssh into your box and…
systemctl stop mediacenter
rm -r ~/.kodi/userdata/Thumbnails/
systemctl start mediacenter
1 Like
Thank you, I’ll try that today. Appreciate the quick reply.
Did not help, thanks though. Still fails either to a hang, or sad face.
I would run the following just to make sure that this was what was eating up so much space on the eMMC…
df -h /dev/vero-nand/root
If that looks good then what I would try next is to disable the Embuary Info add-on and see if that makes a difference. I looked over on the Kodi forum and it seems that there is some people who have been having crashing issues with it. You could also try switching the skin to Estuary or the OSMC skin and see if that makes a difference.
Thanks. I’m ok with running the scripts, not so much in deciphering them.
Assume I should have run this from the Home/OSMC dir?
If so:
/home/osmc$ df -h /dev/vero-nand/root
Filesystem Size Used Avail Use% Mounted on
/dev/vero-nand/root 14G 5.1G 8.2G 39% /
Will look at disabling the Embuary addons…if I’m not running the Embuary skin, do i need these? Assumed yes since they integrate with Movie and TVDB?
Will also look at switching from Aeon Silvo skin to Embuary or OSMC
Your internal storage was over 99% full and now it is only at 39% usage. As suspected there was a lot of old stale artwork needlessly taking up space. As for the add-on that would be something that some skins use to provide extra function to their skin. Different skins use, and sometimes automatically install various add-ons to extend what they can do. At this point I’m just trying to narrow down exactly what the issue is and switching to a lighter more stable skin and not running an add-on that might have issue is an attempt to do that.
Roger that, thank you.
I’ve disabled both the embuary helper and embuary info add-ons.
I think a combo of clearing out the cache and these 2 add-ons may have made it better. I made it through scanning the 2 drives with only 2 crashes.
I’ll keep monitoring and then check the kodi page if there are newer versions of those add-ons or if I need them at all.I’ll post back in another day or so if no more issues arise.
I’ll switch to one of those lighter skins if the issues persist.
Appreciate the suggestions and help.
1 Like
Went thru the post and checked the space on /dev/vero-nand/root, disabled embuary info… but it’s still crashing like there is no tomorrow. 
What more can be done?
I would be inclined to try stock settings to see if there is something in your current Kodi configuration causing the issue. Basically, move your current setup, let Kodi generate stock files again, configure your sources, update your library. If it crashes at that point then there is something messed up with your files or hardware most likely. If it works as it should then there is something wrong with your current settings/database/add-ons/skin/etc…
Let’s test with Kodi default settings. Enter the following commands with an SSH connection.
systemctl stop mediacenter
mv ~/.kodi ~/kodi.bak
systemctl start mediacenter
If needed you can restore:
systemctl stop mediacenter
mv ~/.kodi ~/kodi.bk2
mv ~/kodi.bak ~/.kodi
systemctl start mediacenter
If your original setup was restored as expected and you want get rid of the unneeded clean install you can delete that with the following command.
rm -r ~/kodi.bk2
Ok thanks, that’s a considerable amount of work. I’ll have to leave that for the weekend.
Work’s pretty nuts right now, not left with much energy by the end of the day.
It shouldn’t be. You would just ssh and run those first three commands. The only thing you want to change in Kodi once it loads back up is set your sources. For this test you don’t want to make any other changes. Restoring afterword if that is what you want to do is just a matter of running a few more terminal commands.
When I initially responded back to you I didn’t notice that you have bounced in on someone else’s thread. What can be done is to start a new thread providing as much relevant information as you can and include logs that preferably, contain the crash. There can be various reason why Kodi may crash during a library update so it isn’t the best option to make blind guesses.
Apologies for that! 
I will start a new thread.
Update : crashes, freezing and sad faces still happening even just when scrolling through Movies or Show screens. Happens in OSMC skins as well as Estuary.
Will try your rebuild scripts, but as an FYI, with 9 hard drives and 2-3 source folders on each, simply re-setting those up again from scratch is a lot of work and time consuming.
Did the rebuild scripts and done scanning 3 hardrives and 5 media sources, 5 or 6 freeze/crashes over 2 days, assuming I can just stop?
I’m using the Osmc skin.
All my movies only have a few artwork images at most and maybe subtitles, most are just the mkv.
TV shows are the same. Show–Season–episodes.
So are you saying my data is what’s causing this? Since the last update?
I would stop and just go back to your original settings. Outside of it crashing whenever it hits a particular file (like from a bad NFO file or something), it shouldn’t crash at all with a clean setup. I would look into if there is a power supply issue. Are all the drives self powered or running through a powered hub? Is there crashes if you only have a single self powered drive connected and you do a library update on just that? Do you have another power supply compatible with the one that came with the Vero that you can use to test?
I’ll check. Not sure about the power supply, I’d have to check the specs on it and sort through my bins.
Not to pile on, but now with the new build and using OSMC skin, powering down my TV turns off the Vero. sigh never made any changes to that although I believe there were some CEC issues?
Anyways, I’ll come back to that if I can sort this out.
All hard drives have there own power and plugged into a powered USB3 hub.
I’ll try 1 hard drive on the vero tonight.
The latest update should restore CEC behaviour to how it was before the August update.
Sam
1 Like
The latest update has indeed gotten rid of the CEC bad behavior and after several restarts over the last 5 days, I think the crashes may have subsided. I re-scanned the whole library across the 9 drives using the OSMC skin after the rebuild.
Later today I’ll install the Aeon Silvo skin (Aeon MQ8 is too heavy for the Vero if I recall) and continue monitoring the stability. Hopefully we’ve crossed a turning point, thanks guys.
1 Like