[MB Premium Twin HD] Box failed to wake up from Deep Standby for a recording

[birdman]

Today my box failed to wake up from Deep Standby to do a recording. (In fact it missed 3 - 2 this morning and 1 this evening).
The timers were in place and when I started the box manually this evening (15 mins after a timer was meant to be running) it started the recording (in the middle of the programme).

Any ideas?

 

[birdman]

There does seem to be one possibility here....

I has occurred to me that I did shut the box down on Saturday by using "shutdown -h now" from the command line (as I was logged in at the time,. and the box is in a different room).

So I've just done some tests.

"shutdown -h now": shuts down the box and the blue LED (searchlight on this box!) comes on. But it doesn't wake-up to record.

"shutdown now": stops the box, but leaves the front LED displaying the name of last channel it was on (but this is no longer scrolling). It also doesn't wake-up to record. (It is also unresponsive to the remote control, so you needed to switch it off/on using the rear power button to get it back up.)

Selecting "Deep Standby" from the menu shuts it down so that it appears to be in the same state as after "shutdown -h now". But this does wake up to record.

Is this expected behaviour?

And, if so, is there anyway to put the system into Deep Standby from the command line?

 

[Larry-G]

is there anyway to put the system into Deep Standby from the command line?

Not that I know of.

Sent from my SM-G900F using Tapatalk

 

[birdman]

Not that I know of.

Which sounds odd, given that it's the software on the box has to put it into Deep Standby.
Perhaps I need to look at the AutoTimer code...

 

[Larry-G]

Which sounds odd, given that it's the software on the box has to put it into Deep Standby.
Perhaps I need to look at the AutoTimer code...

There very well may be one but I dont know of one personally and I'm not a coder either.

 

[judge]

Have you tried:

shutdown -P now

root@vusolo2:~# shutdown
Usage:    shutdown [-akrhPHfFnc] [-t sec] time [warning message]
                  -a:      use /etc/shutdown.allow
                  -k:      don't really shutdown, only warn.
                  -r:      reboot after shutdown.
                  -h:      halt after shutdown.
                  -P:      halt action is to turn off power.
                  -H:      halt action is to just halt.
                  -f:      do a 'fast' reboot (skip fsck).
                  -F:      Force fsck on reboot.
                  -n:      do not go through "init" but go down real fast.
                  -c:      cancel a running shutdown.
                  -t secs: delay between warning and kill signal.
                  ** the "time" argument is mandatory! (try "now") **
root@vusolo2:~#

 

[birdman]

Have you tried:

shutdown -P now

Not as part of my recent testing, no.
But worth a go, thanks. [I can do it now, as a recording has just stopped]
EDIT: No, that doesn't work either....

I'm just confused by "-h" not working.
My "mental picture" of the box is that the front-panel has knowledge of the next event (a wakeup or recording) and so will ensure that the box is powered on and running at (before) that time.
Given that "-h" does switch the system off and, at last as far the external visual appearance goes, put the box into the same state as the Deep Standby menu option does, I'd expect the front-panel controller to restart it.

So obviously my model is wrong.

If anyone knows what the actual model is then I'd be pleased to know.

 

[Joe_90]

But maybe the normal shutdown (from the menu or from a standby timer) has code to check the next wakeup time and set the ticker accordingly? Maybe when you run shutdown from telnet all it is doing is killing processes and the wakeup ticker is not set? I originally thought that these boxes would have a real time clock, but I have been informed otherwise and this is also borne out by the fact that when awoken from deep standby the clock time defaults to 1/1/1970 which in itself causes problems with log dates, but that's another issue ...

 

[judge]

-h & -P are different options.
Just type shutdown into a shell & see the available options, should work the same way on all linux devices.

 

[judge]

otherwise and this is also borne out by the fact that when awoken from deep standby the clock time defaults to 1/1/1970 which in itself causes problems with log dates, but that's another issue ...

That's a long standing issue. E2 restart uses correct time, reboot doesn't.

 

[Joe_90]

I assume that this is because it's a full linux restart and the clock data is lost once you go into deep standby?

 

[judge]

I assume that this is because it's a full linux restart and the clock data is lost once you go into deep standby?

No idea, full reboot produces logs with old linux dates, E2 restart has the correct time.

 

[Joe_90]

@judge - why are being shown as offline, when you are posting? Invisibility shield

 

[judge]

@judge - why are being shown as offline, when you are posting? Invisibility shield

No idea? Not using any invisibility shields?

 

[birdman]

-h & -P are different options.
Just type shutdown into a shell & see the available options, should work the same way on all linux devices.

As it turns out -P is an option to -h, so -P on it's own won't do anything (except tell you that you need -h as well).

I'd expect -h to power down as well. It's difficult to imagine a situation where you'd want the power to still be on (or, indeed, for the hardware to be able to do it) unless you've shutdown to a specific run-level, which BusyBox doesn't cater for anyway.

 

[birdman]

But maybe the normal shutdown (from the menu or from a standby timer) has code to check the next wakeup time and set the ticker accordingly?

It would make far more sense to always have the current first event always loaded in the front-panel controller. That way if, for instance, their is a power cut it would still be able to wake up for the next recording once power is restored.

 

[judge]

Think you need to learn linux & then E2?
shutdown will work the same on all linux boxes.

 

[Larry-G]

@judge - why are being shown as offline, when you are posting? Invisibility shield

off topic but In your user CP on the forum you can choose to show your self as invisible rather than online, Judge has had this active for as long as I can remember same as my self.

 

[birdman]

That's a long standing issue. E2 restart uses correct time, reboot doesn't.

Presumably because the board in the box has no real-time clock, so only gets a time once the system is sufficiently up to get a time from the Internet or TV feed.

The Raspberry Pi has the same issue, and Raspbian "solves" (== works around) that by writing a file every few minutes (/etc/fake-hwclock.data) with the current time and uses this to set an "approximate" time as soon as possible during boot. May be ~1minute slow on a reboot, but is better that 1 Jan 1970.

 

[Larry-G]

Presumably because the board in the box has no real-time clock, so only gets a time once the system is sufficiently up to get a time from the Internet or TV feed.

when you setup your receiver you have the option of synchronizing the date and time from the Internet or directly from the satellite feed.