I have tried to look in other threads to see if anything there will solve my problem but I didn't find anything. Here is the situation:
I have several Series 1 Tivos running 3.0-01-1-000
They have 500GB drives in them that were all created from the same image.
This image has been working well for years on various drives.
Today I bought a new 500GB drive and formatted it. I put it in a Tivo to make sure it was working before installing it in the Tivo it would eventually go in. But to do this I had to disconnect the drive that was already in that Tivo. After the new drive booted I reconnected the drive that is normally in that Tivo and it entered a GSOD.
The drives were formatted using the following commands:
mfstool restore -s xxx -r4 -xzpi <source file> <target drive>
tpip --verbose --series1 --mkswap <target drive> --swaptype=1
(I'll explain the xxx below)
mfstool is v 2.0
tpip is v 1.2
Here is where I think the problem is. My notes say to use a swap space of 511if the drive is larger than 274GB, but it looks like when I formatted the GSOD drive I accidently read an older note which said 127.
So the drive that has the GSOD loop has a swap of 127 and the new one has 511.
I put both drives in a computer to look at the sizes in pdisk and confirmed that. The differences in size are as follows:
Partition 8 Swap/Linux Swap
Partition 13 MFS/New MFS Media
Interesting note - when I put the new drive back in the Tivo it GSODed!!! But it was not in a quick loop like the other. It stayed on the GSOD screen for a few minutes, rebooted, went back to a GSOD for a few minutes, rebooted and it came up.
So it seems like the swap is working on the new drive which has nothing on it (I plan to reformat it anyway just to play it safe since), but not the old drive which I have been using for the last 2 months.
To make matters more complicated, the image was based on a previous drive that had GSODed and had a small swapspace. I was able to restore it by reducing the size of the alternate boot partitions and adding it to the swap partition. As a result, the alternate boot partitions do not have any room.
Here are the sizes of the partitions:
Is there any way to fix this?
The drive has alot of things on it but I don't think it was full to the point that it was deleting anything yet.
If I were to get a new drive and format it with a swap space of 511 and dd copy everything but the swap, will that work? I realize that partition 13 which has most of the program data will not have enough room but its only a .3G difference and hopefully theres nothing in that space since the drive isn't full.
I've also had problems copying large drives, even using the boot CD that recognizes large drives.
Is there a specific way I would need to copy them?
Should I use vmlnodma when I boot?
Should I use bswap?
Can anything be done to save the programs on it?