PVR hard drive Wester Digital WD1600AVBB fail

[fzabkar]

Offsets 0x38 - 0x3B appear to hold the cluster size for the "Standard File System" partition, namely 0x20000 (= 128KiB).

Offsets 0x3C - 0x3F appear to hold the number of clusters in the partition, namely 0x8000 (= 32K).

That amounts to a partition size of 4GiB.

Similarly, offsets 0xA0 and 0xA4 hold the cluster size and the number of clusters in the "AV PES/TS File System" partition, namely 0x4000000 (= 64M ) and 0x908, respectively.

That amounts to a partition size of 144.5GiB.

[Vilpo]

I PM:d michael. Prior to shipping to him, i was able to recover a few of the mp3:s on the drive using Photorec with the ext2/ext3 option, so it uses Linux file system? I have not had the drive connected to my computer in the past, so im not sure which drivers to use...

[fzabkar]

Photorec recovers files in raw mode. It doesn't care about the file system. In any case the file system is not a Linux type -- it is a proprietary format.

To mount your PVR drive in a Windows box, just use the "Fusion Filesystem Reader". You don't need any data recovery software.

[michael chiklis]

fzabkar is right, this is not linux filesystem so can't be loaded on linux OS.
Also, photorec is for files recovery in raw mode, we need some type of tool which is able to emulate the pvr partition in windows so then we will be able to see folders and files.
I downloaded the Fusion Filesystem Reader:
http://www.hope.co.nz/projects/fusion/

but seems not working, it's not able to read the boot sector

[michael chiklis]

Answering to Vilpo PM...

Photorec just does a file search on the hard drive surface, this is called "RAW recovery" or "file carving".
Raw recovery doesn't read through filesystem, this means that recovered files might result corrupt due to file fragmentation, and can't read files name or folders.
Reading via filesystem is the best way, so we will be able to see all files inside folders as they are!

I can't find any pvr emulator for this proprietary filesystem, this means that is not possible to see what's inside the drive with a computer.
You have to attach again the drive into your pvr machine and see from there (i'm pretty sure it will work right away), it should work because now the drive is phisically good and i was able to see the filesystem code in R-Studio.

"usbexplorer" is a tool needed just for file conversion when you attach the pvr recorder to the computer via usb, i don't have your pvr recorder so i'm not able to see folders and files inside.

Also, your pvr may be faulty (maybe the power supply is not working good).
Have you measured voltages with multimiter when the pvr was on with a drive inside?
11.76v it's ok but you have to measure it when there is a drive attached inside, if goes under 11.7v when the drive is attached then most likely the pvr power supply is faulty.

Do not attach any of your computer data drive inside the pvr machine because as i know some of these pvr do format the drive MBR and filesystem with proprietary filesystem in the instant you turn it on, data would be lost!

[michael chiklis]

I did file carving with R-Studio and i was able to recover videos and MP3, now we can say that the case is closed, it only remains to reinsert the HDD in the PVR.

[fzabkar]

I downloaded the Fusion Filesystem Reader:
http://www.hope.co.nz/projects/fusion/

but seems not working, it's not able to read the boot sector

What happens if you ignore the warning? Could you upload the first 16 sectors in BIN form? I'm wondering whether the "boot signature" is actually a checksum.

In any case ISTM that the similarity between the OP's file system and that which is described on Daniel Hope's web page is too much to dismiss lightly. In fact the cluster sizes and partition sizes that I've calculated correspond exactly to those in Daniel Hope's screenshots.

See these two threads:
http://forums.digitalspy.co.uk/showthread.php?t=297712
http://forums.digitalspy.co.uk/showthread.php?t=297714

They talk about a second data extraction tool (Syphon):

http://web.archive.org/web/201203260221 ... rg/Syphon/
http://web.archive.org/web/200711051603 ... 0.1.20.zip

[michael chiklis]

What happens if you ignore the warning?

It happens nothing, see the pic:

Could you upload the first 16 sectors in BIN form? I'm wondering whether the "boot signature" is actually a checksum.

WDC WD1600AVBB-63SYA0.rar

(383 Bytes) Downloaded 695 times

They talk about a second data extraction tool (Syphon):

http://web.archive.org/web/201203260221 ... rg/Syphon/
http://web.archive.org/web/200711051603 ... 0.1.20.zip

I used also the second tool, the pvr partition s still not detect in windows but i can see some infos:

[fzabkar]

I've been in touch with the author of the Fusion reader (Daniel Hope) and he has kindly given me the boot sector information from his source code (I'm waiting for his permission to publish it). The structure appears to be identical to that in the Syphon screenshot. The boot signature in the Fusion PVRs was 0x31415926 (the value of pi) rather than the OP's 0x11115921, so that accounts for the warning message.

I'm still waiting for confirmation from Daniel, but I suspect that the reason that the Fusion screenshot shows blank partition information may be that it doesn't recognise the partition ID bytes. Offsets 0x30 and 0x98 contain partition IDs of 0x0B for each of the 2 partitions whereas the Fusion reader recognises the following 3 PVR brands and partition IDs:

Code:

Fusion / Thomson            Digiality                  Nokia 260T
Std FS       A/V FS         Std FS       A/V FS        Std FS      A/V FS
0x0000000C   0x00000008     0x00000009   0x00000008    0x0000000D  0x00000008

Perhaps you could edit those 2 bytes in sector 0 and try the Fusion reader again? Otherwise there may be a workaround in the Syphon threads at Digitalspy. I would run the program natively on a Windows XP platform rather than in compatibility mode in later Windows versions, assuming that's what you've done.

BTW, the Syphon source code was published at the following URL, but unfortunately the link is dead and the Wayback Machine hasn't archived it.

http://www.eccleson.org/Syphon/Source_0.1.20.zip

[michael chiklis]

Thank you fzabkar for your help, however i think now the best thing to do is to insert again the drive in his pvr recorder and see if it will be detect, it should work...
I shipped it to Vilpo today

[fzabkar]

Here is the boot sector structure (with the author's permission):

Code:

/**
* Fusion Viewer Project
*
* Tool to view the drive contents of the Fusion FVRT100 PVR hard drive
*
* fusion.h - Contains common definitions for fusion drive layout
*
* $Revision: 1.9 $
* $Date: 2007/08/27 20:58:35 $
* $Author: danielh $
* $Log: fusion.h,v $
* Revision 1.9  2007/08/27 20:58:35  danielh
* Version 0.98 (27 August 2007)
*
* Revision 1.8  2007/08/27 16:18:28  danielh
* Version 0.98 (27 August 2007)
*
* Revision 1.7  2006/07/17 22:03:26  danielh
* Increase version to 0.9.7
*
* Revision 1.6  2006/04/14 19:18:34  danielh
* Win95 support
*
* Revision 1.5  2006/01/31 02:02:33  danielh
* Digiality support
* Version 0.9.6
*
* Revision 1.4  2006/01/11 02:22:24  danielh
* Update version to 0.9.5
*
* Revision 1.3  2005/12/30 21:15:24  danielh
* Changes to compile on linux
*
* Revision 1.2  2005/10/21 04:37:58  danielh
* 0.92
*
* Revision 1.1  2005/10/06 20:33:41  danielh
* Initial Revision
*
*
*
* Copyright: (c) 2005 Daniel Hope http://www.hope.co.nz
*/
#ifndef _FUSION_H_
#define _FUSION_H_

#define FUSION_PRODUCT     "DigiFusion FVRT100 File System Reader"
#define FUSION_VERSION     "0.9.8"
#define FUSION_VERDATE     "27 August 2007"
#define FUSION_COPYRIGHT   "Copyright 2007 Daniel Hope"

#include "ftypes.h"

#define SECTOR_SIZE 512

typedef struct tagFATHEADER {
   uint8 fat_sequence[4];        // FAT sequence number
   uint8 directory_sequence[4];  // Root directory sequence number
   uint8 signature[4];           // always 0x12345678
   uint8 clusters_used[4];
   uint8 unused[0x0200];
   uint8 cluster_size[4];
   uint8 cluster_count[4];
} FATHEADER; // 0x218 = 536 bytes

#define PARTTYPE_STANDARD   0x0000000C
#define PARTTYPE_DIGIALITY  0x00000009
#define PARTTYPE_NOKIA      0x0000000D
#define PARTTYPE_AV         0x00000008

typedef struct tagPARTITION {  //   Fusion / Thomson          // Digiality
// Nokia 260T
   uint32 unknown0;           // 0x00000001   0x00000001     0x00000001
0x00000001   0x00000001  0x00000001
   char fs_name[32];          // Std FS       A/V FS         Std FS       A/V
FS       Std FS      A/V FS
   uint32 part_type;          // 0x0000000C   0x00000008     0x00000009
0x00000008   0x0000000D  0x00000008
   uint32 unknown2;           // 0x00000FFF   0x000000FF     0x000001FF
0x000000FF   0x00001FFF  0x000000FF
   uint32 cluster_size;       // 0x00020000   0x04000000     0x00008000
0x04000000   0x00020000  0x04000000
   uint32 cluster_count;      // 0x00008000   0x00000212     0x00000400
0x00000726   0x00003000  0x0000048E
   uint32 unknown5;           // 0x00000004   0x00000004     0x00000004
0x00000004   0x00000004  0x00000004
   uint32 max_files;          // 0x00001000   0x00000100     0x00000200
0x00000100   0x00002000  0x00000100
   uint32 fat_count;          // 0x00000004   0x00000004     0x00000004
0x00000004   0x00000004  0x00000004
   uint32 fat_sector;         // 0x00000010   0x00821030     0x00000010
0x00010220   0x00000010  0x00321CF0
   uint32 fat_length;         // 0x00010400   0x00007800     0x00000C00
0x00019400   0x00006400  0x00010200
   uint32 directory_sector;   // 0x00000220   0x00821120     0x00000030
0x00010550   0x000000E0  0x00321F00
   uint32 directory_size;     // 0x0001C200   0x0000D200     0x00003A00
0x0000D200   0x00038200  0x0000D200
   uint32 first_data_sector;  // 0x00001030   0x008217B0     0x00000200
0x00010BE0   0x00001CF0  0x00322590
   uint32 last_data_sector;   // 0x00801030   0x04A617B0     0x00010200
0x0E4D0BE0   0x00301CF0  0x094E2590
   uint32 unknown14;          // 0x00000001   0x00000000     0x00000001
0x00000000   0x00000001  0x00000000
   uint32 unknown15;          // 0x00821030   0x00000000     0x00010200
0x00000000   0x00301CF0  0x00000000
   uint32 unknown16;          // 0x00200000   0x00000000     0x00000020
0x00000000   0x00020000  0x00000000
   uint32 unknown17;          // 0x00821030   0x00000000     0x00010200
0x00000000   0x00321CF0  0x00000000
} PARTITION; // 104 bytes = 0x68 bytes


#define BOOT_SIGNATURE 0x31415926

typedef struct tagBOOTSECTOR {
   uint16     init_date;         // EPG style date
   uint16     zero1;
   uint32     signature;         // signature - 0x31415926
   uint32     sector_count;
   PARTITION  partition1;
   PARTITION  partition2;
   uint8      padding1[4];       // 0 filled
   uint8      av_direntry[0xD0]; // see fsav.h for definition - actually -
this is likely just junk...
   uint8      padding2[80];
} BOOTSECTOR;


#endif /* _FUSION_H_ */

He says that hacking the boot sector would have been worth a try.

[michael chiklis]

I really don't know how to hack the boot sector, however i already shipped back the drive to Vilpo.

[Dmitri]

I have a problem with the Hard drive of my Vision 4400 pvr

Seeing that michael chiklis has finished working, I'm curious to ask: what exactly device you refer as PVR?

Is it some device used to record television programs on demand or it is security surveillance system, which records video streams from multiple cameras (usually in H.264) and frequently called DVR?

I ask because Vision brand isn't marketed here and if it is the latter, then we are likely to be able to help, depending on what your goal is: just to repair the hard drive or to recover the videos?

We do digital video recorder recoveries (the ones, which are security surveillance systems) for both physically damaged DVR hard drives and logical problems.
But that's not so obvious task, as due to the insane format diversity and complete lack of standards we basically have to develop a custom data extraction utility for each job after performing initial data analysis. So a bit more input from you would be appreciated.

[fzabkar]

Is it some device used to record television programs on demand ...

I have a problem with the Hard drive of my Vision 4400pvr -set top box ...

[Vilpo]

Is it some device used to record television programs on demand ...

I have a problem with the Hard drive of my Vision 4400pvr -set top box ...

Yes, that's correct. It's a set top box to record programs on digital television channels. My first priority is to recover videos from the drive.
Vision or Division is a brand not much used in other countries but Finland, to my knowledge. From what i hear, Medion 4400 is pretty much the same device as this, only different name.
One thing i noticed weird about the pvr is that the +12v coming to the hdd is only at 11,76 volts at the moment. The +5v seems fine at little over 5 volts.
But im wondering if this could have contributed to the hard drive pcb failure in the first place..?
Still waiting for the drive being shipped back from Michael, should be here next week, i will post results once i get a chance to test it in the pvr.

[fzabkar]

The user manuals for the Medion and Vision 4400 PVRs look very similar.

Vision VDC 4400 PVR User Manual:
http://fi.pdf-instructions.com/dref/3242870

Medion MDC 4400 PVR User Manual:
http://fi.pdf-instructions.com/dref/3828722

Photos of Medion MDC 4400:
http://cache.osta.ee/iv2/auctions/1_1_17598185.jpg (inside)
http://cache.osta.ee/iv2/auctions/1_1_17598192.jpg (rear panel)
http://cache.osta.ee/iv2/auctions/1_1_17598189.jpg (front slots)
http://cache.osta.ee/iv2/auctions/1_1_17598186.jpg (front panel)

AFAIK, Medion is an Aldi supermarket brand. I have a Tevion DVD/HDD recorder which is also an Aldi trademark. My Tevion is just an OEM version of a Chinese brand, with a different front panel. The same device was also OEM-ed by Salora. In fact the Salora service manual is applicable to my Tevion.

Page 46 of the Medion 4400 manual refers to a firmware upgrade file named "ODC7200CPVR_V0075.pgm". This would suggest that your PVR may be an OEM version of Opentech's ODC7200CPVR. In fact their rear panels appear identical. The front panel differs cosmetically, but I suspect that it is functionally identical.

Opentel/Opentech ODC7200CPVR:
http://www.tele-satellite.com/TELE-sate ... entech.pdf (review)
http://web.archive.org/web/200606282020 ... asp?no=288 (brochure)
http://web.archive.org/web/200607191828 ... stb40.html (product specs)

[Vilpo]

The user manuals for the Medion and Vision 4400 PVRs look very similar.

Vision VDC 4400 PVR User Manual:
http://fi.pdf-instructions.com/dref/3242870

Medion MDC 4400 PVR User Manual:
http://fi.pdf-instructions.com/dref/3828722

Photos of Medion MDC 4400:
http://cache.osta.ee/iv2/auctions/1_1_17598185.jpg (inside)
http://cache.osta.ee/iv2/auctions/1_1_17598192.jpg (rear panel)
http://cache.osta.ee/iv2/auctions/1_1_17598189.jpg (front slots)
http://cache.osta.ee/iv2/auctions/1_1_17598186.jpg (front panel)

AFAIK, Medion is an Aldi supermarket brand. I have a Tevion DVD/HDD recorder which is also an Aldi trademark. My Tevion is just an OEM version of a Chinese brand, with a different front panel. The same device was also OEM-ed by Salora. In fact the Salora service manual is applicable to my Tevion.

Page 46 of the Medion 4400 manual refers to a firmware upgrade file named "ODC7200CPVR_V0075.pgm". This would suggest that your PVR may be an OEM version of Opentech's ODC7200CPVR. In fact their rear panels appear identical. The front panel differs cosmetically, but I suspect that it is functionally identical.

Opentel/Opentech ODC7200CPVR:
http://www.tele-satellite.com/TELE-sate ... entech.pdf (review)
http://web.archive.org/web/200606282020 ... asp?no=288 (brochure)
http://web.archive.org/web/200607191828 ... stb40.html (product specs)

Thanks for the info, fzabkar!
Infact, from your pictures, my pvr is identical to medion 4400. Outside and inside, only name is different. Also opentel looks very much similar, same remote.
Does this tell anyone anything about the file system?

[Dmitri]

set top box ...

Thanks, fzabkar, with the pictures you've posted it's obvious what this topic is about. I've never heard "set top box" term previously (that's why I skipped it in my quote above) and would expect something like "receiver" or "tuner" for the device pictured (and here we use a completely different word for them).

My first priority is to recover videos from the drive.

Thanks, I believe we should be able to help with this, please check your PMs.

i will post results once i get a chance to test it in the pvr.

If possible, please make a full sector-by-sector image of the drive before doing anything with the drive.
With DVRs it isn't uncommon for us to face the situation when users do something with the drive in DVR or initialize it in Windows. That affects the data stored, making recovery more difficult.

Does this tell anyone anything about the file system?

I can't tell for sure about the PVR, but DVRs don't have any file system in the traditional meaning of this term.
That's why it's impossible even just to tell quickly which dates available on the DVR drive, and it's necessary to "jump" between the entries manually through the raw data.

[Vilpo]

Ok, i just want to update this thread.
I was able to recover the necessary files. After michael chiklis replaced the pcb for me, i was able to put the drive back in the pvr and it was working normally again, everything still there.
So i used usb cable to transfer files to pc.
Thanks to everyone who helped track down the broken pcb issue and helped otherwise.

[michael chiklis]

nice to hear it!