I have a TiVo Series3 (OLED TCD648250B). In 2010 I updated the drive to a 1.5T WD EARS HD and expanded it up to the 1.26T capacity via WinMFS. I turned off intelipark via WDidle3 /d. This worked fine for 2.5 years. The S3 has recently begun to reboot and so I decided to just re-image a new drive. I took backups of my original 250G HD in 2010.

So I restore the image to another WD 1.5T with intelipark turned off, I answer yes to expand and then supersize it. Put it back into the Tivo and it reports 36 hrs of HD capacity, when I expect to see 157 Hrs.

I am following these steps here, exactly.

• In WinMFS, select File -> Select Drive and select the new replacement SATA drive
• In WinMFS, select File -> Restore and select the backup file you saved earlier. Click Start. This will restore the TiVo software to the new drive.

Note: Do not change the swap size. Leave it at the default of 128.
• When the restore is complete, WinMFS will ask you if you want to expand the drive to use the new space. Click Yes.

If you do not see this dialog box, then select Tools-> Mfsadd.
• Select Tools-> MfsSuperSize -> On.

I’ve done this half a dozen times now with different drives (all WD 1.5T) and I even downloaded a new version of winMFS ( beta 9.3f) and every time it does not show the expanded capacity to 157Hrs.

I am using an eSata drive dock and winMFs sees the drive just fine and does the image OK.

I tried to do the kickstart 54 and it just would not take, not sure what I was doing wrong there.

I downloaded a virgin image from a member here via dropbox for my S3 model, restored from that one too and it also reported 36 hrs.

What in the world am I doing wrong/missing? I don’t recall any of these issues when I did my upgrade in 2010.

I don't care about the content on the old 1.5T HD. I can get the S3 back up and running, but kinda wanted to get full use of the new 1.5T HD to get me back where I was before.

I have a TiVo Series3 (OLED TCD648250B). In 2010 I updated the drive to a 1.5T WD EARS HD and expanded it up to the 1.26T capacity via WinMFS. I turned off intelipark via WDidle3 /d. This worked fine for 2.5 years. The S3 has recently begun to reboot and so I decided to just re-image a new drive. I took backups of my original 250G HD in 2010.

So I restore the image to another WD 1.5T with intelipark turned off, I answer yes to expand and then supersize it. Put it back into the Tivo and it reports 36 hrs of HD capacity, when I expect to see 157 Hrs.

I am following these steps here, exactly.

• In WinMFS, select File -> Select Drive and select the new replacement SATA drive
• In WinMFS, select File -> Restore and select the backup file you saved earlier. Click Start. This will restore the TiVo software to the new drive.

Note: Do not change the swap size. Leave it at the default of 128.
• When the restore is complete, WinMFS will ask you if you want to expand the drive to use the new space. Click Yes.

If you do not see this dialog box, then select Tools-> Mfsadd.
• Select Tools-> MfsSuperSize -> On.

I’ve done this half a dozen times now with different drives (all WD 1.5T) and I even downloaded a new version of winMFS ( beta 9.3f) and every time it does not show the expanded capacity to 157Hrs.

I am using an eSata drive dock and winMFs sees the drive just fine and does the image OK.

I tried to do the kickstart 54 and it just would not take, not sure what I was doing wrong there.

I downloaded a virgin image from a member here via dropbox for my S3 model, restored from that one too and it also reported 36 hrs.

What in the world am I doing wrong/missing? I don’t recall any of these issues when I did my upgrade in 2010.

I don't care about the content on the old 1.5T HD. I can get the S3 back up and running, but kinda wanted to get full use of the new 1.5T HD to get me back where I was before.

thanks for your help.

Curious and interesting.
Make sure run WinMFS as administrator.
Try saying no right after the restore to expand the drive. Check MFSInfo and see what information it gives. If you can post it here. Then run MFSAdd and if it asks to limit the drive to 1TB tell it no. Then run Supersize. After that MFSInfo again and compare the two outputs. Post the information pre and post MFSAdd so we can see what else can be done.

__________________
"Delay is preferable to error" - Thomas Jefferson
"If I have seen further it is by standing on the shoulders of Giants" - Sir Isaac Newton

Curious that 157 hrs is what is normally reported for a 1 TB drive -- sounds like you never actually had more than that in use.

__________________
"It must be swell to be so perfect and odor-free" -- Del Griffith

VideoReDo users: Try To view links or images in signatures your post count must be 10 or greater. You currently have 0 posts.

pyTivo users: Try To view links or images in signatures your post count must be 10 or greater. You currently have 0 posts. and To view links or images in signatures your post count must be 10 or greater. You currently have 0 posts.

>> Did you use the same eSata drive dock when you imaged the original 1.5 TB drive in 2010?
I really have no idea if I used the same dock. I was just trying to avoid opening up a case and messing with Sata + power connectors. I can do that, I just went with the dock for simplicity.

I have a TiVo Series3 (OLED TCD648250B). In 2010 I updated the drive to a 1.5T WD EARS HD and expanded it up to the 1.26T capacity via WinMFS. I turned off intelipark via WDidle3 /d. This worked fine for 2.5 years. The S3 has recently begun to reboot and so I decided to just re-image a new drive. I took backups of my original 250G HD in 2010.

So I restore the image to another WD 1.5T with intelipark turned off, I answer yes to expand and then supersize it. Put it back into the Tivo and it reports 36 hrs of HD capacity, when I expect to see 157 Hrs.

I am following these steps here, exactly.

• In WinMFS, select File -> Select Drive and select the new replacement SATA drive
• In WinMFS, select File -> Restore and select the backup file you saved earlier. Click Start. This will restore the TiVo software to the new drive.

Note: Do not change the swap size. Leave it at the default of 128.
• When the restore is complete, WinMFS will ask you if you want to expand the drive to use the new space. Click Yes.

If you do not see this dialog box, then select Tools-> Mfsadd.
• Select Tools-> MfsSuperSize -> On.

I’ve done this half a dozen times now with different drives (all WD 1.5T) and I even downloaded a new version of winMFS ( beta 9.3f) and every time it does not show the expanded capacity to 157Hrs.

I am using an eSata drive dock and winMFs sees the drive just fine and does the image OK.

I tried to do the kickstart 54 and it just would not take, not sure what I was doing wrong there.

I downloaded a virgin image from a member here via dropbox for my S3 model, restored from that one too and it also reported 36 hrs.

What in the world am I doing wrong/missing? I don’t recall any of these issues when I did my upgrade in 2010.

I don't care about the content on the old 1.5T HD. I can get the S3 back up and running, but kinda wanted to get full use of the new 1.5T HD to get me back where I was before.

thanks for your help.

Was the TiVo software already updated to 11.0k before you imaged the original drive?

There's no reason that you have to keep the swap size the same (just don't make it smaller, but you can make it bigger if you want to).

Did you check to see if your power supply might be the reason for the reboots?

Was the TiVo software already updated to 11.0k before you imaged the original drive?

Yes/No - my 250 image was not 11.0k, but I also backed up the 1.5T HD with 11.0k. Same behavior with both

Quote:

Originally Posted by unitron

Did you check to see if your power supply might be the reason for the reboots?

The newly restored drives that report 36 hrs after a restore do not reboot. The problem is on my previous 1.5T drive. I put in on my WHS and ran Stablebit scanner on it. It reports bad sectors. I'd say the Tivo is trying to read these bad sectors and causes the reboot.

.... OK, got a new problem (or perhaps the real problem). I bypassed the eSata dock, open the tower case (core-i7 DT system) and connected directly to the internal Sata/power connectors. Run winMFS, select a drive and it hangs/fails - immediately reports GUI backup and restore to TIvo program is not working... Tried this with two different hard drives. Downloaded a new copy of winMFS from here: http://www.mfslive.org/forums/viewto...91fe70750e0519
to see if I had a bad .exe - same behavior.

Next steps, try another DT system and see if I can even get winMFS to select a drive without this error.

What the heck... I don't recall any of this drama 2.5 years ago. This should be simple. I just want a working Tivo with 200+ hrs of HD capacity.

OK, I finally got one of these hard drives (WD15EARS – I bought a case of 20 in 2010) to complete thru the process. I used WD lifeguard Diagnositic to view SMART (all OK), ran the write zeros test to the drive to clear it out. I ran winMFS, select drive, restore (using a clean image from a TC member for the S3 (OLED) with version 11.0j. Answered no to expand. Following this successful restore, I ran MSInfo, here’s the B4 report:

Results: newly Restored drive reports 237 Hrs HD, 2072 Hrs SD. Success.... but i get a tivo msg that report and error has been detected... #51. I reboot as needed and the error persists. Hmmm?

OK, i see a post that explains #51 is a mismatch on the disc and Tivo MB, which is prob due to me using the DL .tbk image file. Looks like a C&DE will clear it up. How many hours does that take again ?

C&D actually went pretty fast @ < 1h. I am up and running now with full expanded capacity of the 1.5T HD @ 237 hrs. Tivo no longer reports error #51.

My guess is 1) I had some bad hard drives that were causing winMFS to act up and/or 2) my previous backup images are corrupt. My final working drive was imaged from a new blank 648 image I sourced from a member here on TCF.

Like I said I don't care about preserving my previous programs, so this new image will be fine.

Not sure if it will completely boot up. It would be like trying to take your Windows XP drive off your Pentium III computer and placing in your new i7 computer. It may boot up or blue screen. If it boots it will limp along because it does not have the drivers to fully support the computer.

__________________
"Delay is preferable to error" - Thomas Jefferson
"If I have seen further it is by standing on the shoulders of Giants" - Sir Isaac Newton