Panasonic DMR hard drive data recovery - It CAN be done!! - Page 6 - AVS Forum
Forum Jump: 
Reply
 
Thread Tools
post #151 of 156 Old 04-15-2014, 03:40 PM
Senior Member
 
mickinct's Avatar
 
Join Date: Nov 2005
Posts: 465
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Quoted: 1 Post(s)
Liked: 13
Sorry to say that the eh55 and eh75 drives can not be done this way tried many many times, no luck.

MickinCT
mickinct is online now  
Sponsored Links
Advertisement
 
post #152 of 156 Old 04-15-2014, 03:47 PM
AVS Special Member
 
jjeff's Avatar
 
Join Date: Nov 2007
Location: Minneapolis MN
Posts: 9,635
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Quoted: 43 Post(s)
Liked: 80

Those instructions seem to have been written prior to the EH-55/75v models, Panasonic must have changed something in later models :(

jjeff is online now  
post #153 of 156 Old 04-19-2014, 04:42 AM
Newbie
 
Chanbara's Avatar
 
Join Date: Apr 2014
Posts: 3
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Quoted: 0 Post(s)
Liked: 10
Like others before me, finding this thread was an answer to my prayers. After my much loved and much used 10 year-old Panasonic DMR-E85H recorder became stuck in an endless "Please Wait..." loop, and being told by the repair technician that it needed a full drive replacement and that there was no way to get anything off of my 120GB (really 111GB) HDD, I was sick. Then I found this thread and suddenly there was hope that I could still get my lost recordings.

Reading through the various posts it seemed a daunting task at first, particularly when it looked like I’d need to gather up and work with Hexadecimal codes, but then as I continued to read through more posts by posters like worley45, im2020, and 0x1BBE898 it looked much easier than expected. A huge thanks to all who contributed to creating a process to salvage our HDDs. Absolutely brilliant!

I followed the instructions in the post by PC7211, and was able to get a full image of my HDD. I installed and ran the python scripts and everything was going smoothly until I hit a snafu during the final export process.

It exported the first 93 files which totaled up to 11GB (I have a lot of short segments and interview clips from various programs), before the script spit out the following errors and stopped running:

Exporting file #94
Traceback (most recent call last):
File "dvr-recover.py", line 1161, in
Main().run()
File "dvr-recover.py", line 1152, in run
func()
File "dvr-recover.py", line 1127, in export
export_file(chunk, index)
File "dvr-recover.py", line 1117, in export_file
export_chunk(reader, outf, chunk, 1)
File "dvr-recover.py", line 1101, in export_chunk
speed = float(chunk.block_size) / float(delta)
ZeroDivisionError: float division by zero

I’m really hoping someone can tell me what I can do to get over this hurdle and have the script run successfully so that it can hopefully export the remaining 100GB.

Any help would be much appreciated. Thanks in advance.
Chanbara is offline  
post #154 of 156 Old 04-19-2014, 01:54 PM
Senior Member
 
mickinct's Avatar
 
Join Date: Nov 2005
Posts: 465
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Quoted: 1 Post(s)
Liked: 13
YOUR machine is repairable, send me a PM for more info.

MickinCT
mickinct is online now  
post #155 of 156 Old 04-19-2014, 05:36 PM
Newbie
 
Chanbara's Avatar
 
Join Date: Apr 2014
Posts: 3
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Quoted: 0 Post(s)
Liked: 10
Quote:
Originally Posted by mickinct View Post

YOUR machine is repairable, send me a PM for more info.

 



Really? Man, I wish I'd known about this a few weeks back. I've already gotten replacements for my recording needs, so at this point my main goal is to just hopefully get the content of my HDD copied over. Still, I'm intrigued so will follow-up with a PM.

I decided to try the process over again, this time with min_chunk_size set to something higher than 0, hoping this might make the script ignore what looks to be a problematic spot. Unfortunately, 6 hours later I got the same error at the same spot (after copying 11.7GB of data - first attempt got 11.6GB). The only slight difference was in the number of files created (71 instead of 93).

Here's what it spit up when it stopped running:

Exporting file #71
Part #1: 0.03s (7741.96 blocks/s; 15.12 MiB/s).
Traceback (most recent call last):
File "dvr-recover.py", line 1161, in
Main().run()
File "dvr-recover.py", line 1152, in run
func()
File "dvr-recover.py", line 1127, in export
export_file(chunk, index)
File "dvr-recover.py", line 1117, in export_file
export_chunk(reader, outf, chunk, 1)
File "dvr-recover.py", line 1109, in export_chunk
export_chunk(reader, outf, chunk2, part+1)
File "dvr-recover.py", line 1101, in export_chunk
speed = float(chunk.block_size) / float(delta)
ZeroDivisionError: float division by zero

I can't help thinking that if the script could just skip over this file/section on the HDD, it would keep going and copy over the rest. I saw that the author of dvr-recover had a contact email in the readme file, so I'm hoping he may have a solution, or someone else who sees this will.

Keeping my fingers crossed...
Chanbara is offline  
post #156 of 156 Old 04-21-2014, 11:36 AM
Newbie
 
Chanbara's Avatar
 
Join Date: Apr 2014
Posts: 3
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Quoted: 0 Post(s)
Liked: 10
UPDATE: I've made a little progress, in that I was able to create a script to run the export command on each block one by one.

The answer to how to do this was in the readme file:

"You can also specify a chunk id to export. In this example the script would export only the chunk with the id 4 (including the chunks which should be concatenated to this one)."
python dvr-recover.py export 4

I'm not sure how I missed it, but taking this into account I created a DOS batch file called finish.bat containing one line for each of the remaining chunks:

python dvr-recover.py export 72
python dvr-recover.py export 73
python dvr-recover.py export 74
python dvr-recover.py export 75
etc...

I then ran it using the following command which put all the output messaging text (including error messages - so I could check if any failed) to a log file:

finish 1> log.txt 2>&1

Once it was complete I got a total of 1598 files and 172 GB of data recovered. This had me scratching my head since my HDD is only 111 GB. Going through the files, I spotted more than a few duplicates (some full, some partial), so it's hard to tell how much I truly got extracted.

When I started putting the pieces together on a bunch of hour-long programs, I noticed something even stranger and more troubling. All of them only had the first 20 minutes or so. Some of them were split up into multiple files, and a couple were single files, but they're all missing the last 38-42 minutes!

The log.txt file had a full rundown of what transpired so I was able to check if any other blocks had the same ZeroDivisionError that # 71 did. All told there were 110 exports that failed due to this same error, which I can only assume is a bug in the script.

Anyway, I'm still hoping to hear back from the author of the script, or someone else who may have an idea how to fix this bug or at least offer an explanation as to why I'm getting these ZeroDivisionErrors when no one else who previously used it did...

Thanks.
Chanbara is offline  
Reply DVD Recorders (Standard Def)

User Tag List

Thread Tools
Show Printable Version Show Printable Version
Email this Page Email this Page


Forum Jump: 

Posting Rules  
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are Off
Pingbacks are Off
Refbacks are Off