Error Code 05 on DishScapes?

[zippyfrog]

I have never had this happen before - I just went to watch some previous Dish Scapes, and most of the Dish Scapes that I could watch previously now have an error code of 05. Attached are 3 examples - there are quite a few more that have them as well. I know I was able to watch them previously because I will watch them on a faster playback speed to make sure I see everything, but now when I go and watch them I can't. It is just the Dish Scapes - all my other recordings work fine.

I usually create a manual timer overnight on the first of the month and have them record for one hour. Any idea why all of a sudden just the Dish Scapes have this error? I went and did a recording of the current Dish Scape for about 10 minutes and it worked fine.

My receiver is a VIP211k

 

[brittanygarden]

00-01-02-03-04-05-06-07-08-09 are all error messages for corrupted recordings. There's no way to restore on the box. You'll need to delete and record again.

 

[Pepper]

00-01-02-03-04-05-06-07-08-09 are all error messages for corrupted recordings. There's no way to restore on the box. You'll need to delete and record again.

So if a user is seeing these, especially if there are a lot, and the recordings worked previously, that tells me the drive is failing.

Would this in itself be enough to warrant a receiver swap? Or does it have to fail completely first?

- note, after typing all that out, I did notice that OP's receiver is a 211k meaning the failing drive is his, not Dish's so that question would be more regarding the DVR receivers. Zippy, if the rest of the recordings on that drive are important to you, I'd look at cloning that drive because it's experiencing hardware failure which will likely eventually cause total loss.

 

[brittanygarden]

Not necessarily, Pepper - This error message is typically due to a file error, not the entire drive. If it's consistent on a DVR box, we can check the overall health of the box.

 

[zippyfrog]

So if a user is seeing these, especially if there are a lot, and the recordings worked previously, that tells me the drive is failing.

Would this in itself be enough to warrant a receiver swap? Or does it have to fail completely first?

- note, after typing all that out, I did notice that OP's receiver is a 211k meaning the failing drive is his, not Dish's so that question would be more regarding the DVR receivers. Zippy, if the rest of the recordings on that drive are important to you, I'd look at cloning that drive because it's experiencing hardware failure which will likely eventually cause total loss.

Thanks for this insight. I will double check. The drive is 10ish years old, maybe it is starting to fail. I am surprised that it is just the Dish Scapes that have the error. I thought maybe Dish someone protected them so they couldn't be recorded.

 

[Pepper]

Thanks for this insight. I will double check. The drive is 10ish years old, maybe it is starting to fail. I am surprised that it is just the Dish Scapes that have the error. I thought maybe Dish someone protected them so they couldn't be recorded.

Based on Brittany's reply, it could also be something in software that occasionally corrupts a file. At the very least you could connect it to a computer and run a SMART utility that might tell you whether failure is imminent.

 

[Jim5506]

Not necessarily, Pepper - This error message is typically due to a file error, not the entire drive. If it's consistent on a DVR box, we can check the overall health of the box.

Brittany, have you seen the reports of a problem with PTAT on H383?
If you watch a program on PTAT and then want to watch the next program on PTAT, you cannot skip forward through the end of program time barrier. You must exit to the PTAT program listing and select the next program to have the skip forward utility available. You can just play through the time barrier but if you try to skip forward it jumps to the end of the previous program. This is similar to the previous problem in that I believe it only occurs while PTAT is recording. The next day or after PTAT has shut down the problem does not present itself.