Error playing a recording

[snook789]

I get this radom error message when going to play a recording on our now playing list

"Error playing a recording

The TIVO DVR was not able to record this program because there was no video signal on the channel. You may be trying to record on a channel that you don't recieve"

I can not figure out what is causing it.
Both tuners work.
Have tested recording the 2 channels just now, on the 2 statons it happend on (tested while they were both still recording tho)

It happens like 1 out of ever 25 shows.
Very radom, and hard to figure out why it is doing this.

Tried a search for the error, but didn't find any help.

Any ideas ?

[PlainBill]

Was it hacked? How? Did you disable encryption?

PlainBill

[snook789]

I'm sorry, I thought I had my hacks in my signiture, and I don't

I started with a fresh 160 gig hard drive
image from the eMule Tivo-S2-4.0.1b-02-2-xxx.mfs
killhdinitrd'd 4.0.1a kernel
I have
Superpatch-4all, S2 utility collection, telnet, ftp, TivoWebPlus, Hackman, mfs_ftp, vserver, yac.

Been up and running on this for about 6 weeks

Would like to note one thing, that may have something to do with this.

I notice in Hackman, that its either when I reload TWP, or restart Tivo, I need to Remount my tivo, as it sets to read/write (not sure why it does this)
But just notice it was open, to read/write, and I just remounted it.

Other then that, everything seems ok.
It happends very randomly, and it doesn't matter if it is recording on both tuners or just 1, Happens both ways..
I did find 1 other post on this same error, but don't see what the solution was or what caused it

Odd Error Message (http://www.dealdatabase.com/forum/showthread.php?t=37106&highlight=error+playing+recording)

[snook789]

Ok, now this is weird, I can extract it wit TyShow, and watch it.....
But Tivo won't play it...

Any ideas ?

[Jamie]

Ok, now this is weird, I can extract it wit TyShow, and watch it.....
But Tivo won't play it...

Any ideas ?
What does ciphercheck.tcl show? Sounds like the encryption status of the stream may disagree with the CSO settings.

[snook789]

What does ciphercheck.tcl show? Sounds like the encryption status of the stream may disagree with the CSO settings.

Man you 2 always come to my rescue
So much appricated

CipherCheck.tcl by AlphaWolf_HK

TyStream encryption is currently disabled.

Here is the status of your current recordings:

Encrypted CSO Set Stream Name
--------- ------- -----------------------------------------------------------
No No Overhaulin'
No No The Tonight Show With Jay Leno
No No Rides
Yes No Desperate Housewives

You can see which one got the wife upset :)

Why is it encrypting for some, and not all...

[Jamie]

Why is it encrypting for some, and not all...That looks peculiar. I expected to see unencrypted streams that still had CSO values set. Particularly if you can play this stream with TyShow. But yours shows an encrypted stream without no CSO. I don't know how that might have happened, unless the stream was corrupted on disk somehow. If TyShow can play it, it must not be encrypted. Perhaps the magic number at the start that identifies an unencrypted stream got corrupted somehow.

[snook789]

Ya, I undeleted it, grabbed it with TyShow, and then when through the steps
Make Keys
Mulitplex file
Then watch it in Nero Showtime...

[snook789]

Perhaps the magic number at the start that identifies an unencrypted stream got corrupted somehow.

Any ideas on how I should attempt to fix this ?

Watch everything, then do a clear and delete ?

[Jamie]

Any ideas on how I should attempt to fix this ?

Watch everything, then do a clear and delete ?
I don't see how a clear and delete everything would help.

I'm at a loss to explain why you occasionally see streams that appear to be encrypted (magic at the start of the stream isn't right), but aren't. My first guess might be that you have conflicting no-scramble methods applied, but it doesn't sound like that from your description of what you've done to it. A second guess might be corrupted streams from a disk going bad, or an lba48 problem (non lba48 kernel on a drive with partitions about the lba28 mark). I would think you'd have much more serious problems if it was that.

You might want to check the md5sum of your tivoapp against the correct value for a properly Superpatch-4all version to make sure your patches are correctly applied.

[snook789]

this is still happening to me, and it looks like I am going to have to pull the drive, and start from scratch (lost backups, long story :( )

Before I do, coming back for one last attempt to see if anyone may know what this is, and if it can be fixed.

AlphaWolf would probably know (read post that were similar to this) but I don't want to pm him..

[snook789]

My first guess might be that you have conflicting no-scramble methods applied, but it doesn't sound like that from your description of what you've done to it..

I am thinking you might be on the right track with this.

What other scripts are used for no scrambling, other then Superpatch-4all ?
Maybe I have something else on there that is doing that.

Along with the error message in my top post, I am also getting freezing now, were I can't fast forward. It gets stuck, and I have to go next tick up to get past it

sucks :(

[ronnythunder]

you said you have a 160gb drive, but there's no mention of an lba48 kernel for the tivo. did you do the pc side (mfstools) with a lba48 kernel? if so, you've probably got a disk corruption problem. how many hours does your unit report?

ronny

[Jamie]

you said you have a 160gb drive, but there's no mention of an lba48 kernel for the tivo. did you do the pc side (mfstools) with a lba48 kernel? if so, you've probably got a disk corruption problem. how many hours does your unit report?This sounds like the most likely thing to me now too. Go look for lba48chk (in the tivopart package) and run it to check whether you have this problem.

[snook789]

you said you have a 160gb drive, but there's no mention of an lba48 kernel for the tivo. did you do the pc side (mfstools) with a lba48 kernel? if so, you've probably got a disk corruption problem. how many hours does your unit report?

ronny

Thanks for the reply ronny. I followed your post, with chrsturbo's on building kernel for s2 (http://www.dealdatabase.com/forum/showthread.php?t=27298) when I found that the 4.0 I wanted to run, didn't have a supported lba48 kernel, so I looked into that post for how to build my own. But for the 23 more gigs or so, it wasn't worth it to me, and I installed the non-lba48 4.0.1a kernel with mfstools

My hours in the system info read variable 133

More info from my Tivo
File System/Disk Information
Filesystem Type Size Used Avail Capacity Mounted on
/dev/hda4 ext2 124M 80M 37M 68% /
/dev/hda9 ext2 124M 30M 87M 26% /var

/dev/hda:
multcount = 16 (on)
I/O support = 0 (default 16-bit)
using_dma = 1 (on)
readahead = 8 (on)
geometry = 4161/16/63, sectors = 268435455, start = 0
drive state is: active/idle

Device: WDC WD1600JB-00GVA0 Supports ATA Version 6
Check S.M.A.R.T. Passed

User Space
Expired Invisible 68 1454 MB 1.0% 33:59:59
Expired Wishlist 10 9855 MB 6.5% 9:39:03
Expired Season Pass 27 32472 MB 21.4% 27:49:47
Expired Single 7 12953 MB 8.5% 11:15:19
Single 1 2480 MB 1.6% 2:20:02
Season Pass 8 8056 MB 5.3% 6:32:13
Invisible 1 21 MB 0.0% 0:30:00
Live Cache 2 1792 MB 1.2% 0:42:02
Used User Space 124 69083 MB 45.6% 92:48:25
Reserved Space
Expired Tivo Clips 88 19277 MB 12.7% 19:56:01
Tivo Clips 3 209 MB 0.1% 0:15:06
Used Reserved Space 91 19486 MB 12.9% 20:11:07
Space Summary
Total Space - 151594 MB 100.0% 169:13:52
Total Used 215 88569 MB 58.4% 112:59:32
Total Free - 63025 MB 41.6% 70:21:27
Deleted** 59 59209 MB 39.1% 51:09:20

That is kinda hard to read, I will attach a screen shot

Jamie, as alway, thank you! I really appricate you trying to help.
I will do a lba48chk check, and report back

[ronnythunder]

yep, this is what happened. you built the system using a pc kernel that supported lba48.

at this point, you have no choice but to start over (restore your image). this time, you either need to chain load (using monte) an lba48 tivo kernel, or make sure you have a *non* lba48 kernel when you do the restore on the pc.

to be sure, there is no way to recover from this damage without a re-restore; your current config is toast.

ronny

[snook789]

yep, this is what happened. you built the system using a pc kernel that supported lba48.

ronny

I thought the 2.4.18 kernel I used, Didn't support lba48

[Jamie]

I thought the 2.4.18 kernel I used, Didn't support lba48And that's exactly the problem. You expanded the drive beyond the 137GB mark, but the tivo kernel is not capable of accessing the drive beyond that point and it "wraps around" instead, overwriting data at the beginning of the drive.

The problem stems from what kernel was booted on your pc when you expanded the drive. If it was lba48 aware then it will expand MFS to use the whole 160GB disk. If you use a non-lba48 kernel on the PC side, it will only expand up to the 137GB mark. The standard mfstools boot cd is not lba48 aware, but there are boot cds around that are, for example, the ptvupgrade boot cd labeled as an lba48 product.

Here's a quote from the product page for the ptvupgrade lba48 boot cd:
Proper Use of thisCD

If you are building a replacement drive kit for a Series2 unit which does not have a supported LBA48 kernel, and you are using any drives which are greater than 137GB in capacity (each drive, not the sum total of the two) then you must NOT use this CD unless you have the intentions of using a modified Series2 kernel and the associated tools. You can use our Universal Boot CD as an alternative (not available for download yet, but we are working on a new version) or Tiger's Original Disk, for non-lba48 drives with non-lba48 TiVo kernels.

[snook789]

errrr, I'm upset, because I was aware of this and why I used the Knoppix Lite CD...

bummer!

Guess I will have to do again...

How is your custom kernel (http://www.dealdatabase.com/forum/showpost.php?p=202967&postcount=26) holding up, any problems ?
May give that a try now...

[ronnythunder]

errrr, I'm upset, because I was aware of this and why I used the Knoppix Lite CD...afaik, the knoppix cd is lba48-aware (as i believe you've confirmed.)

ronny

[Jamie]

errrr, I'm upset, because I was aware of this and why I used the Knoppix Lite CD...

bummer!

Guess I will have to do again...

How is your custom kernel (http://www.dealdatabase.com/forum/showpost.php?p=202967&postcount=26) holding up, any problems ?
May give that a try now...I use it. Several people report it works on rid units.

You might be able to monte to an lba48 kernel and force an mfs check without starting over from scratch. I'd be a little nervous about the file system after that though. I don't know how thorough the mfscheck is. Seems like there is the possibility of corruption in the guide data or elsewhere that could cause problems downstream. It would be safest to start over from scratch.