IMac – I can t find the internal HDD drive (part of fusion drive) on iMac 27 late 2012

To expand your CoreStorage Logical Volume Macintosh HD you have to delete the blocking NO NAME EFI partition (disk1s5). The two unnamed parts (138.62 GB and 99.9 GB) are no partitions but unallocated disk space.

To remove the second EFI partition (and expand Macintosh HD) you have to boot to Internet Recovery Mode or an OS X system on an external device.

Preparation:

• Backup your data.
• Detach any external drive (especially your external Time Machine backup drive).

• Restart to Internet Recovery Mode by pressing alt cmd R at startup.
  The prerequisites are the latest firmware update installed, either ethernet or WLAN (WPA/WPA2) and a router with DHCP activated.
  On a 50 Mbps-line it takes about 4 min (presenting a small animated globe) to boot to a recovery netboot image which usually is loaded from an Apple/Akamai server.

  I recommend ethernet because it's more reliable. If you are restricted to WIFI and the boot process fails, just restart your Mac until you succeed booting.

  Alternatively you may start from a bootable installer thumb drive (Mavericks, Yosemite or El Capitan) or a thumb drive/external disk containing a full system (Mavericks, Yosemite or El Capitan). If you boot from a full system on an external volume and login as a user with admin permissions (which is required) you have to prepend sudo for the gpt command below.

Remove the second EFI partition and modify CoreStorage stack:

• Open in the menubar Utilities/Terminal

First you should get an overview of your disks and the partition layout:

• Enter diskutil list and gpt -r show /dev/disk1 (assuming disk1 is your HDD)

To resize the CoreStorage volume you have to delete any blocking partition first (the Recovery HD doesn't count because it usually will be moved with the resizeStack command).

• First you have to unmount all mounted volumes on disk0 and disk1 (first the CoreStorage volume, which has its own disk identifier (e.g. disk3) but resides on disk0 and disk1) then all other Fusion Drive disks (assuming disk0 = SSD/disk1 = HHD. Please check the diskutil list output for the proper disk identifiers and replace them in the commands below if necessary):

  diskutil umountDisk /dev/disk3
  

  then additional disks. Example:

  diskutil umountDisk /dev/disk0
  diskutil umountDisk /dev/disk1
  

• Remove the second EFI partition (assuming the 103 MB partition has the index number 4 in the gpt listing you got earlier)

  gpt remove -i 4 /dev/disk1
  

• Remount all disks in the reverse order

  diskutil mountDisk /dev/disk0
  diskutil mountDisk /dev/disk1
  diskutil mountDisk /dev/disk3
  

• Since any blocking partition is deleted you may now resize the CoreStorage volume with

  diskutil cs resizeStack LVUUID size 
  

  in your example that's

  diskutil cs resizeStack 5E88EF38-D2A8-4A7D-8508-5C24D948877D 1100g 
  

  to expand it to ~1,1 TB (or 1100 GB) or

  diskutil cs resizeStack 5E88EF38-D2A8-4A7D-8508-5C24D948877D 0g 
  

  to expand it to the full available size (0g is a magic number here).

  The Recovery HD partition (disk1s3) will be moved to the end of disk1 automatically.

• Quit Terminal and reboot to Macintosh HD

Your 3.1 TB Fusion Drive isn't really missing space. Stopping the Windows install and trying to revert to a previous state inflated the size of the Recovery HD at the expense of your main macOS volume "Macintosh HD". The normal size of the Recovery HD partition is 650.0 MB with ~526 MB occupied by a base macOS system and ~124 MB of free space.

Now you can either remove the oversized recovery partition (alluding to this answer: How do I regain unaccessible free space after a failed Boot Camp install on a non-Fusion drive?), expand the Logical Volume disk2 and reinstall macOS to recreate the recovery partition or you can resize your current recovery partition to a smaller but non-standard size and expand the Logical Volume disk2.

The first option takes at least 90 minutes, the second probably less than two minutes.

The second option works like this:

• Boot to your main macOS volume
• Get the partition list with diskutil list and here the device identifier of the recovery partition

• Resize the oversized 1.5 TB recovery partition:

  diskutil resizeVolume diskXs3 1024m #with X either 0 or 1
  

  If you get a "too small" error choose a slightly larger size like 1088m until you are successful.

• Get the UUID of the Logical Volume with diskutil cs list

• Resize the CoreStorage stack with:

  diskutil cs resizeStack lvUUID size
  

  In your case that's:

  diskutil cs resizeStack ED2463F3-F297-4C53-88C7-6701DBF8E63E 3105817m
  

  If you get a "too large" error choose a slightly smaller size like 3105812m until you are successful. The larger your Recovery HD has to be in the first resize step, the smaller the size has to be here.