Unable to mount FAT32 fs pendrive:/

[ineedserioushelp]

Here’s the info:

Disk /dev/sdb: 58.45 GiB, 62763565056 bytes, 122585088 sectors
Disk model: Cruzer Blade    
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x136c604a
Device     Boot Start       End   Sectors  Size Id Type
/dev/sdb1        8192 122585087 122576896 58.4G  c W95 FAT32 (LBA)

I get an error while mounting it, but the error doesn’t specifies any reason. Here’s the error screenshot: https://imgur.com/6zycvS1.png
Is there a way to access it without having to format it? Or should I go for an OTG Cable?

[maycne.sonahoz]

You may have a better error message trying to mount from the terminal:

mount -t auto /dev/sdb1 /run/media/devadvik/3B22C7AE0ADDE826

---

@maycne.sonahoz

Avoid using screenshots of text outputs.
It is largely preferred to post text outputs as preformatted text , so your helpers can directly use them, and may help other users in need to find your thread.

[ineedserioushelp]

Here’s the USB info:

Disk /dev/sdb: 58.45 GiB, 62763565056 bytes, 122585088 sectors
Disk model: Cruzer Blade
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x136c604a

Device Boot Start End Sectors Size Id Type
/dev/sdb1 8192 122585087 122576896 58.4G c W95 FAT32 (LBA)

Error Text:

$MFTMirr does not match $MFT (record 0).Failed to mount '/dev/sdb1': Input/output errorNTFS 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.

Is there a way to access it without having to format it? Or should I go for an OTG Cable?

I’m not using windows in dual boot, just the Manjaro OS. But idk why it says to reboot into windows:/

[koshikas]

that is not a FAT32 error, rather an NTFS error. first try repairing it from Manjaro;

sudo ntfsfix -d /dev/sdb1

if it fails you will have to use ;

chkdsk /f <drive>

in windows

[ineedserioushelp]

Here’s the USB info:

Disk /dev/sdb: 58.45 GiB, 62763565056 bytes, 122585088 sectors
Disk model: Cruzer Blade
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x136c604a

Device Boot Start End Sectors Size Id Type
/dev/sdb1 8192 122585087 122576896 58.4G c W95 FAT32 (LBA)

Error Text:

$MFTMirr does not match $MFT (record 0).Failed to mount '/dev/sdb1': Input/output errorNTFS 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.

Is there a way to access it without having to format it? Or should I go for an OTG Cable?

I’m not using windows in dual boot, just the Manjaro OS. But idk why it says to reboot into windows:/

[linux-aarhus]

@ineedserioushelp

Disklabel type: dos
Disk identifier: 0x136c604a

Device Boot Start End Sectors Size Id Type
/dev/sdb1 8192 122585087 122576896 58.4G c W95 FAT32 (LBA)

@ineedserioushelp

NTFS is either inconsistent, or there is a hardware fault, or it's a SoftRAID/FakeRAID hardware

@ineedserioushelp

But idk why it says to reboot into windows:

Because the system cannot figure out if it is FAT32 or NTFS - there is errors.

@ineedserioushelp

Is there a way to access it without having to format it

Create a disk image from the stick - then mount the image on loop device and use forensic tools like testdisk to find if there is salvagable data.

When you have an image - you can format the stick - or put in a drawer until you have the guts to do it.

[ineedserioushelp]

Refusing to operate on read-write mounted device /dev/sdb1.
This is what I get. I don’t have windows tho

[ineedserioushelp]

I’ll try that, thanks!

[linux-aarhus]

@ineedserioushelp

Refusing to operate on read-write mounted device /dev/sdb1.

sudo umount /dev/sdb1

Then run the command again.

There is a risk of losing your data because the command operates on the assumption your device is NTFS formatted.

If you know that to be true - then it’s OK - but as your topic title states you assume it is FAT32.

[ineedserioushelp]

Ok so that command did failed but for some reason after running that, I was able to access my USB. Idk how but yeah.
Thanks alot!

[linux-aarhus]

@ineedserioushelp

I was able to access my USB

You have had a last minute luck or rescue - now backup your valuables - then reset the stick - if you don’t share crossplatform - use Linux filesystem.