Eject Disk Error Message

By +Steve B
in Apple (macOS)

 Share

Recommended Posts

Mentor

+Steve B Subscriber²

Posted
  • Subscriber²
Posted

Is anyone else getting the error message you get when unplugging a disk such as an external HDD without ejecting it first? Lately, I've been noticing it and I haven't done anything. I do have one external HDD for time machine and its still plugged in. This message has popped up about 3 times now for no reason.

Link to comment
https://www.neowin.net/forum/topic/1061204-eject-disk-error-message/
Share on other sites
Grand Master

Nick H. Supervisor

Posted
  • Supervisor
Posted

Maybe it's to do with a power saving setting? The drive goes to sleep but the computer thinks that it disconnected without properly ejecting?

That's a total stab in the dark, I don't believe it's the cause myself. But it's the only thing I can think of right now.

Mentor

+Steve B Subscriber²

Posted
  • Author
  • Subscriber²
Posted

Well twice now, it was one my screen (login screen) when coming to my computer after not being used for a few hours. I would use my computer, click on "login window" and my computer's screen would go off after a while and I would come back, click on the track pad and the screen would come on and I would see the login window but I would also see the message about the disk not being ejected properly.

  • 2 weeks later...
Mentor

+Steve B Subscriber²

Posted
  • Author
  • Subscriber²
Posted

Apparently, this is a more wide-spread issue then I thought. i did some searching and people with various brands of external HDDs are reporting this problem. Some have resolved it by turning off the built-in sleep timer and it looks like some others are still having the problem such as myself. I've tried possible solutions such as shutting off the built-in sleep timer but to no avail.

Grand Master

.Neo

Posted
Posted

Can't edit my post anymore, but I wanted to add: Not all external drives respect the operating system's preferences. So even though you told OS X (or Windows for that matter) to not put your hard disks to sleep, the drive's firmware could overwrite that and go idle regardless. This explains why unchecking "Put the hard disk(s) to sleep when possible" doesn't solve the problem for everyone.

Mentor

+Steve B Subscriber²

Posted
  • Author
  • Subscriber²
Posted

Can't edit my post anymore, but I wanted to add: Not all external drives respect the operating system's preferences. So even though you told OS X (or Windows for that matter) to not put your hard disks to sleep, the drive's firmware could overwrite that and go idle regardless. This explains why unchecking "Put the hard disk(s) to sleep when possible" doesn't solve the problem for everyone.

I actually went into the external drive's settings via WD software and told it to disable to the sleep timer along with going into the OSX energy saver preferences and unchecking that box. You did have a good point which is true about it not solving the problem for everyone. From what I've found in internet and other forum searches is that certain things have resolved it for some while other things have solved it for other people.

Have you tried researching this in their own support forums? You're probably not the only person having this issue and they may have offered a solution. If you do find one, come and share it here!

That actually was going to be my next shot. I actually hadn't gone there yet only because I thought maybe OSX was at fault (I was only guessing) but, I will be going to WD support forums and seeing what I can find out.
Grand Master

.Neo

Posted
Posted

I actually went into the external drive's settings via WD software and told it to disable to the sleep timer along with going into the OSX energy saver preferences and unchecking that box.

In that case I'd contact WesternDigital. I did so in the past and they were fairly (strong emphasis on fairly :p ) fast in getting back to me. It doesn't seem like this issue lies with OS X.

Mentor

+Steve B Subscriber²

Posted
  • Author
  • Subscriber²
Posted

In that case I'd contact WesternDigital. I did so in the past and they were fairly (strong emphasis on fairly :p ) fast in getting back to me. It doesn't seem like this issue lies with OS X.

I completely agree with you. I think this drive or current firmware (yes, FW is up to date) is crap. Its being random now whether I can get it to mount at all. I sent in for a RMA replacement as its still under warranty. Its replacement should be here soon and the current one will be going back. That's going to be my next step. We'll see how it goes from that point on.

Mentor

+Steve B Subscriber²

Posted
  • Author
  • Subscriber²
Posted

Keep us posted! Interested to learn how this thing plays out. :)

If I had to take a stab at this and guess. My best guess would be that its bad firmware. Even though I told the drive's own sleep timer to never sleep, it still does it. The System Preferences regarding HDD sleep is also unchecked.

Community Regular

brink668

Posted
Posted

I had the same problem with my mouse and keyboard on an iMac as well Circa 2009ish model. Would randomly make the disconnect and connect noise. No functionality loss just would happen at times. I disabled my Bluetooth at one point and all of that stopped. I have no idea if that was what caused all of that to stop. I would say firmware or driver problem. Check for updates.

  • 2 weeks later...
  • 2 weeks later...
This topic is now closed to further replies.
 Share
Go to topic listing

  • Recently Browsing   0 members

    • No registered users viewing this page.

  • Posts

    • UK nudity blockers are a looming privacy disaster, we must be able to see the source code

      By ExecutiveFunction404 · Posted

      Wonder what MPs have ties to these privacy/verification/data harvesting companies that are going to step in this time. Last time under the Tories half the cabinet had fingers in the pies, heck even the PM and his wife at the time was working for silicon valley, probably made a fortune.
    • Google Chrome is killing all uBlock Origin bypasses, Microsoft Edge, Opera to follow

      By hellowalkman · Posted

      Google Chrome is killing all uBlock Origin bypasses, Microsoft Edge, Opera to follow by Sayan Sen For a while now the transition away from Manifest V2 (MV2) to MV3 has been on-going and it looks like it is entering its final phase of deprecation, at least, in the case of Google Chrome. A recent discussion thread in the w3c WebExtensions Community Group GitHub repo has highlighted how the latest and upcoming versions of the most popular browser are expected to be its final releases with support for MV2 extensions. Chromium contributor Andrey Bershanskiy shared details about recent Chromium changes and according to comments from Google engineer Devlin Cronin, Chrome has now started removing the flags that previously controlled MV2 availability. kExtensionManifestV2Disabled, the Chromium feature flag that allowed controlled disabling of MV2 add-ons, is now completely removed, which means you will likely no longer find uBlock Origin in your browser extensions list. He wrote: "The kExtensionManifestV2Disabled feature has been default-enabled for over a year. Remove the feature and the effectively-dead code. ... Any tests that relied on being in the "warning" phase (i.e., with the kExtensionManifestV2Disabled) for their sole behavior testing are removed, since this stage is no longer reachable." Cronin further explained why MV2 extensions are no longer allowed in supported Chrome versions as maintaining the associated functionality indefinitely is no longer possible. He cited growing technical difficulties and implementation complexities as well as security concerns. He wrote: "MV2 extensions are no longer allowed in any supported version of Chrome, and we are removing support for them and the associated functionality. We won't be able to provide / maintain this functionality indefinitely due to the complexity and tech debt, as well as the security risks it entails (we've actually found a number of bugs that are specific to MV2 lately). Of course, other browsers can continue supporting these if they so desire. Unfortunately, we won't be putting code behind a compilation flag ... We won't be removing all the MV2 code wholesale right away, so many of these things will continue working for awhile (but they will go away eventually, and some may go away sooner than others)." What this essentially means is that the tricks and bypasses that were used to keep MV2 extensions like uBlock Origin and others alive will not work any more on Chrome, or at least not for very long. For example the Windows Registry mod that could extend MV2 availability will cease to function after Chromium version 151. Here is a rundown of the changes coming in the final such releases of Chromium releases: Chromium 150 lost ExtensionManifestV2Disabled option Chromium 151 will loose ExtensionManifestV2Unsupported option Chromium 151 will loose ExtensionManifestV2Availability option Chromium 151 will likely loose AllowLegacyMV2Extensions option Other Chromium-based browsers like Opera and Microsoft Edge could soon follow suit too. Although it is not specified, Edge began disabling uBlock Origin back in February, and Opera could also stop the functioning of MV2 add-ons, even though it had committed to support MV2 for longer in October 2024. uBlock Origin developer Raymond Hill (gorhill) apparently stated the following: "For Opera I did submit 1.70.0 rather late, but this was weeks ago. A while ago I received an email from Opera that they plan to abandon MV2-based extension so maybe they are no longer allocating resources for reviewing such extensions." The email which developers like Gorhill mentions was received from Opera last year. Here is what it seemingly said: Hence for now the only Chromium browser that seems to be on-board fully with MV2 support is Brave, and perhaps Vivaldi as well. Meanwhile if you want to ditch Chromium browsers entirely then Mozilla Firefox is an excellent alternative as MV3 and MV2 are both supported. Of course the easiest solution is to switch to uBlock Origin Lite if you want to remain on Chrome, as it is MV3-based, but from our experience, uBO Lite does not seem to be as good as the original non-Lite version. Source: w3C (GitHub repo) As an online publication, Neowin too relies on ads for operating costs and, if you use an ad blocker, we'd appreciate being whitelisted. In addition, we have an ad-free subscription for $28 a year, which is another way to show support!
    • UK nudity blockers are a looming privacy disaster, we must be able to see the source code

      By ParadiseLost · Posted

      Write to your MP 😄 Like believing in Santa. Total surveillance IS the goal. Wake up.
    • Politically funny images of the World

      By PsYcHoKiLLa · Posted

    • UK nudity blockers are a looming privacy disaster, we must be able to see the source code

      By RejZoR · Posted

      This whole dumb age verification thing needs to die and be replaced by giving parents tools to control devices. Why am I required to plaster my ID all over the internet to prove I'm old enough when parents should be the ones dictating what their kids are doing on their phones. Apple released great set of tools for iPhones coming to iOS 27 that do just that. Why are governments not mandating that kind of control to phone makers to built them into phones. This whole thing is so absolutely idiotic it's wild.

  • Recent Achievements

    • Very Popular
      Captain_Eric earned a badge
      Very Popular
    • One Month Later
      amusc earned a badge
      One Month Later
    • One Month Later
      DJC50PLUS earned a badge
      One Month Later
    • Week One Done
      DJC50PLUS earned a badge
      Week One Done
    • Proficient
      Eric Biran went up a rank
      Proficient

  • Popular Contributors

    1. 1
      +primortal
      511
    2. 2
      PsYcHoKiLLa
      220
    3. 3
      ATLien_0
      92
    4. 4
      +Edouard
      90
    5. 5
      Steven P.
      83
    Show More

  • Tell a friend

    Love Neowin? Tell a friend!