PDA

View Full Version : Partition error using RTVPatch


SeanS
12-23-04, 12:42 PM
I replaced a 5040 40GB drive with a 200 GB WD drive using ReplayPatch and it went well for a year. Then after moving house I changed network settings. The unit never booted up again. I talked to ReplayTV tech support and tried stuff until they said I should send them the unit for replacement. For a fee, of course.

I tried to patch the drive with an image from the drive image server and received the error "Partition 2 does not immediately follow partition 1". I did a full low level disk format using the Maxtor tools, and still received the same message. I got the same error using four different images.

Then I tried to patch an image to the original Maxtor 40GB drive. ReplayPatch didn't recognize it as a Replay drive, so I did a low level disk format, and then re-tried. And I got the same partition error.

The 200GB drive ended up completely failing, and the nice people at WD are sending me a replacement drive in the next few days. I'm wondering if I should persist in this vein. I just stumbled upon my original backup.rtv file, and maybe I'd have better luck with it than with a zipped drive image.

Thanks,
Sean

FlipFlop
12-23-04, 08:53 PM
The "partition 2 doesn't follow partition 1" error generally means your partition table is scrambled. This could happen if you forgot to unzip the image file prior to using it with the "Restore target" button. The file should be somewhere around 510MB in size. If it is smaller than this, then the image isn't right.

SeanS
12-23-04, 09:01 PM
Interesting. The single-drive upgrade instructions say to point to the unzipped drive image. But I will try with an unzipped image. Thanks for the reply.

boekjar
01-03-05, 11:04 PM
Whoa. I was just posting my experience in another thread. I got this same error message when I was responding "NO" to the Large Cluster question, but the error cleared up when I selected "YES" to the Large Cluster question. (This is copying the ReplayTV 5000 image to the hard disk, then patching using the Linux Boot Disk method.)

Give it a try?