Help. My tivo is hosed

[rkshack]

My orignial configuration was an 80gb drive and an original 30 gb drive in an hdr612. A week or so ago my tivo started rebooting continuously. I pulled the drives and checked them with powermax. The 80 gb had an error. I bought a new 250gb drive and started what I thought would be an easy repair process. This what I have done:

I installed the original 80 in hdb and the new drive in hda and did dd_rescue. That was successful. I then tried to do the copykern from ptvupgrade. Once I figured out copykern would not accept hda everything seemed ok. I could not mount any of the tivo drives. I went ahead and tried mfsadd. It said it was successful but did not increase the tivo space because not enough space it said. I tried pdisk but when I did the pdisk-l /dev/hda /dev/hdb command it said could not find block 0 or 1 or something. Sorry I don't remember exactly. I gave up and put the drives in the tivo and am booting repeatedly. I will attach my kernel log. Help I am lost!

What should I do next.


Update: Ok I figured out how to access the drives by using vmlnodma and can now mount the drives. I wanted at this point to get the drives to boot my tivo before I try increasing the size or anything. What do I need to do to get the drive working. I added a new kernel log. My original had the error cut off.

[Narf54321]

It looks like you have series-1 (PPC) unit, so you'll need to do all your backup/recovery with byte-swapping enabled.

Also, you only have 64MB of swap, you'll want more for a 250GB drive. And you'll need an LBA-48 aware kernel to "see" all of the bigger drive.

[rkshack]

Since my first post I have installed on the 250 gb drive an image from a clean backup. The tivo worked fine so I now know it is not a problem with the tivo just the drive. I had originally did a dd_rescue and it took about 1.5 hrs. Because that did not work I used the command dd conv=noerror,sync if=/dev/hdb of=/dev/hda. It was about 10 hours in when I last looked at it. The dd was of an 80gb drive. I am hoping that will make a difference. I will still need the lba kernel. I was going to use copykern but I can not get the pvrupdate disk to recognize my drive. It says unknown partition table even if I type swap in at boot:. Would the weakknees disk be better to use? I will try it again with the new drive after the dd completes. Any other suggestions as to why I can't get my drive recognized would be appreciated.

Rkshack