this post was submitted on 29 May 2024
20 points (95.5% liked)

Linux

48323 readers
725 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 5 years ago
MODERATORS
AgreeableLandscape@lemmy.ml
nooter692@lemmy.ml
MarcellusDrum@lemmy.ml
cypherpunks@lemmy.ml
cyclohexane@lemmy.ml
d3Xt3r
20
[SOLVED] [Manjaro XFCE] Trying to mount an SSD but gives me a "Failed to mount" error (lemmy.world)
submitted 5 months ago* (last edited 5 months ago) by SpiceDealer@lemmy.world to c/linux@lemmy.ml
13 comments fedilink hide all child comments
 

I'm trying to mount one of my SSDs on my systems but it gives me this error when trying to mount from File System: "Failed to mount "New Volume" - No object for D-Bus interface." If I go into Gparted and check the description of the device in question it gives me this: $MFTMirr does not match $MFT (record 3). Failed to mount '/dev/nvme0n1p2': Input/output error NTFS is inconsistent. Run chkdsk /f on Windows then reboot it TWICE! The usage of the /f parameter is very IMPORTANT! No modification was made to NTFS by this software.

Failed to open '/dev/nvme0n1p2'.

$MFTMirr does not match $MFT (record 3). Failed to mount '/dev/nvme0n1p2': Input/output error NTFS is inconsistent. Run chkdsk /f on Windows then reboot it TWICE! The usage of the /f parameter is very IMPORTANT! No modification was made to NTFS by this software.

Unable to read the contents of this file system! Because of this some operations may be unavailable. The cause might be a missing software package. The following list of software packages is required for ntfs file system support: ntfs-3g / ntfsprogs.

If I run fsck -l in the terminal It returns this:

fsck from util-linux 2.40.1 e2fsck 1.47.0 (5-Feb-2023) ext2fs_open2: Bad magic number in super-block fsck.ext2: Superblock invalid, trying backup blocks... fsck.ext2: Bad magic number in super-block while trying to open /dev/nvme0n1

The superblock could not be read or does not describe a valid ext2/ext3/ext4 filesystem. If the device is valid and it really contains an ext2/ext3/ext4 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock: e2fsck -b 8193 <device> or e2fsck -b 32768 <device>

/dev/nvme0n1 contains DOS/MBR boot sector MS-MBR Windows 7 english at offset 0x163 "Invalid partition table" at offset 0x17b "Error loading operating system" at offset 0x19a "Missing operating system"; partition 1 : ID=0xee, start-CHS (0x0,0,2), end-CHS (0x30,254,63), startsector 1, 4294967295 sectors' data

Any advice? Thanks in advance.

Edit: I have since solved this issue with the help of @d3Xt3r@lemmy.nz. For anyone having a similar problem, the comment thread that led to the eventual solution is down below.

top 13 comments
sorted by: hot top controversial new old
[–] d3Xt3r 12 points 5 months ago* (last edited 5 months ago) (1 children)

The following list of software packages is required for ntfs file system support: ntfs-3g / ntfsprogs.

First of all, make sure you install ntfsprogs-ntfs3 from the AUR (this package doesn't install the old/buggy ntfs-3g driver).

Once it's installed, you can then then attempt to fix drive using sudo ntfsfix /dev/nvme0n1p2 --clear-dirty.

Run it a second time to verify, and that should do the trick. No need to boot into Windows.

Btw, in case you're mounting this drive manually, make sure you specify -t ntfs3, otherwise it'd use the old/buggy ntfs-3g driver - which we don't want. In fact, I'd say get rid of ntfs-3g if you've got it - no point keeping it around if you're on a recent kernel.

[–] SpiceDealer@lemmy.world 2 points 5 months ago (1 children)

I went ahead tried this but got an error when using makepkg -si:/home/[username]/ntfsprogs-ntfs3/PKGBUILD: line 45: autoreconf: command not found ==> ERROR: A failure occurred in build(). Aborting...

I went to file in question and line 45 says this: autoreconf -vfi

[–] d3Xt3r 4 points 5 months ago (1 children)

Do you have base-devel installed? If not, install that and try again.

[–] SpiceDealer@lemmy.world 5 points 5 months ago (1 children)

HOLY SHIT! YES! Thank you so much! I thought that drive was a goner. I was on the verge of just buying a new SSD. You just saved me a couple hundred bucks. Thank you once again!

[–] d3Xt3r 4 points 5 months ago (1 children)

Nice, glad that got sorted. :) BTW could you edit the title please and mark it as [SOLVED]? Thanks!

[–] SpiceDealer@lemmy.world 1 points 5 months ago

No problem.

[–] krolden@lemmy.ml 5 points 5 months ago

Run chkdsk /f on Windows then reboot it TWICE!

[–] bloodfart@lemmy.ml 5 points 5 months ago (1 children)

Stop trying to fsck a ntfs files system. Boot into windows and run chkdsk /f then reboot windows twice, like the program and the other person said.

Do you have ntfsprogs installed and can you confirm that the partition has an ntfs file system?

[–] SpiceDealer@lemmy.world 2 points 5 months ago (2 children)

That's the thing: I don't have Windows installed on that SSD. I double checked.

[–] bloodfart@lemmy.ml 2 points 5 months ago

Oh if you are sure it’s an ext file system, point fsck at the backup superblock with -b [block number].

Your fsck error says -b 8193 but id do -b 32768 instead. Just historically I’ve found more backup super blocks there.

[–] krolden@lemmy.ml 1 points 5 months ago (1 children)

So why use NTFS?

Download hirens bootcd or any other live windows image and use that

[–] furikuri@programming.dev 1 points 5 months ago

If it's an external SSD I could see it being useful in order to keep native compatibility with Windows and MacOS (IIRC their other option would be FAT32 but I don't use a Windows machine so who knows)

[–] some_guy@lemmy.sdf.org 2 points 5 months ago

This is one of those threads that I'm saving to my read-it-later app of choice because you never know. Awesome work, d3Xt3r.