Hi,
Attempting to complete the upgrade using instant cake for my HR10-250 to a single new seagate 400gb hd. Everything fine until I get to .....................now we will begin baking..... then I receive:

mount: medium not found

/etc/rc.d.S: /cdrom/ .live/bin/ptvbake: No such file or directory

What is happening? It looked as though everything was found as it should have. Problem with the download of instant cake?

I have upgraded several different units for myself and a couple of friends. I now have a refurbished Hughes SD-DVR40 which I want to upgrade for a friend to two 200 GB hard drives. I've checked the machine and it seems to work properly but it has the 3.xxxxx software. My underestanding is that it has to have the 6.xxxx software in order to recognize the entire 400 GB due to the limits on the older software. I can't activate with DTV and force the new software upgrade since I'm upgrading this for a friend who lives on the other side of the country. My question is this: If I choose the option in the option list that I have less than the 6.2 software version in the weaknees interactive upgrade instructions, will the upgrade process do whatever is necessary to recognize the entire 400 GB? Or will the software have to be upgraded first. If it will not recognize the entire 400 GB, must I have the DTivo upgraded to the higher version software first and can I do that without sending the machine to my friend to activate and force the upgrade, then send it back to me to upgrade with the larger drives?

Hi- newbie question here. I am trying to upgrade my TiVo 540040 with a Seagate 300GB drive. I downloaded the newest version of PTVupgrade LBA48 Boot Disk (version 4.04) and loaded it onto my computer. It is an old AMD K6 with 256MB ram running Windows 95- I borrowed it from the trash heap at our office.

I have gone over the instructions on the PTVUpdate site and Weaknees numerous time. I have been planning on doing this for 2 months- today I took the plunge.

I took apart my TiVo and put the drives in place. I have my c: drive recognized in the hda position, the Seagate is recognized in the hdb position and the CD Rom is recognized in the hdd position. In lieu of it saying hdc it says

OK ... I'm not sure what your _ACTUAL_ problem is ... but you can ignore the "ide: Assuming 33MHz system bus speed for PIO modes; override with idebuss=xx" ... since that is just the system telling you that the linux kernel did not recognize the IDE controller, and so is unable to use DMA transfer ... the net result is slightly slow upgrades ...

This thread seems to be on the subject I need help on. i'm haveing a lil problem HERE

to summerise..
I have a UK spec series 1 single drive TiVo version 2.5.5. I used Hinsdales guide to upgrade it to a 250gb single drive. I need to make my TiVo see all 250gb and understand I need to change the kernel to lba48.

This CD that this thread is based about.. does it cater for my needs on a UK (only ever series1) spec TiVo?

Is there a guide on what/how to use copykern or this disc to help me out?

I've read and read and found little tit bits on UK machines but no definitive answers.

Hi,
Attempting to complete the upgrade using instant cake for my HR10-250 to a single new seagate 400gb hd. Everything fine until I get to .....................now we will begin baking..... then I receive:

mount: medium not found

/etc/rc.d.S: /cdrom/ .live/bin/ptvbake: No such file or directory

What is happening? It looked as though everything was found as it should have. Problem with the download of instant cake?

Thanks

Oops, my bad, had the HD connected to the wrong IDE ribbon and forgot to disconnect the other two cd/dvd drives. Once I woke up and connected properly, all went smooth!

Does someone have a link to a 2.4.18 kernel thats been patched for lba 48 support. Need the old kernel for a 4.x software to monte to. Its preferred that it be pretty standard without other hacks, but I will try any that are provided.

It was hdi, but I believe I tried that. Oh well, I will probably never delve into a Linux command prompt again.

I happened to be installing a new motherboard, without the problem of the first 8 channels being used and the cdrom/drive device ids changed to hda / hdb respectively. Ran copykern and it worked fine. Thanks tivoupgrade man!

Hello, I was wondering if you could help me out. I've been working on this for 10hrs or more and have not gotten anywhere with the msfbackup command.
I have a Tivo 2 Series 40GB HD Life Time
I use the boot disk with the mfstools 2.0 on it and come to the #
My hard drive setup is....
Prim Master: hda1 (80GB C drive Fat32)
Prim Slave : hdb1 (120GB Replacement Tivo HD Fat32)
Sec. Master: hdc1 (40GB Tivo HD)
Sec. Slave :hdd(cd-rom)

All disk show correct size. i.e. all are unlocked and master and slave pins are setup correctly on HDs and ribbins setup correctly too. i.e. Prim/Sec Master on end of ribbin etc. BIOS setup to auto detect HDs.
Also, for some reason I cannot mount hda1 or c: drive. It's FAT32x and so are the other ones which I can mount.

Deleted some unnecessaries; what you were really missing is you backup (and restore for that matter) an entire device (/dev/hdc) as opposed to a partition. Have you read the Hinsdale howto (google it); lot of good info there...

I have a Series 1 standalone. I tried to re-initalize the singe drive after I removed the second one. I even redid copykern. Any ideas? Another option I have is put in a smaller second drive (80g from 250g) but not sure what commands to use. I built this using instantcake (which I don't have anymore because all 3 of my backups are jacked up).
Thanks,
Scott

I made an ISO from the V4.04 as reccomended. Never found copykern, instead it redid my drive, wiping out Tivo 3.5, now back t 3.1 again and lost what programs I had. At the # prompt I tyed in copykern but it would not take the command.

1. Where did I screw it up?
2. I am going to let it load 3.5 again but know I will have the same issue.. any help out there?

I'm having a problem with the LBA48 kernel replacement. Maybe someone can help.

1) This morning, I watched a program, and when I deleted it, the GXCEB0T rebooted. When it completed rebooting, I checked the software revision, and I had 3.5b installed.
2) When I went to the "Now Playing" list, the TiVo rebooted again, so I went online and found that the new software update probably replaced my kernel with a non-LBA48 version.
3) I downloaded the V4.04 ISO and burnt a CD. I used "copykern" to replace my kernel with 3.1
4) I installed the drives back into the TiVo, and after rebooting, I could see my recordings (I played a recent one), but I could not download satellite data (my account was listed as CLOSED in the information screen). I re-ran guided setup, and was able to get info from the satellite, and my account was back in good standing. I could watch live TV, but when I went to the "Now Playing" screen, the TiVo rebooted again. The software was still listed as 3.5b
5) I tried to reinstall the LBA48 kernel. I noticed that the CDROM did not mount, so the new kernel was not being found. I had not updated the kernel as I thought.
6) I mounted the CD drive, and installed the new kernel properly.
7) I reinstalled the drive in the TiVo, and now I'm stuck at the "Welcome. Powering up..." screen.

I double checked the drive jumpers, and they are correct. I have a 40GB main drive, and an 160GB second drive installed. I used the InstantCake CD two months ago to build this system.

Am I hosed?

**Update - as I was typing this, the TiVo booted. I still have 3.5b listed, and when I go into the Now Playing list, the TiVo reboots still. Any suggestions?

I posted this in the undergroung playground but was giving a like to here so I reposted it here. Sorry

I have a series 1 Directv tivo model GXCEBOTD that I upgraded the hard drive to a single 400gb drive using the PTVupgrade TiVo Upgrade CD a bout 6 months ago or so and everything was working great.

I updated the software that Directv came out with for for the Day light savings time update.
The software before the DST update was 3.5.01-1-031
After the update it is now 3.5B.01-1-031 THE ONLY DIFFERENCE IS THE "B"
Now almost all my programs are gone. when I select it they say: Error play a recording. The recorder was not able to record this program because there was no video signal on the channel. You may have been trying to record on a channel that you don't receive.

What would be the best way to try to save the programs and get it back working again If any.

Michaelrj9, my DSR6000 had the same error after the 3.5b update. From what I understand, until you replace the non-LBA48 kernel, the longer you use your tivo after the upgrade, the more programs you will lose. Once I replaced my kernel with the LBA48 kernel from the v4.04 cd (I used the 3.10+ kernel), all but two of my programs were viewable again.

Michaelrj9, my DSR6000 had the same error after the 3.5b update. From what I understand, until you replace the non-LBA48 kernel, the longer you use your tivo after the upgrade, the more programs you will lose. Once I replaced my kernel with the LBA48 kernel from the v4.04 cd (I used the 3.10+ kernel), all but two of my programs were viewable again.

I seen that too but if you go to the website that has killinitrd it says for series 2 tivo's and I have a series 1.

Yes, I believe you need to use killinitrd. In addition to using the 3.10+ kernel, I also had to reinstall my cachecard drivers so I zapped the new initrd while running nic_config from the Silicondust driver boot cd.

New Release of the LBA48 CD (ver 4.04) includes a revised copykern and a recompiled kernel (labeled 3.10+) in the s1_kernels directory. We have done preliminary testing with this kernel in conjunction with version 3.5 of the Series1 DirecTV TiVo release and early tests are encouraging. If you have built LBA48 drives which are spuriously rebooting, or contain content that is not accessible through the "Now Playing" list, we encourage you to use copykern to transplant this newly updated kernel. Also note that you will need to use killinitrd to zap the new initrd (or use nic_config in the silicondust network driver release to achieve the same result).