TiVo Community Forums Archives - Another CD restore failure message!

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

Another CD restore failure message!
(Click here to view the original thread with full colors/images)

Posted by: scout 73

I have been trying to restore a hard drive with my tivo.bak. I am getting a message error:

(This error happens at 64 of 816 megabytes)

Cleaning up restore. Please wait

Restore failure: Premature end of backup data.

Has anyone come across this error and know what is causing it??

My Tivo.bak is 167,541 Kb.

tnks
scout 73

Posted by: Robert S

The message is clear enough. Your backup file ends before MFS Tools thinks it should. You'll have to try another file.

Posted by: scout 73

Thks for answering Robert, Yea I knew what the message was telling me, I was just curious as to what was causing it ( bad file) so that maybe in the future there was something I could look for to prevent this.

Maybe its just the way it is sometimes.

Anyhow tnks again.

Scout 73

Posted by: scout 73

Robert S,

Got it working-it was the way I mounted, I used Hda1 instead of Hda2.

Once I corrected that everything went smooth, I am now up and running.

Scout 73

Posted by: moonslice

I got the same message after downloading a backup image to my XP drive, and trying to restore. 183 of 960 megabytes, then "cleaning up restore, restore failed: premature end of backup data

Should I also try hda2? What's the difference between hda1 and hda2?

Posted by: Robert S

Probably not. I think what happened here was that scout had a hidden partition on his hard drive that wasn't big enough to hold the output from mfsbackup. hda2 was his C: drive and thus had enough space to hold the full backup.

Having downloaded a backup, I think we can assume that there was enough space on the drive for it. You either didn't get is all or it was corrupted in some way.

Was this an image you downloaded as a .bak file, or as one or more RAR files?

Posted by: moonslice

The one that couldn't complete restore was the hd112 3.0 one (from abs.net) that had 10 rar files - I used WinRAR and first clicked on the zip to open it to 10 rar files and then clicked on part 1.rar which appeared to meld all 10 together into a 148mb file, and then clicked again on that to extract it. I re-downloaded it just in case the download was corrupted, but i got the exact same error message.

I also tried downloading a version hd212 2.1 which downloaded straight as a .bak file. But when i tried to restore that one, it said "can't find file". I had it named tivo212.bak. (Is it possible msf can't recognize numbers?). I re-downloaded that again and named it tivoearliest.bak, but haven't had time to try that yet.

Posted by: moonslice

I must be doing something wrong, as not matter what i name a backup file (other than tivo.bak), mfsrestore says it can't find it (I put it in my root C).

BUT... even if i have NO file named tivo.bak (in root C), it starts to do a restore anyway, but then "fails" after 11% is done. These are my steps:

1) downloaded clean mfs 1.0 backups (hd112, hd212, hd312) from internet site
2) extracted those files and put in my root of C drive - Primary Master (hda)
new tivo drive is Primary Slave (hdb)
I'm on WinXP, with 40gig C drive with 21gig free
3) boot from mfs 2.0 CD
4) # mkdir /mnt/dos
# mount /dev/hda1 /mnt/dos
5) # mfsrestore -s 127 -xzpi /mnt/dos/tivo.bak /dev/hdb

So is there an obvious error here? Is my problem WinXP?

Thanks!!!!

Posted by: Robert S

As you know, I recommend temporarily renaming the file you're going to restore to c:\tivo.bak so you can use the command precisely as in Hinsdale.

As you didn't attempt to reproduce the command lines you typed it's impossible to tell where the problem lies.

There are no issues with numeric characters in Unix file names.

If you do ls (that's LS in lowercase) it lists the files in the current directory. ls /mnt/dos should list the files in the root of your C: drive is all is working well.

It is possible that you haven't got vfat long name support working, so your correct filename would be something like tivo21~1.bak.

You can get long filenames working by modifying the mount command:

mount -t vfat /dev/hda1 /mnt/dos

or just use the munged version of the filename (ls will tell you what it is).

Posted by: moonslice

hi robert,

I was JUST editing my reply above yours while you were posting yours. See the info in that reply just above yours.

Posted by: moonslice

While waiting for your response, i went and did an ls. In xp I had tivo212.bak and tivo.bak. When i looked at it thru ls on the CD boot, it ONLY showed tivo.bak.

BUT **** when i renamed tivo.bak to tivoa.bak (in XP), and then did an ls, it STILL showed a tivo.bak, even though there WAS NO tivo.bak on my C drive. (and of course none of the other bak's showed up at all)

Posted by: Robert S

Weird.

Try burning the images on to a CD, but keep the names in 8.3 format. Then you should be able to mount /dev/hdd and read the files from the CD, avoiding what appear to be problems with NTFS partition.

Posted by: moonslice

What is 8.3 format? (btw all my names are less than 8 characters)

Is this correct?
1) boot from mfs CD
2) take out mfs CD and put in CD with backup images
3) mkdir /mnt/dos
4) mount /dev/hdc /mnt/dos (my CD is master secondary)
5) mfsrestore -s 127 -xzpi /mnt/dos/tivo.bak /dev/hdb

Posted by: Robert S

Yeah, 8.3 is shorthand for 'no more than eight characters, followed by a dot, followed by three more characters'. ISO9660 only supports 8.3 names - the Joliet and Rock Ridge extentions fix that.

Your command sequence is correct.

Posted by: moonslice

It worked!!!! 142 hours of recording bliss.

Thank you, thank you, thank you.

Going the route of backing up to the cd insted of a PC hard drive seems like the best solution all-around, as
a) lots of people have XP now, and it would avoid all the problems associated with that
b) you would want to have a backup on cd anyway for future use/emergencies.