Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

High Sierra: Opening DMG displays wrong DMG name

EugW

EugW

macrumors P6
Original poster
Jun 18, 2017
16,411
15,276
Earth (for now)
I’ve noticed this once now, if I’ve opened DMG ABC before, later on if I open DMG XYZ, it will open with ABC’s name but contains all of XYZ’s content. However, the content will be inaccessible.

The only fix is a reboot.

I saw someone else report this too so I’m not alone.
 
I can't seem to recreate the circumstances required to make it happen. But when it did, it just seemed safer to reboot.

Good to see your workaround, but it would make me nervous depending on a workaround for dmg files.
 
Nobody could fix this problem? Tired every time to restart the computer :mad:
 
EugW said:
Both. I use HFS+ on my old unsupported machines (MacBook5,1 & MacBookPro5,5), and APFS on my new machines (MacBook10,1 & iMac18,3).

All of them are running 10.3.3.
Click to expand...
maybe it's only on a hackintosh?
 
AslashA said:
maybe it's only on a hackintosh?
Click to expand...
Dunno, but with Hackintosh, all bets are off.

All four of my machines are real Macs, but two of them aren't officially supported by 10.13. Nonetheless, all of the machines are running fine, and I no longer have the dmg issue on any of the machines. Actually, I also have a 5th machine - an iMac11,3 - that is also running fine in 10.13.3, but since it's only being used as an external monitor, it's hard to say. I don't actually use it as a real Mac, just as a monitor. But the few times I've opened dmg files on it with the last couple of versions of 10.13, they were fine.
 
  • Like
Reactions: AslashA
EugW said:
Dunno, but with Hackintosh, all bets are off.

All four of my machines are real Macs, but two of them aren't officially supported by 10.13. Nonetheless, all of the machines are running fine, and I no longer have the dmg issue on any of the machines. Actually, I also have a 5th machine - an iMac11,3 - that is also running fine in 10.13.3, but since it's only being used as an external monitor, it's hard to say. I don't actually use it as a real Mac, just as a monitor. But the few times I've opened dmg files on it with the last couple of versions of 10.13, they were fine.
Click to expand...
Do you have hdd hfs + on your computer except apfs? At me APFS ssd (OS) and HFS+ hdd (Data). Maybe this is the conflict between apfs and nfs+?
 
I've had this issue with initial version of 10.13 - before supplemental update. I have then reinstalled 10.12 and returned when 10.13.2 was released.

Either they have fixed it in some update between 10.13 and 10.13.2 or reinstall fixed the issue.

I do not have hackintosh.
 
Merode said:
I've had this issue with initial version of 10.13 - before supplemental update. I have then reinstalled 10.12 and returned when 10.13.2 was released.

Either they have fixed it in some update between 10.13 and 10.13.2 or reinstall fixed the issue.

I do not have hackintosh.
Click to expand...
No. They have not fixed this problem so far in 10.13.3((
 
Did you guys check for orphaned or duplicate entries (stuck mountpoints) in the /Volumes/ directory, which may cause the mismatches mentioned?

When macOS/OS X tries to mount a .dmg (or any drive) it does it by default with creating a directory in /Volumes and then mounting it to that point (so a drive gets accessible at /Volumes/NAME_OF_DISK_OR_DMG).

Sometimes it happens that the /Volumes/ directory includes (duplicate) directories or left overs, even if the originating drive or dmg has been successfully unmounted in the meanwhile, leading to situations where (inaccessible) ghost drives or wrongly named drives appear when remounting.

The Volumes directory then may include several orphaned directories (/Volumes/NAME_OF_DMG, /Volumes/NAME_OF_DMG-1, /Volumes/NAME_OF_DMG-2, r other strangely named entries or unknown drive names etc.)

To get rid of these (if existing):
  • Verify all drives and dmg have been unmounted (check with 'diskutil list' or the disk utility to be sure).
  • Check the contents of /Volumes/ e.g. with 'ls -laF /Volumes'. There should only be one here with the name of your startup disk (/Volumes/NAME_OF_STARTUP_DISK )
  • Delete the remaining (orphaned) directories 'sudo rm -rf ORPHANED_DIR'.
    (As always, the necessary disclaimer to use a sudo rm -rf with all your caution!)
 
I've just erased my MBP ssd and reinstalled High Sierra, and I've just run into this issue for the first time.
Clearly it hasn't been fixed in any recent update.
 
  • Like
Reactions: AslashA
FatalFallacy said:
Did you guys check for orphaned or duplicate entries (stuck mountpoints) in the /Volumes/ directory, which may cause the mismatches mentioned?

When macOS/OS X tries to mount a .dmg (or any drive) it does it by default with creating a directory in /Volumes and then mounting it to that point (so a drive gets accessible at /Volumes/NAME_OF_DISK_OR_DMG).

Sometimes it happens that the /Volumes/ directory includes (duplicate) directories or left overs, even if the originating drive or dmg has been successfully unmounted in the meanwhile, leading to situations where (inaccessible) ghost drives or wrongly named drives appear when remounting.

The Volumes directory then may include several orphaned directories (/Volumes/NAME_OF_DMG, /Volumes/NAME_OF_DMG-1, /Volumes/NAME_OF_DMG-2, r other strangely named entries or unknown drive names etc.)

To get rid of these (if existing):
  • Verify all drives and dmg have been unmounted (check with 'diskutil list' or the disk utility to be sure).
  • Check the contents of /Volumes/ e.g. with 'ls -laF /Volumes'. There should only be one here with the name of your startup disk (/Volumes/NAME_OF_STARTUP_DISK )
  • Delete the remaining (orphaned) directories 'sudo rm -rf ORPHANED_DIR'.
    (As always, the necessary disclaimer to use a sudo rm -rf with all your caution!)
Click to expand...
Thanks. Something to keep in mind.

ArcticCascade said:
I've just erased my MBP ssd and reinstalled High Sierra, and I've just run into this issue for the first time.
Clearly it hasn't been fixed in any recent update.
Click to expand...
Arrggh...

I haven't noticed it recently on 10.13.3, but then again I haven't been using very many disk images simultaneously recently either. I was using disk images a lot more early on for software installs, etc.
 
Happened when I first set up a 13” 2017 Pro with Chrome / Brackets / Adobe CC Installer. It was indeed very strange.

This was after updating to 10.3.3
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back