Announcement

Collapse
No announcement yet.

Should I be concerned that my Series 1 sees all of a 160G drive?

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Should I be concerned that my Series 1 sees all of a 160G drive?

    I just upgraded the single hard drive in my Series 1 Philips HDR212 to a new 160G drive using MFS Tools. It was my understanding from the how-to that the Series 1 TiVos would only be able to see 137GB of the drive. However, my TiVo's system info says that the recording capacity is now 193 hours, and so it looks like it at least partially knows about the full capacity. Should I be concerned about this? Could the TiVo be counting partitions in the capacity count which it will choke on when trying to use? Or has the capacity limitation been addressed by kernel upgrades which have occurred since the how-to was written?

    I had previously installed a secondary "add one" weakNees upgrade drive in this TiVo (it has only one drive now), and the added capacity showed up as something closer to 137GB, so I want to make sure I haven't done something wrong now. I didn't see a way in MFS Tools to partition the drive to a size that's larger than the original but not as large as the full capacity.

    Thanks,
    - Tim Macinta

  • #2
    Yup - you're going to have a problem. The drive shouldn't use more than 137 GB, which is something like 160 hours.

    The problem is that when you booted your Linux to run mfstools, you booted from a newer Linux kernel. If you boot from an older one, like 2.4.16, then it would automatically limit you to 137 GB.
    Been here a long time . . .

    Comment


    • #3
      Alright, thanks for the tip on how to work around this. I'm off to try and find something that will boot into an older kernel.

      Comment


      • #4
        The boot floppy referenced here has the old kernel:

        http://tivo.upgrade-instructions.com
        Been here a long time . . .

        Comment


        • #5
          Thanks for all your help, here and in the other thread I started. I had a copy of Tom's Root Boot disk lying around already, so I tried booting from that and rerunning the restore. That seems to have done the trick - the recording capacity in the system info is as expected now.

          Comment

          Working...
          X