I was recently handed an old backup hard drive that my co-workers couldn't read because it used one of the EXT file systems. They didn't tell me what they wanted at first, so I assumed I should try to get the data off of it.
I plugged it in, and my a dialog asked me to initialize, eject, or ignore.

I ignored it, because I knew I would need to install osxfuse and ext4fuse, which I did, and I was able to read the disk just fine. Only after that, my coworker told me that he wanted the disk erased and formatted with a filesystem that he could use on his PC. But even though I had the disk mounted and readable, my attempts to format it failed. I tried:
- Disk Utility > Erase > ExFAT, which gave a simple "operation failed" error,
diskutil eraseVolume ExFAT NewName disk2, which gave a "cannot unmount disk" error,umount, which gave a "disk isn't mounted" error, and- all of the above after unplugging the drive various ways.
Finally, I rebooted, and when I plugged in the drive again, I was asked to initialize, eject, or ignore. I choose to initialize this time, and suddenly I could erase to various formats with no issues.
This behavior surprised me because I assumed "initialize*, erase, and format were all synonyms. I guess they're not. So what's the difference? How can one force the initialize dialog to appear?
How is that different from your definition for Initialize? You're not clear whether you actually think these are different operations.
– Merchako Aug 26 '17 at 09:07diskutil eraseDiskhas the ability to both initialize and erase a device and as stated in my answer, initializing will inherently, erase the device – Allan Aug 26 '17 at 13:07