mount img from data recovery The 2019 Stack Overflow Developer Survey Results Are In Unicorn Meta Zoo #1: Why another podcast? Announcing the arrival of Valued Associate #679: Cesar Manara 2019 Community Moderator Election ResultsHow to mount sdb directly or using LVM partitions on sda?Overwritten superblock and dd backup files recoveryProblems with partition table on 3tb NTFS driveWhich sector size shall I choose to run ddrescue with direct access on an Advanced Format drive?Can't mount disksMount .img created by ddrescue-guiMounting a 4tb lvm in Centos 7 keeps saying not enough space on deviceFUSE exfat 1.2.8 ERROR: too small sector size: 2^0. Mount ErrorUsing gdisk on drive with valid MBR and corrupt GPTWrong fs type, bad option, bad superblock on /dev/sdX
Separating matrix elements by lines
Can I visit the Trinity College (Cambridge) library and see some of their rare books
Drawing vertical/oblique lines in Metrical tree (tikz-qtree, tipa)
Student Loan from years ago pops up and is taking my salary
What can I do if neighbor is blocking my solar panels intentionally?
Python - Fishing Simulator
Working through the single responsibility principle (SRP) in Python when calls are expensive
Sub-subscripts in strings cause different spacings than subscripts
Did the UK government pay "millions and millions of dollars" to try to snag Julian Assange?
Simulating Exploding Dice
University's motivation for having tenure-track positions
What's the point in a preamp?
Didn't get enough time to take a Coding Test - what to do now?
Are spiders unable to hurt humans, especially very small spiders?
ELI5: Why do they say that Israel would have been the fourth country to land a spacecraft on the Moon and why do they call it low cost?
Was credit for the black hole image misappropriated?
Keeping a retro style to sci-fi spaceships?
Can a flute soloist sit?
What happens to a Warlock's expended Spell Slots when they gain a Level?
Is this wall load bearing? Blueprints and photos attached
Deal with toxic manager when you can't quit
Example of compact Riemannian manifold with only one geodesic.
Does Parliament hold absolute power in the UK?
Did the new image of black hole confirm the general theory of relativity?
mount img from data recovery
The 2019 Stack Overflow Developer Survey Results Are In
Unicorn Meta Zoo #1: Why another podcast?
Announcing the arrival of Valued Associate #679: Cesar Manara
2019 Community Moderator Election ResultsHow to mount sdb directly or using LVM partitions on sda?Overwritten superblock and dd backup files recoveryProblems with partition table on 3tb NTFS driveWhich sector size shall I choose to run ddrescue with direct access on an Advanced Format drive?Can't mount disksMount .img created by ddrescue-guiMounting a 4tb lvm in Centos 7 keeps saying not enough space on deviceFUSE exfat 1.2.8 ERROR: too small sector size: 2^0. Mount ErrorUsing gdisk on drive with valid MBR and corrupt GPTWrong fs type, bad option, bad superblock on /dev/sdX
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;
This is my very first question in a forum, so please be patient with me.
So that's the situation :
win10 laptop with both ssd & hdd unmountable. I booted with live-debian and copied hdd with safecopy in an .img-file on external usb hdd. This worked, 100% copied, no bad blocks, no unrecoverable blocks, say's safecopy.
That is the output of file :
/media/tom/My Book/mdat.img: `DOS/MBR boot sector; partition 1 : ID=0xee, start-CHS (0x0,0,2), end-CHS (0x3ff,255,63), startsector 1, 976773167 sectors, extended partition table (last)`
This is from fdisk :
Command (m for help): p
Disk /media/tom/My Book/mdat.img: 465.8 GiB, 500107862016 bytes, 976773168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 4AAA6B26-E1FC-4335-BBF3-9456FC4F35C9
Device Start End Sectors Size Type
/media/tom/My Book/mdat.img1 2048 976771071 976769024 465.8G Microsoft basic data
Then I tried :
losetup -f --show -o 1048576 --sizelimit 976769024 mdat.img
/dev/loop0
mount -t ntfs-3g /dev/loop0 /mnt/meldat/
NTFS signature is missing.
Failed to mount '/dev/loop0': Das Argument ist ungültig
The device '/dev/loop0' doesn't seem to have a valid NTFS.
Maybe the wrong device is used? Or the whole disk instead of a
partition (e.g. /dev/sda, not /dev/sda1)? Or the other way around?
I have only basic Linux knowledge and non in data recovery (as you can see).
the more i search and read in the net the more confused i get. where do i go wrong ?
edit:
I tried gdisk as well, same result in the end :
gdisk mdat.img
GPT fdisk (gdisk) version 1.0.1
The protective MBR's 0xEE partition is oversized! Auto-repairing.
Partition table scan:
MBR: protective
BSD: not present
APM: not present
GPT: present
Found valid GPT with protective MBR; using GPT.
Command (? for help): i
Using 1
Partition GUID code: EBD0A0A2-B9E5-4433-87C0-68B6B72699C7 (Microsoft basic data)
Partition unique GUID: 66AD43C4-69FF-4274-B121-07462B71A1F1
First sector: 2048 (at 1024.0 KiB)
Last sector: 976771071 (at 465.8 GiB)
Partition size: 976769024 sectors (465.8 GiB)
Attribute flags: 0000000000000000
Partition name: 'Basic data partition'
mount data-recovery
edited 10 hours ago
Prabhjot Singh
155213
asked Apr 9 at 10:01
TomTom
63
New contributor
Tom is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
This is my very first question in a forum, so please be patient with me.
So that's the situation :
win10 laptop with both ssd & hdd unmountable. I booted with live-debian and copied hdd with safecopy in an .img-file on external usb hdd. This worked, 100% copied, no bad blocks, no unrecoverable blocks, say's safecopy.
That is the output of file :
/media/tom/My Book/mdat.img: `DOS/MBR boot sector; partition 1 : ID=0xee, start-CHS (0x0,0,2), end-CHS (0x3ff,255,63), startsector 1, 976773167 sectors, extended partition table (last)`
This is from fdisk :
Command (m for help): p
Disk /media/tom/My Book/mdat.img: 465.8 GiB, 500107862016 bytes, 976773168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 4AAA6B26-E1FC-4335-BBF3-9456FC4F35C9
Device Start End Sectors Size Type
/media/tom/My Book/mdat.img1 2048 976771071 976769024 465.8G Microsoft basic data
Then I tried :
losetup -f --show -o 1048576 --sizelimit 976769024 mdat.img
/dev/loop0
mount -t ntfs-3g /dev/loop0 /mnt/meldat/
NTFS signature is missing.
Failed to mount '/dev/loop0': Das Argument ist ungültig
The device '/dev/loop0' doesn't seem to have a valid NTFS.
Maybe the wrong device is used? Or the whole disk instead of a
partition (e.g. /dev/sda, not /dev/sda1)? Or the other way around?
I have only basic Linux knowledge and non in data recovery (as you can see).
the more i search and read in the net the more confused i get. where do i go wrong ?
edit:
I tried gdisk as well, same result in the end :
gdisk mdat.img
GPT fdisk (gdisk) version 1.0.1
The protective MBR's 0xEE partition is oversized! Auto-repairing.
Partition table scan:
MBR: protective
BSD: not present
APM: not present
GPT: present
Found valid GPT with protective MBR; using GPT.
Command (? for help): i
Using 1
Partition GUID code: EBD0A0A2-B9E5-4433-87C0-68B6B72699C7 (Microsoft basic data)
Partition unique GUID: 66AD43C4-69FF-4274-B121-07462B71A1F1
First sector: 2048 (at 1024.0 KiB)
Last sector: 976771071 (at 465.8 GiB)
Partition size: 976769024 sectors (465.8 GiB)
Attribute flags: 0000000000000000
Partition name: 'Basic data partition'
mount data-recovery
edited 10 hours ago
Prabhjot Singh
155213
asked Apr 9 at 10:01
TomTom
63
New contributor
Tom is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Nowadays there's often no need to play withlosetup -o,mountcan handle this:mount -o offset=$((2048*512)) …. I think you set--sizelimitwrong (you gave sectors instead of bytes; maybe yourlosetupis different than mine), but I'm not really sure this is the culprit. You said HDD was unmountable; so maybe the filesystem is corrupt and for this reason the image is unmountable.
– Kamil Maciorowski
Apr 9 at 10:30
Thank you for you're answer. you are right, i had wrong sizelimit, but even with correct(500'106'788'352) or with "mount -o loop,offset=1048576 mdat.img /mnt/meldat/" it did not work.
– Tom
Apr 9 at 12:00
add a comment |
This is my very first question in a forum, so please be patient with me.
So that's the situation :
win10 laptop with both ssd & hdd unmountable. I booted with live-debian and copied hdd with safecopy in an .img-file on external usb hdd. This worked, 100% copied, no bad blocks, no unrecoverable blocks, say's safecopy.
That is the output of file :
/media/tom/My Book/mdat.img: `DOS/MBR boot sector; partition 1 : ID=0xee, start-CHS (0x0,0,2), end-CHS (0x3ff,255,63), startsector 1, 976773167 sectors, extended partition table (last)`
This is from fdisk :
Command (m for help): p
Disk /media/tom/My Book/mdat.img: 465.8 GiB, 500107862016 bytes, 976773168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 4AAA6B26-E1FC-4335-BBF3-9456FC4F35C9
Device Start End Sectors Size Type
/media/tom/My Book/mdat.img1 2048 976771071 976769024 465.8G Microsoft basic data
Then I tried :
losetup -f --show -o 1048576 --sizelimit 976769024 mdat.img
/dev/loop0
mount -t ntfs-3g /dev/loop0 /mnt/meldat/
NTFS signature is missing.
Failed to mount '/dev/loop0': Das Argument ist ungültig
The device '/dev/loop0' doesn't seem to have a valid NTFS.
Maybe the wrong device is used? Or the whole disk instead of a
partition (e.g. /dev/sda, not /dev/sda1)? Or the other way around?
I have only basic Linux knowledge and non in data recovery (as you can see).
the more i search and read in the net the more confused i get. where do i go wrong ?
edit:
I tried gdisk as well, same result in the end :
gdisk mdat.img
GPT fdisk (gdisk) version 1.0.1
The protective MBR's 0xEE partition is oversized! Auto-repairing.
Partition table scan:
MBR: protective
BSD: not present
APM: not present
GPT: present
Found valid GPT with protective MBR; using GPT.
Command (? for help): i
Using 1
Partition GUID code: EBD0A0A2-B9E5-4433-87C0-68B6B72699C7 (Microsoft basic data)
Partition unique GUID: 66AD43C4-69FF-4274-B121-07462B71A1F1
First sector: 2048 (at 1024.0 KiB)
Last sector: 976771071 (at 465.8 GiB)
Partition size: 976769024 sectors (465.8 GiB)
Attribute flags: 0000000000000000
Partition name: 'Basic data partition'
mount data-recovery
edited 10 hours ago
Prabhjot Singh
155213
asked Apr 9 at 10:01
TomTom
63
New contributor
Tom is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
This is my very first question in a forum, so please be patient with me.
So that's the situation :
win10 laptop with both ssd & hdd unmountable. I booted with live-debian and copied hdd with safecopy in an .img-file on external usb hdd. This worked, 100% copied, no bad blocks, no unrecoverable blocks, say's safecopy.
That is the output of file :
/media/tom/My Book/mdat.img: `DOS/MBR boot sector; partition 1 : ID=0xee, start-CHS (0x0,0,2), end-CHS (0x3ff,255,63), startsector 1, 976773167 sectors, extended partition table (last)`
This is from fdisk :
Command (m for help): p
Disk /media/tom/My Book/mdat.img: 465.8 GiB, 500107862016 bytes, 976773168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 4AAA6B26-E1FC-4335-BBF3-9456FC4F35C9
Device Start End Sectors Size Type
/media/tom/My Book/mdat.img1 2048 976771071 976769024 465.8G Microsoft basic data
Then I tried :
losetup -f --show -o 1048576 --sizelimit 976769024 mdat.img
/dev/loop0
mount -t ntfs-3g /dev/loop0 /mnt/meldat/
NTFS signature is missing.
Failed to mount '/dev/loop0': Das Argument ist ungültig
The device '/dev/loop0' doesn't seem to have a valid NTFS.
Maybe the wrong device is used? Or the whole disk instead of a
partition (e.g. /dev/sda, not /dev/sda1)? Or the other way around?
I have only basic Linux knowledge and non in data recovery (as you can see).
the more i search and read in the net the more confused i get. where do i go wrong ?
edit:
I tried gdisk as well, same result in the end :
gdisk mdat.img
GPT fdisk (gdisk) version 1.0.1
The protective MBR's 0xEE partition is oversized! Auto-repairing.
Partition table scan:
MBR: protective
BSD: not present
APM: not present
GPT: present
Found valid GPT with protective MBR; using GPT.
Command (? for help): i
Using 1
Partition GUID code: EBD0A0A2-B9E5-4433-87C0-68B6B72699C7 (Microsoft basic data)
Partition unique GUID: 66AD43C4-69FF-4274-B121-07462B71A1F1
First sector: 2048 (at 1024.0 KiB)
Last sector: 976771071 (at 465.8 GiB)
Partition size: 976769024 sectors (465.8 GiB)
Attribute flags: 0000000000000000
Partition name: 'Basic data partition'
mount data-recovery
mount data-recovery
edited 10 hours ago
Prabhjot Singh
155213
asked Apr 9 at 10:01
TomTom
63
New contributor
Tom is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
edited 10 hours ago
Prabhjot Singh
155213
asked Apr 9 at 10:01
TomTom
63
New contributor
Tom is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
edited 10 hours ago
Prabhjot Singh
155213
edited 10 hours ago
Prabhjot Singh
155213
edited 10 hours ago
Prabhjot Singh
155213
155213
asked Apr 9 at 10:01
TomTom
63
New contributor
Tom is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked Apr 9 at 10:01
TomTom
63
asked Apr 9 at 10:01
TomTom
63
63
New contributor
Tom is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
Tom is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Tom is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Nowadays there's often no need to play withlosetup -o,mountcan handle this:mount -o offset=$((2048*512)) …. I think you set--sizelimitwrong (you gave sectors instead of bytes; maybe yourlosetupis different than mine), but I'm not really sure this is the culprit. You said HDD was unmountable; so maybe the filesystem is corrupt and for this reason the image is unmountable.
– Kamil Maciorowski
Apr 9 at 10:30
Thank you for you're answer. you are right, i had wrong sizelimit, but even with correct(500'106'788'352) or with "mount -o loop,offset=1048576 mdat.img /mnt/meldat/" it did not work.
– Tom
Apr 9 at 12:00
add a comment |
Nowadays there's often no need to play withlosetup -o,mountcan handle this:mount -o offset=$((2048*512)) …. I think you set--sizelimitwrong (you gave sectors instead of bytes; maybe yourlosetupis different than mine), but I'm not really sure this is the culprit. You said HDD was unmountable; so maybe the filesystem is corrupt and for this reason the image is unmountable.
– Kamil Maciorowski
Apr 9 at 10:30
Thank you for you're answer. you are right, i had wrong sizelimit, but even with correct(500'106'788'352) or with "mount -o loop,offset=1048576 mdat.img /mnt/meldat/" it did not work.
– Tom
Apr 9 at 12:00
Nowadays there's often no need to play with
losetup -o, mount can handle this: mount -o offset=$((2048*512)) …. I think you set --sizelimit wrong (you gave sectors instead of bytes; maybe your losetup is different than mine), but I'm not really sure this is the culprit. You said HDD was unmountable; so maybe the filesystem is corrupt and for this reason the image is unmountable.– Kamil Maciorowski
Apr 9 at 10:30
Nowadays there's often no need to play with
losetup -o, mount can handle this: mount -o offset=$((2048*512)) …. I think you set --sizelimit wrong (you gave sectors instead of bytes; maybe your losetup is different than mine), but I'm not really sure this is the culprit. You said HDD was unmountable; so maybe the filesystem is corrupt and for this reason the image is unmountable.– Kamil Maciorowski
Apr 9 at 10:30
Thank you for you're answer. you are right, i had wrong sizelimit, but even with correct(500'106'788'352) or with "mount -o loop,offset=1048576 mdat.img /mnt/meldat/" it did not work.
– Tom
Apr 9 at 12:00
Thank you for you're answer. you are right, i had wrong sizelimit, but even with correct(500'106'788'352) or with "mount -o loop,offset=1048576 mdat.img /mnt/meldat/" it did not work.
– Tom
Apr 9 at 12:00
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Tom is a new contributor. Be nice, and check out our Code of Conduct.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f511419%2fmount-img-from-data-recovery%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Tom is a new contributor. Be nice, and check out our Code of Conduct.
Tom is a new contributor. Be nice, and check out our Code of Conduct.
Tom is a new contributor. Be nice, and check out our Code of Conduct.
Tom is a new contributor. Be nice, and check out our Code of Conduct.
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f511419%2fmount-img-from-data-recovery%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Nowadays there's often no need to play with
losetup -o,mountcan handle this:mount -o offset=$((2048*512)) …. I think you set--sizelimitwrong (you gave sectors instead of bytes; maybe yourlosetupis different than mine), but I'm not really sure this is the culprit. You said HDD was unmountable; so maybe the filesystem is corrupt and for this reason the image is unmountable.– Kamil Maciorowski
Apr 9 at 10:30
Thank you for you're answer. you are right, i had wrong sizelimit, but even with correct(500'106'788'352) or with "mount -o loop,offset=1048576 mdat.img /mnt/meldat/" it did not work.
– Tom
Apr 9 at 12:00