11
Mint-Arch migration led to unmountable drive (lemmy.dbzer0.com)
submitted 1 year ago by to c/linux4noobs@lemmy.world
10 comments fedilink hide all child comments
 

Just installed CachyOS and the drive I used alongside system drive for media\archive storage can't get mounted anymore. It's internal HDD and uses NTFS, I created it on Windows 10 years ago and used all this time from under Mint (no dualboot, only Mint). I did a regular reboot before OS switch and didn't even mount it this time.

While trying to access said drive, dolphin prints that:

An error occurred while accessing 'drive', the system responded: The requested operation has failed: Error mounting /dev/sda1 at /run/media/user/drive: wrong fs type, bad option, bad superblock on /dev/sda1, missing codepage or helper program, or other error

Where can I start my fixing journey? Where I can look for precise reason it fails?

All components are 5-10 years old if it matters. The other HDD that I formatted under Mint works just fine. It's probably a CachyOS vs NTFS problem.

[new]

I succeed at force-mounting it via ntfs 3g, but it seems it really was a problem with a bad block or something originating from windows. Checks were passed with 0 errors, so I assume it's a little funni M$ gave me with a divorce letter.

Instead of finding a way to force-mount it every time, I tried checking it via WinPE, and it helped remove the cause of errors.

I'm yet to understand what is really behind that, filesystem differences and how OSs work with them, so if you have good articles, please share these.

all 10 comments

sorted by: hot top controversial new old
[–] 6 points 1 year ago (3 children)

What was your mount command? You might have to do something like mount -t ntfs3 /dev/sda1 /whereveryouwannamountthething or edit your fstab entry, something like /dev/sda1 /whereveryouwannamountthething ntfs3 defaults 0 0

Here's the Arch wiki page for NTFS, the Arch wiki is usually where I'd start for fixing stuff, their documentation is fantastic.

  • permalink
  • fedilink
  • source
  • hideshow 3 child comments
    •
  • [–] 2 points 8 months ago* (last edited 8 months ago)

    If adding entries to your using fstab you should probably use UUID's instead of device names.

    To get the UUID type sudo blkid | grep /dev/sdb2 where /dev/sdb2 is replaced with your partition name. This should give you the UUID for your partition.

    Then you can make an entry into your fstab that looks like this.

    #/dev/sdb2
UUID=6CE0B016E0AFE514   /mnt/Disk_2     ntfs3            rw,relatime     0       0

    The reason you want to use UUID's is because the device name /dev/sda, /dev/sdb etc... can change but the UUID of your partition stays the same.

  • permalink
  • fedilink
  • source
  • parent
    • [–] 5 points 1 year ago (3 children)

    You are most likely only missing ntfs support, which seems to not be installed by default: https://unix.stackexchange.com/questions/363583/cant-mount-ntfs-on-arch-linux

    I'm not familiar with cachy-os but since its based on arch, the following should work:

    pacman -Syu 
pacman -S ntfs-3g
  • permalink
  • fedilink
  • source
  • hideshow 3 child comments
    •
  • [–] 3 points 1 year ago

    Not sure if cachy-os will auto mount. But after installing the ntfs-3g package, make sure you reboot.

    If it still doesn't work you can try to manually mount it or edit you're fstab so it it auto-mounted and assigned to the same device label.

  • permalink
  • fedilink
  • source
  • parent
  • [–] [S] 1 point 1 year ago (1 child)

    Thank you. I resolved the issue thanks to our brainstorming. Upd in OP.

    (Sorry for a copy-paste answer, it's not about you, it's that my anxiety doesn't handle personal adresses well rn)

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 2 points 1 year ago

    NTFS doesn't like to not cleanly getting shit down. I remember I needed to boot windows again and then shutdown, in order to access my NTFS volume from Linux, because last time windows didnt shutdown cleanly. Glad you got it fixed

  • permalink
  • fedilink
  • source
  • parent
    • [–] 3 points 1 year ago* (1 child)

    see if you can get it to manually mount with ntfs-3g. If you can, set an auto mount after.

    Manually it should look something like

    sudo mkdir /mnt/drivename

    sudo mount ntfs-3g /dev/sda1 /mnt/drivename

  • permalink
  • fedilink
  • source
  • hideshow 1 child comment
    •