Question

3

Mount exited with exit code 13

rated 0 times [ 3] [ 0] / answers: 1 / hits: 31986 / 1 Year ago, fri, january 27, 2023, 10:23:45

I have a 1TB external hard drive that I recently formatted to NTFS. It was mounting on my Ubuntu 11.10 fine until just now. I didn't make any changes to affect my OS or my exhdd.

The error that I get is:

Error mounting: mount exited with exit code 13: $MFTMirr does not match $MFT (record 0).

Failed to mount '/dev/sdb2': 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.

I did read this and this. But neither helped.

I tried installing ntfsfix but no such package exists anymore.
I have never used this HDD on a windows machine. If I need to use an other machine to do stuff to fix this, I have access to a mac.

Any advice?

This is my sudo fdisk -l output:
What in the world is GPT? I didn't do that. It used to be NTFS.

Disk /dev/sda: 500.1 GB, 500107862016 bytes

255 heads, 63 sectors/track, 60801 cylinders, total 976773168 sectors

Units = sectors of 1 * 512 = 512 bytes

Sector size (logical/physical): 512 bytes / 512 bytes

I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk identifier: 0x000586fb



   Device Boot      Start         End      Blocks   Id  System

/dev/sda1   *        2148   961320312   480659082+  83  Linux

/dev/sda2       961320313   976773167     7726427+   5  Extended

/dev/sda5       961320314   976773167     7726427   83  Linux



WARNING: GPT (GUID Partition Table) detected on '/dev/sdb'! The util fdisk doesn't support GPT. Use GNU Parted.





Disk /dev/sdb: 1000.2 GB, 1000204886016 bytes

255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors

Units = sectors of 1 * 512 = 512 bytes

Sector size (logical/physical): 512 bytes / 512 bytes

I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk identifier: 0xcfd88605



   Device Boot      Start         End      Blocks   Id  System

/dev/sdb1               1  1953525167   976762583+  ee  GPT

Answers

Only authorized users can answer the question. Please sign in first, or register a free account.

mouedi

Add To Favorites

Follow

Total Points: 420

Total Questions: 109

Total Answers: 116

Location: Philippines

Member since Wed, Aug 19, 2020

4 Years ago

answered 1 Year ago thellfi · Accepted Answer

GPT is the GUID Partition Table, which is the next-generation partitioning system used on Macs, UEFI-based PCs, and disks over 2TiB in size. It can also be used on smaller disks even on BIOS-based systems, so long as you don't expect to boot Windows from such disks. As the fdisk warning message notes, fdisk doesn't support GPT, so you shouldn't attempt to use fdisk on this disk. Instead, use gdisk (part of the gdisk or gptfdisk package, depending on how you install it) or parted.

GPT doesn't have anything to do with your problem, though. The mount error message indicates an I/O error, which most probably indicates a hardware fault. You might try running a SMART test on the disk using a tool like gsmartcontrol (GUI) or smartctl (text-mode). This should turn up any hardware fault, but the output of a SMART test can be hard to interpret. Since you say it's an external drive, it could also be a loose or damaged cable, so you might try reseating or replacing it. Cable faults won't turn up in a SMART test.

More generally, if it's not actually a hardware fault, you cannot do adequate filesystem tests on NTFS from either Linux or OS X; only Windows provides tools to do this. You may not be able to mount an NTFS disk that needs filesystem checks, so you must be able to get an NTFS disk to a Windows system from time to time to deal with such problems. If you never use the disk on a Windows system, NTFS is the wrong filesystem to use on it.

For Linux-only use, it's best to use a Linux-native filesystem, such as ext2fs, ext3fs, ext4fs, ReiserFS, XFS, JFS, or perhaps Btrfs. (I wouldn't use ext2fs on a 1TB disk, though.) If you use the disk for both Linux and OS X, I'd use either FAT or HFS+. Despite its age, FAT is still the best-supported cross-OS filesystem. It has problems with a maximum file size of 4GiB, though, which can be a problem if you store multimedia or other big files. HFS+ is OK for Linux/OS X use, provided you understand how to disable the journal and deal with permissions issues. (If the journal is enabled, Linux won't write to HFS+ unless you use an override mount option, which may reduce safety.)