One of the first things I tried, Jim, but thanks for the suggestion
Have you enabled persistent logging, as described above by @JimKnopf ?
While it could be a hardware error, such as faulty RAM, that might not show up on the system journal, persistent logging will still give the best chance of spotting what’s happening.
No, its much less frequent now, it froze again today. I have been getting unsafe storage removed messages for a while now, always from the same hdd, it remounts instantly though, could this be a clue?
If it’s still freezing and you would like further support, I’d recommend that you enable persistent logging.
1 Like
Do you mean I have to start logging running from settings/System/Logging? and leave it on?
Yes, that would be good. Besides the kernel logs upload the normal logs as well if possible.
I did that via ssh and set logging on, it has frozen twice in a few minutes, I will upload the logs tomorrow
OK, here are the three freezes so far
https://paste.osmc.tv/ixatiwejam
https://paste.osmc.tv/celizofiti
https://paste.osmc.tv/alisipipeg
Why you only provide the kernel logs and not in addition the full logs + the related normal kodi logs?
The first log you provided shows the system was simply shut down.
here are the corresponding full logs, I missed that line
https://paste.osmc.tv/nijipobupa
https://paste.osmc.tv/ulacogoyil
https://paste.osmc.tv/eyiqajeviy
I did not upload the Kodi log as you did not ask me to, you just said to have logging on. Here it is
https://paste.osmc.tv/jokizotiki
I spent some time in the provided data but I do not get an idea what really happens, here. Interesting is that the first two journal logs always starts with timestamps Feb 14 … ???
I see 3 Seagate disks, 2 x Backup Plus 3TB and an unknown Seagate model 3TB. Are these all self-powered devices?
From what I can see there is no common activity nor common error message before the next boot happens … like the box was simply unplugged from power.
The only clear reboot was caused by a ‘shutdown -r now’ command at Jul 22.
All hdds 3.5" and with their own psus. All the logs that I have posted have been analysed the same, ie “its been powered down” I have to agree, it has to be powered down as its the only way of getting out of the freeze! The Vero4k+ freezes, it will not respond to remote signals (from any source) it is not pingable on the net, it cant be reached via my phone app or Arch via the PC. I have to power it down, wait a few minutes and then power it up! it is not working as it should, it is obvious that the logs are a waste of time in this situation, nothing untoward is being logged. It has even frozen when just connected to its psu (also when connected to a battery via USB) and nothing else, no hdds, no network, no HDMI, it is Kaput, I think I need it replaced.
Out of curiosity, have you ever ran a disk check on the connected drives?
I run eight 6tb drives on my Vero with no issues. I’m not sure about Linux, but if you have a bad drive (one with errors) connected to Windows, freezing/slowdowns,etc. can certainly happen.
The first log says “Document not found”
The second log shows that the machine was shutdown by a shutdown -r now command on Jul 22 at 15:59:36.
The third log ends with a series of journalctl commands, indicating that the machine was accessible.
It looks like the device hasn’t been updated for a while. For example, the current systemd package is version 241-7~deb10u8, while the one installed on the box is 241-7~deb10u5.
But it is on auto update, are you saying its the problem?
Regardless whether this could be the root cause of your box’s behaviour: What do you mean by “auto update”?
In MyOSMC you can only set one of the methods
- Prompt for all actions
- Download and display icon (but it won’t install the downloaded updates automatically)
- Download updates, then prompt (but it won’t install the downloaded updates automatically)
- Display icon on home screen, only (if new updates are availbale)
So, with MyOSMC there is no way to let automatically install updates!
I suggest you invoke
- MyOSMC → Updates → Manual Controls → Scan for updates now
- MyOSMC → Updates → Manual Controls → Install available updates now
I will check what its set on, its not shown any notifications of updates so I assumed it was on auto install
I was referring to @JimKnopf’s observation that the system logs always start with the same timestamp of 14 Feb. My understanding is that, since the V4K doesn’t have a battery.-backed real-time clock, this date probably comes from systemd.
While there should no harm in performing a dist-upgrade from the command line, I’m not convinced that being slightly behind in the update cycle is going to cause the machine to freeze.
It is set to update on default settings, I have tried a manual update, it reports that there are no updates available!
Its been over 3 weeks now and no result from the logs or any decent suggestions as to the cause of the freezing. Can you supply another Vero4k+ to test/use if found to be the problem (it seems the only solution to me)