Ubuntu 17.10 is not booting due to hard disk being full of recovered files
![Creative The name of the picture](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgO9GURib1T8z7lCwjOGLQaGtrueEthgQ8LO42ZX8cOfTqDK4jvDDpKkLFwf2J49kYCMNW7d4ABih_XCb_2UXdq5fPJDkoyg7-8g_YfRUot-XnaXkNYycsNp7lA5_TW9td0FFpLQ2APzKcZ/s1600/1.jpg)
![Creative The name of the picture](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhYQ0N5W1qAOxLP7t7iOM6O6AzbZnkXUy16s7P_CWfOb5UbTQY_aDsc727chyphenhyphen5W4IppVNernMMQeaUFTB_rFzAd95_CDt-tnwN-nBx6JyUp2duGjPaL5-VgNO41AVsA_vu30EJcipdDG409/s400/Clash+Royale+CLAN+TAG%2523URR8PPP.png)
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
17.10 virtualization data-recovery
add a comment |Â
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
17.10 virtualization data-recovery
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
add a comment |Â
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
17.10 virtualization data-recovery
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
17.10 virtualization data-recovery
edited Mar 1 at 15:12
![](https://i.stack.imgur.com/8CW8e.png?s=32&g=1)
![](https://i.stack.imgur.com/8CW8e.png?s=32&g=1)
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
add a comment |Â
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
add a comment |Â
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.
add a comment |Â
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.
add a comment |Â
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.
add a comment |Â
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.
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.
answered Feb 25 at 8:48
dsstorefile1
1,312111
1,312111
add a comment |Â
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
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
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
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
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