Member
Joined: 09/23/2005
One of my 2 Maxtor's finally failed in my stand alone TiVo (Philips PTV100). My backup image is from 2.5.1 though. I installed my backup image to a new Seagate 160gb drive and installed the LBA48 kernel. Everything seems to work fine with the full capacity of the recorder listed at 192 hrs with OS 2.5.1. My concern was what was going to happen when TiVo service updated my OS to 3.0.
I forced several calls and a restart last night. All seems to be functioning fine and my recorder is still indicating the correct recording capacity of the drive. So...
1. Was Linux smart enough not to overwrite the LBA48 kernel because it was newer than the one in the update? Or...
2. Did the kernel get over written and the OS is still reporting the originally calculated recording size - destined to cause trouble at a later date?
and...
Should I just overwrite whatever kernel is there with LBA48 to be safe? I'm sure there is a way to check what kernel is present, but I am not that Linux savvy and would need some very specific direction. I can always take a spare drive, install 2.5.1, force the updates, and make an image of native 3.0 just to have in the future. I am making a backup image of 3.0 with the current kernel now.
Thoughts?