DSR6000 playback issue

[Agix]

I have a very odd issue with playback on my DSR6000.

It seams to record the whole show, the green bar show that it recorded an hour. During playback it will play for a period of time and just stop. If I don't do nothing it will stay there forever. If I fast forward, it will jump ahead a block of time (sometimes 15 minutes, sometime 20 , it varies) and resume playback. If I try to rewind into the 15 minute void, it just stops. It will not rewind back to the beginning of the show. If I hit the advance button, I can make it start back at the beginning, but the process just repeats itself.

Various notes:
It acts like that 15 minutes does not exist.
This is random, can not determine a pattern.

This has been going on for a couple months. I have checked the hard drives and they don't show any errors. I am going to check them again and see it something appears but I don't think it will.


Any one have a clue how to fix this? Will some logs tell me what is happening?

Thanks
Agix

[Agix]

Ok, why was this message moved????

I for one am not a newbie at tivo and this is a hardware issue that I am trying to resolve. Can this please be moved back into the Broken tivo support area?

Thank you

[JJBliss]

Ok, why was this message moved????
Because some moderator or administrator thought it should be.

I for one am not a newbie at tivo
Apparently, you are.

Can this please be moved back into the Broken tivo support area?

No.

[AlphaWolf]

Sounds more like a stream error than anything else. That is likely to be caused by a bad coax line running from your LNB or multiswitch. Theres a small chance that it is a defective tuner, but I highly doubt it. It is also possible that it is an LBA48 issue, which will also cause defective streams.

I would recommend extracting the stream and try to play it on something besides your tivo. That will probably give you the most information.

[Agix]

JJBliss, I am sorry but I don't understand your negative comments to me. But since this deals with a broken / Malfunctioning tivo why would this post not be moved back to the correct forum?


Alphawolf, that is an interesting solution but let me add this strange oddity. This is all hearsay, but I believe I was told that they can be watching it live as it is recording and see the whole show just fine. When the rest of the family goes to watch it, the voids are there. I will try to get to get a bad show extracted and see if it happens there as well. I will investigate further, maybe swapping sat inputs from both of the tivos. The problem should follow to the other tivo if this where the case.

LBA48 should not be an issue, because I never installed it. I think this tivo has two hard drives in it (I have 6 tivos I have worked on, can't remember what this has in it at the moment) possibly one drive would be a 120Gb and the other 160Gb. I just gave up the space, but I wouldn't think this would cause the problem to show up now.


Agix

[JJBliss]

JJBliss, I am sorry
Apology accepted.

but I don't understand your negative comments to me.
Not negative, but that says a lot about your perspective on the Newbie forum. Sad.

But since this deals with a broken / Malfunctioning tivo why would this post not be moved back to the correct forum?
It does not necessarily. See ADH's post.

[AlphaWolf]

I think this tivo has two hard drives in it (I have 6 tivos I have worked on, can't remember what this has in it at the moment) possibly one drive would be a 120Gb and the other 160Gb. I just gave up the space, but I wouldn't think this would cause the problem to show up now.

That can very well cause the problem. If you restored to the drive using the -x option, it would have filled the entire thing and not just the sub 137g area. Thus when you don't use an lba48 kernel, the tivo will attempt to store data in that area but instead the data will be written somewhere where it isn't supposed to be written - e.g. over another stream.

[Agix]

JJBliss,
I think it was just a misunderstanding. I am in no way meaning what you are suggestion about the newbie forum. I was just saying that your statement or assumption was wrong.

Quote:
I for one am not a newbie at tivo

Apparently, you are.
I do not know everything about a tivo that you or other very knowledable people like Alphawolf do, but I would not consider myself a newbie on the topic of tivos. I guess my definition of a newbie was one that had little to no knowledge at all about a topic. Yours must be different and I am fine with that. Thank you for the conversation.


Alphawolf,
I will post when I know the exact configuration of this unit and hopefully I can get an idea what might be happening.

Thanks.

[captain_video]

I wouldn't get your feathers ruffled just because you got a post moved to the newbie forum. It's entirely up to the mods whether they think a thread should be moved, whether you agree or not. In the grand scheme of things here, your vote, or mine for that matter, doesn't really count in the way the mods run the forum so learn to live with it.

I see that you joined the forum in 2002 yet you only have 37 posts, indicating that you are not a very active participant in forum discussions. On the plus side, it could just mean that you read a lot without adding your 2 cents. JJ obviously thought your post was better suited to the newbie section and moved it as a result. It's no big deal so don't lose any sleep over it or take it personally. The bottom line is that you got a response to your post with good info that may help you on the way to a resolution, regardless of where the thread originated.

If you restored to the drive using the -x option, it would have filled the entire thing and not just the sub 137g area.
I think that's only true if you use an LBA48 aware version of the MFS Tools boot disk like the one from PTVUpgrade. I've found that you can't expand a drive beyond the 137GB limit unless you have an LBA48 kernel to support it on the boot CD. I tried using InstantCake with the 4.01b OS and it would not expand beyond 137GB unless I restored the image manually using the PTVUpgrade LBA48 boot disc. I'll probably be proven wrong on this issue but personal experience has shown this to hold true with every drive I've used larger than 137GB. It could just be that MFS Tools is actually expanding the partitions beyond 137GB but the Tivo is only reporting the capacity up to the 137GB barrier even though the partition is larger in reality.

[Agix]

Point well taken Captain Video, thanks

I know the drives have never been restored. These drives where initially installed using Extreme 2.5 and where upgraded to 2.5.2 with Xplusz way back when (well over a year ago). I don't recall LBA48 being available then.

This being the case, could what Alphawolf described be the problem? Should I recrack the case and put LBA48 on the box? I just thought it couldn't address any area above te 137Gb limit and shouldn't be a problem.

Agix

[PlainBill]

<SNIP>

I think that's only true if you use an LBA48 aware version of the MFS Tools boot disk like the one from PTVUpgrade. I've found that you can't expand a drive beyond the 137GB limit unless you have an LBA48 kernel to support it on the boot CD. I tried using InstantCake with the 4.01b OS and it would not expand beyond 137GB unless I restored the image manually using the PTVUpgrade LBA48 boot disc. I'll probably be proven wrong on this issue but personal experience has shown this to hold true with every drive I've used larger than 137GB. It could just be that MFS Tools is actually expanding the partitions beyond 137GB but the Tivo is only reporting the capacity up to the 137GB barrier even though the partition is larger in reality.

The only thing incorrect in the above paragraph is your speculation about being proven wrong - it won't happen. A non-LBA-48 kernel will only 'see' the first 137 Gig of the drive. As you discovered, once a drive has been partitioned with a non-lba-48 cd, you can't expand past that barrier even WITH an LBA-48 boot cd (unless you wipe the partitions).

PlainBill