-
Notifications
You must be signed in to change notification settings - Fork 186
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to repair files with ERROR: bad date 1980-01-00. #160
Comments
facing the same issue |
Same on Linux 5.10.23-1-MANJARO : $ sudo exfatfsck -y /dev/mmcblk0p1
exfatfsck 1.3.0
Checking file system on /dev/mmcblk0p1.
File system version 1.0
Sector size 512 bytes
Cluster size 128 KB
Volume size 119 GB
Used space 38 GB
Available space 81 GB
ERROR: bad date 1980-00-00.
ERROR: bad date 1980-00-00.
ERROR: bad date 1980-00-00.
ERROR: bad date 1980-00-00.
Totally 101 directories and 421 files.
File system checking finished. ERRORS FOUND: 4, FIXED: 0. |
facing the same issue. After the files are removed from the disk, the ➜ ~ sudo fsck -n /dev/sdb1 |
exfatksck can't fix errors like this for now. Leaving this as TODO reminder for me. |
When I first run this, I get
WARN: volume was not unmounted cleanly.
, and then I get:ERROR: bad date 1980-01-00.
I'm willing to bet this is because I think I ejected improperly from my macOS laptop, and now Ubuntu is unhappy with me because of the timezone formatting differences.
Is there a way to automatically repair this issue?
The text was updated successfully, but these errors were encountered: