Posting to see if anyone is having similar issues.
I have an external 256GB m.2 SATA SSD, formatted with APFS, in an enclosure which has worked well for a few years. Its been connected by USB-C to my Mac.
It was working the other day but after updating to 11.2.3 I am unable to use the drive. It does not seem to mount, and when I plug it in it shows up as a drive in Finder but when I click to browse it, I get the spinning loading indicator which never stops.
It does not show up in the Disk Utility GUI either, though I can sometimes see it in
As of now I am unsure if the drive is on its way out, in which case I just need to copy everything over to my internal SSD to save it, or if perhaps a bug was introduced in the latest update which might be sorted out when 11.3 is released in a week or so.
I found some old posts when searching online, indicating if the drive is on its way out fsck can get stuck running on the drive when it first connects, preventing it from being usable. I haven't been able to figure out if that is the case.
One other thing to note, the drive is very full. As in 255.8 GB out of 256.1, was thinking perhaps the EFI partition ran out of space and the drive locks up when trying to initialize.
Any thoughts? Thanks
I have an external 256GB m.2 SATA SSD, formatted with APFS, in an enclosure which has worked well for a few years. Its been connected by USB-C to my Mac.
It was working the other day but after updating to 11.2.3 I am unable to use the drive. It does not seem to mount, and when I plug it in it shows up as a drive in Finder but when I click to browse it, I get the spinning loading indicator which never stops.
It does not show up in the Disk Utility GUI either, though I can sometimes see it in
diskutil list.As of now I am unsure if the drive is on its way out, in which case I just need to copy everything over to my internal SSD to save it, or if perhaps a bug was introduced in the latest update which might be sorted out when 11.3 is released in a week or so.
I found some old posts when searching online, indicating if the drive is on its way out fsck can get stuck running on the drive when it first connects, preventing it from being usable. I haven't been able to figure out if that is the case.
One other thing to note, the drive is very full. As in 255.8 GB out of 256.1, was thinking perhaps the EFI partition ran out of space and the drive locks up when trying to initialize.
Any thoughts? Thanks