The next time you see this, go launch Disk Utility and take a look at the drive. It’s hard to say, since the Samsung manuals I found don’t describe this, but it definitely looks like macOS is continuing to access the drive during this time. Usually, but not always, this is when another external drive is connected (and it doesn’t happen every time that another external drive is connected). Occasionally, the blue light will remain, more faintly than when it alternates flashes with the red. Usually within 15 seconds (and often much sooner), the flashing stops and both lights go out. If they would leave the drive icon in the Finder (desktop, sidebar, etc.) in a grayed-out form until the unmount completes, then most users would know enough to wait before disconnecting it.įWIW, the red light alternates with a blue light, sometimes many times. I’ve reported this to Apple as a bug, but so far it hasn’t been fixed. And then for good measure, if your drive has an in-use light, wait for it to stop blinking before disconnecting it. The workaround is to run Disk Utility and wait for all the volumes to turn gray after ejecting the volumes. This is especially significant if there are multiple APFS volumes (I see it big-time on my bootable backup media). If you disconnect it during this time, then the system will need to inspect/repair it before it can mount again. There’s a bug in macOS where you can eject a volume, but the icon will disappear from the Finder before the unmount operation completes. I had a problem recently where I thought I had ejected all of the volumes on a drive but apparently had not and when I took it back to the computer I normally use it with, only one volume came up A Time Machine APFS volume will have a snapshot for every backup, which could take a very long time to complete. Note that APFS volumes can take a long time to inspect, because it will have to inspect every snapshot. You want to let it run to completion, no matter how long it takes and anything you do to them (like unplug, reboot the computer, etc.) until it completes will likely make the process take even longer. If you see any line other than the grep fsck command you just typed in, then the fsck command is running in the background. To see if this is happening in your case, connect the drive and from a Terminal, type the command ps ax | grep fsck The process took a long time (many hours) to complete, but once it did, it mounted and seemed to work fine. As it turns out, it was because the boot sequence detected a problem and started running the fsck utility to inspect/repair the volume prior to mounting. I saw something like this years ago (not part of a system upgrade, but after a system crash), where a drive wouldn’t mount. #1666: Air quality websites and apps, The Password Gameīefore you do anything drastic, leave the drives connected and powered up for a few days.#1667: OS Rapid Security Responses, 1Password and 2FA, using Siri to request music.#1668: Updated Rapid Security Responses, OS public betas, screen saver bug fixed, “Red Team Blues” book review.#1669: OS security updates, ambiguity of emoji, small business payments with Melio, Twitter now X.#1670: Arc Web browser hits 1.0 release, “Do You Use It?” polls about Apple features.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |