https://bugs.kde.org/show_bug.cgi?id=412145
--- Comment #1 from Brennan Kinney <[email protected]> --- Output for performing `sudo fsck.exfat /dev/sdc1` exfatfsck 1.3.0 Checking file system on /dev/sdc1. WARN: volume was not unmounted cleanly. ERROR: fsync failed: Input/output error. File system checking stopped. ERRORS FOUND: 1, FIXED: 0. The error appears tied to the device becoming unavailable. A physical unplug and re-plug is required as /dev/sdc1 is no longer available afterwards. The warning is the same given when performing `mount -t exfat /dev/sdc1 /mnt/usb_stick`. Windows 7 and Windows 10 systems detected the errors but both failed to repair. The repair/scan could be ignored and data could be copied off the disk, but write activity appears to cause the device to fail in Windows as well, and it becomes available until physical reconnection is made. --- When Windows 7 performed a repair/fix, I was able to mount successfully in Dolphin, although while browsing the files, Dolphin became unresponsive, and ksysguard reported 50% CPU usage(4 cores/threads system), htop revealed <5-10% CPU activity, and ksysguard processes(all) sorted by CPU column showed nothing high usage. Eventually that dropped and Dolphin became responsive again, the mounted location became unavailable and could not mount again. Possibly related to this old bug: https://bugs.kde.org/show_bug.cgi?id=347565 Although another exfat device unmounts cleanly without getting corrupted. --- Related issues: Notification Panel, incorrect error(different from Dolphin): https://bugs.kde.org/show_bug.cgi?id=412146 Partition Manager, gets stuck scanning devices after a failed mount: https://bugs.kde.org/show_bug.cgi?id=412147 -- You are receiving this mail because: You are watching all bug changes.
