Ubuntu 17.10 is not booting due to hard disk being full of recovered files

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP








up vote
1
down vote

favorite












I'm new to Ubuntu.



Yesterday I accidentally deleted my Virtual Machine Windows 7 (32 bit) in VirtualBox on host Ubuntu 17.10. After that I tried to recover using Testdisk. It's not recovered and another method tried using Photorec it recovered some files but not finished because my hard disk storage not enough. So I stopped after my notebook little bit hangs so that's why Restarted bot right now it's showing



dev/sda2 /30498816 /30457001 files, 121959007 /121965056 blocks









share|improve this question























  • What’s your question? What are you trying to achieve?
    – David Foerster
    Feb 26 at 15:03






  • 1




    Some tips: Keep backups, use a trash can / recycle bin instead of straight delete, testdisk should see & recover files and their names, photorec doesn't recover names or folders (everything's in a "big messy pile"). And recovering deleted files onto the same partition will just overwrite anything not yet recovered. Tried freeing some space to get it to boot again?
    – Xen2050
    Feb 27 at 2:18










  • Never attempt data recovery to the same partition. You should always work on an image or clone of the drive as discussed here
    – Elder Geek
    Mar 7 at 19:14














up vote
1
down vote

favorite












I'm new to Ubuntu.



Yesterday I accidentally deleted my Virtual Machine Windows 7 (32 bit) in VirtualBox on host Ubuntu 17.10. After that I tried to recover using Testdisk. It's not recovered and another method tried using Photorec it recovered some files but not finished because my hard disk storage not enough. So I stopped after my notebook little bit hangs so that's why Restarted bot right now it's showing



dev/sda2 /30498816 /30457001 files, 121959007 /121965056 blocks









share|improve this question























  • What’s your question? What are you trying to achieve?
    – David Foerster
    Feb 26 at 15:03






  • 1




    Some tips: Keep backups, use a trash can / recycle bin instead of straight delete, testdisk should see & recover files and their names, photorec doesn't recover names or folders (everything's in a "big messy pile"). And recovering deleted files onto the same partition will just overwrite anything not yet recovered. Tried freeing some space to get it to boot again?
    – Xen2050
    Feb 27 at 2:18










  • Never attempt data recovery to the same partition. You should always work on an image or clone of the drive as discussed here
    – Elder Geek
    Mar 7 at 19:14












up vote
1
down vote

favorite









up vote
1
down vote

favorite











I'm new to Ubuntu.



Yesterday I accidentally deleted my Virtual Machine Windows 7 (32 bit) in VirtualBox on host Ubuntu 17.10. After that I tried to recover using Testdisk. It's not recovered and another method tried using Photorec it recovered some files but not finished because my hard disk storage not enough. So I stopped after my notebook little bit hangs so that's why Restarted bot right now it's showing



dev/sda2 /30498816 /30457001 files, 121959007 /121965056 blocks









share|improve this question















I'm new to Ubuntu.



Yesterday I accidentally deleted my Virtual Machine Windows 7 (32 bit) in VirtualBox on host Ubuntu 17.10. After that I tried to recover using Testdisk. It's not recovered and another method tried using Photorec it recovered some files but not finished because my hard disk storage not enough. So I stopped after my notebook little bit hangs so that's why Restarted bot right now it's showing



dev/sda2 /30498816 /30457001 files, 121959007 /121965056 blocks






17.10 virtualization data-recovery






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Mar 1 at 15:12









Zanna

48.2k13120228




48.2k13120228










asked Feb 25 at 7:24







user777865


















  • What’s your question? What are you trying to achieve?
    – David Foerster
    Feb 26 at 15:03






  • 1




    Some tips: Keep backups, use a trash can / recycle bin instead of straight delete, testdisk should see & recover files and their names, photorec doesn't recover names or folders (everything's in a "big messy pile"). And recovering deleted files onto the same partition will just overwrite anything not yet recovered. Tried freeing some space to get it to boot again?
    – Xen2050
    Feb 27 at 2:18










  • Never attempt data recovery to the same partition. You should always work on an image or clone of the drive as discussed here
    – Elder Geek
    Mar 7 at 19:14
















  • What’s your question? What are you trying to achieve?
    – David Foerster
    Feb 26 at 15:03






  • 1




    Some tips: Keep backups, use a trash can / recycle bin instead of straight delete, testdisk should see & recover files and their names, photorec doesn't recover names or folders (everything's in a "big messy pile"). And recovering deleted files onto the same partition will just overwrite anything not yet recovered. Tried freeing some space to get it to boot again?
    – Xen2050
    Feb 27 at 2:18










  • Never attempt data recovery to the same partition. You should always work on an image or clone of the drive as discussed here
    – Elder Geek
    Mar 7 at 19:14















What’s your question? What are you trying to achieve?
– David Foerster
Feb 26 at 15:03




What’s your question? What are you trying to achieve?
– David Foerster
Feb 26 at 15:03




1




1




Some tips: Keep backups, use a trash can / recycle bin instead of straight delete, testdisk should see & recover files and their names, photorec doesn't recover names or folders (everything's in a "big messy pile"). And recovering deleted files onto the same partition will just overwrite anything not yet recovered. Tried freeing some space to get it to boot again?
– Xen2050
Feb 27 at 2:18




Some tips: Keep backups, use a trash can / recycle bin instead of straight delete, testdisk should see & recover files and their names, photorec doesn't recover names or folders (everything's in a "big messy pile"). And recovering deleted files onto the same partition will just overwrite anything not yet recovered. Tried freeing some space to get it to boot again?
– Xen2050
Feb 27 at 2:18












Never attempt data recovery to the same partition. You should always work on an image or clone of the drive as discussed here
– Elder Geek
Mar 7 at 19:14




Never attempt data recovery to the same partition. You should always work on an image or clone of the drive as discussed here
– Elder Geek
Mar 7 at 19:14










1 Answer
1






active

oldest

votes

















up vote
1
down vote



accepted










Boot your system and tap Esc after the BIOS screen to enter the GRUB menu, then press e to edit and append init=/bin/bash to the line starting with linux. Press Ctrl+x to boot, log in, and make your filesystem writable via mount -oremount,rw /. Navigate to the folder where the recovered files are and delete them as needed.



Alternatively, you can boot a live CD/USB and delete your recovered files from the live session after mounting your disk.






share|improve this answer




















    Your Answer







    StackExchange.ready(function()
    var channelOptions =
    tags: "".split(" "),
    id: "89"
    ;
    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',
    convertImagesToLinks: true,
    noModals: false,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: 10,
    bindNavPrevention: true,
    postfix: "",
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    );



    );













     

    draft saved


    draft discarded


















    StackExchange.ready(
    function ()
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1009530%2fubuntu-17-10-is-not-booting-due-to-hard-disk-being-full-of-recovered-files%23new-answer', 'question_page');

    );

    Post as a guest





























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes








    up vote
    1
    down vote



    accepted










    Boot your system and tap Esc after the BIOS screen to enter the GRUB menu, then press e to edit and append init=/bin/bash to the line starting with linux. Press Ctrl+x to boot, log in, and make your filesystem writable via mount -oremount,rw /. Navigate to the folder where the recovered files are and delete them as needed.



    Alternatively, you can boot a live CD/USB and delete your recovered files from the live session after mounting your disk.






    share|improve this answer
























      up vote
      1
      down vote



      accepted










      Boot your system and tap Esc after the BIOS screen to enter the GRUB menu, then press e to edit and append init=/bin/bash to the line starting with linux. Press Ctrl+x to boot, log in, and make your filesystem writable via mount -oremount,rw /. Navigate to the folder where the recovered files are and delete them as needed.



      Alternatively, you can boot a live CD/USB and delete your recovered files from the live session after mounting your disk.






      share|improve this answer






















        up vote
        1
        down vote



        accepted







        up vote
        1
        down vote



        accepted






        Boot your system and tap Esc after the BIOS screen to enter the GRUB menu, then press e to edit and append init=/bin/bash to the line starting with linux. Press Ctrl+x to boot, log in, and make your filesystem writable via mount -oremount,rw /. Navigate to the folder where the recovered files are and delete them as needed.



        Alternatively, you can boot a live CD/USB and delete your recovered files from the live session after mounting your disk.






        share|improve this answer












        Boot your system and tap Esc after the BIOS screen to enter the GRUB menu, then press e to edit and append init=/bin/bash to the line starting with linux. Press Ctrl+x to boot, log in, and make your filesystem writable via mount -oremount,rw /. Navigate to the folder where the recovered files are and delete them as needed.



        Alternatively, you can boot a live CD/USB and delete your recovered files from the live session after mounting your disk.







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Feb 25 at 8:48









        dsstorefile1

        1,312111




        1,312111



























             

            draft saved


            draft discarded















































             


            draft saved


            draft discarded














            StackExchange.ready(
            function ()
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1009530%2fubuntu-17-10-is-not-booting-due-to-hard-disk-being-full-of-recovered-files%23new-answer', 'question_page');

            );

            Post as a guest













































































            Popular posts from this blog

            pylint3 and pip3 broken

            Missing snmpget and snmpwalk

            How to enroll fingerprints to Ubuntu 17.10 with VFS491