TVserver WHS standby issue (1 Viewer)

[juk]

MediaPortal Version: 1.1.2
MediaPortal Skin: Blue 3
Windows Version: WHS v1
CPU Type: AMD Athlon 4850
HDD:
Memory: 2 GB
Motherboard: Gigabyte ga-ma74gm s2h
Video Card: ATI
Video Card Driver:
Sound Card:
Sound Card AC3:
Sound Card Driver:
1. TV Card: Hauppauge 3000
1. TV Card Type: DVB-t / Analog
1. TV Card Driver: 2.122.26109.0 / 18/04/2008
2. TV Card: Pinnacle Dual Sat Pro
2. TV Card Type: DVB-S
2. TV Card Driver:
3. TV Card: Pinnacle USB 450e
3. TV Card Type:
3. TV Card Driver:
4. TV Card:
4. TV Card Type:
4. TV Card Driver:
MPEG2 Video Codec:
MPEG2 Audio Codec:
h.264 Video Codec:
Satelite/CableTV Provider: Astra 28.2 / Astra 19.2
HTPC Case:
Cooling:
Power Supply:
Remote: MS MCE
TV:
TV - HTPC Connection: S-Video


Hi,
I have been struggling with a standby issue of my WHS server every other day it seems to S3 but not completely, the power is still on but it's not reachable by ping (or the client of course) only a reboot gets it back.
The last message I usually get is that the power scheduler event was handled succesfully, this seems to be when its powering down (Suspend)... but then the next message is after I reset it (several hours later).
I have tried to update the graphic and other drivers, also saw some thing in the forum about EPG settings whicha are now set to "EPG grabbing while timeshifting/recording" and not "EPG grabbing while idle"
I have also set through a task to reboot the server every morning just in case it is a memory leak problem or something but doesn't seem to help either.

Anybody any other ideas how to fix this?

Logs attached (happened today again at around 16.22)

Event Type: Information

Event Source: TV Server
Event Category: None
Event ID: 0
Date: 05/05/2011
Time: 16:22:18
User: N/A
Computer:
Description:
PowerEvent handled successfully by the service.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.



Event Type: Error
Event Source: EventLog
Event Category: None
Event ID: 6008
Date: 05/05/2011
Time: 21:24:47
User: N/A
Computer:
Description:
The previous system shutdown at 16:22:04 on 05/05/2011 was unexpected.

 

[juk]

nobody any suggestions or ideas?

 

[yhoogi]

Sounds not like a MP issue:
1) BIOS settings correct?
There is normally also under power management the option to enable S3 and what events can wake-up the computer

2) Did you check if you can bring him into S3 and awake manually?
Open a remote terminal session or log in locally and try to bring him to S3
In case you configure in BIOS that mouse / keyboard can wake up the system - you can check if the unit comes back by kb event or mouse movement.
Also, normally from S3 you should come back by a short push of the power button.


2) Did you configured the network card as able to receive magic packets?
In any case, there you can also set that all network traffic can wake up the computer
(Also a good check)
Please refer also to the Lightsout tool and the setup guide for S3
Lightsout(en)

Anyhow, if you have WHS trouble, their forum is better suited.

What tool you are using: Powerscheduler++?


Cheers,

 

[juk]

Hi,
thanks for your reply
but I might have to clarify...
the S3 function works gerneraly but every other day it fails so that the system is not reachable (can't wake it up by client or WOL packet, ping etc...) although the power lights are on and only reboot helps.
I think it might happen going into S3 rather than when waking up I am not 100% sure.

I am using the in-build PowerScheduler... maybe I will try the ++ version...

It is probbaly a combination of hardware and drivers and not directly related to MP or WHS I think but I thought I ask anyway if anybody has seen something similar..

 

[yhoogi]

You are aware that there are some services in WHS which may cause problems with S3 if they are not stopped prior to sleep and restarted after awake?

Best would be you go to the WHSBlog, I referred above, and start with installing LightsOut.
There is also a script available from Larry (either in this forum and better in the WHSBlog forum) which handles the coordination of proper sleeping and scheduling for WHS.
The Scheduler++ is not 100% suitable for WHS needs.

Cheers,

 

[HenkV]

maybe you lose power while in S3, than this error can occure

 

[juk]

yhoogi

No Iwasn't aware - thanks for the hint and I'll check it out...
I had LightsOut installed before but had taken it off thinking it might be the causing the issue...

HenkV
power failure every 2nd day would be really scary.. I don't think and hope that is the case

 

[juk]

AW: TVserver WHS standby issue

Hi,

I tried to install the script for LightsOut but it doesn't create the MP_Aufnamen task... so I wonder if that has to do with that I am using MySQL and the script is written for MS SQL... anybody how to amend it?

 

[yhoogi]

For MySQL you have to mod the script according to:
[URL="LO Script"]http://forum.home-server-blog.de/viewtopic.php?f=38&t=4974&start=120#p98414, [/URL]

Seems like there were also some mods proposed by others in the thread. Never did it with MySQL, as I have shifted the TV server to a dedicated Atom system as you have to disable power down of all HDDs in WHS to prevent discontinuities in the record stream during spin-up of stby HDDs. Quite a power consuming system if more than 2 HDDs involved.

Further basic info, you can find here:
https://forum.team-mediaportal.com/mediaportal-1-talk-45/tv-server-whs-collection-fixes-workarounds-69731/#post502756


Anyhow, best would be to ask Larry directly for the script usage if you got stuck. He was also regularly visiting this forum, too.

Cheers,



P.S: Did you tried if you can awake manually the system if it is not reachable by WoL? (i.e. normally pushing briefly the Power Button should do the trick). Also, you should try if you observe same behaviour while using hibernate (suspend to disk) instead of stby
It could be also a network card driver prblem or even a RAM problem

 

[leo7r]

exactly the same issue here. different hardware just WHS and MePo1 and lightsout with script in use. would be great if anyone got idea´s to fix it.