Say hi to everybody. I’m Egg, a newbie from Thailand.
I’m an old user of Ubuntu and Fedora, but this is my first time using Cachy OS (Arch Linux).
I feel like starting from zero with the command that is used for Cachy OS.
By the way, after using Cachy OS for about 5 days, I fell in love with Cachy OS.
But I found some problems connecting my ext. hdd., Cachy OS only found my ext. hdd. but cannot mount it. So I can’t transfer any files.
For more information about my ext. hdd.
- My ext. hdd. is ntfs
- I use it with Windows, Linux, Mac and TV.
- Inside this ext. hdd. has only movies (.mkv)
When I use it with Fedora, I can use it normally. (Nothing to do.)
When I use it with Ubuntu, I found the same problem as Cachy OS.
So I use this command, and the problem is gone.
echo ‘blacklist ntfs3’ | sudo tee /etc/modprobe.d/disable-ntfs3.conf
For Cachy OS, do we have any suggestions that can solve this problem?
Thank you for every answer.
I’m sorry to hear your having issues on ntfs, I have never had any issues on ntfs on Buntu or Arch.
df -hT ─╯
Filesystem Type Size Used Avail Use% Mounted on
dev devtmpfs 7.6G 0 7.6G 0% /dev
run tmpfs 7.8G 2.4M 7.8G 1% /run
efivarfs efivarfs 148K 69K 75K 49% /sys/firmware/efi/efivars
zpcachyos/ROOT/cos/root zfs 386G 9.4G 376G 3% /
tmpfs tmpfs 7.8G 25M 7.8G 1% /dev/shm
none tmpfs 1.0M 0 1.0M 0% /run/credentials/systemd-journald.service
none tmpfs 1.0M 0 1.0M 0% /run/credentials/systemd-resolved.service
tmpfs tmpfs 7.8G 20M 7.8G 1% /tmp
/dev/nvme1n1p1 vfat 511M 688K 511M 1% /boot/efi
zpcachyos/ROOT/cos/home zfs 435G 59G 376G 14% /home
zpcachyos/ROOT/cos/varlog zfs 376G 59M 376G 1% /var/log
zpcachyos/ROOT/cos/varcache zfs 382G 5.9G 376G 2% /var/cache
tank2 zfs 450G 109G 342G 25% /tank2
tmpfs tmpfs 1.6G 96K 1.6G 1% /run/user/1000
╭─░▒▓ ~/Cytadela on main ? ▓▒░──────────────────────────────────────────░▒▓ ✔ at 11:12:09 AM ▓▒░─╮
╰─ df -hT ─╯
Filesystem Type Size Used Avail Use% Mounted on
dev devtmpfs 7.6G 0 7.6G 0% /dev
run tmpfs 7.8G 2.4M 7.8G 1% /run
efivarfs efivarfs 148K 69K 75K 49% /sys/firmware/efi/efivars
zpcachyos/ROOT/cos/root zfs 386G 9.4G 376G 3% /
tmpfs tmpfs 7.8G 25M 7.8G 1% /dev/shm
none tmpfs 1.0M 0 1.0M 0% /run/credentials/systemd-journald.service
none tmpfs 1.0M 0 1.0M 0% /run/credentials/systemd-resolved.service
tmpfs tmpfs 7.8G 20M 7.8G 1% /tmp
/dev/nvme1n1p1 vfat 511M 688K 511M 1% /boot/efi
zpcachyos/ROOT/cos/home zfs 435G 59G 376G 14% /home
zpcachyos/ROOT/cos/varlog zfs 376G 59M 376G 1% /var/log
zpcachyos/ROOT/cos/varcache zfs 382G 5.9G 376G 2% /var/cache
tank2 zfs 450G 109G 342G 25% /tank2
tmpfs tmpfs 1.6G 96K 1.6G 1% /run/user/1000
/dev/sdf1 ntfs3 4.6T 4.3T 291G 94% /run/media/me/My Passport
Are you certain your not affected by the dirtybits.
On Arch Linux, an NTFS partition marked dirty prevents mounting because the file system metadata is inconsistent, often caused by Windows Fast Startup, improper shutdowns, or kernel updates.
sudo ntfsfix -d /dev/sdXN
After clearing the bit, you can mount the partition. If you prefer using the ntfs3 driver and want to ignore dirty flags in the future, you can add the force option to your /etc/fstab entry or mount command, though this is generally discouraged as it bypasses safety checks.
Alternatively, disabling Windows Fast Startup in Windows is the most effective way to prevent the dirty bit from appearing in the first place.
sudo ntfsfix -d /dev/sdf1 ─╯
Mounting volume... OK
Processing of $MFT and $MFTMirr completed successfully.
Checking the alternate boot sector... OK
NTFS volume version is 3.1.
NTFS partition /dev/sdf1 was processed successfully.
And Welcome @EDOUBLEG
Thank you for your warm welcome!!
According to your answer, I still have the same problem.
This is the error that I got when I click on my ext. hdd.
and this is error message from terminal.
Please provide the result of “lsblk -f”. You might also want to check the drive is accessible by attaching it as an external USB or directly to another Windows machine.
Hi and welcome. First of all, a little request: please post text instead of screenshots whenever possible. It is easier to read and to quote.
Regarding your issue: to me, this sounds pretty much like the HDD was not unmounted properly from Windows (== the “dirty bit” is still set).
If you still have a Windows machine around, open a terminal as administrator and run
sfc /scannow
and
chkdsk -f
on that drive, maybe also DISM.
See documentation:
This normally helps.
@anon15508052 What is ntfsfix? Never heard of it and neither pacman nor paru are able to find it anywhere…
It’s bundled in
1 cachyos-extra-v3/ntfs-3g 2022.10.3-2.1 [577.51 KiB 1.65 MiB]
NTFS filesystem driver and utilities
@glennguy Thanks for ur suggestion.
@HardCode4All So sorry that I used screenshots, next time I will use text as ur suggestion and thank you for ur help too.
Finally, I found the solution, but I’m not sure if this is the right solution or not.
I tried the alternative mounting method. I used the ntfs-3g driver explicitly.
sudo mount -t ntfs-3g /dev/sdb1 /mnt
I would have fixed it first before a force mount.
@anon15508052 I got it! I will fix it first. Thank you very much.
Didn’t I read somewhere that ntfs-3g is deprecated? And that ntfs3 is now part of the kernel? Could also remember that wrong, though.
You read right! but the Utility’s are missing from the kernel driver.
lsmod | rg ntf
ntfs3 352256 1
