TiVo Community Forums Archives - Problem Backing Up New SVR-2000 w/MFSTools

TiVoCommunity.com
(c)opyright 1995-2005 All rights reserved
indexcheckTC
This area is a static history of posts in the TiVo Community Forum Archive.
This archive history was made for the simple indexing of search sites like Google.

Pages:1

Problem Backing Up New SVR-2000 w/MFSTools
(Click here to view the original thread with full colors/images)

Posted by: Ophelio

I just purchased a new Sony SVR-2000 (v2.5.1) and it was shipped with a Maxtor 40GB HDD. I pulled the drive and put it into my PC as per Hinsdale's Upgrade FAQ. The BIOS autodetected it and I booted from the boot CD. Linux reported my TiVo drive size as 10MB, so I rebooted and ran qunlock from DOS. I cycled the power, and upon booting my BIOS failed to autodetect the TiVo drive with it unlocked. I turned off the autodetection and booted from the boot CD again. Linux now reported the full size (40GB).

I ran mfstool per the FAQ, and it reported a total size of 819MB to be backed up. It took about 10-20 minutes and reported it was successful. I ended up with a backup file of 94MB which seemed smallish to me (this is my first TiVo).

I let TiVo make the 2 phone calls and the next day I re-pulled the drive and repeated the backing up process. To my surprise I had to run qunlock again...is this normal?

My second backup (again reported successful) stated the same 819MB size that ended up at 128MB. I gave a copy of my first backup to a friend to see if it would restore...it would not work in his SVR-2000 that was purchased in June (v1.3 s/w)...continually restarting with "a severe error message has occurred" message.

Does the qunlock work with the Maxtor? Any ideas as to what may be going on????

Posted by: RobD

Yes, it is normal to have to run qunlock every time you stick the drives back into a PC. Whenever the TiVo boots up from a drive, it re-locks them. But then, you saw that in my e-mail.

FYI - I helped Ophelio out by trying to restore his image to my SVR2000 last night. I had to restore it to my 80GB because it wouldn't fit on the Quantum 40GB I have. I then ran TiVoMad to add the remaining space of the 80 and the 40 to it. Both times I tried booting, the TiVo would get stuck in the endless green screen severe error reboot sequence.

Edit: Used Ophelio's handle instead of his real name, in case he didn't want that known.

Posted by: RobD

I can think of two reasons why, but can't prove why this didn't work.

1) His new Sony has some new PROM that is like the DirectTiVO, where the image only runs on his unit.

2) He has the same issue mentioned in the Hinsdale guide about 2.5.1(a) two-drive units. Maybe this new single drive unit with the 40GB drive is some sort of married 30GB+10GB mess?

Just some ideas. This guy wants to really start hacking his unit, and it would be nice if he could get a backup that he feels confident about. The fact that his image died on mine didn't instill any confidence in what he has!

Posted by: Want1394

Well, the Hinsdale instructions give a great procedure to feel good about the backup.

1. The backup sizes you report are probably just fine.

2. Restore the backup to the new expansion drive and use just it in the Tivo. Keep your original drive untouched for awhile. See that everything works ok. If yes, then continue. If no, :( then come back here and folks will help determine what the problem is.

Rob, neither of your postulations have been reported by anyone else. Of course, I don't know either why his backup image won't work in your machine, so .....

Posted by: c3

Does the image work if you don't run TiVoMad? TiVoMad does not work with the new layout of 13 partitions. I don't know if mfstool has problem with that as well.

Posted by: PVR Joe

I have been running into the same problem with a new SVR2000 w/40gb drive. I am trying to expand onto 2 120's. Except my backup will work just fine unit I try to expand it with MFS tools (Example the 120gb Disk will report 30 Hours) I have also noticed the locked drive everytime, same stats on the backup image and so on, production date on this tivo was 11/20/01. Any Ideas Folks?

Posted by: Ophelio

I've only had my TiVo for 1 week and I am not ready to upgrade just yet...however, I would like to have the warm and fuzzy that comes with knowing that my backup is a good one (read: tested), especially with me mucking about with an OS of which I know precious little!

I'm very happy with my TiVo, and I am very likely going to do the lifetime sub when my trial sub runs out next week, which would make a valid backup significantly more valuable. Also, the nightly phone call happens to be a "local" long distance call for me, so to avoid toll charges I plan to do the PPPoe hack...all of which precludes me from expanding my SVR2000 at the moment.

Maybe by the time I'm ready Hinsdale will have a work-around...

Posted by: PVR Joe

Just tried a older image I had, no dice, it's almost there! then shuts the fan down and continues to run the drives. 2.0.1 Grr Do I see an evil end on the way from Tivo?

Posted by: Ophelio

Does your backup image of v2.0.1 restore to its original size and function properly, and the boot failure occurs when you try to expand it? Does your image of v2.0.1 have the 13 partitions as well?

I wonder if you were to be fortunate enough to find a different image without the extra partitions if that would work?

Well, this issue has caused me to seriously rethink about subbing. I think I'll just wait awhile and see what shakes out of the tree on this.

Sorry, TiVo. If you guys are going to start coming down on the hackers, I'm going to have to keep your electronic hands off my box!

Posted by: hinsdale

Sony had a custom OS v2.0.2 that it was using exclusively on refurbs over the last couple months. Apparently this custom OS has been upgraded to 2.5.1 and they are using it in their new 2.5 production releases. The Sony OS now being used has 13 partitions and as far as I have determined the following applies:

This is so far a SONY only problem.

MFS Tools is apparently able to handle the partition structure and should make a working backup.

TiVoMad is not able to handle the partition structure and apparently will not function in its current form with the 13 partition Sony OS (although perhaps if you send Trevor a copy he could fix this relatively easily.. I believe).

I believe BlessTiVo should function for simple B drive addition upgrades.

The Boot CD would auto-unlock the original Quantum drives, however, will not unlock the Maxtors now being shipped. You will need to run the qunlock utility that is described in Step 4 of the How-To. Everytime you boot the drive in your TiVo it will be re-locked so you will need to run qunlock each time.

Posted by: deeremj

hinsdale,

Thanks for pulling this info together into 1 post.

Do we think that one of these 'new' sony sa boxes which shipped with 2.5.1-13 partitions will work ok if we load a prior version (i.e. 1.3 or 2.5.1 original)? I have heard of several people looking for an older backup. Can you or anyone else please let us know if they have tried it.

-Thank You - MJ

Posted by: RobD

I think Ophelio will be trying my 1.3 virgin image on his Sony when he gets in his drive for some testing. Since we can't be sure his backup is 100% yet, he isn't going to hack on his original drive (at least, I hope he doesn't!).

I'm glad we're starting to get this problem figured out!

Posted by: c3

quote:
Originally posted by hinsdale
The Boot CD would auto-unlock the original Quantum drives, however, will not unlock the Maxtors now being shipped. You will need to run the qunlock utility that is described in Step 4 of the How-To. Everytime you boot the drive in your TiVo it will be re-locked so you will need to run qunlock each time.

Only Quantum and "Quaxtor" drives (4KxxxHx) are lockable by TiVo. Auto drive locking can be disabled through the diagnostic menu if you have the need to do so.

Posted by: Jimland

Any word if anyone is working on a fix for upgrading a Sony 2.5.1 - 13 partition unit?