I just had the exact same problem with a ntfs drive.
Did that. Took a second to fix it. Done & dusted. Same thing might work on FAT.
Thanks to @akya
Now I going to step away from ntfs & stick with linux file systems.
1 Like
Are you mounting this drive via /etc/fstab or manually?
i have tried to mount it through dolphin and i have also tired though command line the error i keep getting is failed mouting wrong fs type bad option bad superblock. i was able to get my ntfs drive mounted but was never able to get the fat32 drive to mount installeing ntfs-automount was able to fix half my problem.
Same problem here. Before doing the last update these days Manjaro recognized ntfs and fat systems on several external drives. After the update it shows the error mentioned above. Other linux systems do not have that problem. So it seems not to be a Windows system failure to repair with chdsk but related to the Manjaro update.
1 Like
This happened to me yesterday with my external USB drive, the ext4 partition worked fine but the NTFS one had the same error.
I tried the ntfstools option but it didn’t work for me.
I then fired up a Win10 VM and it popped up the “there is a problem with this drive” type error, I chose the scan and repair option and it sorted it.
See if the following helps… 
sudo pacman -S ntfs-3g
sudo bash -c 'echo "blacklist ntfs3" > /etc/modprobe.d/disable-ntfs3.conf'
Reboot after the changes.
4 Likes
‘Bad superblock’ usually indicates corruption or damage to a drive; in fact, it can’t mean much different to that. The suggested usage of chkdsk /f X: from within Windows, as an alternative to fsck in Linux, is valid; despite your apparent strawman hypothesis to the contrary; which itself was irrelevant.
In simpler English, a bad superblock can be corrected by either fsck or chkdsk, and has nothing to do whatsoever with any issue resulting from a Manjaro update; whether perceived or actual.
As this was your first post, welcome, and I’m happy to direct you to additional resources before making your next:
1 Like
This helped and solved all my issues.
@soundofthunder I don’t know why you have to be so passive aggressive in your comments. This isn’t a drive problem, thousands of people didn’t suddenly do something to their drives right after the update. Aragorns two commands fixed all my issue and I bet most people issues.
3 Likes
I were being passively aggressive I am confident that you would not even recognize it as such; however, let me address your misguided assumptions in context:
- Information provided by Medec5:
This clearly indicated a drive problem. In fact the error bad superblock has no other interpretation; as far as I am aware.
Based on that information my response was valid. If you have another interpretation, please enlighten us ( ← that was passive aggressiveness ).
- Post from Cornwol:
This also supported my stance.
While I’m glad that your issue was solved, the commands provided by Aragorn fixed issues that were unrelated to a ‘bad superblock’:
sudo pacman -S ntfs-3g … installs ntfs-3g; we might think of it as a translation assistant for NTFS.
sudo bash -c 'echo "blacklist ntfs3" > /etc/modprobe.d/disable-ntfs3.conf disables a similar translation assistant that isn’t playing nicely.
In short, stating that;
… also has nothing to do with my response to a bad superblock error.
I hope this helps. Cheers.
How do you know he hasn’t already got ntfs-3g.? I already have that one installed. It’s included with Manjaro. ntfs3 isn’t installed on my system.?
Pacman would indicate that it was already installed, and ask for permission to reinstall it; reinstalling would likely cause no harm.
That’s my point really. Check first that it’s already installed, especially as ntfs-3g seems to come as standard with Manjaro.
The other thing is mount -t vfat… I’ve never needed to use those options with mount. Linux always seems to recognise partition formats, eg I have an ESP (FAT32 partition) sdb7. So if I want to mount it I use sudo mount /dev/sdb7 /mnt, and that always does the job.
It’s not a separate package. It’s the in-kernel driver, and in recent kernels, it is the default.
ntfs-3g is a separate package, and whether it’s installed or not, if the default is to use ntfs3, then ntfs3 needs to be blacklisted and ntfs-3g used instead. If ntfs-3g is already installed, then reinstalling it won’t cause any problems.
There’s an echo in here… 
Not really. @bendipa1 asked the question how I knew that it’s not already installed. My response meant to convey that I don’t know that, but that if it is indeed already installed, then reinstalling it won’t cause any harm, and therefore, the command I gave to the OP would still work. 
Ah, so, something like this …
Got it! 
1 Like
OK. Thnx for that… Now I know, although on other Linux dists I’ve used ntfs-3g seems to be a package that always comes with them.
2 Likes
Hi. This also solved my problem. Definitively this is an error of the latest update of manjaro, not something related to disks.
Despite there being endless duplicate threads on this same subject, and numerous posts in each thread outlining the situation to varying degrees of verbosity … somehow … the basics are continually skipped over.
There is a new module in new kernels ntfs3 … in the past ntfs-3g was used.
ntfs-3g would more or less use --force by default … meaning it would mount ntfs partitions even if they were marked dirty.
You can go back to using ntfs-3g by making sure it is installed and blacklisting the new module.
But in most cases this is likely just willfully ignoring the real problem (and possibly causing continual harm to your partition and its data).
Its quite possible there are situations where the new ntfs3 is failing for no good reason.
I dont use the proprietary filesystem enough to have much of an opinion on the new module.
But complaining that ‘something broke because of an error from the update’ is missing the mark on numerous counts - and quite possibly facilitates continued bad practice.
( use the corpo OS, or a derivative like Hirens, and run chkdsk on the problematic partitions, then treat them correctly moving forward, like properly unmounting, and disabling ‘fast startup’ in windoze and so on )
3 Likes
No, this is wrong: I had two disks with NTFS format, one old and another completely new. I checked both with chkdsk with no error at all in any of them. The problem IS NOT in the partition or disks, its a problem in manjaro new driver or update. Stop lying and complaining about drives or disks, the source of the problem is completely clear.
1 Like