TiVo Community Forums Archives - Backup failed, HD erased?

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

Backup failed, HD erased?
(Click here to view the original thread with full colors/images)

Posted by: loosetoe

Hi,
I just upgraded my Tivo, and all is working well. However, there was a casualty in the process. I tried to backup to a fat32 HD and received the message "backup failed read only tivo.bak" or something roughly equivalent. I didn't mark it down because I didn't notice the problem until today.

I ended up backing up to a different HD to complete the process and all went smoothly.

Now, however, all the files from the first HD I tried are gone. The disk still says it's 36GB full, but the files are all gone. There are only a couple strange looking 0 byte files named with a box character.

AFTER trying the backup, I did an ls-l on the HD to see if the tivo.bak file made it despite the failure message. It appeared as a 0 byte file and all the other stuff was still there.

Suggestions on how to get my data back? This could really be bad.... Any ideas appreciated.

Posted by: Robert S

Have you tried copying the files to another hard drive under Linux? The Linux copy command is cp source destination

Posted by: loosetoe

just ran scandisk as per your other post.

now I have a folder called found.000 and 10000 files in it names fileXXXX.CHK.

What can I do with these? Based on the file size, I can guess what some of them are, but not many.

As for a linux copy, that's probably been nixed by the scandisk, right?

I really appreciate your help, by the way. It's great to have someone to ask about these things.

Posted by: Robert S

Oh dear, I wish I'd suggested using Linux first. You'll probably find that those CHK files are just fragments of your former files.

You've been very unlucky, Linux is actually very reliable indeed. Did you forget to umount your hard disk before you rebooted?