Hard Drive Failing...

[Mark Holtz]

I got a annoying click this morning on my DirecTiVo, so it sounds like one of the two drives (dunno which) is about to fail. What I'd like to do is copy the contests from one of the the 160GB over to a 250GB while the drive is being RMA-ed. It appears the according to Hinsdale (http://www.newreleasesvideo.com/hinsdale-how-to/index9.html), the following procedure should be used:

UPGRADE CONFIGURATION #4:
From: Any Dual Drive TiVo
To: New A or New B Drive (replacing only one or the other)

Is this correct?

[larrystotler]

Well, there really is no point in using the 250GB drive since the box will only se the first 137GB due to the drive adressing limitaions and the fact that TiVo has never bothered to implement Linux's ability to override that. If you have a linu distro or a live CD like Knoppix handy, you can use the "dd" command to copy the drive after mounting the old drive and the new drive. However, the old drive may or may not manage to make it. Also, remeber that opening your TiVo box voids the warrenty.......

[Mark Holtz]

The 250GB drive is only a stopgap measure while I try to get the 160GB RMA-ed. However, I think it may something else entirely. I won't know until I pop off the lid.

[Mark Holtz]

Well, I cracked the lid and the problems disappeared. Noticed that the fan in the back wasn't really pushing the air out. Fortunately, I did have another 60mm fan, and now I can feel the air coming out. So, it could be heat related.

[beejaycee]

...the box will only se the first 137GB due to the drive adressing limitaions and the fact that TiVo has never bothered to implement Linux's ability to override that.
I don't think that this is quite correct and not fair to blame Tivo for the limitation. The 137 GB limitation was imposed by the Linux kernel that was originally used. More recently, TiVo has implemented a newer distribution that suports larger drives. However we, as DirecTV subscribers, are limited to what DTV will allow to be implemented on their boxes. As someone younger than me might say, "That 3.X software is sooo 5 minutes ago." :lol: But at least it is as stable as we can hope for.

I wonder if the new R10 boxes or the new 6.X software that is pending will have the same limitations?

[larrystotler]

TiVo has done software updates, and there is no reason that they could not have done the upgrade, however, they really don't have any incentive to "fix" this problem since we aren't supposed to modify the thing anyway. Also, it is amusing to note that TiVo charges $12.95/$6.95 for their stand alone boxes, but the $4.98 DVR fee w/ D* covers all DVRs on your account. Sounds like they are screwing themselves. It's really ass-backwards. D* should be charging per DVR, whereas E* should only charge per account since E*'s DVRs don't have the features of TiVo as well as only having a 9 day guide.........

[beejaycee]

TiVo has done software updates, and there is no reason that they could not have done the upgrade, however, they really don't have any incentive to "fix" this problem since we aren't supposed to modify the thing anyway.
Larry, we'll just scratch you off of the "TiVo Fans" list! :lol: Again I say to you, TiVo can only release what DTV allows them to release for their DTiVos. I doubt that they are intentionally "screwing themselves" since DTV is their biggest established market. The uniformity of platforms allows the porting of software so it is more likely that DTV is worried about support costs. As you noted, they are only getting ~$5 per account and that has to be split 2 ways so there is no real motivation for DTV to provoke people to call the 1-800 number to ask thought-provoking questions such as "what are all these folder thingies and where did my recordings go?" :rolleyes:

[larrystotler]

Actually, I have never cared for TiVo. It's an interesting idea, but I can't say I care for their implementation. To each their own. And, I guess the big question is whether or not we can get away with upgrading the kernel on the system ourselves? I seriously doubt that there is an entire gcc compiler on the disk(don't know yet, but plan on looking soon). E*'s 721 is also based on Linux, but they have a mechanism that reinstalls the system software if you tamper with it too much.

[beejaycee]

Actually, I have never cared for TiVo. It's an interesting idea, but I can't say I care for their implementation.
Kudos to you for being honest about your perspective! I probably would have been much more critical of my DTivo had I originally had a 721 instead of a 501. But from my perspective, it's been kind of like comparing Win3.1 to Win95 when I compare the 501 to the DTiVo - it's much better but not as great as it can be, especially when you know that WinXP (meaning the 4.X software) is out there! (Oh wait, I have 'WinxP'! ;) )

I guess the big question is whether or not we can get away with upgrading the kernel on the system ourselves?
I know that some DTiVos can use the lba48 kernel (I believe by using the monte procedure) but mine was not one of them when I read over the info so I put it out of my too-small, too-cluttered mind. From a practical standpoint, it does involve removing and hacking the HD. Probably not something an average user is going to do. There is a practical limit on how far you can go before the TiVo tries to (a) heal itself and wipe out the hacks, (b) stops booting, or (c) both a & b.

As for me, I just loaded JaveHMO on my PC last night and life with a hacked DTiVo just keeps getting "funner!"