Failed to mount TOSHIBA EXT
Error mounting /dev/sda1: wrong fs type, bad option, bad superblock on /dev/sda1, missing code page or helper program, or other error.
I found an article online suggesting I use fsck /dev/sda1 but the graphic shows a warning that I will cause severe damage to my system.
Another Toshiba HDD mounts just fine on my system. There is still a lot I don’t wish to lose on the HDD that is not mounting. Please can someone help or advise?
The picture clearly suggests that fsck should not be run on a mounted drive. Boot with a Live Installer, for example, and run it from there while the disk/partition is in an unmounted state.
There are likely another methods, but that might be easiest for you if you are unfamiliar with terminal commands.
If it’s not you main drive, then that part isn’t necessary. I think. But it can’t so any harm either.
Since it’s possibly NTFS, your best bet would be to let Windows deal with it. Scan the disk for problems with Windows. Look at Hiren’s rescue PE for that it you don’t have Windows:
If the drive is formatted as NTFS do not use fsck; instead, consider @Mirdarthos comment; unless:
Does this drive contain anything you wish to keep?
Do you wish to use this drive as extra storage for Manjaro?
If you answer no to the first question, and yes to the second question, it might be easier to create a new GPT partition table, create a partition, and format it as ext4; and then just run fsck as previously described.
Doing so will destroy all data currently on the drive, and prepare it for use as additional storage for manjaro. From that point, it’s only a matter of creating a mount point to the drive and adding the correct entry in the /etc/fstab file. There will be someone here who can guide you, if needed.
chkdsk on Windows (since Linux doesn’t have that) or simply blacklist the new kernel driver ntfs3 and use the userspace driver ntfs-3g instead. ntfs3 refuse to mount when it is in a dirty state.