Crash (not the issue), on reboot none of my other drives that were connected at the time will mount

This would be in the Kernel, boot, graphics & hardware category, but I’m only 75% sure the problem is of that nature, and I’m not exactly confident in my tech skills, so Newbie category it is. From what I remember of this particular forum software it shouldn’t be too hard to move me if that’s needed…?

Right so uh, a crash of unknown cause happened (but as the thread title says that isn’t what I’m seeking help with) and when I booted I couldn’t mount any of my other at the time connected drives besides the default one Endeavour is installed on. I have a whole separate Windows Drive in my computer that I select with a boot manager when I need Windows for something, neither of its partitions will mount, despite it still booting into Windows mostly fine. I have three external hard drives (though I usually only have one plugged in at a time, which will prove relevant in a second) and the one I had plugged in at the crash isn’t mounting either. The other two are still operating fine.

When mounting the now-problematic drives I get the error message (where [NUMERAL] is a consistent number for each error message and [DRIVE NAME] is the name of the drive)

The requested operation has failed: Error mounting /dev/sdc[NUMERAL] at /run/media/sysid-ace/[DRIVE NAME]: wrong fs type, bad option, bad superblock on /dev/sdc[NUMERAL], missing codepage or helper program, or other error

I read various threads by people suffering somewhat similar issues, but none of what people suggested in those threads that I tried worked, so here I am.

Among the things I’ve tried are

  • reinstalling ntfs-3g using yay
  • reinstalling ntfs-3g again using a more targeted pacman command, in case I got something wrong earlier (sudo pacman -S ntfs-3g was what it was)
  • running sudo ntfsfix /dev/sda1 (this just uh, couldn’t run)
  • reading half a thread where people speculate hardware issues are occurring, which I don’t think can be the case here

And maybe one or two other things.

One thing the drives are definitely not, I’d like to underscore again, are dead. I can boot into the Windows ones just fine, and even then read the problematic external drive when in Windows.

Anyway time for that stuff I’m meant to attach, huh? I hope I understood that post properly and am including all I need to…

https://0x0.st/84HO.txt

https://0x0.st/84HW.txt

NAME   TYPE   SIZE PTTYPE FSTYPE
sda    disk 931.5G gpt
├─sda1 part     1G gpt    vfat
└─sda2 part 930.5G gpt    ext4
sdb    disk   3.6T gpt
├─sdb1 part   100M gpt    vfat
├─sdb2 part    16M gpt
├─sdb3 part   1.4T gpt    ntfs
├─sdb4 part   518M gpt    ntfs
├─sdb5 part   500M gpt    ntfs
└─sdb6 part   1.9T gpt    ntfs
sdc    disk   3.6T gpt
├─sdc1 part    16M gpt
└─sdc2 part   3.6T gpt    ntfs

Boot into Windows and do a repair on NTFS drives. You can’t just ‘ntfsfix’ (hack) and expect good things to happen.
Best practice is to NOT use an alien filesystem in Linux.

1 Like

Welcome to the forum :enos_flag: :enos:

You can try this:

sudo ntfsfix --clear-dirty /dev/sdb3

Then try the same thing for the other partitions
Have to say just tried this and it worked for me.

1 Like

As I understand it, you’re just hackily setting the dirty bit off…you’re not fixing any possible errors, which can result in filesystem melt-downs.

No you are not fixing possible errors , I guess ,but you know I have to believe the topic starter that a thorough check for disk errors was done already, but you never no if that is correct :thinking:

NTFS is notorious for not existing clean. I would never ever use that format for my Linux.

1 Like
May 01 09:51:06 BEYONDEVENELSEWHERE kernel: ntfs3(sdc2): It is recommened to use chkdsk.
May 01 09:51:06 BEYONDEVENELSEWHERE kernel: ntfs3(sdc2): volume is dirty and "force" flag is not set!
May 01 09:52:11 BEYONDEVENELSEWHERE kernel: ntfs3(sdc2): It is recommened to use chkdsk.
May 01 09:52:11 BEYONDEVENELSEWHERE kernel: ntfs3(sdc2): volume is dirty and "force" flag is not set!
May 01 09:58:31 BEYONDEVENELSEWHERE kernel: ntfs3(sdc2): It is recommened to use chkdsk.
May 01 09:58:31 BEYONDEVENELSEWHERE kernel: ntfs3(sdc2): volume is dirty and "force" flag is not set!
May 01 09:59:37 BEYONDEVENELSEWHERE kernel: ntfs3(sdc2): It is recommened to use chkdsk.
May 01 09:59:38 BEYONDEVENELSEWHERE kernel: ntfs3(sdc2): volume is dirty and "force" flag is not set!
May 01 10:11:33 BEYONDEVENELSEWHERE kernel: ntfs3(sdb3): It is recommened to use chkdsk.
May 01 10:11:34 BEYONDEVENELSEWHERE kernel: ntfs3(sdb3): volume is dirty and "force" flag is not set!
May 01 10:11:37 BEYONDEVENELSEWHERE kernel: ntfs3(sdc2): It is recommened to use chkdsk.
May 01 10:11:37 BEYONDEVENELSEWHERE kernel: ntfs3(sdc2): volume is dirty and "force" flag is not set!
May 01 10:11:38 BEYONDEVENELSEWHERE kernel: ntfs3(sdb3): It is recommened to use chkdsk.
May 01 10:11:38 BEYONDEVENELSEWHERE kernel: ntfs3(sdb3): volume is dirty and "force" flag is not set!
May 01 10:11:39 BEYONDEVENELSEWHERE kernel: ntfs3(sdb6): It is recommened to use chkdsk.
May 01 10:11:41 BEYONDEVENELSEWHERE kernel: ntfs3(sdb6): volume is dirty and "force" flag is not set!

It is recommened to use chkdsk.

Use your Windows installation and run a chkdsk. Search for a proper execution of the command.

Also make sure that your Windows is shutting down properly and not hibernating and the like.

Thanks to dbarronoss and cactuax, even I should have thought of chkdsk repairing the drives over in Windows! Jeez, I’ve had to use that a few times in my time, but for some reason it wasn’t part of my workflow at all here!

Anyway thank you all for helping so quickly! We’re good to lock the thread now I think, but I’ll try to keep in mind that thing about not using NTFS on Linux systems… It’s not workable as advice I can implement Right right now, but I can definitely start changing some things to make it workable in the future…

1 Like

Just to finalize some things @sysid-ace

This is bad.

This is the truth.

This also means making sure ‘Fast Startup’ is disabled in windoze - otherwise it never shuts down. It is a common cause of the kinds of errors you experienced (even if it wasnt the reason for this problem), inability to use network cards, and more.

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.