Comment on Screw it, I’m installing Linux
BartyDeCanter@lemmy.sdf.org 1 day agoEh? I’ve never had a problem with reading NTFS drives in linux, including USB sticks and SATA/USB adapters. Are you just wanting to read them or use them as read/write? Write is a bit more tricky, requiring ntfs-3g, but most reasonable distros come with that nowadays.
LoafedBurrito@lemmy.world 1 day ago
Read/Write and linux will disconnect them randomly and they show up as a completely different drive. So i tried to permanently mount the UID in fstab, but still didn’t work. Most of the fixes i’ve found online don’t work for my drives.
Fantabread@lemmy.world 21 hours ago
I had the same problem with USB docks. The filesystem didn’t matter. Without going into much detail, the solution is to use the usb-storage driver with quirks enabled instead of the uas driver. I blacklisted uas to force usb-storage on the affected devices. Some googling should turn up decent instructions.
BartyDeCanter@lemmy.sdf.org 1 day ago
Interesting. When you say that they show up as a different drive completely, do you mean that their UUIDs change, or that they get mounted at a different point?
Anyway, random disconnection sounds like a hardware issue, maybe a USB brownout, as much as anything else. What’s your connection setup, distro and kernel version?
LoafedBurrito@lemmy.world 1 day ago
The mounting point changes. So it may be sd1, then disconnect and show up as sb1 and then i tried to permanently mount through fstab, but still didn’t work. Connection setup? Not sure what you mean by that, but computer is hardwired to the network, external drive was connected via USB 3.0 in several different ports to see if it was a motherboard issue. I am on Cinnamon Mint 22 and i believe kernel 6.14.
BartyDeCanter@lemmy.sdf.org 1 day ago
The mount point changing like that means that it disconnected and then reconnected. That really makes it sound like the drive isn’t getting quite enough power, which causes a brown out, which Linux detects as the drive getting unplugged and coming back, which is why it gets a new dev entry.
A look through the usb logs by using something like usbrip would confirm that.