Couldn't mount file The disk image file is corrupted












1















Not so long ago I Backed up Entire Windows 10 partition of my drive using dd under ubuntu and since then I have two main problems - first it turned out that even the unused space is imaged which is quite bad considering that the drive was 80/150GB full.



And even worse I couldn't mount it in Windows using it's built in mount function(even though it was completely fine to open the image with 7zip). I didn't bother with these problembs back then but now I want to run the OS in VirtualBox and cannot mount the image in the VM also.



Does anyone has any ideas how to resolve these problems? Thanks a lot in advance :)










share|improve this question

























  • dd copies disc sectors blindly, so it cannot take account of the occupancy of whatever file system is being copied. However, if the unused space is zeroed, then the output image file will compress well. I use VMware, so I cannot help with VBox problems.

    – AFH
    Jan 31 at 17:54






  • 1





    see if this helps: forensicfocus.com/Forums/viewtopic/t=15861 dd makes an exact duplicate of your disk, Windows wants a VHD format to mount, not what dd creates. There are tools for creating virtual disk containers, like disk2vhd.

    – essjae
    Jan 31 at 17:54
















1















Not so long ago I Backed up Entire Windows 10 partition of my drive using dd under ubuntu and since then I have two main problems - first it turned out that even the unused space is imaged which is quite bad considering that the drive was 80/150GB full.



And even worse I couldn't mount it in Windows using it's built in mount function(even though it was completely fine to open the image with 7zip). I didn't bother with these problembs back then but now I want to run the OS in VirtualBox and cannot mount the image in the VM also.



Does anyone has any ideas how to resolve these problems? Thanks a lot in advance :)










share|improve this question

























  • dd copies disc sectors blindly, so it cannot take account of the occupancy of whatever file system is being copied. However, if the unused space is zeroed, then the output image file will compress well. I use VMware, so I cannot help with VBox problems.

    – AFH
    Jan 31 at 17:54






  • 1





    see if this helps: forensicfocus.com/Forums/viewtopic/t=15861 dd makes an exact duplicate of your disk, Windows wants a VHD format to mount, not what dd creates. There are tools for creating virtual disk containers, like disk2vhd.

    – essjae
    Jan 31 at 17:54














1












1








1








Not so long ago I Backed up Entire Windows 10 partition of my drive using dd under ubuntu and since then I have two main problems - first it turned out that even the unused space is imaged which is quite bad considering that the drive was 80/150GB full.



And even worse I couldn't mount it in Windows using it's built in mount function(even though it was completely fine to open the image with 7zip). I didn't bother with these problembs back then but now I want to run the OS in VirtualBox and cannot mount the image in the VM also.



Does anyone has any ideas how to resolve these problems? Thanks a lot in advance :)










share|improve this question
















Not so long ago I Backed up Entire Windows 10 partition of my drive using dd under ubuntu and since then I have two main problems - first it turned out that even the unused space is imaged which is quite bad considering that the drive was 80/150GB full.



And even worse I couldn't mount it in Windows using it's built in mount function(even though it was completely fine to open the image with 7zip). I didn't bother with these problembs back then but now I want to run the OS in VirtualBox and cannot mount the image in the VM also.



Does anyone has any ideas how to resolve these problems? Thanks a lot in advance :)







windows-10 ubuntu virtualbox mount dd






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Jan 31 at 17:47







Hristo Mitrev

















asked Jan 31 at 17:40









Hristo MitrevHristo Mitrev

62




62













  • dd copies disc sectors blindly, so it cannot take account of the occupancy of whatever file system is being copied. However, if the unused space is zeroed, then the output image file will compress well. I use VMware, so I cannot help with VBox problems.

    – AFH
    Jan 31 at 17:54






  • 1





    see if this helps: forensicfocus.com/Forums/viewtopic/t=15861 dd makes an exact duplicate of your disk, Windows wants a VHD format to mount, not what dd creates. There are tools for creating virtual disk containers, like disk2vhd.

    – essjae
    Jan 31 at 17:54



















  • dd copies disc sectors blindly, so it cannot take account of the occupancy of whatever file system is being copied. However, if the unused space is zeroed, then the output image file will compress well. I use VMware, so I cannot help with VBox problems.

    – AFH
    Jan 31 at 17:54






  • 1





    see if this helps: forensicfocus.com/Forums/viewtopic/t=15861 dd makes an exact duplicate of your disk, Windows wants a VHD format to mount, not what dd creates. There are tools for creating virtual disk containers, like disk2vhd.

    – essjae
    Jan 31 at 17:54

















dd copies disc sectors blindly, so it cannot take account of the occupancy of whatever file system is being copied. However, if the unused space is zeroed, then the output image file will compress well. I use VMware, so I cannot help with VBox problems.

– AFH
Jan 31 at 17:54





dd copies disc sectors blindly, so it cannot take account of the occupancy of whatever file system is being copied. However, if the unused space is zeroed, then the output image file will compress well. I use VMware, so I cannot help with VBox problems.

– AFH
Jan 31 at 17:54




1




1





see if this helps: forensicfocus.com/Forums/viewtopic/t=15861 dd makes an exact duplicate of your disk, Windows wants a VHD format to mount, not what dd creates. There are tools for creating virtual disk containers, like disk2vhd.

– essjae
Jan 31 at 17:54





see if this helps: forensicfocus.com/Forums/viewtopic/t=15861 dd makes an exact duplicate of your disk, Windows wants a VHD format to mount, not what dd creates. There are tools for creating virtual disk containers, like disk2vhd.

– essjae
Jan 31 at 17:54










1 Answer
1






active

oldest

votes


















1















Not so long ago I Backed up Entire Windows 10 partition of my drive using dd



Did you image the entire disk? dd if=/dev/sda of=/path/to/disk.img status=progress

Or, did you image just the Windows partition? dd if=/dev/sda2 of=/path/to/disk.img status=progress



If you did the latter, that explains why Windows cannot mount it; as far as I know, mounting disk images under Windows requires that the image in question have a valid partition table, which imaging a single partition will not do.



it turned out that even the unused space is imaged which is quite bad considering that the drive was 80/150GB full



You can use your favorite partitioning tool (like gparted) to reduce the size of the partition to its used extent. GParted can modify disk images by launching from it from the terminal, with the path to your disk image as an argument:
gparted /path/to/disk.img, and then use truncate to reduce the size of the entire image with something like (careful with this, it can easily render data unreadable):
truncate -s 81GB /path/to/disk.img



I want to run the OS in VirtualBox and cannot mount the image in the VM also.



This can only be done if you can find the Windows EFI bootloader, which is stored on the ESP (EFI System Partition), which is (obviously) a separate partition on your drive, which only exists in the disk image if you imaged the entire drive. The path to it is (EFI System Partition)/EFI/Microsoft/Boot/bootmgfw.efi



If you have the bootloader I'll edit my post with instructions to boot it using VirtualBox.






share|improve this answer























    Your Answer








    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "3"
    };
    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: true,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: 10,
    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
    });


    }
    });














    draft saved

    draft discarded


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1400682%2fcouldnt-mount-file-the-disk-image-file-is-corrupted%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    1















    Not so long ago I Backed up Entire Windows 10 partition of my drive using dd



    Did you image the entire disk? dd if=/dev/sda of=/path/to/disk.img status=progress

    Or, did you image just the Windows partition? dd if=/dev/sda2 of=/path/to/disk.img status=progress



    If you did the latter, that explains why Windows cannot mount it; as far as I know, mounting disk images under Windows requires that the image in question have a valid partition table, which imaging a single partition will not do.



    it turned out that even the unused space is imaged which is quite bad considering that the drive was 80/150GB full



    You can use your favorite partitioning tool (like gparted) to reduce the size of the partition to its used extent. GParted can modify disk images by launching from it from the terminal, with the path to your disk image as an argument:
    gparted /path/to/disk.img, and then use truncate to reduce the size of the entire image with something like (careful with this, it can easily render data unreadable):
    truncate -s 81GB /path/to/disk.img



    I want to run the OS in VirtualBox and cannot mount the image in the VM also.



    This can only be done if you can find the Windows EFI bootloader, which is stored on the ESP (EFI System Partition), which is (obviously) a separate partition on your drive, which only exists in the disk image if you imaged the entire drive. The path to it is (EFI System Partition)/EFI/Microsoft/Boot/bootmgfw.efi



    If you have the bootloader I'll edit my post with instructions to boot it using VirtualBox.






    share|improve this answer




























      1















      Not so long ago I Backed up Entire Windows 10 partition of my drive using dd



      Did you image the entire disk? dd if=/dev/sda of=/path/to/disk.img status=progress

      Or, did you image just the Windows partition? dd if=/dev/sda2 of=/path/to/disk.img status=progress



      If you did the latter, that explains why Windows cannot mount it; as far as I know, mounting disk images under Windows requires that the image in question have a valid partition table, which imaging a single partition will not do.



      it turned out that even the unused space is imaged which is quite bad considering that the drive was 80/150GB full



      You can use your favorite partitioning tool (like gparted) to reduce the size of the partition to its used extent. GParted can modify disk images by launching from it from the terminal, with the path to your disk image as an argument:
      gparted /path/to/disk.img, and then use truncate to reduce the size of the entire image with something like (careful with this, it can easily render data unreadable):
      truncate -s 81GB /path/to/disk.img



      I want to run the OS in VirtualBox and cannot mount the image in the VM also.



      This can only be done if you can find the Windows EFI bootloader, which is stored on the ESP (EFI System Partition), which is (obviously) a separate partition on your drive, which only exists in the disk image if you imaged the entire drive. The path to it is (EFI System Partition)/EFI/Microsoft/Boot/bootmgfw.efi



      If you have the bootloader I'll edit my post with instructions to boot it using VirtualBox.






      share|improve this answer


























        1












        1








        1








        Not so long ago I Backed up Entire Windows 10 partition of my drive using dd



        Did you image the entire disk? dd if=/dev/sda of=/path/to/disk.img status=progress

        Or, did you image just the Windows partition? dd if=/dev/sda2 of=/path/to/disk.img status=progress



        If you did the latter, that explains why Windows cannot mount it; as far as I know, mounting disk images under Windows requires that the image in question have a valid partition table, which imaging a single partition will not do.



        it turned out that even the unused space is imaged which is quite bad considering that the drive was 80/150GB full



        You can use your favorite partitioning tool (like gparted) to reduce the size of the partition to its used extent. GParted can modify disk images by launching from it from the terminal, with the path to your disk image as an argument:
        gparted /path/to/disk.img, and then use truncate to reduce the size of the entire image with something like (careful with this, it can easily render data unreadable):
        truncate -s 81GB /path/to/disk.img



        I want to run the OS in VirtualBox and cannot mount the image in the VM also.



        This can only be done if you can find the Windows EFI bootloader, which is stored on the ESP (EFI System Partition), which is (obviously) a separate partition on your drive, which only exists in the disk image if you imaged the entire drive. The path to it is (EFI System Partition)/EFI/Microsoft/Boot/bootmgfw.efi



        If you have the bootloader I'll edit my post with instructions to boot it using VirtualBox.






        share|improve this answer














        Not so long ago I Backed up Entire Windows 10 partition of my drive using dd



        Did you image the entire disk? dd if=/dev/sda of=/path/to/disk.img status=progress

        Or, did you image just the Windows partition? dd if=/dev/sda2 of=/path/to/disk.img status=progress



        If you did the latter, that explains why Windows cannot mount it; as far as I know, mounting disk images under Windows requires that the image in question have a valid partition table, which imaging a single partition will not do.



        it turned out that even the unused space is imaged which is quite bad considering that the drive was 80/150GB full



        You can use your favorite partitioning tool (like gparted) to reduce the size of the partition to its used extent. GParted can modify disk images by launching from it from the terminal, with the path to your disk image as an argument:
        gparted /path/to/disk.img, and then use truncate to reduce the size of the entire image with something like (careful with this, it can easily render data unreadable):
        truncate -s 81GB /path/to/disk.img



        I want to run the OS in VirtualBox and cannot mount the image in the VM also.



        This can only be done if you can find the Windows EFI bootloader, which is stored on the ESP (EFI System Partition), which is (obviously) a separate partition on your drive, which only exists in the disk image if you imaged the entire drive. The path to it is (EFI System Partition)/EFI/Microsoft/Boot/bootmgfw.efi



        If you have the bootloader I'll edit my post with instructions to boot it using VirtualBox.







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Jan 31 at 19:04









        ShadowcoderShadowcoder

        1068




        1068






























            draft saved

            draft discarded




















































            Thanks for contributing an answer to Super User!


            • 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.




            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1400682%2fcouldnt-mount-file-the-disk-image-file-is-corrupted%23new-answer', 'question_page');
            }
            );

            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







            Popular posts from this blog

            flock() on closed filehandle LOCK_FILE at /usr/bin/apt-mirror

            Mangá

             ⁒  ․,‪⁊‑⁙ ⁖, ⁇‒※‌, †,⁖‗‌⁝    ‾‸⁘,‖⁔⁣,⁂‾
”‑,‥–,‬ ,⁀‹⁋‴⁑ ‒ ,‴⁋”‼ ⁨,‷⁔„ ‰′,‐‚ ‥‡‎“‷⁃⁨⁅⁣,⁔
⁇‘⁔⁡⁏⁌⁡‿‶‏⁨ ⁣⁕⁖⁨⁩⁥‽⁀  ‴‬⁜‟ ⁃‣‧⁕‮ …‍⁨‴ ⁩,⁚⁖‫ ,‵ ⁀,‮⁝‣‣ ⁑  ⁂– ․, ‾‽ ‏⁁“⁗‸ ‾… ‹‡⁌⁎‸‘ ‡⁏⁌‪ ‵⁛ ‎⁨ ―⁦⁤⁄⁕