4

Recently I have switched from Ubuntu 18.04 to Ubuntu 22.04. One of my external hard disks, a Western Digital Elements 3 TB hard disk, which has always mounted properly in 18.04, did mount and worked properly for a few days in 22.04. Then it stopped working because it became impossible to mount it. When using it with another computer under Windows 11, it mounts and works properly. The error message in Ubuntu 22.04:

Unable to access "Elements". 
Error mounting /dev/sdi1 at /media/lubomir/Elements1: Unknown error when mounting /dev/sdi1

Please help me to resolve this.

Ajay
  • 2,241

4 Answers4

5

Actually this worked for me.

  • Check the status of the disks by using : lsblk.
  • Then use the command : sudo ntfsfix /dev/sdb1, here replace the /dev/sdb1 drive with your drive name found using the lsblk.

More info from option 1 in this URL: https://learnubuntumate.weebly.com/fix-82038203error-mounting.html

guntbert
  • 13,475
Viraj
  • 101
2

I was able to fix it using Disks app -> Repair Filesystem.

enter image description here

karel
  • 122,292
  • 133
  • 301
  • 332
1

I thank everybody who responded so far. A solution was found successfully and it is, in a way, a collective solution based on a combination of more than one of the above pieces of advice, as follows. It turns out that this error was known when switching between 18.04 and 20.04 see the above response by steeldriver, and one of the solutions proposed there, worked here, too. Namely, on the terminal I started firs by 'sudo ntfsfix /dev/sdi1' with response 'Error opening '/dev/sdi1': No such file or directory. Volume is corrupt. You should run chkdsk.' This seems to suggest that the above response of waltinator directs towards the cause of the failure -- the harddisk was indeed working for some time in Windows 11 before moved back to Ubuntu 22.04. I did not rush to use chkdsk in Windows 11, however, and instead first ran in the terminal the second recommendation in the link provided by steeldriver: 'sudo apt install --reinstall ntfs-3g'. THIS SOLVED THE PROBLEM without resorting to using chkdsk in Windows.

1

check for the nfts file system install nfts using this command: sudo apt install nfts-3g