J'ai un 4TB HDD used for storing backups made by UrBackup server run on Ubuntu - but formatted as NTFS. (Ie, data was written by linux on NTFS drive). In windows Explorer and on Ubuntu it reports as being less than half full when asked about disk space. When trying to write any fichier vers le drive: On Ubuntu, it acts full (ne peut pas remember the exact erreur message, but c'est quelque chose about being full), and on Windows, it gives erreur "Erreur 0x8007012E: The volume is too fragmented to complete this operation." Windows' "Optimize Drives" dialog says "last analyzed or optimized: Jamais run" and "Current status: Optimization not disponible" - ie Windows ne va pas let me defrag it. When using windows "chkdsk /f" it jamais completes -- au moins, it seemed to be stuck in a loop, so I gave up on it and closed it. HWiNFO64 reports healthy. CrystalDiskInfo reports healthy. WinDirStat says il y a over 8TB of data stored (drive is seulement 4TB), so I'm guessing there doit être window's version of Hard Links present. (Not that hard links are bad, c'est just a data point).
Après collecting all this information, Je ne suis pas sûr what to do next: Je viens de want to understand qu'est-ce que going on avec this drive.
TL;DR: HDD acts full (Je ne peux pas write any nouveau data) but reports as half full. Is it a bad drive? What tool puis-je use to figure this out? Je veux be able to store more data on it.
HDD: 0x8007012E The volume is too fragmented to complete this operation
Re: HDD: 0x8007012E The volume is too fragmented to complete this operation
Your fichier système is corrupted - save your data and reformat the
disk. Check well the correctness du saved data.
The problème that `chkdsk` jamais completes pourrait être parce que the
corruption is too profound.
The fact that WinDirStat finds double the data than is
the capacity du disk, is probably explained by crossed
fichier-chains, so that the same data is counted twice (or more).
HWiNFO64 and CrystalDiskInfo report the disk as healthy, but
you'd better keep on checking the SMART data dans le future.
Si le problème repeats dans le future, it pourrait être healthier not
to let this Linux product do extensive mises à jour to an NTFS disk.
disk. Check well the correctness du saved data.
The problème that `chkdsk` jamais completes pourrait être parce que the
corruption is too profound.
The fact that WinDirStat finds double the data than is
the capacity du disk, is probably explained by crossed
fichier-chains, so that the same data is counted twice (or more).
HWiNFO64 and CrystalDiskInfo report the disk as healthy, but
you'd better keep on checking the SMART data dans le future.
Si le problème repeats dans le future, it pourrait être healthier not
to let this Linux product do extensive mises à jour to an NTFS disk.