I installed R5F1 over R5D1 and got everything going just fine. One morning I noticed the backend was down. I couldn't ssh into the box or get any response. A power cycling restored it to full working but I don't know how or what happened. How can I start the Mythbox to collect the necessary information to help me (and you wonderful people out there) debug the story?

It will go for a week and no problems, or lock up 2 nights in a row.

Any other R5F1 users with this issue?

Thanks in advance!

I would guess that is a heating or hardware issue. Usually, the first thing to fail in a computer and the easiest to replace is the power supply. Yours may be getting to its end of life.

_________________
LinHES 8.3, 1 BE, 3 FE

How can I get the information to tell when it shut down or how to tell if it is a power supply issue or something else?

Hi

What version & what type of hardware?

I have had issues with F1 and sata being tricky to play nice together.

Mike

Hardware is a homebuilt PC, Athlon 2400 proc. 80,320G IDE HD (together using lvm), Win-150 capture (2x)

Knoppmyth r5f1 with no addl. updates.

Motherboard and chipset?

For example, there is an old issue that I encountered with the Nvidia Nforce2 chipset boards, where if the "C1 Disconnect" was enabled in the BIOS the machine would lock up randomly during heavy disk activity (such as when recording/watching a show). Basically the CPU would go into power saving sleep mode while the disk controller is using the bus for DMA and never wake up...

Shuttle AK32E with VIA chipset (it was inexpensive...)

Ooo... Via chipset... Possible DMA problems... See my "Hardware to avoid" posting which has a link to a page on the Hauppauge website which includes some mitigation strategies. Actually here it is:

http://www.hauppauge.com/html/lockups.htm#MOMLIST

I'll check that, but I had already checked using r5d1 before based on your message. Is there anything inherently different in r5f1 that would make this potential for lockups worse? I had only very rare lockups with r5d1 + 0.20(fixes).

Update: I changed the FastWrite option. We'll see what happens (hopefully nothing bad...)

I had same problem with my new AUTOINSTALL R5F1. I have been running knoppmyth from R5C7 thru R5F1 for over a year now without many problems. There are some problems with getting the extras working, but for basic DVR they all worked great.

I have found that if I record many shows that my backend will lockup or freeze requiring a HARD reboot. I find that some shows have a 0 byte file length and occur most often before a CRASH. I think it may have something to do with commflag or commercial flagging. If I set the allowed times from 1am to 5am; I have less problems. HDPARM does show DMA enabled.

Currently I have also reduced the number of shows I'm recording so that only one encoder is going at once. I have also went into my BIOS are reset the NV memory for PNP. After a few days I will add some more shows to my recording schedule.

I'm trying to avoid the outage shown in image below.


I'll post my system info once I dig it up.

How do you get that cool graph?

So far, no crashes (I hope I didn't just jinx it)...

The graph is one of the normal ones produced by the rrd tool setup available from the KnoppMyth web interface running on your KM box.

http://YOUR_KM_IP_ADDRESS_HERE/rrd/index.html

The graph is only available if you enable RRD during the configuration process. If not:

I found a thread about removing all of the capture cards and readding them in MYTHTV-SETUP.

I think the problem predictively occurred when the second encoder was called upon to record a show.

I may have even hastely set both capture sources to video0. I have pushed the system a few times to record two shows at same time and it has not failed again.

I did do some stuff listed above too. Commflag between 1am-5am. I'll add more back and report to this thread. I'll also dig up the original posting that may have repaired this problem.