So no bugs or problems, just a misunderstanding on my part. I have been testing with an external USB 3.0 hdd and I get consistent results on Fedora, Windows 10 and Arch linux even if it is formatted as NTFS. This however takes a long time because the usb drive is just very slow. However, as they were cached, they were still being written to the usb device (and the unmounting took very long as it was waiting on this write). What happened is that the entire test was small enough to be swallowed up by the writecache reporting to the graphical copying dialog that the copy was complete. A few very big ones but most of them were only a few kb. The case for which I opened the thread is writing a lot(about 900) smaller files to my usb drive. I tried it with a few different drives and I can now say with confidence that it is a fluke due to the nature of writecaching and the very very slow writing of small files to usb sticks. As far as I can tell, my drives are being automounted with the async option (a lot faster than sync, so I prefer this default setting). Thanks! I have been testing a lot today and I came across the sync/async mounting option. You won't get your prompt back until the copy is complete You can also tell it not to copy asynchronously with (I think) the 'flush' option when you mount - but that may be an old method. Linux cannot run in NTFS mode this is a Windows thingy - a USB drive must be in FAT32 and also you cannot install linux kernel in a ntfs partition see the Linux not windows article and also '_guide on the archlinux wiki. It might be I configured some of them poorly and they are interfering (might not be as logical as I installed postfix, nginx, gitlab, php-fpm, openssh, phpmyadmin and mariadb which have nothing to do with removable devices). This is my first Arch install and I have been installing services like crazy the last few days. If I try an fuser -mv on the mounted spot after a (forced) release (/run/media//), it says that there are quite a few users on that spot even though they have nothing to do there but I don't think that is the problem as the problem only arises after I write to the usb stick myself.Īnyone any clue as to what is going on? Thank you guys very much in advance!! After the (forced) release, the write seems to have succeeded and the drive is still usable. The second time it took 10-20 minutes before it released it again. The first time this released the drive back and I could mount it again. I have tried killing the umount and mount.ntfs process. If I run umount from another terminal (while the original one hangs), I get an error saying it is not mounted. If I remove the usb stick, it is in an unusable state and no computer can read from it anymore and I need to repartition it. I also tried manually umounting it from a terminal but the process never ends. I tried using the umount/eject from Thunar (I use XFCE as a desktop) which displays the spinner and just hangs. However, if I first write to the usb stick and wait for that to finish, the unmount/ejecting process hangs. If I try to eject/unmount directly after the partitioning, it works fine and the usb stick seems happy. Filesystems not directly supported by the kernel can be mounted via a -bare attach and then invoking the relevant FUSE driver. To partition the stick, I used GParted with an MBR partition table. This means that it's not possible to use installed filesystem drivers (such as ntfs-3g for example) by calling wsl -mount. I have been having some issues regarding writing to an NTFS formatted USB 3.0 stick and than unmounting it. Will continue to debugĮDIT2: I found out that it isn't actually a bug/problem. d: clear-dirty - Clear the volume dirty flagĥ.EDIT1: I am having the same problems with an USB 2 stick that is NTFS formatted.b: clear-bad-sectors - Clear the bad sector list.Now run the ntfs-3g command to check/repair your corrupt/problematic NTFS partition: If you do not have ntfs-3g installed, you can install it using the following command:Ĥ. Please note, the command is 'umount' and not 'unmount.'ģ. Now unmount the NTFS partition using the following command. In my case, the NTFS parition is '/dev/sda6.'Ģ. You should be getting a list of parition as shown in the image below. NTFS-3G can create, remove, rename, move files, directories, hard links, and streams it can read and write normal and transparently compressed files, including streams and sparse files it can handle special files like symbolic links, devices, and FIFOs, ACL, extended attributes moreover it provides full file access right and ownership support. First list all the partition in your hard drive. Few days back I used GParted to expand my main ext4 partition that has Ubuntu installed on it by using a chunk from another NTFS partition. & I am know why this issue has cropped up. Ntfsclone-ng.c: NTFS Volume '/dev/sda6/' is scheduled for a check or it was shutdown uncleanly. Twice I got the following error, when I tried to backup my full hard drive by using Clonezilla. Since yesterday, I've been trying to backup my hard drive using Clonezilla but without any success.
0 Comments
Leave a Reply. |