Greetings,
I have a USB flash drive that has a small NTFS partition, and the rest is ext4.
When I plug it in to my Xfce MX Linux box, the ext4 partition mounts automatically.
But I cannot figure out how to mount the NTFS partition (I need to copy a file from the NTFS partition to the ext4 partition).
Both “gparted” and “lsblk --fs” see and report on the NTFS partition. So it is just a matter of using the “mount” command (or some other command or GUI that someone can recommend).
I ran:
$ man mount
…and it gave me a headache.
I ran:
$ mount -U someUUIDnumber (that I copied/pasted from the lsblk --fs output.
That complained about not being found in /etc/fstab. And that is where the trail turns cold.
How do I mount the USB flash drive's NTFS partition?
Linux mount command question for USB drive containing ext4 and NTFS partitions [Solved]
Re: Linux mount command question for USB drive containing ext4 and NTFS partitions [Solved]
I found the problem and it is resolved.
When I plugged the drive into my Windows box, it asked to check the file system. It then asked to repair it.
Upon doing so, my MX Linux box mounts it.
But a slap on the wrist for Linux not detecting the problem or (if it did detect it) not offering any help.
When I plugged the drive into my Windows box, it asked to check the file system. It then asked to repair it.
Upon doing so, my MX Linux box mounts it.
But a slap on the wrist for Linux not detecting the problem or (if it did detect it) not offering any help.
Re: Linux mount command question for USB drive containing ext4 and NTFS partitions
Linux did detect it, that's why it refused to show it.
Windows will not tell you that a ntfs partition has a dirty flag, it just grinds away trying to work it out and writing spurious log files endlessly causing the machine to run poorly. If Windows doesn't tell you until the filesystem is broken and near the point of data loss, why would you expect Linux to shout it from the rooftop?
Windows will not tell you that a ntfs partition has a dirty flag, it just grinds away trying to work it out and writing spurious log files endlessly causing the machine to run poorly. If Windows doesn't tell you until the filesystem is broken and near the point of data loss, why would you expect Linux to shout it from the rooftop?
Mike P
Regd Linux User #472293
(Daily) Lenovo T560, i7-6600U, 16GB, 2.0TB SSD, MX_ahs
(ManCave) AMD Ryzen 5 5600G, 32G, 8TB mixed, MX_ahs
(Spare)2017 Macbook Air 7,2, 8GB, 256GB SSD, MX_ahs
Regd Linux User #472293
(Daily) Lenovo T560, i7-6600U, 16GB, 2.0TB SSD, MX_ahs
(ManCave) AMD Ryzen 5 5600G, 32G, 8TB mixed, MX_ahs
(Spare)2017 Macbook Air 7,2, 8GB, 256GB SSD, MX_ahs
Re: Linux mount command question for USB drive containing ext4 and NTFS partitions
It is all well and good for Linux to detect the issue. But if it keeps it to itself; if it does not offer a message when the USB drive is plugged in and the user is expecting it to mount, then how is that helpful?m_pav wrote: Thu Mar 24, 2022 3:22 am Linux did detect it, that's why it refused to show it.
Windows will not tell you that a ntfs partition has a dirty flag, it just grinds away trying to work it out and writing spurious log files endlessly causing the machine to run poorly. If Windows doesn't tell you until the filesystem is broken and near the point of data loss, why would you expect Linux to shout it from the rooftop?
If your doctor sees an issue, but tells no one, that is not helpful.
Windows did tell me that there was a dirty flag (not in those words). When I plugged in the USB drive, it recommended that I let it do a scan. I clicked "Yes", and the scan reported issues and fixed them.
Windows did not do what you wrote. It did not grind away. If fixed it as soon as I plugged in the drive.
Re: Linux mount command question for USB drive containing ext4 and NTFS partitions
@Butters there is a difference between a dirty flag and a nearly borked partition. Windows trudges along for far too long with drives in poor condition.
As for Linux telling you, are you not the administrator of your own system? As the administrator, it's up to you to track your own log files, that is unless you want your machine to interrupt you with spurious messages printed to your display, most of which require no action every time a log file is written to.
With Linux, it's your choice, have it your way. Allow the log files to litter your experience, or learn how to administer your system, which may require the occasional peek at the log files or use of the command line.
As for Linux telling you, are you not the administrator of your own system? As the administrator, it's up to you to track your own log files, that is unless you want your machine to interrupt you with spurious messages printed to your display, most of which require no action every time a log file is written to.
With Linux, it's your choice, have it your way. Allow the log files to litter your experience, or learn how to administer your system, which may require the occasional peek at the log files or use of the command line.
Mike P
Regd Linux User #472293
(Daily) Lenovo T560, i7-6600U, 16GB, 2.0TB SSD, MX_ahs
(ManCave) AMD Ryzen 5 5600G, 32G, 8TB mixed, MX_ahs
(Spare)2017 Macbook Air 7,2, 8GB, 256GB SSD, MX_ahs
Regd Linux User #472293
(Daily) Lenovo T560, i7-6600U, 16GB, 2.0TB SSD, MX_ahs
(ManCave) AMD Ryzen 5 5600G, 32G, 8TB mixed, MX_ahs
(Spare)2017 Macbook Air 7,2, 8GB, 256GB SSD, MX_ahs