![]() ![]() If you'd prefer to go first-party, it's worth seeing if your disk manufacturer has its own tool, such as Western Digital's Drive Utilities, or Seagate's handy SeaTools. That's where standalone programs come in handy, which can offer more extensive info.įor Windows, CrystalDiskInfo is a free tool that can delve a bit deeper into your disk's status, while macOS users should take a look at DriveDX, which costs $19.99 but comes with a free trial. tool is quick and easy, it doesn't do much beyond telling you whether your disk is fine or about to die. Note: This information won't appear if you're running a post-2015 machine with an SSD installed. status" section in the bottom-left, or by clicking the " i" icon in the top-right. Click the drive you want to check, and its status will read either " Verified" or " Failing" in the " S.M.A.R.T. The other option is to do what the original error message mentioned and erase the physical drive as GUID partition and MacOS Extended (Journaled), but of course you will need to temporarily transfer the files from the external Seagate drive to another location.To do this on macOS, open the Disk Utility tool by going to Applications, then Utilities. You could try using the paid app Disk Warrior to try to fix the HFS+ file system errors, but there is no guarantee it will do any better although I've found DW to do an extremely good job, but it won't repair APFS volumes. Even if First Aid shows everything as "Ok" click "Show Details" and manually scroll back through the report to see if there are any unfixed errors listed (more of a curiosity to see if is just hiding the problem from you). Have you tried using the other USB port? Or another USB cable?ĭisk Utility has never been very good at repairing file system issues plus I've seen First Aid actually lie to me about the status of a file system scan. ![]() However, the read & write speed reported is extremely slow even for a hard drive (especially the write speed). None of the usual hard drive health attributes are showing any problems. In any case, I would treat this as an unreliable drive unless you can run the long extended tests in DriveDX (not just the short test) and only if it get good scores on all the physical drive parameters.īy the way, Catalina can work well with both HFS+ and APFS external drives used for storage. When I saw that error on an external drive, I have never been able to rescue such a drive or repair it.Ĭan you still both read and write to the drive? It can examine the physical condition of both internal and external drives, provide you with information on physical errors, lifetime left on a drive, and temperature (running hot is another symptom of a failing drive), plus details on all the SMART parameters. I ended up purchasing it because I found it so useful. The physical condition can be checked with DriveDX, which can be used in a free mode for a short time. Remember that Disk Utility is checking the file system on the drive, which may be ok, but the drive could be starting to physically fail. I have seen that error message on external drives when they are starting to (physically) fail. ![]() So maybe asking again in 2020 could help. I'm out of options, and I can't either find what these errors means, nor how to fix them. Time Machine is disabled since 4 days and every external drive is unplugged. Running tmutil listlocalsnapshots / returns nothing as I don't have local snapshots. Running Disk Utility multiple times, as you can see from the past points, it's an entire week I'm continuosly running Disk Utility in normal and recovery mode. Recovery mode and "Reinstall MacOS" didn't fix it either Partition the disk manually (Disk Utility) doesn't work either Network Recovery, unmount volumes and use fsck_apfs -y I know this question may look like a duplicate, but I tried everything I can find online:įirst Aid in Recovery and Single User modes If I run first aid that's the output I get: I fixed it by running network recovery, unmounting the disk and analyzing them with fsck. Running First Aid it was giving me some orphaned files in the dstream. ![]() I'm using bootcamp, but it always get stuck at partitioning, telling me it can't partition the disk and check it and fix it with First Aid. Unfixable disk errors (Mismatch between extentref and fsroot & alloced_size of dstream does not match calculated size) I'm trying to install Windows along side my Mac OS (Catalina 10.15.15). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |