Eject Disk Error Message


Recommended Posts

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

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.

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...

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.

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.

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.

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.

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.

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.

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.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Write to your MP 😄 Like believing in Santa. Total surveillance IS the goal. Wake up.
    • 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.
    • Remeber this decade, when the free internet died... tell your grand kids about this, record there reaction and post it on InstaTwitBook.com
    • UK nudity blockers are a looming privacy disaster, we must be able to see the source code by Paul Hill Image via Pexels The UK government, just like many state governments in the US and national governments around the world, has begun going on a bit of a power trip when it comes to digital safety. The major step taken so far is the introduction of the Online Safety Act, which requires users to prove their age to access adult websites (it includes more than this, too). Now, UK PM Keir Starmer is calling on Apple and Google, and presumably other mobile OS makers, to scan phones for explicit images to protect children. This potentially mandatory on-device scanning by vendor-controlled software will create unacceptable harms to individual freedoms and transparency, and introduce massive surveillance risks. In a statement on June 8, the Prime Minister stated that big tech companies, such as Apple and Google, must add features to their platforms, such as iOS and Android, that will detect and block sexually explicit or nude images involving under-18s on phones or tablets. Adults who want to take or send nudes would be required to hand over some form of identification to stop their phone from blocking these pictures, creating unnecessary privacy risks. According to the government, it wants to see these measures implemented within three months; otherwise, the government will introduce legislation to force them to introduce such technology. The legislation will include fines for companies and maybe even criminal liability for tech bosses who do not comply with the measures. In its announcement, the government said that stopping users from taking, sending, or receiving nudes without verifying their age is technically feasible, and pointed to a British firm called SafeToNet, which has made proprietary, closed-source, uninstallable software called HarmBlock and is actively selling a device with it enabled and is working with other OEMs. The fact that this software is closed source is a huge problem because it’s a black box; you do not know what it is doing on your device. The fact that it is unremovable is also a problem because you lose control of a phone that you own. Laughably, the government, just before highlighting SafeToNet, says that companies must introduce such measures “without threatening privacy or collecting any data.” It then says over-18s will still be able to view adult content by providing proof of age… Which sounds to me like data collection. SafeToNet makes some debatable claims about HarmBlock The government’s example software, HarmBlock, is a hugely alarming choice to espouse the virtues of this type of software. SafeToNet claims that HarmBlock is “ethically developed,” but this is the opposite of the truth. This black box software puts digital handcuffs on you if it’s installed in your device, taking away your freedom to control what software runs on your device, as it cannot be removed. It is not even free software, so we cannot inspect the source code to see what it is doing. For all we know, it could be acting maliciously. While that’s unlikely, we can’t verify that it’s not doing that. When Google and Apple do inevitably integrate these features on devices in the UK, they are very likely to be closed-source binaries, which will also be non-auditable. They will also have identity services built into them, which will require at least temporary collection of sensitive identity documents to verify your age. One saving grace for Android users is that this nudity blocker will very likely be implemented within the Google Play infrastructure that’s deeply tied into commercial Android devices. However, anyone with enough determination to throw out Google apps from their phone by flashing a custom ROM could find they regain control over their phone again without these digital handcuffs. Obviously, this is only how I expect Google to implement the feature; if it bakes it into the open-source Android somehow, that would be bad news for anyone looking to escape it. Outside of stripping mobile phone users of their freedom and sovereignty over their devices, these proprietary on-device machine learning or hash-matching solutions cannot be independently audited. This means that hackers could potentially exploit them because security researchers can’t investigate the code, and they could overstep their intended use case and collect even more user data without anybody knowing. We also wouldn’t know if the code is prone to detecting false positives or biased classification, because we can’t see the code. In the government’s announcement, contributing comments from the Internet Watch Foundation keep talking about “on-device protections” as if to say that users don’t need to worry about server-side processing; however, this is misleading, as data could flow from devices for the purpose of updates, remote model changes, telemetry, or server-side matching. We’ve also seen with the Online Safety Act that the government is never content with the laws it introduces; it always wants to expand the controls. If this scanning functionality arrives on devices, it might only block nudes initially, but later governments could pressure vendors for expanded access or use mandated features for other surveillance aims. The introduction of on-device scanners opens the door to massive risks in the future. Once nude blocking becomes normalized, regulators like Ofcom or politicians themselves could push for more controls over people’s devices. Very possible candidates for blocking include hate speech, misinformation, or undesirable political content. Also, there is a chance that once Apple and Google have developed this software, they might attempt to reuse the infrastructure for commercial or foreign requests, putting customers in greater danger. Just the UK's demand for this sets a precedent. What if a dictatorship decides to spy on activists by demanding that Google or Apple implement similar controls? Another concern with this scanning is that it adds compliance costs for businesses looking to get into the mobile operating system space. While Google and Apple dominate the space right now, there are lots of smaller companies creating mobile operating systems too, including community projects with very shallow pockets. How are these smaller competitors supposed to implement sophisticated nudity detectors? Simply put, they can’t. Then the government goes after them, causes them to shut down, and Google and Apple have less competition. Image via Aurora Store For us users who value sovereignty over our technology, this development will force us to seek freedom-respecting alternatives. The simplest path forward will likely be to install a custom ROM on an Android device; however, kicking Google off the phone with its black box nudity blocker could also make it harder to access apps such as banking apps, which tend to need you to pass Google's integrity checks. Thankfully, Google Play Store apps can still be obtained by storefronts such as the Aurora Store, but it just adds to the friction. To be fair to those pushing this measure to protect children, I think it will be reasonably effective, but people will still try to find ways around it, just as they’ve done with age gates on adult websites introduced under the Online Safety Act. In the effort to find circumvention methods, it could lead users to join riskier platforms that introduce new dangers. This effort also diverts resources from proven interventions such as law enforcement cooperation, targeted investigations, education, and support services to broad technical controls that have uncertain effectiveness (due to their newness). If the government is set on introducing such tools, then there ought to be safeguards in place. Any mandated code should be released as free software so that it can be audited, and the binaries should be reproducible builds so that the public knows nothing has been tampered with in the code used to create the binaries shipped out. Ideally, these tools should also be voluntary, opt-in, and even community-run. This would also allow people to have full control over their hardware while allowing parents to flip a switch to turn on these protections for children, with the knowledge that the code being run is doing exactly what it says on the tin, and nothing nefarious, like a black box solution could be doing. The government should also have a narrow legal scope where this technology stays with blocking nudes and not spreading to blocking political opinions, hate speech, and so on. Ideally, any implementation should avoid identity-linked age verification to keep user data safe, and matching should be done locally with no server telemetry to ensure it is truly on-device. While I do understand that stakeholders such as parents want to keep children safe, the potential for abuse with this type of software is colossal. It would entrench black-box surveillance and take away our freedom to use our devices as we want. There is also the acute risk that the government will demand this surveillance be expanded to block other activities, which could be particularly dangerous. If you are in the UK and don’t wish to see these measures implemented, it is still possible to write to your MP, which could lead to some better safeguards being introduced before it’s too late. Once we get more technical information about how this will be implemented, then we will be able to see if de-Googling Android devices will bypass this measure. For anyone with an iPhone, there is zero chance that you’ll be able to take off these handcuffs because Apple doesn’t let you mess with your software.
  • 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
  • Tell a friend

    Love Neowin? Tell a friend!