High Sierra. WD external drive won't mount.

[MacUser09]

Updated 2015 MBP to High Sierra.

I have a WD External USB 2 Hard Drive. When I connect to my MBP, it no longer mounts. Nothing on desktop or sidebar.

Can see it under External in Disk Utilities, but it is greyed out. The drive is powered and I can feel it spinning in case.

Shows in bar as USB External Physical Volume ExFAT. Not mounted.

I have a Seagate with my iTunes Library on it, and it connects, no problem.

Any ideas folks?

 

[BrianBaughn]

You'll have to try it on another computer to eliminate possibilities.

It won't mount via Disk Utility (right-click..."Mount")?

 

[MacUser09]

Thanks. That's what I have already done. When I tried it again on my Mac, it worked. Sometimes it does, and sometimes it doesn't. Weird.

 

[blackmatchstick]

I had the same problem took long time figure this out.

Situation:
You can not see your External HDD or Usb Pen Drives appearing on the desktop.

Solution:
(If you can see your drive mounted in the disk utility but its not showing in finder.)
All you need to do is to fix the launch services database on your mac, the easiest way to do is to
download Onyx software (its free) and rebuild the launch services database using the maintenance tab, it will take time
so relax have a cup of coffee. After its done restart your machine.

Thanks

 

[infantrytrophy]

I had the same problem took long time figure this out.

Situation:
You can not see your External HDD or Usb Pen Drives appearing on the desktop.

Solution:
(If you can see your drive mounted in the disk utility but its not showing in finder.)
All you need to do is to fix the launch services database on your mac, the easiest way to do is to
download Onyx software (its free) and rebuild the launch services database using the maintenance tab, it will take time
so relax have a cup of coffee. After its done restart you machine.

Thanks

Do you think that booting into Safe Mode, then re-booting normally, would do the same thing? It has been my experience that a Safe Mode boot-then-reboot sequence frequently solves this type of obscure problem.

 

[blackmatchstick]

Do you think that booting into Safe Mode, then re-booting normally, would do the same thing? It has been my experience that a Safe Mode boot-then-reboot sequence frequently solves this type of obscure problem.

I really can not comment on that part, however, whenever this issues comes up i do what i mentioned and all is sorted.