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.
No problem.