i started using KDE Plasma officially about a week ago now and am running dual boot with windows 11 (both are on separate NVME drives)
I have two major issues and i think they are related to each other.
the first being, that every time i boot manjero, every drive aside from my root drive i have to remount. (even if i restart the computer and do not login to windows)
the second is today trying to mount my HDD’s, both refuse to mount (both are wd black 10tb pn:WD102FZBX), and i get the following error:
“An error occurred while accessing ‘big D 2.0’, the system responded: The requested operation has failed: Error mounting /dev/sdc2 at /run/media/lucas/big D 2.0: wrong fs type, bad option, bad superblock on /dev/sdc2, missing codepage or helper program, or other error”
All other drives mount fine. i have been able to mount and use drives fine yesterday, and this started after shutting down my computer last night.
i have searched google and a few threads on here and since i cannot share the link here is the title to the closest thread i could find:
[r/archlinux] • 1 yr. ago
error mounting/dev/sdb2 ar run/media wrong fs type, bad option, bad superblock on /dev/sdb2, missing codepage or helper program or other error
I followed each step from the reddit OP and here are inputs/outputs:
$ sudo fsck /dev/sdb2 ✔
[sudo] password for lucas:
fsck from util-linux 2.40.4
~ sudo ntfsfix /dev/sdb2 ✔ 4s
Mounting volume... OK
Processing of $MFT and $MFTMirr completed successfully.
Checking the alternate boot sector... OK
NTFS volume version is 3.1.
NTFS partition /dev/sdb2 was processed successfully.
~ sudo mount /dev/sdb2 /mnt ✔
~ sudo badblocks -v /dev/sdb2 ✔
badblocks: Value too large for defined data type invalid end block (9766418432): must be 32-bit value
~
When posting terminal output, copy the output and paste it here, wrapped in three (3) backticks, beforeANDafter the pasted text. Like this:
```
pasted text
```
Or three (3) tilde signs, like this:
~~~
pasted text
~~~
This will just cause it to be rendered like this:
Sed
sollicitudin dolor
eget nisl elit id
condimentum
arcu erat varius
cursus sem quis eros.
Instead of like this:
Sed sollicitudin dolor eget nisl elit id condimentum arcu erat varius cursus sem quis eros.
Alternatively, paste the text you wish to format as terminal output, select all pasted text, and click the </> button on the taskbar. This will indent the whole pasted section with one TAB, causing it to render the same way as described above.
Thereby increasing legibility thus making it easier for those trying to provide assistance.
For more information, please see:
As I’m a moderator on the forum, I have taken the liberty of doing this for you, this time.
Additionally
If your language isn’t English, please prepend any and all terminal commands with LC_ALL=C. For example:
LC_ALL=C bluetoothctl
This will just cause the terminal output to be in English, making it easier to understand and debug.
Note that the above text is partially pre-prepared as a general introduction for new forum Users. Please take the time to to understand how it is done and encourage quality responses.
When dual booting it is crutial to switch off Windoze’ “Fast startup” feature which basically does a hibernate/sleep instead of shutting down. This causes issues when sharing ntfs partitions with Linux, especially if the ntfs3 driver (new default) is used which is a bit more sensitive for dirty bit being set.
Other than locking the Windoze partitions the “Fast startup” feature keeps the Windoze firmware loaded (instead of flushing it at reboot) on wifi chips (and possibly other hardware). This causes the Linux firmware to fail to load and wifi (and possibly other hardware) become unavailable on Linux.
It seems you might also benefit from the link given (see my previous post). The information will help you understand why blacklisting NTFS3 in favour of NTFS-3G (which was once actively suggested) is not a solution to the problem.
If the NTFS file system is damaged, there is only one reliable tool to repair that file system, and that is chkdsk which must be run from a Windows environment.
Of course, if the disk in question is not part of a functioning Windows OS, reformatting it to a native Linux file system is always preferable.
Thanks all for the fast replies. Unfortunately as soon as i posted the thread, my HDD’s decided to work fine again, which made replicating the issue much more difficult. i was able to get it to replicate once more by just walking away from my computer for bit (frustratingly) , and i did as many of you have recommended. Disabled windows fast boot, chkdsk (ran both disks were fine), and mounted from konsole. since doing these i have not been able to replicate the issue.
What still does not make sense to me, is why both of my HDD’s were affected, but none of my NVME, or SSD were affected. They all run NTFS except the Manjero root drive.
Tip