I use for my truck music. Its simply music I place on drive. Problem is EOS will not open drive. My head unit requires Fat32, or Ex Fat, but either or. It don’t matter. When I try, I get:
OK. Apparently Something inst quite right. I can accept that. What perturbs me is I can connect the same drive to a Pop OS system, and it has no problem reading drive. This is the only reason why I keep Pop OS on my laptop. After thinking about it I come to the conclusion that I appreciate the variances. If one doesn’t work I try another. Ultimately the goal is met, and one can move on. My only regret is EOS has problem with a drive that another OS doesn’t.
GParted is a partition manager, to my knowledge. Interesting that it doesn’t show anythin- The file system is NTFS. I wonder if that is somehow related…
Yea. I forgot it was ntfs . Interesting that ntfs is causing the problems it is though. I ll have to dink around with ntfsfix now. Thankyou for the heads up.
It s Interestingly though. Addressing the fact that Pop OS opens the drive without any hesitation when EOS precludes any movement forward begs questions…though I can already guess where that line of reasoning will go…
I tend to disagree. ntfs3 driver is mature enough for daily operations, and constantly being improved. You will not get super performance, and there are some caveats, but I don’t know about nothing which would justify opinion “bad idea”. Source: I use it daily for one year.
Unless you plan on using a drive with a Windows environment at any point, there’s no reason to use NTFS (and even then, ExFAT is a more universally useful format - I have yet to find a device that supports NTFS but not ExFAT, and own many, many devices that specifically require FAT32/ExFAT rather than NTFS).
Yes, till you get a dirty filesystem and have to use a native Windows installation to fix it. It doesn’t play nicely. Or you get a corrupted filesystem…
I tend to disagree. While it is mature enough to use and to my knowledge is developed by Microsoft themselves, if you use NTFS somewhere, it is likely because you have Windows installed. Reading and writing to a file system and booting up from it will very likely get you into problems at some point, sooner or later. It has happened to me before and I had to re-install Windows because of it.
I’m going to kick this dead horse and explain why I need ntfs. I have several large music and 4k movie files that are too large for Linux to transfer using fat32. My lg oled tv does not see exfat but does see ntfs. This is the same for the excellon headunit in my truck.
The wiki may tell you the following two commands will fix the problem:
$ sudo ntfsfix --clear-dirty /dev/sdb1
$ sudo ntfsfix -d /dev/sda2
Not fortunately, the two commands still do not work.
As far as i know, only the following method will work with thunar. (During a past upgrading, the same error occured to me. By a step by step upgrading each time with ten packages targeted, i successfully detected the following error-making packages.)
$ yay -Rdd libblockdev-crypto libblockdev-fs libblockdev-loop libblockdev-mdraid libblockdev-nvme libblockdev-part libblockdev-swap
You said that your Pop OS Linux install can read your ntfs external hard drive at the moment, correct?
And your EOS install still gives the error message above at the moment?
If so, what is the output after you tried to connect your hard drive:
sudo dmesg -H | grep -i ntfs3
What ntfs package is installed on your EOS? (yay -Ss ntfs)
. Interesting that ntfs is causing the problems it is though. I ll have to dink around with ntfsfix now. Thankyou for the heads up.