Hi community,
I had no problem mounting my ntfs file external HDD and copy all my important hard work to this hard drive.
i unmounted and later after 20 min when i remounted the drive, the hard drive is empty, when i enter the properties i see that the file system type is somehow fuseblk.
i did the following to get permission to my files:
when i enter i can see that there is 68 folders but don’t show up in dolphine.
i ran the command:
mount | grep /dev/sdc1
/dev/sdc1 on /run/media/username/FCE70030E6FFE932 type fuseblk (rw,nosuid,nodev,relatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096,uhelper=udisks2)
This is how far i can get, i dont know where to take it from here, please help me to get access to my folders and files, they are really important to me, and i don’t want this problem again with any of my other external hard drive!
i have made changes to fstab, i dont know if its correct.
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a device; this may
# be used with UUID= as a more robust way to name devices that works even if
# disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
UUID=423E-B4E5 /boot/efi vfat umask=0077 0 2
UUID=dde9994f-55bb-42d8-8082-88eb99da6a9b / btrfs subvol=/@,defaults,discard=async,ssd 0 0
UUID=dde9994f-55bb-42d8-8082-88eb99da6a9b /home btrfs subvol=/@home,defaults,discard=async,ssd 0 0
UUID=dde9994f-55bb-42d8-8082-88eb99da6a9b /var/cache btrfs subvol=/@cache,defaults,discard=async,ssd 0 0
UUID=dde9994f-55bb-42d8-8082-88eb99da6a9b /var/log btrfs subvol=/@log,defaults,discard=async,ssd 0 0
UUID=5f3b70fe-cbe8-4643-96d8-c762dea5dc68 swap swap defaults,noatime 0 0
tmpfs /tmp tmpfs defaults,noatime,mode=1777 0 0
UUID=FCE70030E6FFE932 /run/media/username/FCE70030E6FFE932 /ntfs defaults 0 1
/FCE70030E6FFE932 is the mountpoint - a directory which must exist (maybe it does - I doubt it)
You can use any other name you like, but the directory has to exist before you can mount to it.
and /ntfs is supposed to be the filesystem type - it should be just ntfs (without the slash in front)
I can’t speak to the rest of the line - I’d have to look that up myself.
You very likely do neither need nor want to use this drive in this way anyway.
It was auto mounted - or at least through a GUI file manager.
You already unmounted it - plugging it back in (after disconnecting it) should show it again as present in your file manager (which you likely use).
Use a different port if you can.
ps:
you changed your line while I was writing - don’t use that directory
as it might not even exist at the moment - and this will be the place where it will be put by the automatism in your file manager anyway
suggestion:
open a terminal and type: journalctl -f
and Enter, of course
then watch the output as you plug in your drive
Blockquote ps:
you changed your line while I was writing - don’t use that directory
as it might not even exist at the moment - and this will be the place where it will be put by the automatism in your file manager anyway.
and your journalctl -f trace indicates to me that the filesystem is corrupt
The drive will only be readable - if even that (just like you described above)
A good filesystem check tool for ntfs filesystems is not available for Linux - AFAIK.
Not much you can do from here at this point.
NTFS is a native Windows filesystem - support for it in Linux is incomplete, esp. in regards to error correction.
Take the drive to a Windows machine and have it’s filesystem checked there.
That is the safest option to get to see your data intact again.
Just plug it in - the check will, from all I know, happen/start automatically.