External HDD not mounting

u9477100 · 10-29-2019, 08:17 AM

I am quite new in Linux. My mobo is Gigabyte B85M-D3H. Processor i3. Ram 8GB. OS Linux Mint 19.2 One of my External HDD suddenly not mounting I can see it in Computer but cannot open it. It is connected Directly with the Box not by any hub. I used the folloing command but no result.

Code:

 soma@soma-B85M-D3H:~$ lsblk
NAME   MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
loop0    7:0    0 140.7M  1 loop /snap/gnome-3-26-1604/97
loop1    7:1    0  89.1M  1 loop /snap/core/7917
loop2    7:2    0  44.2M  1 loop /snap/gtk-common-themes/1353
loop3    7:3    0   156M  1 loop /snap/gnome-3-28-1804/91
loop4    7:4    0 150.2M  1 loop /snap/opera/57
loop5    7:5    0  28.9M  1 loop /snap/chromium-ffmpeg/15
loop6    7:6    0 229.7M  1 loop /snap/krita/52
loop7    7:7    0  84.3M  1 loop /snap/simplenote/129
loop8    7:8    0  54.5M  1 loop /snap/core18/1223
sda      8:0    0 931.5G  0 disk 
└─sda1   8:1    0 931.5G  0 part /
sdb      8:16   0 931.5G  0 disk 
└─sdb1   8:17   0 931.5G  0 part 
sr0     11:0    1  1024M  0 rom  
soma@soma-B85M-D3H:~$ grep $USER /etc/passwd
soma:x:1000:1000:soma,,,:/home/soma:/bin/bash
soma@soma-B85M-D3H:~$ sudo mount /dev/sdb1 /Full/path/ -
[sudo] password for soma:          
mount: bad usage
Try 'mount --help' for more information.
soma@soma-B85M-D3H:~$

I also tried

CODE] soma@soma-B85M-D3H:~$ sudo mount -t ntfs /dev/sdb1 /media
$MFTMirr does not match $MFT (record 0).
Failed to mount '/dev/sdb1': Input/output error
NTFS is either inconsistent, or there is a hardware fault, or it's a
SoftRAID/FakeRAID hardware. In the first case run chkdsk /f on Windows
then reboot into Windows twice. The usage of the /f parameter is very
important! If the device is a SoftRAID/FakeRAID then first activate
it and mount a different device under the /dev/mapper/ directory, (e.g.
/dev/mapper/nvidia_eahaabcc1). Please see the 'dmraid' documentation
for more details.[/CODE]

I am feeling helpless. Please guide me what to do.

teckk · 10-29-2019, 08:28 AM

Quote:

One of my External HDD suddenly not mounting

What file system is on it? If it's NTFS then use ntfs-3g
What is the output of:

Code:

fdisk -l /dev/sdb1

or

Code:

parted /dev/sdb1

Oh ok I can read.

Quote:

NTFS is either inconsistent, or there is a hardware fault

You may need to stick it into a microsoft machine and fix its file system.

rnturn · 10-29-2019, 08:43 AM

Quote:

Originally Posted by u9477100

I am quite new in Linux. My mobo is Gigabyte B85M-D3H. Processor i3. Ram 8GB. OS Linux Mint 19.2 One of my External HDD suddenly not mounting I can see it in Computer but cannot open it. It is connected Directly with the Box not by any hub. I used the folloing command but no result.

Code:

 soma@soma-B85M-D3H:~$ lsblk
NAME   MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
loop0    7:0    0 140.7M  1 loop /snap/gnome-3-26-1604/97
loop1    7:1    0  89.1M  1 loop /snap/core/7917
loop2    7:2    0  44.2M  1 loop /snap/gtk-common-themes/1353
loop3    7:3    0   156M  1 loop /snap/gnome-3-28-1804/91
loop4    7:4    0 150.2M  1 loop /snap/opera/57
loop5    7:5    0  28.9M  1 loop /snap/chromium-ffmpeg/15
loop6    7:6    0 229.7M  1 loop /snap/krita/52
loop7    7:7    0  84.3M  1 loop /snap/simplenote/129
loop8    7:8    0  54.5M  1 loop /snap/core18/1223
sda      8:0    0 931.5G  0 disk 
└─sda1   8:1    0 931.5G  0 part /
sdb      8:16   0 931.5G  0 disk 
└─sdb1   8:17   0 931.5G  0 part 
sr0     11:0    1  1024M  0 rom  
soma@soma-B85M-D3H:~$ grep $USER /etc/passwd
soma:x:1000:1000:soma,,,:/home/soma:/bin/bash
soma@soma-B85M-D3H:~$ sudo mount /dev/sdb1 /Full/path/ -
[sudo] password for soma:          
mount: bad usage
Try 'mount --help' for more information.
soma@soma-B85M-D3H:~$

I also tried

CODE] soma@soma-B85M-D3H:~$ sudo mount -t ntfs /dev/sdb1 /media
$MFTMirr does not match $MFT (record 0).

[snip]

First thing to do: Fix your "broken" CODE tag in the second bit of session you were trying to post. The content can still be read but it's a bit of a pain.

Second thing I'd do: Have you googled for that error message? I got a lot of hits when I did. Bottom line: Most of the hits suggest that the disk was unmounted incorrectly while on Windows. Did this come from a Windows system that suffered a crash? Or was the disk unplugged before it was finished writing data? Try plugging the drive into a Windows system (or, if you have one, booting your Windows partition) and running "scandisk". One post suggested that the disk might need defragging but I'm not experienced enough using NTFS disks to know whether that's a really useful suggestion or not. I suspect it's not but if "scandisk" doesn't show any NTFS errors I suppose it's worth doing the defragmentation on Windows. (Caveat: I don't do enough Windows any more to help out too much on that part. I'm just reporting what the pages returned by the Google said.)

Good luck...

Rickkkk · 10-29-2019, 09:39 AM

I concur that it sounds like either a corrupt file system or failing hardware.

I also concur with the recommendations of previous posters to hook it up to a Windows system and running the diagnostics / repairs from there and seeing what the results are.

Let us know how you make out.

uteck · 10-29-2019, 09:52 AM

Most trouble shooting in Linux can be solved by copy and paste the error message into Google. Usually the top results will get you going.

$MFTMirr does not match $MFT (record 0).
First search result goes into why this happens and recommends running the ntfsfix command. So in your case: sudo ntfsfix /dev/sdb1
If you don't have that command, that first result says to install the ntfs-3g package to get it and other ntfs tools installed.

Rickkkk · 10-29-2019, 10:11 AM

Quote:

Originally Posted by uteck

Most trouble shooting in Linux can be solved by copy and paste the error message into Google. Usually the top results will get you going.

$MFTMirr does not match $MFT (record 0).
First search result goes into why this happens and recommends running the ntfsfix command. So in your case: sudo ntfsfix /dev/sdb1
If you don't have that command, that first result says to install the ntfs-3g package to get it and other ntfs tools installed.

This is an interesting alternative to going back to Windows for repairs ... I have never used ntfs-3g's repair utilities - even though I rarely use ntfs on linux, it's good to know they exist

.

Thanks uteck.

teckk · 10-29-2019, 10:33 AM

Quote:

I have never used ntfs-3g's repair utilities

They don't do much @Rickkkk. You will usually have to stick it into a windows machine and let windows fix its proprietary file system.

If you unmount a ntfs volume and then pull out the usb plug before it's done umounting, you'll have a corrupt ntfs volume. The only way you'll fix it is with windows.

When you unmount a ntfs volume, wait 10 seconds after you umnount it before you pull the plug out. That will solve the problem. ntfs doesn't unmount as quickly as ext4 or fat.