Largest size drive for series one

[Happy Chappy]

With the new PTVUpgrade cd what is the largest size single drive that can be installed on a series one?

[mick66]

750GB but only until they start selling larger capacity hard drives.

[GreenLantern]

sorry to hijack this thread, but my question is related...

i have a Series 1 with 1.3 software and an upgraded drive to 80Gig. the drive was acting up so i replaced it with a 160Gig using Tiger's MFSTools 2.0 bootCD. i did not use the non-Tiger MFSTools 2.0 bootCD because Hinsale's How-To says it is for "older" Series 1 and i didn't know exactly what that meant. i take it that Tiger's bootCD is LBA48, and that may be a problem.

MFSInfo reports
/dev/hdd10: 521MiB
/dev/hdd10: 20515MiB
/dev/hdd10: 4MiB
/dev/hdd10: 56679MiB
/dev/hdd10: 0MiB
/dev/hdd10: 78832MiB
Total MFS volume size: 156543MiB
since the Series 1 w/1.3 software can only address 137GB and my drive is reporting over 150GB, what's going to happen? will recordings "wrap" at 137GB and overwrite other recordings? or will the additional space just be wasted? i don't care if it's wasted, i just don't want to lose recordings (after a 13-hr copy from the dying drive to preserve 70GB of recordings).

also, can i just use PTVUpgrade's "copykern" on the new drive and it will see the additional space? and not mess up anything already on the drive?

thanks!

p.s. forgot to mention. TiVo System Information thinks there are 199 hrs (Basic). since i had 96 hrs (Basic) with the old 80GB drive, going to 160GB ought to theoretically double it, so the 199 seems consistent with the drive size. is this bogus and i will still be bitten by the 137GB limit? or did Tiger's MFSTools 2.0 disk do some magic on the kernel to make it LBA48? is there any way for me to check the drive to know for sure?

[blindlemon]

Well, 199 hours certainly implies that the upgrade expanded to fill the whole 160gb. Which CD, exactly did you use - can you provide a link?

The drive can be expanded to any size without installing the LBA48 kernel as long as the linux version on the boot CD is LBA48-aware - but you will need to install the LBA48 kernel before the TiVo OS tries to write past the 137gb boundary or you will run into problems as you surmise.

However, the good news is that yes, you should be able to use copykern to install the LBA48 kernel and all will be well :)

[GreenLantern]

phew, being able to copykerrn is good news--i'm glad i didn't put the cover back on the unit! the CD i used is Tiger's BootCD named MFSLBA48.ISO. it is linked from Hinsdale's How-To but i can't enter the URL even though i'm a 5-yr member and have made way more than 5 posts! :( excerpt from Hinsdale's How-To:
For most model TiVos and most common upgrades you should download Tiger’s Mfs Tools Boot CD 11.5MB containing all necessary utilities (If you have older Series 1 models you should use Mfs Tools Boot Cd (10.3MB)). i wonder if that CD has a replacement kernel or a patch on it...

[GreenLantern]

i am confused about byteswapping. i copied my Series 1 v1.3OS unsubbed drive to a new drive using Tiger's MFSTools bootCD which i am pretty sure used DMA and not byteswapped. the copy worked in my TiVo.

i now want to edit rc.sysint using joe on the bootCD. do i need to boot with no DMA and yes byteswap?

basically, when do i need to be careful about byteswapping for my old TiVo?

[blindlemon]

You need to boot with byteswapping enabled to mount the partitions in your PC, as S1 TiVos are all byteswapped.

MFSTools handles byteswapping transparently, so although the CD boots (by default) in non-byteswapped mode, byteswapping is preserved during the backup-restore process.

Tiger's boot CD is only LBA48-aware (ie. it can 'see' past the 137gb boundary because the linux kernel booted by the CD is LBA48 aware) - but it doesn't add an LBA48 kernel to a restored backup that was taken from a TiVo with a non-LBA48 kernel.

You should therefore use copykern to add a compatible LBA48 kernel to your drive ASAP.

[GreenLantern]

thanks for all your help--i'm up and running (i confess that i chickened out on copykern and reran the upgrade using non-LBA48 tools so i'm limited to only 137GB of the 160GB drive, but that's ok since i plan to upgrade soon to a larger, better drive).

it's ok to let this thread die, but i do have one more question. about byteswapping. i want to edit rc.sysinit but i can't. when i use the bootCD it says it can't recognize the upgrade disk and the signature is 1492 instead of 9214 (or vice versa, i forget exactly). that looked byteswapped, so i boot using the "swap" option and then the disk is recognized and 15 partitions listed, then i get a kernel panic on VFS and it's dead.

if i don't use the "swap" option then i can boot to a command prompt but cannot mount the 4 or 7 partition, mount says i need to tell it what the filesystem is. (the drive was on secondary slave).

the upgrade disk does work fine in the TiVo, so it seems like the copy worked, but i can't use the tools that everyone else seems to be able to use. did i mess something up?

[blindlemon]

Try booting from a NIC CD from silicondust.com (http://www.silicondust.com/forum/viewtopic.php?t=990) instead.

That will boot up in byteswapped mode by default and you should be able to mount the partitions.