Do you have a link to the documentation on how to do a dump?
I'm not sure how its done. Thanks
SAGEM DTR67250
Forum rules
When asking for technical support:
- Search for posts on the same topic before posting a new question.
- Give clear, specific information in the title of your post.
- Include as many details as you can, MOST POSTS WILL GET ONLY ONE OR TWO ANSWERS.
- Post a follow up with a "Thank you" or "This worked!"
- When you learn something, use that knowledge to HELP ANOTHER USER LATER.
Before posting, please read https://www.cgsecurity.org/testdisk.pdf
When asking for technical support:
- Search for posts on the same topic before posting a new question.
- Give clear, specific information in the title of your post.
- Include as many details as you can, MOST POSTS WILL GET ONLY ONE OR TWO ANSWERS.
- Post a follow up with a "Thank you" or "This worked!"
- When you learn something, use that knowledge to HELP ANOTHER USER LATER.
Before posting, please read https://www.cgsecurity.org/testdisk.pdf
Re: SAGEM DTR67250
- Hex Dump of SAGEM sector 0
- sagem-sector-0.jpg (85.61 KiB) Viewed 7964 times
Re: SAGEM DTR67250
It's very curious. Your first sector does have a signature, but it's 0xAA55 instead of 0x55AA.
It may be because your enclosure use inversion in byte order.
At 0x1Bh, there's a partition begin :
80 (bootable)
0EFFFF : begin of partition (old MBR before 32GB limit)
0B : FAT32
0EFFFF : end (like above)
E0A3261B : number of sector before partition (usaly read last-to-first : 0x1B26A3E0) but that make no sense there
8675D101 : size of the partition (usaly read last-to-first : 0x01D17586) but... no sense too.
It looks like your MBR was written with ytorder inversion (big-endian) instead of the way it should be (little-endian).
How to deal with that ? I don't know... Please provide the same hexadecimal dump inside the enclosure, to see if there's a difference...
I'll ask Christophe if he has an idea how to solve this.
It may be because your enclosure use inversion in byte order.
At 0x1Bh, there's a partition begin :
80 (bootable)
0EFFFF : begin of partition (old MBR before 32GB limit)
0B : FAT32
0EFFFF : end (like above)
E0A3261B : number of sector before partition (usaly read last-to-first : 0x1B26A3E0) but that make no sense there
8675D101 : size of the partition (usaly read last-to-first : 0x01D17586) but... no sense too.
It looks like your MBR was written with ytorder inversion (big-endian) instead of the way it should be (little-endian).
How to deal with that ? I don't know... Please provide the same hexadecimal dump inside the enclosure, to see if there's a difference...
I'll ask Christophe if he has an idea how to solve this.
Re: SAGEM DTR67250
not sure what is meant by "inside the enclosure", so I'll give you sectors 1 to 256
Sector 3 is filled with 0x01
So has sector 4, all the way to sector 255. Sector 256 has data.
- SAGEM sector 1
- sagem-sector-1.jpg (90.38 KiB) Viewed 7960 times
- SAGEM sector 2
- sagem-sector-2.jpg (89.75 KiB) Viewed 7960 times
So has sector 4, all the way to sector 255. Sector 256 has data.
- SAGEM sector 256
- sagem-sector-256.jpg (86.12 KiB) Viewed 7960 times
Re: SAGEM DTR67250
sector 256 also has a signature AA55 instead of 55AA.
I've asked to Christophe, who told me that you'll have to duplicate your disk with dd tool (under gnu/linux) using option conv=swab.
Do you have a linux working and/or some knowledge about it ? If you try alone, be really carrefull with dd to copy source on destination, and not destination over the source...
I'll help you, but that's just to know what kind of help you'll need.
I've asked to Christophe, who told me that you'll have to duplicate your disk with dd tool (under gnu/linux) using option conv=swab.
Do you have a linux working and/or some knowledge about it ? If you try alone, be really carrefull with dd to copy source on destination, and not destination over the source...
I'll help you, but that's just to know what kind of help you'll need.
Re: SAGEM DTR67250
I dont have linux. I did make an image of the HD -- not too confident about the software, though, because half way through the copy, drive 0 disappeared from the list of HDs. But the operation did complete, and I've used the software before on other drives successfully.
I did a search for HDD1_AV1 and found a few links, notably
http://www.generationcable.net/gcmag_faq_tv.php, and http://wiki.lagamel.fr/doku.php?id=sage ... :disquedur
Phil78 on http://www.tvnt.net/forum/sagem-pvr-624 ... 3-135.html, suggests that sagem is using an Amiga file system.
I used iRecover, and although it found no files it did show that it had a 15Gb partition. Which seems to tally with what they say.
I've been assured that http://www.ezvan.fr/public/logiciels/papa/DVBT2MPG.ZIP will read sagem drives, but with my drive a message pops up stating that it cant find the DVBT stream on any devices.
I considered emailing him but his website is in French, I noticed, Remy, that your signature is in French. So, perhaps if you were to email him this may yield quick results.
I did a search for HDD1_AV1 and found a few links, notably
http://www.generationcable.net/gcmag_faq_tv.php, and http://wiki.lagamel.fr/doku.php?id=sage ... :disquedur
Phil78 on http://www.tvnt.net/forum/sagem-pvr-624 ... 3-135.html, suggests that sagem is using an Amiga file system.
I used iRecover, and although it found no files it did show that it had a 15Gb partition. Which seems to tally with what they say.
I've been assured that http://www.ezvan.fr/public/logiciels/papa/DVBT2MPG.ZIP will read sagem drives, but with my drive a message pops up stating that it cant find the DVBT stream on any devices.
I considered emailing him but his website is in French, I noticed, Remy, that your signature is in French. So, perhaps if you were to email him this may yield quick results.
Re: SAGEM DTR67250
I can try to contact him, but that won't be easy to explain a problem without having the disk and made a diagnose of it by myself. And the post you linked is 5 years old :/
In my opinion it may be esaier to drive you with some basic linux commands, so that you will be able to duplicate you disk using conversion to put bytes in a readable order and recover your data then with testdisk.
In my opinion it may be esaier to drive you with some basic linux commands, so that you will be able to duplicate you disk using conversion to put bytes in a readable order and recover your data then with testdisk.
Re: SAGEM DTR67250
is ubuntu ok, or does it have red hat?
I have a spare HD I can install the OS on.
Is there any other software I'll need to install?
I have a spare HD I can install the OS on.
Is there any other software I'll need to install?
Re: SAGEM DTR67250
Ubuntu, perfect.
Installation on spare HD : perfect (you'll have persistance of data, and will work quicker than a liveCD)
Other tools to install :
download testdisk 6.14 for linux after install, uncompress, and copy testdisk_static in your personal folder.
Then, connect your sagem, your disk for duplication, and give feedback for :
Installation on spare HD : perfect (you'll have persistance of data, and will work quicker than a liveCD)
Other tools to install :
download testdisk 6.14 for linux after install, uncompress, and copy testdisk_static in your personal folder.
Then, connect your sagem, your disk for duplication, and give feedback for :
Code: Select all
sudo sfdisk -luSRe: SAGEM DTR67250
The sfdisk shows
Disk /dev/sda: 30401 cylinders, 255 heads, 63 sectors/track
sfdisk: ERROR: sector 0 does not have an MSDOS signature
/dev/sda: unrecognised partition table type
No partitions found
Disk /dev/sda: 30401 cylinders, 255 heads, 63 sectors/track
sfdisk: ERROR: sector 0 does not have an MSDOS signature
/dev/sda: unrecognised partition table type
No partitions found