I’ve been getting spontaneous reboots, especially after my Vero4k has been sitting there overnight.
I turn on the TV and UI is there, but when I click and button on my remote, it reboots. No sad face or anything. Never seems to happen when it’s in use. This also seems to be only since the last update. Currently 2024.08-1 and MyOSMC says there are no updates available.
Since I can’t predict when this happens, I didn’t do the proper way of generating a log file, though I hope something can be figured out from what I did upload
I think I finally managed to capture a proper log of this event happening. I was in the process of having my Vero4k start up during my 2nd reboot and it spontaneously restarted.
I hope someone can glean something from the log file because it’s driving me nuts.
Fyi, especially when starting with the log info floating in the upper left corner, the CPU-KODI number reads well in excess of 100%. Last time I noticed, it said 210% or something equally strange.
Unfortunately, these logs only contain kernel and mediacenter logs from the last boot but not any information what happened before.
The Vero booted with timestamp “Sep 11 23:01:43” which must be around the time when the system crashed/has frozen/was powered off and got a time update to “Sep 12 00:02:03” by ntp which is around the time when you rebooted the OSMC device.
From the symptom I think a dying power supply is a possible explanation. I would try a new good power supply first.
Specification: DC 5V, min. 2A, center positive, coaxial power connector male with OD 5.5mm and ID 2.1mm. Don’t use wall adapters designed for charging since they do not provide a stable voltage.
FYI, I also have noticed that this spontaneous reboot never happens when it’s playing a video file. Only when it’s just been just sitting there idle for a while. It also always reboots twice. The logo will appear and then immediately reboot again. After that it seems stable.
Nonetheless, I’ve ordered a new official power supply and will update when it gets swapped out.
Just to be sure: You mean you see twice the screen with black background, text please stand by and the OSMC logo … or the screen with a blue background and the OSMC logo?
this is similar to what mines been doing since Aug update
can be fine for weeks, works fine when its been used. but when left for idle over night/next day, turn TV on and its froze, but if you leave it for 30secs I get the blue screen unhappy face then system comes back on
Thanks for that question. I’ve been taking notes of what it’s happening and it is consistent, though I cannot trigger it, it just happens after a while.
I will use my remote and you’ll see it pause for a sec and then the screen will go black and “please stand by” with a little osmc logo below it will appear. It will then restart with a black screen and the various Linux commands scrolling up the screen. When that is done, the screen will go blue and a larger osmc logo will appear. Then the logo for my skin will appear (Arctic Zephyr Reloaded). Without me doing anything, the process starts again at “please stand by”. Once it gets back to the Arctic Zephyr Reloaded logo, it now proceeds to properly display everything and I can watch a video file.
It has definitely started happening more often, but still does not occur when a file is actually playing. I have ordered a new power supply as suggested in a previous response, though I haven’t received it yet.
I haven’t received my replacement power supply yet, but I wanted to add to my observations.
Last night, on a whim, I started playing a video file, paused it and just left it over night. When I came back, the remote worked fine with no reboots. I then left it idle on the home screen for a while and it went through the whole reboot process again.
It would be great to know the outcome of this, because my Vero4K has starting crashing randomly - a lot! - over the past couple of weeks.
I remember after the update, the skin had to be reset as I was running Artic Zephyr : Reloaded and it said that the version I was running wasn’t supported by the latest update. After it updated though, I switched back to the skin and it seemed to work. Maybe it’s the cause of it…
2024-09-25 16:18:38.059 T:9466 info <general>: weather.metoffice: Fetching Hourly Observation for 'Bingley Samos (3344)' from the Met Office...
2024-09-25 16:18:38.077 T:9466 info <general>: weather.metoffice: Fetching Daily Forecast for 'Wakefield (324229)' from the Met Office...
2024-09-25 16:18:38.089 T:9466 info <general>: weather.metoffice: Fetching 3 Hourly Forecast for 'Wakefield (324229)' from the Met Office...
2024-09-25 16:48:38.258 T:9598 info <general>: WEATHER: Downloading weather
Which is normal then its not a full reboot just media center crash
Okay, I have received my replacement power supply and it seems to be doing the trick.
I can’t explain how a faulty power brick could cause these problems only while the device is idle, but it certainly seems to have.
@benfolkman I use the same skin and indeed the last update broke it, but as you have found, the skin has an update available that fixes the incompatibility.
I’ll let everyone know if the random reboots start again, but for now, replacing the power supply seems to have fixed the problem.
@benfolkman There is really no helpful information in these logs and the first part of the system journal is even missing. For sure the device wasn’t shut down in a clean way since the file system was not clean while boot time … but that’s all.
If it is an Vero 4k/4k+, I recommend the same to you like @BGIYYZ.