Main Hard Disk Corrupted!

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








up vote
0
down vote

favorite












My main disk (with Ubuntu 16.04 on it) has gotten corrupted. It drops me into "Busy Box" instead of into the desktop. I have found (through Google) that I need to put the HD into an enclosure and USB to it, then to do an fdisk on it.



I have done all of that and I can see it, but now I am getting an error as follows:



Command I am using
fdisk /media/mike/???/ where ??? is the name of the external hard disk I want to do the fdisk on.



Error I am getting
fdisk: cannot open /media/mike/???: is a directory



Thank You,
Mike







share|improve this question




















  • I don't think you had to remove the hdd & put in enclosure; you could have booted a 'live' distro from thumb or dvd & done the same checks from original hardware. As such either you're following strange instructions (maybe you should provide link) or misunderstood them. I'd check hardware (ie. your drive) first (smartctl) and I'm not sure what they trying to do with fdisk (you didn't display options; -l for list is about all I'd use fdisk for, then badblocks maybe, or more likely a e2fsck (ext filesystem check; changing if you used a different fs)..
    – guiverc
    Apr 21 at 12:08











  • Please provide more info. Dropping to Busy Box doesn't mean your HD got corrupted completely. How did you reach /media/mike/...? It's the location of mounted disks. All of the drives located in /dev/sda1, /dev/sda2, /dev/sdb1, etc.
    – kenn
    Apr 21 at 12:18










  • Use a liveusb or livedvd then check out your partition with e2fsck /dev/sd(your partition number), the drive must be not mounted`
    – kenn
    Apr 21 at 12:25















up vote
0
down vote

favorite












My main disk (with Ubuntu 16.04 on it) has gotten corrupted. It drops me into "Busy Box" instead of into the desktop. I have found (through Google) that I need to put the HD into an enclosure and USB to it, then to do an fdisk on it.



I have done all of that and I can see it, but now I am getting an error as follows:



Command I am using
fdisk /media/mike/???/ where ??? is the name of the external hard disk I want to do the fdisk on.



Error I am getting
fdisk: cannot open /media/mike/???: is a directory



Thank You,
Mike







share|improve this question




















  • I don't think you had to remove the hdd & put in enclosure; you could have booted a 'live' distro from thumb or dvd & done the same checks from original hardware. As such either you're following strange instructions (maybe you should provide link) or misunderstood them. I'd check hardware (ie. your drive) first (smartctl) and I'm not sure what they trying to do with fdisk (you didn't display options; -l for list is about all I'd use fdisk for, then badblocks maybe, or more likely a e2fsck (ext filesystem check; changing if you used a different fs)..
    – guiverc
    Apr 21 at 12:08











  • Please provide more info. Dropping to Busy Box doesn't mean your HD got corrupted completely. How did you reach /media/mike/...? It's the location of mounted disks. All of the drives located in /dev/sda1, /dev/sda2, /dev/sdb1, etc.
    – kenn
    Apr 21 at 12:18










  • Use a liveusb or livedvd then check out your partition with e2fsck /dev/sd(your partition number), the drive must be not mounted`
    – kenn
    Apr 21 at 12:25













up vote
0
down vote

favorite









up vote
0
down vote

favorite











My main disk (with Ubuntu 16.04 on it) has gotten corrupted. It drops me into "Busy Box" instead of into the desktop. I have found (through Google) that I need to put the HD into an enclosure and USB to it, then to do an fdisk on it.



I have done all of that and I can see it, but now I am getting an error as follows:



Command I am using
fdisk /media/mike/???/ where ??? is the name of the external hard disk I want to do the fdisk on.



Error I am getting
fdisk: cannot open /media/mike/???: is a directory



Thank You,
Mike







share|improve this question












My main disk (with Ubuntu 16.04 on it) has gotten corrupted. It drops me into "Busy Box" instead of into the desktop. I have found (through Google) that I need to put the HD into an enclosure and USB to it, then to do an fdisk on it.



I have done all of that and I can see it, but now I am getting an error as follows:



Command I am using
fdisk /media/mike/???/ where ??? is the name of the external hard disk I want to do the fdisk on.



Error I am getting
fdisk: cannot open /media/mike/???: is a directory



Thank You,
Mike









share|improve this question











share|improve this question




share|improve this question










asked Apr 21 at 11:56









Michael LaPointe

1




1











  • I don't think you had to remove the hdd & put in enclosure; you could have booted a 'live' distro from thumb or dvd & done the same checks from original hardware. As such either you're following strange instructions (maybe you should provide link) or misunderstood them. I'd check hardware (ie. your drive) first (smartctl) and I'm not sure what they trying to do with fdisk (you didn't display options; -l for list is about all I'd use fdisk for, then badblocks maybe, or more likely a e2fsck (ext filesystem check; changing if you used a different fs)..
    – guiverc
    Apr 21 at 12:08











  • Please provide more info. Dropping to Busy Box doesn't mean your HD got corrupted completely. How did you reach /media/mike/...? It's the location of mounted disks. All of the drives located in /dev/sda1, /dev/sda2, /dev/sdb1, etc.
    – kenn
    Apr 21 at 12:18










  • Use a liveusb or livedvd then check out your partition with e2fsck /dev/sd(your partition number), the drive must be not mounted`
    – kenn
    Apr 21 at 12:25

















  • I don't think you had to remove the hdd & put in enclosure; you could have booted a 'live' distro from thumb or dvd & done the same checks from original hardware. As such either you're following strange instructions (maybe you should provide link) or misunderstood them. I'd check hardware (ie. your drive) first (smartctl) and I'm not sure what they trying to do with fdisk (you didn't display options; -l for list is about all I'd use fdisk for, then badblocks maybe, or more likely a e2fsck (ext filesystem check; changing if you used a different fs)..
    – guiverc
    Apr 21 at 12:08











  • Please provide more info. Dropping to Busy Box doesn't mean your HD got corrupted completely. How did you reach /media/mike/...? It's the location of mounted disks. All of the drives located in /dev/sda1, /dev/sda2, /dev/sdb1, etc.
    – kenn
    Apr 21 at 12:18










  • Use a liveusb or livedvd then check out your partition with e2fsck /dev/sd(your partition number), the drive must be not mounted`
    – kenn
    Apr 21 at 12:25
















I don't think you had to remove the hdd & put in enclosure; you could have booted a 'live' distro from thumb or dvd & done the same checks from original hardware. As such either you're following strange instructions (maybe you should provide link) or misunderstood them. I'd check hardware (ie. your drive) first (smartctl) and I'm not sure what they trying to do with fdisk (you didn't display options; -l for list is about all I'd use fdisk for, then badblocks maybe, or more likely a e2fsck (ext filesystem check; changing if you used a different fs)..
– guiverc
Apr 21 at 12:08





I don't think you had to remove the hdd & put in enclosure; you could have booted a 'live' distro from thumb or dvd & done the same checks from original hardware. As such either you're following strange instructions (maybe you should provide link) or misunderstood them. I'd check hardware (ie. your drive) first (smartctl) and I'm not sure what they trying to do with fdisk (you didn't display options; -l for list is about all I'd use fdisk for, then badblocks maybe, or more likely a e2fsck (ext filesystem check; changing if you used a different fs)..
– guiverc
Apr 21 at 12:08













Please provide more info. Dropping to Busy Box doesn't mean your HD got corrupted completely. How did you reach /media/mike/...? It's the location of mounted disks. All of the drives located in /dev/sda1, /dev/sda2, /dev/sdb1, etc.
– kenn
Apr 21 at 12:18




Please provide more info. Dropping to Busy Box doesn't mean your HD got corrupted completely. How did you reach /media/mike/...? It's the location of mounted disks. All of the drives located in /dev/sda1, /dev/sda2, /dev/sdb1, etc.
– kenn
Apr 21 at 12:18












Use a liveusb or livedvd then check out your partition with e2fsck /dev/sd(your partition number), the drive must be not mounted`
– kenn
Apr 21 at 12:25





Use a liveusb or livedvd then check out your partition with e2fsck /dev/sd(your partition number), the drive must be not mounted`
– kenn
Apr 21 at 12:25











1 Answer
1






active

oldest

votes

















up vote
1
down vote













Reinstall your hard disk back into your computer.



Then to check the file system on your Ubuntu partition...



  • boot to the GRUB menu

  • choose Advanced Options

  • choose Recovery mode

  • choose Root access

  • at the # prompt, type sudo fsck -f /

  • repeat the fsck command if there were errors

  • type reboot

If for some reason you can't do the above...



  • boot to a Ubuntu Live DVD/USB

  • start gparted and determine which /dev/sdaX is your Ubuntu EXT4 partition

  • quit gparted

  • open a terminal window

  • type sudo fsck -f /dev/sdaX # replacing X with the number you found earlier

  • repeat the fsck command if there were errors

  • type reboot





share|improve this answer




















  • That seems to have worked! Thank You heynnema!
    – Michael LaPointe
    Apr 21 at 20:49










  • @MichaelLaPointe please remember to accept my answer, if it was helpful, by clicking the grey checkmark. Thanks.
    – heynnema
    Apr 21 at 20:54











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%2f1026925%2fmain-hard-disk-corrupted%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













Reinstall your hard disk back into your computer.



Then to check the file system on your Ubuntu partition...



  • boot to the GRUB menu

  • choose Advanced Options

  • choose Recovery mode

  • choose Root access

  • at the # prompt, type sudo fsck -f /

  • repeat the fsck command if there were errors

  • type reboot

If for some reason you can't do the above...



  • boot to a Ubuntu Live DVD/USB

  • start gparted and determine which /dev/sdaX is your Ubuntu EXT4 partition

  • quit gparted

  • open a terminal window

  • type sudo fsck -f /dev/sdaX # replacing X with the number you found earlier

  • repeat the fsck command if there were errors

  • type reboot





share|improve this answer




















  • That seems to have worked! Thank You heynnema!
    – Michael LaPointe
    Apr 21 at 20:49










  • @MichaelLaPointe please remember to accept my answer, if it was helpful, by clicking the grey checkmark. Thanks.
    – heynnema
    Apr 21 at 20:54















up vote
1
down vote













Reinstall your hard disk back into your computer.



Then to check the file system on your Ubuntu partition...



  • boot to the GRUB menu

  • choose Advanced Options

  • choose Recovery mode

  • choose Root access

  • at the # prompt, type sudo fsck -f /

  • repeat the fsck command if there were errors

  • type reboot

If for some reason you can't do the above...



  • boot to a Ubuntu Live DVD/USB

  • start gparted and determine which /dev/sdaX is your Ubuntu EXT4 partition

  • quit gparted

  • open a terminal window

  • type sudo fsck -f /dev/sdaX # replacing X with the number you found earlier

  • repeat the fsck command if there were errors

  • type reboot





share|improve this answer




















  • That seems to have worked! Thank You heynnema!
    – Michael LaPointe
    Apr 21 at 20:49










  • @MichaelLaPointe please remember to accept my answer, if it was helpful, by clicking the grey checkmark. Thanks.
    – heynnema
    Apr 21 at 20:54













up vote
1
down vote










up vote
1
down vote









Reinstall your hard disk back into your computer.



Then to check the file system on your Ubuntu partition...



  • boot to the GRUB menu

  • choose Advanced Options

  • choose Recovery mode

  • choose Root access

  • at the # prompt, type sudo fsck -f /

  • repeat the fsck command if there were errors

  • type reboot

If for some reason you can't do the above...



  • boot to a Ubuntu Live DVD/USB

  • start gparted and determine which /dev/sdaX is your Ubuntu EXT4 partition

  • quit gparted

  • open a terminal window

  • type sudo fsck -f /dev/sdaX # replacing X with the number you found earlier

  • repeat the fsck command if there were errors

  • type reboot





share|improve this answer












Reinstall your hard disk back into your computer.



Then to check the file system on your Ubuntu partition...



  • boot to the GRUB menu

  • choose Advanced Options

  • choose Recovery mode

  • choose Root access

  • at the # prompt, type sudo fsck -f /

  • repeat the fsck command if there were errors

  • type reboot

If for some reason you can't do the above...



  • boot to a Ubuntu Live DVD/USB

  • start gparted and determine which /dev/sdaX is your Ubuntu EXT4 partition

  • quit gparted

  • open a terminal window

  • type sudo fsck -f /dev/sdaX # replacing X with the number you found earlier

  • repeat the fsck command if there were errors

  • type reboot






share|improve this answer












share|improve this answer



share|improve this answer










answered Apr 21 at 14:26









heynnema

15.4k21945




15.4k21945











  • That seems to have worked! Thank You heynnema!
    – Michael LaPointe
    Apr 21 at 20:49










  • @MichaelLaPointe please remember to accept my answer, if it was helpful, by clicking the grey checkmark. Thanks.
    – heynnema
    Apr 21 at 20:54

















  • That seems to have worked! Thank You heynnema!
    – Michael LaPointe
    Apr 21 at 20:49










  • @MichaelLaPointe please remember to accept my answer, if it was helpful, by clicking the grey checkmark. Thanks.
    – heynnema
    Apr 21 at 20:54
















That seems to have worked! Thank You heynnema!
– Michael LaPointe
Apr 21 at 20:49




That seems to have worked! Thank You heynnema!
– Michael LaPointe
Apr 21 at 20:49












@MichaelLaPointe please remember to accept my answer, if it was helpful, by clicking the grey checkmark. Thanks.
– heynnema
Apr 21 at 20:54





@MichaelLaPointe please remember to accept my answer, if it was helpful, by clicking the grey checkmark. Thanks.
– heynnema
Apr 21 at 20:54


















 

draft saved


draft discarded















































 


draft saved


draft discarded














StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1026925%2fmain-hard-disk-corrupted%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