fsck failed

[trvatrva]

I have problem with my Sumsung Portable SSD T5 (SSD disk). I can't mount it in my system. I wrote in bash:

sudo fsck /dev/sdb1

and reply is:

fsck from util-linux 2.41.3
fsck: fsck.ntfs not found; ignore /dev/sdb1

Can you help me to fix my SSD Disk by fsck.

[oshunluvr]

There isn't an fsck for ntfs because it's not a Linux file system.

I assume you are sharing this device with a Windows machine so use that to attempt repair.

[Snowhog]

Warning: AI answers can be wrong

AI Overview

The fsck command is ignoring /dev/sdb1 because Linux does not have a standard filesystem check utility called fsck.ntfs natively mapped to its automatic checking tool. The fsck wrapper wrapper utility only knows how to handle native Linux filesystems (like ext4) out of the box.
You can fix this error and successfully check or repair your NTFS drive using two different methods:

Method 1: Use ntfsfix (Recommended)

Instead of relying on fsck, you should use ntfsfix. This tool comes bundled with standard NTFS drivers in Ubuntu/Kubuntu and is specifically designed to handle basic NTFS inconsistencies and clean up dirty volume flags.

• Open your terminal.

• Run the following command directly on your partition:

sudo ntfsfix /dev/sdb1

[oshunluvr]

I believe that ntfsfix only resets the "dirty" flag and does not actually check the file system.

[die.boer]

first identify the filesystem on the SSD before attempting any repairs.
plug in the SSD and run

lsblk -f​

post output here
if the SSD doesn't appear in the output, we should investigate USB detection before trying to repair its filesystem

[claydoh]

Also, add more details if you can, such as what exactly is happening when you are trying to mount the partition, the errors seen, how you are trying to mount this, and what is on the partition.
What is pointing you to try using fsck?

There are many reasons why something won't mount so the more info you have, the easier it will be to narrow things down.

If this happens to be your Windows drive, do look at disabling Windows fast-startup. This puts hardware in a hibernation state, and can lock the drive from access in onter operating systems.