Separate names with a comma.
Discussion in 'TiVo Upgrade Center' started by tivoupgrade, Oct 4, 2004.
If only Lou could post a list of which models this disk is suitable for, then you'd be sure.
So basically, the CD is useless for my SD-DVR80, and 250 GB upgrade drive.
Thanks for being honest.
I wouldn't say its useless.
But if you were to use your 250GB drive for the upgrade, you'd be wasting almost half of it.
So from what I can understand, there is not a LBA48 kernel that will work in the DVR40/DVR80 Series 2 DirecTiVos....is that correct?
Are they out there and just not on the CD, or do they not exist?
They are out there and just not on the CD. Kernel replacement on the Series2 is not the same as on the Series1; to get a new kernel to work on the Series2 involves the use of a few other tools. We may offer something on the "free CD' and something a little more automated as an inexpensive download at some point in the future.
First time TiVo hacker writes...
- Read Hinsdale-How-To
- Bought 250MB drive for my TiVo Series 2 (TCD540040)
- Downloaded mfstools2.iso
- Used Dell Dimension 4100 (no BIOS support for LBA 48)
- # mfsbackup -aqo - /dev/hdc | mfsrestore -xpi - /dev/hda
- Now, I have a 137MB unit.
I think that the problem is with the BIOS on my Dell PC. It is not explicitly stated in this thread if "PTVupgrade LBA 48 CD with MFStools and Enhancements" will help. Am I right to think that I need a PC with LBA 48 BIOS support to be successful?
Any suggestion on how to proceed will be appreciated.
I had the exact same problem today, so I guess the automount still does not work in all cases. Thanks for the post Kaelum!
I've done a drive size upgrade in the past with my series 1, but having trouble with my series 2.
Series 2 TDC24004A (single 40G)
No sub yet, I'm trying to copy the 40G to a 72G before applying more hacks.
No big drive, so I shouldn't need to worry about the tivo not having lba48 support.
I'm using ptvlba48-4.01.iso, but just using mfstools so far.
hdb=new tivo drive, 72G IBM deskstar
hdc=old tivo, 40G
I got no errors with the following command (tivo.upgrade-instructions.com):
mfsbackup -Tao - /dev/hdc | mfsrestore -s 127 -xzpi - /dev/hdb
After this I checked the partitions on the new drive and partitions 4 and 9 had stuff, so I put it in the tivo and it won't boot. It just loops resetting the video every 30s or so.
I put it back in the PC and dmesg shows all drive present but shows the old drive having partitions 1-13 while the new drive has 1-16.
dmesg also shows:
EXT2-fs warning: maximal mount count reached, running e2fsck is recommended
(but I can mount partitions from the new drive)
mfsinfo on the new drive shows partition 14 is zero size. Is this normal?
I checked the help messages for mfsbackup and mfsrestore and can't see any errors in the command I'm using.
Help, what else can I look for?
If you have more than one CD/DVD device in your computer, automount can be a problem; that is the only scenario I know of where it won't work as predicted. Is that the case with your PC?
No I was using some bits I threw together in a case. I had:
HD0: Nothing attached (Pri Master)
HD1: Old Tivo B (Pri Slave)
HD2: New TiVo A (Sec Master)
HD3: CD Rom (Sec Slave)
Nothing was set cable select either, all jumpers were set true.
Hmm. Interesting. Definitely different than I've ever seen (usually, the CDROM would be either primary slave or secondary master) but I don't know off-hand why the mountcd script didn't work. With the variety of BIOS' and potential configuration issues out there, its really impossible to make these things bulletproof...
They were hooked up that way because Hinsdale's guide calls for that config in my situation. Thanks for the ISO though, It was a great help!
<snip>If you are REPLACING YOUR EXISTING A DRIVE with the new larger upgrade drive:
(Assumes existing TiVo A drive as Primary Master, existing TiVo B drive as Primary Slave, and new larger upgrade drive as Secondary Master)
Use the following command to copy the existing A drive to your new upgrade drive at the # prompt:
dd if=/dev/hda of=/dev/hdc bs=1024k </snip>
I didn't think you could have a slave without a master. Try changing the Old Tivo B over to Pri Master.
Bob, thanks. Sure you can. I did have a Pri Master (old tivo A) until I pulled it. Anyway, it worked, just did not automount from the CD.
I was able to get my Tivo upgraded with the LBA48 disk sucessfully and it worked great for about two weeks, then recently I started getting errors on older programs until finally my Tivo got stuck at "Welcome, powering up" (something like that).
I've gone through all the posts and everything but I haven't seen a solution for Tivo's that actually worked, but failed later. What do I need to do? If I missed the solution a link would be great.
Did you ensure that the TiVo you upgraded either had a native LBA48 kernel or that you installed an LBA48 kernel onto the TiVo?
I had this same exact thing happen to me yesterday. For now, I have given up on the LBA48 kernel and am using 137GB of a 160GB drive.
Plug the hard drive back into your PC, boot with the LBA48 ISO, then hit <shift>-<page up> to scroll up the boot messages. I'll bet your hard drive is only 137 GB in size!
You need a PC that supports LBA48 when you do the upgrade. Sometimes you have to set the BIOS's IDE detection to "auto" or "none" to get it to work. Or you need to upgrade your BIOS, or use a new (less than one year old) PC. This should be added to the instructions at the beginning of this thread, as this is a frequent stumbling point.
It is also possible that the copykern command did not work. It always reports it was successful, even when it didn't do anything. I will ask again if there is a way to independently verify copykern was successful, as no one has answered me yet.
Finally, I haven't had time to verify this, but I swore the hard drive said 160 GB before I put it in the Tivo. I remember using IBM's drive fitness test as well as Spinrite, and they both reported 160 GB as the drive size. After I pulled the drive from the Tivo, they now both report only 137 GB! Did the hard drive sense the slow, outdated, UDMA-33 connection of Tivo and automatically cap itself at 137 GB? I haven't heard of anything like this before, but I can't think of a different explanantion.
I am using a Samsung Spinpoint SP hard drive. I didn't have time to rerun the Samsung utilities, but I remember you can set the HD to report any size you want. I remember it was set to 160GB before the upgrade. I wonder if it's set to 137 GB now?
For now, my 20GB to 137 GB upgrade seems enormous, so I'm not worried about the missing 23 GB. I'll let you know in two weeks if my second attempt at upgrading was successful.
We are using the LBA48 CD on systems over 4 years old. You definitely don't need a new PC to boot a kernel that supports LBA48. Practically any PC will work - even an old Pentium MMX should work.
As for verifying whether copykern works, ie ensuring that the correct kernel was installed, you can look in /var/log/kernel after the system has booted (if you can't telnet into the unit, then pull the drive mount the /var partition -- /dev/hdX9) and search for the string "court" in the file -- you should find a kernel log entry that confirms the build of the kernel with the "courtesan" name in it - that is what Todd Miller used when he built the kernel (sorry I can't give you the full entry right now as I do not have access to a system running that kernel at this moment).
Lastly, in the last several posts -- there has been NO mention of what type of TiVo you are talking about here. If you are using a Series2 unit, then this entire sub-discussion is moot; CopyKern is for Series1 units only....
Thanks for telling me how to verify copykern worked. I have a sneaking suspicion this was the problem, but it is weird that my drive suddenly starting reporting only 137 GB. I might never pull the drive again, as the Tivo seems to be happy now. More importantly, my wife seems to be happy now.
I understand the LBA48 issue, and I understand that the BIOS and PC shouldn't matter, but I also understand that some older PCs simply choke when the hard drive is larger than 137 GB (or 33.8 GB or 8 GB). I have a old Pentium 133 PC that wouldn't POST with the new hard drive attached. Other PCs do different things.( http://www.pcguide.com/ref/hdd/bios/sizeHandling-c.html )
New PCs have to be able to handle large hard drives properly, especially if they are shipping with them! Using a new PC eliminates one possible problem someone may be having. If your old PC works then go for it.
I am using a Series 1 HDR212. Series 2 standalone owners without LBA48 should just wait for TivoToGo to get downloaded before they upgrade. Other Series 2 owners have to go "other places" for instructions or software.