![]() ![]() It is impossible to recover accidentally deleted data from an SSD after the Trash has been emptied, plus an SSD can fail at any time without any warning signs (even a brand new SSD).Īnother Followup Update: I got MacOS Monterey 12.3.1 installled and working on an early-2015 13" MacBook Air that has a third party SSD. People should always have frequent and regular backups of their computer and all external media (including cloud stored items) which include important & unique data. It is so important, that I will reiterate it here: I hope others will read you post and see how beneficial your backup was. About the only ways to detect a bad SSD is by seeing if a Kernel Panic report mentions "nvme" issues, booting from an external drive and waiting to see if the internal SSD disappears from the bus, or by installing another SSD to see if the problem disappears (using an SSD adapter complicates matters too). Unfortunately many SSD failures today don't show up in the SMART health report since it is usually the SSD's controller that tends to fail. Unfortunately DriveDx and other similar apps do not always correctly interpret the SMART health attributes so a manual inspection and interpretation is best (there are a lot of false failure warnings that may not actually be a problem). Post the complete DriveDx text report here using the "Additional Text" icon which looks like a piece of paper. Unfortunately with most current SSDs today, even if the SSD does support SMART health monitoring, they don't tend to include a lot of details in the health report like the older SSDs did. I'm not sure if Fledging even supports SMART health monitoring, but if it does, then perhaps there may be a clue in the health report. ![]() I've never heard of "Fledging" before, but you may want to try checking the health of the SSD by running DriveDx. But what happened? Was it just standard APFS file system corruption that First Aid could not fix, or was there a third party app causing a problem after the update, or did the SSD have a physical problem that damaged either the file system or system files? Most likely erasing the SSD was the trick. If the M.2 SSD works with either of these options, then the SSD adapter is likely the problem. To test an M.2 SSD you would need to use a generic PC, or install the M.2 SSD into a USB M.2 enclosure to see if the SSD is Ok. If you are using a standard M.2 SSD, then from reading these forums I have discovered the only reliable & compatible SSD adapter is from Sintech. If you are using an OWC Aura SSD, then contact OWC tech support for assistance. If the physical drive does not appear on the left pane of Disk Utility, then it may mean the SSD or possibly the SSD adapter is bad. Within Disk Utility you may need to click "View" and select "Show All Devices" so that the physical drives appear on the left pane of Disk Utility. Keep in mind the third party NVMe SSD will only be visible while booted to macOS 10.13+ since older versons of macOS don't have the necessary NVMe driver. Thoughts or other directions to go with this.? I tried to downgrade to Catalina from a bootable USB, but the installer does not "see" the installed Fledging SSD. Wondering if this update has screwed up SSD firmware or the ability of these laptops to recognize these SSDs. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |