Vero 4k Freezing when cleaning video library

[sam_nazarko]

@philsnewhouse

Shouldn’t this be abundantly clear somewhere, I’ve not seen anything about this issue?

The Vero 4K + implements the USB 2.0 specification. This means we can only output 500ma per port. This is touch and go for 2.5" disks.

We do try and make it as clear as possible that you really need a dedicated power supply or a powered hub if you plan to attach several peripherals or a hard disk.

Sam

[philsnewhouse]

Thanks Darwin,

I’ve reconnected the drive with a powered usb hub and copied the Kodi/user folder to PC. So fairly safe if it all goes wrong.

The disk repair option on Sentinel should preserve my good data, but Its unable to tell me what files are on the bad sectors as the drive is unmounted.

I’m assuming it would be ok to mount it, try and find the corrupt file, and then unmount it again.

Or will my Vero still thinks it’s the same drive if its mounted or not?

Just want to make sure…

Phil

[darwindesign]

I don’t think mounting the drive on another computer should have any effect on how it shows up in OSMC. I believe the auto mount in OSMC uses the drive name for the mount folder, and if the drive is not named then it uses a hardware id. Neither should get changed by simply mounting the drive on any system. Even if it was, fixing that issue should not be all that difficult.

[philsnewhouse]

@darwindesign

When it freezes if you can still establish a connection with SSH then you can type in…

grab-logs -A

…which should gather the logs and then return a url that you can post in this thread. This will hopefully show what is going on with the system prior to the freeze.

Managed to repair my HDD Successfully, but still the same problem.

New logs taken as requested: https://paste.osmc.tv/lumutokoba

Phil

[bmillham]

Your log has several errors like this:

2020-08-17 19:05:28.124 T:4064882688   ERROR: CCurlFile::Exists - Failed: Timeout was reached(28) for https://192-168-0-10.be1dc883f7814d5889c2d7f6afc1ca43.plex.direct:32400/video/:/transcode/universal/start.mkv

It looks like there is a problem with your plex configuration.

[darwindesign]

It did finish…

CleanDatabase: Cleaning videodatabase done. Operation took 22:07

It just took a long time because you have issues with your Plex setup. There is a bunch of this type of stuff…

2020-08-15 17:04:22.099 T:4064882688 ERROR: CCurlFile::Exists - Failed: Timeout was reached(28) for https://192-168-0-10.be1dc883f7814d5889c2d7f6afc1ca43.plex.direct:32400/library/parts/7734/1585175024/file.mkv

The cleaning time is related to how many entries it can’t access as it has to wait for the access attempt to timeout which dramatically slows things down.

[philsnewhouse]

Thanks for both replies.

Pc mouse decided to pack up this evening as well this evening, Replying on my phone…

I’ve not used or opened Plex for months, server is not running on pc either, but will remove programme from vero. And check again.

Also lots of stuff on the log about the weather app! How do I totally disable it, didn’t like it much, thought I’d disabled program already?

Or would I be better off just reloading OSMC and starting from fresh?

Regards Phil

[bmillham]

You could remove the current database and build a new one. I did notice the weather app errors, but I didn’t look that close at them.

It may just be easier to start fresh with a new OSMC installation.

[darwindesign]

I assume the database entries were from you running PKC at some point and that add-on does some tweaks to Kodi that may not all get reversed by just uninstalling the add-on. I’m pretty sure the dev behind it recommends a clean install if you decide to stop using it.

[kparkin0]

I’ve had this problem for years. The only suggestion has been to recreate the database, fed up with doing that and just remove as I go now. I’m connected to a Synology diskstation. It just started happening a few years ago, before that it worked perfectly.

[philsnewhouse]

Thanks for everyone’s help, have reinstalled OSMC and reloaded my user data, all seems to be working fine.

Sorry it took so long, had blue screen of death on my pc, so my spare time was taken up with sorting that out first.

Phil

[tessus]

@darwindesign

The cleaning time is related to how many entries it can’t access as it has to wait for the access attempt to timeout which dramatically slows things down.

However, after the cleanup those entries should be gone and you never would have to experience that slowness again, right?. Otherwise why would there be a cleanup, if it doesn’t cleanup files that are not reachable/accessible?

Also, maybe there’s a way to tweak the timeout to a lower value, let’s say 2s.

I changed my network at home (IP addresses) which shouldn’t matter since I access my media files via a share that is mounted to a local filesystem. (Thus Kodi only sees the /mnt/bla and not any ip addresses or hostnames.)
Yet, I had to wait 37h for the cleanup to finish. This is ridiculous and no, I will no delete my database, because it took me a while to fix all the scraping errors.

[darwindesign]

@tessus

after the cleanup those entries should be gone and you never would have to experience that slowness again, right?

It removes library entries for media that no longer exists. It does not seem to remove old source paths from the db that no longer exist. To get rid of those you have to edit the db manually I think (that is how I have gotten rid of them in the past).

@tessus

maybe there’s a way to tweak the timeout to a lower value, let’s say 2s.

Not that i’m aware of.

@tessus

I had to wait 37h for the cleanup to finish. This is ridiculous

That is insane. Clean library on my video db takes seconds. I would think if you turn on debug logging before a clean and take a look at Kodi’s log you should see what is going on.

[tessus]

@darwindesign

It removes library entries for media that no longer exists. It does not seem to remove old source paths from the db that no longer exist. To get rid of those you have to edit the db manually I think (that is how I have gotten rid of them in the past).

The database is not entirely 3NF, so a guide for doing so would be great.

@darwindesign

I would think if you turn on debug logging before a clean and take a look at Kodi’s log you should see what is going on.

I will certainly do that when I run into this problem again. I haven’t cleaned the db since then, so I don’t know, if the problem still exists.

The part I don’t understand is why there would be any ip addresses in the database at all. As mentioned before, I use a local mount point (since I mount via fstab and not Kodi).

[darwindesign]

@tessus

so a guide for doing so would be great

My knowledge of db’s is pretty minimal. I’ve just used HeidiSQL to connect to the db, searched “path” for the old path, and then delete any rows with outdated paths.

I think there is actually also a way to do it with the Texture Cache Maintenance utility python script but i’ve not personally tried it for this task as it seemed like a more effort than the aforementioned method.

[randallspicher]

The issue is that the database contains things like stream urls that you visited via plugins, or tvheadend recordings, etc (storing the watched status) that it wants to check, and many of those links will be dead, resulting in a lot of attempts to load dead links that time out. Kodi then decides the timeouts are a temporary connection problem, and leaves the dead links in the database, so it ends up trying to connect to all of them every time.

Luckily someone wrote a utility for that.
https://forum.kodi.tv/showthread.php?tid=272112