NTFS partitions won't mount after failed sleep

Hi all,

I am having an issue accessing my other drives. This came after last night when I tried to turn on the PC which had gone into sleep on its own so I can shut it down, but it was unresponsive with a black screen so i ended up holding the power button to turn it off. This was not the first time I did that, but usually there isn’t an issue afterwards. (The sleep problem is a separate issue)

So now when I try to open the drives in dolphin like I usually do, I type in my pw and then get this error:

An error occurred while accessing ‘Games’, the system responded: The requested operation has failed: Error mounting /dev/nvme1n1p2 at /run/media/xxx/yyy: wrong fs type, bad option, bad superblock on /dev/nvme1n1p2, missing codepage or helper program, or other error

Here’s the result of my lsblk -f

lsblk -f
NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS
sda
├─sda1
└─sda2 ntfs xxx 66F4551CF454F033
sdb
├─sdb1
└─sdb2 ntfs yyy 7ADCB87CDCB8346B
nvme1n1
├─nvme1n1p1
└─nvme1n1p2 ntfs zzz 66F4551CF454F033
nvme0n1
├─nvme0n1p1 vfat FAT32 FE5B-E15A 298.4M 0% /boot/efi
├─nvme0n1p2 btrfs 114c93e4-68f1-4223-864b-6ea1b61ef0ad 791.7G 13% /var/cache
│ /var/log
│ /home
│ /
└─nvme0n1p3 swap 1 swap c92522df-6e8f-43d7-a505-546ac947d509 [SWAP]

So I can access the root drive which is good, but I can’t open ‘xxx’, ‘yyy’, or ‘zzz’

I tried booting off a fresh manjaro from USB, and still couldn’t access the drives (same error), and timeshift didn’t help either.

EDIT
The solution was:
-running windows 10 through virtualbox
-using that to make a bootable drive with Hiren’s boot CD (https://www.hirensbootcd.org/)
-booting into that
-running chkdsk on all my drives (~10 hour job)

They’re all ntfs, so boot up windows and run chkdisk on them. If you don’t have windows then you might be able to use the hirens boot cd.

You should be able to mount them after that.

In future try this :down_arrow: instead (it needs to be enabled first).

3 Likes

I no longer have windows, but those drives were set up back when I still did.
Some web searching led me to this site

Download | Hiren's BootCD PE

Are you suggesting I boot into that, and then run chkdsk?

1 Like

You should consider using a native filesystem, otherwise you’ll have this issue again in future.

Yes, but I’ve never used it myself. AFAIK that’s the only way to do it without windows.

1 Like

Thanks for the help.
Any suggestions for doing that while preserving my files?

A Windows installation in e.g. Virtualbox will also work fine. I’ve done this before. One just needs to enable decent USB support and attach the external drive(s).

It might be handy to keep a Windows VM around whilst still needing to manage legacy NTFS partitions.

1 Like

Fix your ntfs partitions first.

Then one partition at a time.

  1. Copy the files somewhere safe (another partition)
  2. Check they copied properly
  3. Reformat the partition
  4. Copy the files back.
  5. Check they copied properly

Repeat.

3 Likes

Ok so I got windows running in virtualbox. Problem is I don’t know how to pipe my drives into there. Any advice?

You’ll need to go into the VB machine settings (with the virtual machine not running, or paused etc. otherwise you won’t be able to change the settings), and add a USB controller.

Then you should be able to attach your USB drive and select it from a list of “detected devices”.

I don’t have any VMs set up on this particular machine yet, so will have to get back to you with e.g. screenshots later, if you need them. :wink:

Screenshots would be super helpful thanks. I don’t need any data from the drives right now so no rush.

Turns out I did have a few VMs copied over, just not all of them:

… See where my mouse pointer is? I think that’s what you’ll need to select. I don’t have any USB storage attached at the moment, though, and that VM is in a “Saved” state so not sure if I could add one anyway.

It’s not detecting my usb devices. I tried installing the virtualbox extension pack and that didn’t help.

Is the VM you set up in a “Powered Off” state? Otherwise the options for USB type etc. will be greyed-out (unselectable) anyway.

I just switched to one of the others which is “Powered Off”, and the USB device (a Ventoy-formatted stick) I’d plugged in prior to this showed up straight away. :thinking:

Yes it is.
edit: I saw the error. trying to figure out what that means in the manual

I think the top image you just added explains it. I completely forgot about that, sorry.

ETA:

sudo usermod -aG vboxusers $USER

should fix this. It’s been ages since I originally set up VirtualBox so had to dig that one up. :wink:

Oh, and you need to log out and back in.

1 Like

Thanks, I arrived at the conclusion right before i saw this message. Working on formatting the drive now. It’s taking its time, will update how it goes.

1 Like

There’s another thing to consider (which, AFAIK shouldn’t be such an issue in KDE Plasma) that the host system can “grab” the device, making it unavailable to the guest.

I don’t have anything set to “auto-mount” as I do that manually when I need to. :wink:

It worked. TYSM everyone.

1 Like

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